Ashby
Senior Product Engineer, Americas
Base pay range: $153,000.00/yr - $220,000.00/yr
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.
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. We’ll share more details once we meet.
You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3‑4 days (often sooner).
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.
I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand‑ups, no t‑shirt sizing, no planning meetings.
I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation.
Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of “Agile” processes like sprint planning. In those companies, I felt like a JIRA jockey.
About At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. 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.
What We’re Building As engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.
Scheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last‑minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. TA software didn’t help.
As hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s intelligent and powerful. Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are!
Why You Should or Shouldn’t Apply
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. We’ll provide a supportive environment to do it.
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 speed 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
To you, 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
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.
Minimal Process & Lots of Ownership Traditional product‑development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.” At Ashby, we want to build an environment that encourages every engineer to be their best. Engineers take on the rest: research, write specs, build wireframes, and implement solutions end‑to‑end.
Collaboration is Natural & Communication is Deliberate Our engineering team consists of lifelong learners who are talented but also humble and kind. These attributes create an environment where collaboration happens naturally. We combine research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is sacred, and with thoughtful communication, engineers are in
Increase Leverage, not Team Size
Great developer tooling. Our CI/CD takes ~10 min, deploy at least 15× a day. A debugger that works out of the box.
Building blocks to create powerful and customizable products fast.
Put Effort into Diversity Diverse teams drive innovation and better outcomes. Having seen my mother and partner build careers as minority women, we 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.
Interview Process At Ashby, our interview process is designed 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. No leetcode or whiteboard exercises.
Our Interview Process Is Three Rounds
Introduction call with Hiring Manager (15–30 min, live)
A technical screen where we pair in our actual codebase (1 h, live)
Three non‑coding interviews focusing on product thinking, technical design, and infrastructure (3 h 15 min, live; can be split across multiple days)
Your First Three Months at Ashby We want an exceptional onboarding experience for every new hire. On day one, your dev environment is set up with a single script, you push your first product change, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The scope increases from simple copy changes to delivering impactful features. Your manager will conduct 30‑, 60‑, and 90‑day reviews.
Technology Stack TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis.
Benefits
Competitive salary and equity.
10‑year exercise window for stock options.
Unlimited PTO.
Minimum of 12‑week fully paid parental leave.
Generous equipment, software, and office furniture budget.
$100/month education budget.
Top‑tier health insurance for US employees; supplemental insurance worldwide.
Job Details
Seniority level: Mid‑Senior level
Employment type: Full‑time
Job function: Engineering and Information Technology
Industries: Software Development
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.
#J-18808-Ljbffr
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.
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. We’ll share more details once we meet.
You’ve probably seen this role posted before, and it’s because we’re always expanding the team (we’re on track to double this year). We’re bubbling with ideas on how to support Talent Acquisition through software, and we’ve started the journey of building products beyond Talent Acquisition. We read every application and aim to respond to yours within 3‑4 days (often sooner).
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.
I started my career building software for artists in the Visual Effects industry. It was a formative experience for me as a software engineer because success relied on my ability to be a product manager and designer. I talked to artists to understand their needs. I came up with ideas. I did industry research, designed interfaces, and prototyped ideas. I watched artists use what I built and decided what to tackle in the next iteration. No daily stand‑ups, no t‑shirt sizing, no planning meetings.
I studied computer science to solve problems, not tickets, and this felt exactly like that. I not only felt creative and fulfilled but the agency and ownership we were given as engineers powered an incredible amount of innovation.
Innovation came differently (or not at all) at technology startups beyond the seed stage, often through an engineer’s force of will and ability to push back against culture (rather than any encouragement from it). Engineering was narrowed to implementation and delivery, partly due to the influence of other departments and partly due to the influx of “Agile” processes like sprint planning. In those companies, I felt like a JIRA jockey.
About At Ashby, we’re building an environment that is optimistic about what engineers can own and achieve. An environment that embraces innovative engineers, and, frankly, often stays out of their way. 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.
What We’re Building As engineers, we are used to tooling that makes us better at what we do. When we started Ashby, we saw the opposite with Talent Acquisition software. Recruiting teams were leveling up how they did their work, but instead of software meeting this new standard, it held them back.
Scheduling a final round is an excellent example. Recruiting teams wanted to schedule candidates faster, track interviewer preparation and quality, and do it with half the headcount. A recruiter needed to manually collect availability from the candidate, identify qualified interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and make any last‑minute adjustments as availability changed. They must do this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. TA software didn’t help.
As hiring managers, we know TA is a critical function, and as engineers, we know software can do better. So, we built and continue to build Ashby to give TA teams the highest standard of tooling. Software that’s intelligent and powerful. Software that provides insights into where they’re failing and automates or simplifies many of the tasks they’re underwater with. We want other functions and departments to be jealous of what TA teams can do with Ashby, and today they often are!
Why You Should or Shouldn’t Apply
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. We’ll provide a supportive environment to do it.
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 speed 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
To you, 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
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.
Minimal Process & Lots of Ownership Traditional product‑development processes aren’t meant for the best engineers. Their purpose is to create consistent outcomes regardless of the engineer’s skill. But consistency comes at the expense of an engineer’s time and freedom—both ingredients necessary to generate those magical outcomes. As a result, process stifles the best engineers and doesn’t give others the opportunity to practice the behaviors that made the best engineers the “best.” At Ashby, we want to build an environment that encourages every engineer to be their best. Engineers take on the rest: research, write specs, build wireframes, and implement solutions end‑to‑end.
Collaboration is Natural & Communication is Deliberate Our engineering team consists of lifelong learners who are talented but also humble and kind. These attributes create an environment where collaboration happens naturally. We combine research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is sacred, and with thoughtful communication, engineers are in
Increase Leverage, not Team Size
Great developer tooling. Our CI/CD takes ~10 min, deploy at least 15× a day. A debugger that works out of the box.
Building blocks to create powerful and customizable products fast.
Put Effort into Diversity Diverse teams drive innovation and better outcomes. Having seen my mother and partner build careers as minority women, we 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.
Interview Process At Ashby, our interview process is designed 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. No leetcode or whiteboard exercises.
Our Interview Process Is Three Rounds
Introduction call with Hiring Manager (15–30 min, live)
A technical screen where we pair in our actual codebase (1 h, live)
Three non‑coding interviews focusing on product thinking, technical design, and infrastructure (3 h 15 min, live; can be split across multiple days)
Your First Three Months at Ashby We want an exceptional onboarding experience for every new hire. On day one, your dev environment is set up with a single script, you push your first product change, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The scope increases from simple copy changes to delivering impactful features. Your manager will conduct 30‑, 60‑, and 90‑day reviews.
Technology Stack TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis.
Benefits
Competitive salary and equity.
10‑year exercise window for stock options.
Unlimited PTO.
Minimum of 12‑week fully paid parental leave.
Generous equipment, software, and office furniture budget.
$100/month education budget.
Top‑tier health insurance for US employees; supplemental insurance worldwide.
Job Details
Seniority level: Mid‑Senior level
Employment type: Full‑time
Job function: Engineering and Information Technology
Industries: Software Development
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.
#J-18808-Ljbffr