Senior Software Engineer - Product Engineering (Basé à London)

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.

If you’ve seen this role posted before, it’s because we’re always looking for incredible engineering talent to help build the future of Ashby, as we more than double our business year over year. But we’re not just collecting resumes: So far we’ve hired 10 Product Engineers in 2025 (that’s a 20% increase in our total engineering headcount from this one role in the first 4 months!)

We aim to respond to applicants within 3-4 days (often quicker). 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: thousands of daily users who depend on your software and eagerly await your next feature. 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.

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.

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.

What We’re Building

Talent teams aspire to build a hiring process that identifies great candidates, moves them quickly through the interview process, and provides an excellent experience for the candidate. To accomplish this, recruiters perform thousands of daily tasks to coordinate and relay information between candidates, interviewers, and hiring managers. Teams struggle to keep up!

Scheduling a final round is an excellent example of our customers' challenges. A recruiter needs to collect availability from the candidate, identify potential interviewers, perform “Calendar Tetris” to find who is available to interview the candidate, schedule on the earliest date possible, and perform any last-minute adjustments as availability changes. They must perform this while considering the interview load on each individual and whether interviewers need to be trained and shadowing others. Ashby provides talent teams with 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 put a lot of effort into designing products that are approachable to beginners but mastered and extended by power users.

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

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

Collaboration is Natural & Communication is Deliberate

Our engineering team (and the team at large) consists of lifelong learners who are humble and kind. These attributes create an environment where collaboration happens naturally. We combine this with research, prototyping, and written proposals to see around corners and get feedback from the team across time zones. Focus time is something that we hold sacred, and, with thoughtful and deliberate communication, engineers are in here.

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.

Give Engineers Ownership & Agency

We, as engineers, find clever ways to solve problems, which amplifies when we deeply understand the problem. Our engineering culture reflects this experience: engineers own projects end-to-end, from speaking with users to writing product specs to UX design.

Put Effort into Diversity

Diverse teams drive innovation and better outcomes. Today, 26% of engineers at Ashby are from underrepresented groups. It’s not great, and we are taking conscious steps to improve.

Interview Process

At Ashby, our team and interview process want to help you show your best self. Our interview process is three rounds:

• 15 to 30-minute introduction call
• A technical screen (60-minute in-person)
• A remote final round of 3 hours and 15 minutes (can be split across multiple days)

Your hiring manager will be your main point of contact and prep you for interviews. If we don’t give an offer, we’ll provide feedback!

Your First Two Months at Ashby

We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment sets up with a single script, you push your first change on day one, and we spend the rest of the time building your confidence in our codebase and practices.

Technology Stack

TypeScript (frontend & backend), Node.js, React, Apollo GraphQL, Postgres, Redis.

Benefits

• Competitive salary and equity.
• 10-year exercise window for stock options.
• Unlimited PTO with four weeks recommended per year.
• Twelve weeks of fully paid family leave in the US.
• Generous equipment, software, and office furniture budget.
• $100/month education budget.
• Top-notch health insurance for you and your dependents.

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.