Requirements
- Comfort using AI tools (e.g. Claude Code) as a core part of how you build, with judgment on when output is wrong
- Experience with high-volume or real-time data: streaming, ingestion, time-series, or similar
- Strong opinions on API design
- BS/MS/PhD in Computer Science, Statistics, Applied Mathematics, Operations Research, Aerospace Engineering, or related quantitative field
- Can make architecture calls with incomplete information and explain them to non-engineers
- Cloud infrastructure (AWS, GCP, or similar), infrastructure as code, and monitoring you actually rely on
Skills
Nice to have
Full job description
- As a Lead Backend Engineer here, you’d own the backend behind a mature consumer product, one that’s been featured in the app stores multiple times and has a large, loyal user base on iOS and Android. The backend handles high-volume, real-time data and serves both the apps and a commercial API with paying customers. It works. It has also been around a while, and it’s moving to new infrastructure and you’d lead that migration
- Own the backend end to end: architecture, reliability, cost, on-call, and its roadmap
- Migrate the existing production stack to new infrastructure without users or API customers noticing. Plan it, sequence it, and know when to roll back
- Learn the current system well before replacing any of it. Some of it is worth keeping
- Design and build what comes next: new data pipelines, new APIs, and the backend for features that don’t exist yet
- Keep the commercial API fast, stable, and documented. Real customers depend on it
- Work closely with the iOS and Android engineers on API contracts and what the apps actually need
- Help hire and set the engineering bar as the team grows
- Work the way this team works: AI-assisted development is the default here, not a novelty. We use Claude Code daily and expect you to be fluent with agentic coding tools, or to get fluent fast. We’ll be able to tell which
- Comfort using AI tools as a core part of how you build, with the judgment to know when the output is wrong
- Experience with high-volume or real-time data: streaming, ingestion, time-series, or similar
- Strong opinions on API design
- BS/MS/PhD degree in Computer Science, Statistics, Applied Mathematics, Operations Research, Aerospace Engineering, or a related quantitative field
- You can make architecture calls with incomplete information and explain them to people who aren’t engineers
- Cloud infrastructure (AWS, GCP, or similar), infrastructure as code, and monitoring you actually rely on
- 10+ years of software engineering experience, mostly backend
- At least one major migration you led on a live system with real users. Tell us how it went, including the parts that didn’t
- You’ve owned a production backend, not just contributed to one. We’ll ask what you ran, what broke at 2am, and what you changed afterward
- Geospatial data experience
- You’ve run a public or commercial API, including the billing and rate-limiting side of it
- Audio or media streaming experience
- Aviation knowledge, or a real interest in it. Pilots and aviation nerds, this is your moment
- You’ve shipped in a regulated or safety-adjacent industry and know how that changes engineering culture
Opens Archer’s own application page in a new tab.