Platform Engineer, Americas

Join to apply for the Staff Platform Engineer, Americas role at Ashby

This range is provided by Ashby. Your actual pay will be based on your skills and experience — talk with your recruiter to learn more.

$/yr - $/yr

We’re looking for a curious, rigorous, problem-hungry platform engineer (who codes!) to carry the ball as we bring Ashby to the big leagues. Ashby builds software that lets talent teams build an efficient, delightful, respectful hiring process. Similarly, you’re an engineer who wants to build a “paved road” that excellent engineering teams can safely take to the moon and back. 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, over 2,500 customers, very low churn, and many years of runway. We’ll share more details once we meet, but you now probably have a good idea as to why we’re hiring for this role.

Hi 👋 I’m Colin, Head of EMEA Engineering. I’ve spent a number of years leading engineering teams in startups, and that has always included being close to infrastructure teams – no matter what name they’ve worn (SRE, infrastructure, platform, etc). I’ve got my hands dirty building the initial infrastructure for startups and know the value a talented infrastructure engineer brings. The rigour, the discipline, the peace and quiet when everything just hums along.

Our infrastructure is in a good place for now. Nothing is static. Ashby continues to grow rapidly, putting strain on our existing infrastructure. We’re always looking to give our customers more powerful hiring software, and building new product features often requires new pieces of infrastructure. Having herded plenty of snowflake servers in the past, I’ve learned there’s a better way. I (and Ashby) place a lot of value on code-as-infrastructure.

As a Platform Engineer at Ashby, you’ll dive into scaling problems, add new capabilities to our platform, and think about how our entire team interacts with infrastructure. All our own engineers own their projects end‑to‑end and ship with minimal oversight. You’ll be responsible for ensuring our systems are secure, reliable, and can grow to meet the demands of a massive customer base.

Your decisions will impact how we operate internally and how we serve customers.

• Optimize our homegrown ultra‑dynamic recruiting DSL‑to‑SQL compiler, and create tools to help developers do so.
• Create automated guardrails for the security and privacy of our customer data.
• Help our developers ship features fast through canary deploys, gradual rollouts and feature flags, while keeping complexity manageable and reducing downtime.
• Work with the business and the engineering team to define SLOs and implement the corresponding SLIs.
• Ensure all communication with external services supports retries and circuit‑breakers.
• Implement the infrastructure to support an event‑driven architecture and data warehouse.

• You never stop. You get weirdly obsessed about a problem that doesn’t yet make sense, turn it every which way in your head until the explanation dawns.
• You don’t take shortcuts. You speak up for the future user, the edge case, the doomsday design.
• You’re someone who cares about what you do and the team you do it with, and want to work with others who do as well.
• You’ve built infrastructure at a slightly later stage than Ashby is at - you know how to deal with millions of data points, have seen great (or not great) infrastructure make or break customer experience, and have automated everything from provisioning to monitoring and release process.
• You’re a Swiss army knife. You’ll get every hard problem the company faces: infrastructure updates, security enforcements, database optimization, Kubernetes debugging, and digging through Type Script traces figuring out what doesn’t work.

• You don’t want to make your own decisions on what is the best paved road to build for Ashby, and expect a lead or manager to make the final call on what that is.
• You hate SQL. We have a lot…