Principal Software Engineer, Product Engineering, EU, UK in England

Hi, I’m Abhik, Ashby’s Co-Founder and VP of Engineering. We’re looking for an ambitious full‑stack engineer who is laser‑focused on solving customer problems and making the right long‑term investments to solve them not only today but in our future features and products.

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.

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.

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.
• 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.
• Specced, designed, and implemented a feature that allows users to complete signing offers entirely within Ashby.

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.

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.

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’ve tackled projects with a lot of product and technical ambiguity.
• 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:

• 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.