Senior Software Engineer - Product Engineering, Berlin (m/f/d)

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.

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

This is a fully remote role, with Berlin as the official location. We welcome applicants based in Germany or nearby time zones.

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. 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 I talk about in "What We\'re Building."
• 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

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 is necessary to successfully deliver a feature, whether writing frontend or choosing new infrastructure. We’ll provide a supportive environment to do it successfully (e.g., design system, SRE team).
• You’ve tackled projects with a lot of product and technical ambiguity, and you thrive at the intersection of the two. We’re not building a simple CRUD app, and many of the challenges we tackle require you to use your knowledge of our customers to build powerful abstractions and flexibility in the system to solve a class of problems.
• You know how to strike the right balance between speed and quality. Ashby wasn’t built quickly. We took four years to launch publicly because convincing customers to switch required a high-quality product. However, time isn’t infinite, especially for a startup, so we still move with urgency—we’ve built the equivalent of three or more VC-backed startups with a very small team.
• You are ambitious and always looking to improve your skills. For most engineers, this role will give you more freedom and responsibilities than you’ve experienced in the past. To thrive (and level up), you’ll need to be open to feedback (and we give lots of it).
• You’re an excellent collaborator and communicator. Ownership and freedom don’t mean you work in a vacuum. You’ll need to vet your decisions with the appropriate stakeholders, keep them up to date when necessary, and work with other engineers to get your projects across the finish line. Clear and concise communication helps a lot here!
• You seek to create leverage in your work. The nature of software is that you can often automate or abstract what would be tedious, time-consuming work. Your impatience usually leads to new abstractions, tools to allow Support to debug before Engineering, new lint rules to prevent common bugs, etc.

Put another way, you shouldn’t apply if:

• You need company-driven process and structure to get your projects across the finish line. Sprints and well-defined project management processes are things you need or look to others to lead. You’d rather focus on the technical details and challenges.
• You only want to do exciting work. We’re building a team of kind, collaborative folks. Customer issues and investigations are distributed across the team, including our high-level ICs.
• You can get lost in the details. Once you start implementation, it can be hard to take a step back and think about the project as a whole. You like everything to be planned upfront.
• You haven’t led or taken ownership of projects before. You’re used to working with tech leads and taking on tasks distributed by them.
• You want to mentor earlier-career engineers. We rely on engineers owning their projects, so we need engineers with that experience. This requires the team to be reasonably tenured. More than 90% of the team would be considered Senior or above in the industry today, so mentorship opportunities are very limited.
• You want a tech lead, staff, or principal engineer who spends most of their time project managing or doing architecture reviews. Our most tenured engineers spend most of their time building, and we often trust them with our most challenging problems. While they lead product and technical areas and help other engineers plan their most challenging work, it’s not a requirement, nor do engineers need their sign-off.

Engineering Culture

Our engineering culture is motivated by Benji’s 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

Minimal Process & Lots of Ownership

The best engineers deliver magical outcomes by solving customer problems with minimal oversight while keeping stakeholders informed. We favor ownership over process, and encourage engineers to push information outward and pull in designers and infra as needed.

Collaboration is Natural & Communication is Deliberate

Our team consists of lifelong learners who are talented, humble, and kind. We emphasize collaboration, prototyping, and written proposals to see around corners. Focus time is sacred, and we communicate deliberately to keep meetings under two hours per week.

We meet in person at least twice a year and provide a budget to meet with folks in your city or region.

Increase Leverage, not Team Size

We invest in great developer tooling and building blocks to create powerful, customizable products fast. Our core components (analytics modeling and query language, policy engine, workflow engine, design system) are continually improved and scale across the app.

Here’s a quote from a teammate about building features at Ashby and a demo of our building blocks.

Put Effort into Diversity

Diverse teams drive innovation. Today 21% of engineers at Ashby are from underrepresented groups. We are taking steps to improve, including sourcing diverse candidates, generous paid family leave, no leetcode interviews, and more.

Interview Process

Our interview process helps you show your best self. We simulate working together via pair programming, writing product and tech specs collaboratively, and discussing decisions. There are no leetcode or whiteboard exercises.

Process is three rounds:

1. Introduction call with Hiring Manager (15–30 minutes, live)
2. A technical screen pairing in our codebase (1 hour, live)
3. Three non-coding interviews focusing on product thinking, technical design, and infrastructure (3 hours 15 minutes, live; can span multiple days)

Hiring manager is your main contact and will prep you for interviews. Each round includes written guidance. You’ll meet 4–6 people in engineering. If we don’t extend an offer, we’ll provide feedback.

Your First Three Months at Ashby

We aim for exceptional onboarding. Your dev environment is set up with a single script, you push your first product change on day one, and you ship features to learn the codebase and practices. The manager will do 30-, 60-, and 90-day reviews to calibrate how we work together.

You’ll have a peer to pair with, and the team will run training sessions on culture, product, engineering process, and technical architecture.

Technology Stack

TypeScript (frontend & backend), React, GraphQL API, Node.js, Postgres, Redis. We don’t require prior experience in it, but a love of typed languages helps. Engineers who joined from other languages have found the transition smooth and valuable.

Benefits

• Competitive salary and equity.
• 10-year exercise window for stock options.
• Unlimited PTO and encouragement to take it.
• Minimum 12 weeks fully paid parental leave, with regional variations as needed.
• Generous equipment, software, and office furniture budget.
• $100/month education budget.
• In the US, top-tier health insurance for you and dependents; elsewhere, high-quality supplemental insurance, fully covered.

Ashby’s success hinges on hiring great people and creating an environment where we can be happy, feel challenged, and do our best work. We’re building that environment from the ground up.

We are an equal employment opportunity employer and welcome applicants from all backgrounds, experiences, perspectives, and abilities.