Staff Software Engineer, Product Engineering, UK in Cambridge

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.

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

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

Why You Should or Shouldn’t Apply:

• 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’d rather focus on the technical details and challenges.
• You like everything to be planned upfront.
• You want to mentor earlier‑career engineers.

Our Engineering Culture Is Motivated By Our Belief That a Small, Talented Team, Given The Right Environment, Can Build High‑quality Software Fast. We Do It Through Minimal process with ownership over decisions normally made by product and design, natural collaboration and deliberate communication, and investing in tools and abstractions that give us leverage.