Principal Product Engineer, Americas

Principal Product Engineer, Americas Hi I’m Abhik, Ashby's Co-Founder and VP of Engineering. We’re looking for a versatile, persistent product engineer who’s not afraid to set up reusable building blocks across the stack and advocate for the time and space to do so. At Ashby, all our engineers ship features end-to-end at a high pace. Example is the best leadership. We’ll give you the room to do your best work, and you’ll be our guide If that speaks to you, read on. Base pay range $202,000.00/yr - $330,000.00/yr What Ashby gives you in return is the best of both early and growth-stage environments. The agency and no-nonsense of a seed startup: you write product specs, make product and design decisions, and build in an almost-no-meeting culture. While also the product‑market fit and scale of a growth‑stage startup: tens of thousands of daily users who depend on your software and eagerly await your next feature. We have notable customers like Notion, Linear, Shopify, and Snowflake. Our growth and retention metrics are best‑in‑class among our peers: we have tens of millions in ARR, growing >100% year over year, very low churn, and many years of runway. About the Role and How We Work Our engineering culture strives to recreate the environments where we did our best work as ICs – where we had the ownership and agency to impact our users with creative and innovative software. As a Product Engineer, you’ll take ownership over a large portion of one of our products and own projects end‑to‑end (wearing hats traditionally worn by product and design). You’ll research competitors, write product specs, make wireframes, and more. To ground it with examples, product engineers at Ashby have: Designed and built automated interview scheduling. This feature automates scheduling by calculating possible times from a pool of interviewers and other constraints, and then presenting these times to the candidate for selection via our responsive web app. This solves the “Calendar Tetris” problem. Built a generalized declarative filter architecture that allows users to create complex filters for any record with a consistent UI and compile it to SQL in our backend. Many user‑facing features use it. Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby. This project involved talking to customers to understand their requirements, deciding what technologies to use, building a prototype, and working with other team members to integrate the final implementation into additional features. Why You Should or Shouldn’t Apply Software Engineers Come In Many Flavors, Not All Of Which Fit Our Model. Here Are Some Things To Help You Decide If This Fits You And What You’re Looking For: You’re not afraid to tackle any part of a technology stack. You do what’s necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. You know how to strike the right balance between and quality. You are ambitious and always looking to improve your skills. You’re an excellent collaborator and communicator. You seek to create leverage in your work. Put Another Way, You Shouldn’t Apply If: A tech lead, staff, or principal engineer is someone who spends most of their time project managing or doing architecture reviews. You need company‑driven process and structure to get your projects across the finish line. You only want to do exciting work. You can get lost in the details. You haven’t led or taken ownership of projects before. You want to mentor earlier‑career engineers. Engineering Culture Our Engineering Culture Is Motivated By Benji’s (my Co‑founder And CEO) And My Belief That a Small, Talented Team, Given The Right Environment, Can Build High‑quality Software Fast (and Work Regular Hours). We Do It Through: Minimal process with ownership over decisions normally made by product and design. Natural collaboration and deliberate communication. Investing in tools and abstractions that give us leverage. Putting effort into building a diverse team. Increase Leverage, not Team Size We Built Ashby With The Quality, Breadth, And Depth That Many Customers Would Expect From Much Larger Teams Over Larger Time Scales. We’ve Done This Through Investment In: Great developer tooling. Our CI/CD takes ~10m, and we deploy at least 15x a day. A debugger that works out of the box. Everyone on the team has contributed to our developer experience. Building blocks to create powerful and customizable products fast. At the core of Ashby is a set of common components (analytics modeling and query language, policy engine, workflow engine, design system) that we constantly improve. Each improvement to a common component cascades throughout our app. Put Effort into Diversity Diverse teams drive innovation and better outcomes. Having seen my mother and partner build their careers as minority women in non‑diverse fields, I want to make sure Ashby creates opportunities for the next generation of engineers from underrepresented groups. Today, 21% of engineers at Ashby are from underrepresented groups. It’s not great, and we are taking conscious steps to improve, like sourcing diverse candidates, providing generous paid family leave, no leetcode interviews, and more. Interview Process Our interview process wants to help you show your best self. We’ll dive into past projects and simulate working together via pair programming, writing product and tech specs collaboratively, and talking through decisions. There are no leetcode or whiteboard exercises. Introduction call with Hiring Manager (15 to 30m, live) A technical screen where we pair in our actual codebase (1h, live) Three non‑coding interviews that focus on product thinking, technical design, and infrastructure (3h 15m, live can be split across multiple days) Depending on our leadership team’s bandwidth, we may start with an additional 30m screen with a recruiter. Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect. You’ll meet 4 to 6 people in engineering (with 5‑15 minutes in each interview to ask them questions). If we don’t give an offer, we’ll provide feedback Your First Three Months at Ashby We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. You will pair with a peer, attend training sessions on our culture, product, engineering process, and technical architecture. Technology Stack TypeScript (frontend & backend), React, GraphQL API, Node.js, PostgreSQL, Redis. We don’t require previous experience in these specific languages; a love of typed languages is helpful. Benefits Competitive salary and equity. 10‑year exercise window for stock options. Unlimited PTO. A minimum of 12 weeks fully paid parental leave. Generous equipment, software, and office furniture budget. $100/month education budget. Top‑tier health insurance for you and your dependents, 100% of premiums covered in the US. Ashby provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities. Seniority level Mid‑Senior level Employment type Full‑time Job function Engineering and Information Technology Industries Software Development #J-18808-Ljbffr