> Markdown version of [/jobs/ext/2720761-technology-stack](https://www.wearedevelopers.com/jobs/ext/2720761-technology-stack). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Technology Stack

- **Company:** Ashby's Brake And Truck Repair, Inc.
- **Location:** Ashby, MN, United States (Remote available)
- **Contract:** Permanent contract
- **Skills:** Amazon Web Services, Cloud Computing, Customer Data Management, Data Warehousing, Software Debugging, Programming Tools, PostgreSQL, Node.Js, Redis, Reliability Engineering, Shopify, SQL Databases, TypeScript, Datadog, ReactJS, Snowflake, Database Optimization, Backend, Event Driven Architecture, Kubernetes, Sentry, Build Tools, Build Process, Graphql, Front End Software Development, Service Stack
- **Published:** September 4, 2026
- **Apply:** https://startup.jobs/staff-platform-engineer-americas-ashby-7463860

## About the Role

I'm sharing our tech stack with the caveat that we don't require previous experience in it: TypeScript (frontend & backend), Node.js, React, Apollo GraphQL, Postgres, Redis.

## Description

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

We've listed this role twice: as a Platform Engineer and Site Reliability Engineer - our team does both, and we are open to candidates who lean towards one or the other., 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 snowflakeservers 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 get to 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. We don't put roadblocks to ensure security when common sense will do and we don't build processes like change management boards around the lowest common denominator. But with great power comes great responsibility: we handle personal and confidential data about some of the biggest decisions we ever make at work. As we grow, more and bigger customers rely on us to be reliable and secure and how we operate internally will need to evolve.

We're at an inflection point where our ability to scale and deliver a seamless experience has a make-or-break impact - we have some of the fastest growing companies using our platform every day to hire hundreds of people per month. We need someone like you to make good decisions, debug thorny issues, and build us a future-proof platform that can withstand this scale. Our small but mighty infrastructure team has set up a secure and simple environment (we don't believe in spinning up a new service unless necessary!) for our growing product team to build in. That's where you come in: you, too, will own projects end-to-end and have an impact on core parts of the Ashby developer and user experience. For instance, you could work on:

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

We're looking for someone who can build systems that an engineer would like to work with: mature and boring but open-minded and approachable. We have to balance reliability with flexibility. Software and its availability are now mission critical to almost every working professional. To be in an SRE in today's world, you have to be extremely comfortable evaluating risk, those you take and those others take., * 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'll search every rock, inventory every clue, hunt every mismatch. We do that, too - together we'll be armed with state-of-the-art monitoring tools and an impressive amount of data, and join you in the adventure.

 * You don't take shortcuts. You're speaking up for the future user, the edge case, the doomsday design. You know product engineers want to build it with you, and see them as allies, where you give them the power and knowledge to access greater things.
 * 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'll be on interview panels choosing your next colleagues, and you'll take that seriously. You only want to work with people who make you better, and want to make you better.
 * 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 (all nationalities welcome ;) ). You'll get every hard problem the company faces. You'll get to do infrastructure updates, security enforcements, database optimization, Kubernetes debugging, and digging through Typescript traces figuring out what doesn't work. You probably don't feel like an expert at at least some of that... and that appeals to you.

All that makes for a pretty specific kind of role, and the job isn't to everyone's tastes! You should not apply if:

 * 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. Our leads (and managers) give ample commentary and feedback on technical decisions and how they're made, but you ship what you want to build and are accountable for it.
 * You hate SQL. We have a lot of features built around making the best out of data, and our platform engineers also sometimes dive into a gnarly report or advise engineers on a more performant data model to use.
 * You don't want to code. Our SREs are some of our best software engineers and they are just as responsible for the application as the other engineering teams - albeit at a platform level. Reviewing code and submitting code changes will be part of your day to day.
 * Your primary mode of communicating best practices to engineers is live meetings. We're a very async culture and written communication (and code) is how changes get made. As an Ashby SRE, you will need to share new tooling and best practices with engineers faster than your next meeting opportunity will take you.
 * You've never delivered a project, on your own, without someone prodding you for updates. We have no project or delivery managers to fill your calendar with busy work, but the flip side is you have to do your project management, seek the help you need to get unstuck and cut scope when it's worthwhile., We use Datadog and Sentry on 100% cloud-based (AWS) infra. We take developer experience and reliability seriously: all engineers are on call in a follow-the-sun model, and everyone contributes to developer tooling., Your hiring manager will be your main point of contact and prep you for interviews. Each round will have written guidance so you know what to expect (you'll need minimal preparation). You'll meet 4 to 6 people in engineering (with 5-15 minutes in each interview to ask them questions). If we don't give an offer, we'll provide feedback!, We want an exceptional onboarding experience for every new hire. At Ashby, your dev environment is set up with a single script, you push your first product change on day one, and you spend the rest of your time shipping product changes that give you a tour of our codebase and best practices. The product changes increase in scope and ambiguity from simple copy changes to the delivery of a prominent, impactful feature. Your manager will do a 30, 60, and 90-day review to give feedback and calibrate on how we work together.

It's a team effort to get you successfully onboarded; you'll have a peer paired with you to answer questions, pair program, and check in often to see if you need help. The rest of the team will run training sessions on our culture, product, engineering process, and technical architecture.


## Related Videos

- [Putting the Graph In GraphQL With The Neo4j GraphQL Library](https://www.wearedevelopers.com/videos/257-putting-the-graph-in-graphql-with-the-neo4j-graphql-library)
- [From Doubt to Confidence: How Sentry Uses Verdaccio to Bulletproof SDK Releases](https://www.wearedevelopers.com/videos/739-from-doubt-to-confidence-how-sentry-uses-verdaccio-to-bulletproof-sdk-releases)
- [Reducing LLM Calls with Vector Search Patterns - Raphael De Lio (Redis)](https://www.wearedevelopers.com/videos/1714-reducing-llm-calls-with-vector-search-patterns-raphael-de-lio-redis)
- [Tracking vehicles at scale](https://www.wearedevelopers.com/videos/1999-tracking-vehicles-at-scale)
- [Event based cache invalidation in GraphQL](https://www.wearedevelopers.com/videos/433-event-based-cache-invalidation-in-graphql)
- [GraphQL + Apollo + Next.js: A Lovely Trio](https://www.wearedevelopers.com/videos/311-graphql-apollo-next-js-a-lovely-trio)

## Related Articles

- [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers)
- [20 Essential Tools For Backend Development](https://www.wearedevelopers.com/magazine/218-20-essential-tools-for-backend-development)
- [Dev Digest 139 - Soft and hard queries](https://www.wearedevelopers.com/magazine/487-dev-digest-139-soft-and-hard-queries)
- [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers)
- [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss)
- [Dev Digest 113 - Debugging above the cloud](https://www.wearedevelopers.com/magazine/422-dev-digest-113-debugging-above-the-cloud)