The ad says“Familiarity with Apache Airflow or workflow orchestration systems”
The ad says“Multi-cloud experience, not just multi-cloud exposure. You’ve made considered architectural decisions across AWS, GCP, and/or Azure — not just consumed managed services, but evaluated tradeoffs between them and lived with those decisions in production”
The ad says“Multi-cloud experience, not just multi-cloud exposure. You’ve made considered architectural decisions across AWS, GCP, and/or Azure — not just consumed managed services, but evaluated tradeoffs between them and lived with those decisions in production”
The ad says“Distributed systems depth, grounded in practice. You have a solid working model of how production systems fail — consistency and availability tradeoffs, failure cascades, backpressure, graceful degradation”
The ad says“Multi-cloud experience, not just multi-cloud exposure. You’ve made considered architectural decisions across AWS, GCP, and/or Azure — not just consumed managed services, but evaluated tradeoffs between them and lived with those decisions in production”
The ad says“Strong Go proficiency. The platform team writes production Go. You should be fluent: you’ve built and shipped systems in it, and you have opinions about what good Go looks like”
The ad says“Kubernetes at operator depth. You know what happens inside the scheduler and the control loop when things go wrong, because you’ve been there. You’ve operated clusters under real load, not just deployed workloads onto them”
The ad says“Experience working on a SaaS/PaaS product across multiple cloud providers”
The ad says“Experience with storage primitives at the system level — you’ve reasoned about when to reach for a relational store vs. an object store vs. something else, and you have real opinions informed by real failures”
The ad says“Familiarity with Apache Airflow or workflow orchestration systems”
Astronomer’s products run on a complex, multi-cloud platform — and the scalability, and operational maturity of that platform is what we’re actively investing in
The work ahead on our Platform team isn’t about managing data or curating pipelines; it’s about building the foundational systems that everything else runs on — the kind of systems where the failure modes matter, the latency budgets are real, and getting it wrong has visible consequences for hundreds of enterprise customers
This is a foundational role at a consequential moment: your work will directly shape what Astronomer’s products — Astro, Observe, and our IDE — are capable of over the next several years
Stronomer has a healthy and complex infrastructure estate spanning multiple cloud providers, a mix of managed and self-hosted systems, and an increasingly ambitious set of requirements as our products evolve
We have a clear sense of where we need to go; we need the right person to figure out how to get there and then go build it
This is very much a technical role — you’ll be just as involved in building these systems as in specifying and designing them
Blaze a Trail: Own and develop our platform infrastructure strategy, with the sponsorship and responsibility to match. Map out what we need, make the calls, and own the outcomes
Be an Owner: Be directly involved in deciding what we work on and how we work on it. Make promises, and keep them
Do Sensible Things: Make principled build vs. buy assessments and advocate for the right tools for the right job — not the fashionable ones, not the ones already in the estate just because they’re there
Garage Door Open: Create and maintain comprehensive internal documentation and decision records for systems and processes. Participate in architectural forums and make principled, open decisions that the rest of the organisation can learn from and hold us to
Benefits
Remote friendly, work from anywhere
If you’re in a city with an office, it’s there (and stocked with snacks) when you need it
Co-workers in over 40 states and 15 countries around the world
Health, dental, and vision insurance at little to no cost for individuals, and at competitive rates for your dependents
Disability and life insurance policies in case something happens
Unlimited vacation - we do track vacation days and actively encourage people to take it (on average, Astronomers take 20 days of vacation per year)
Parental leave
Laptop of your choice, and a stipend to help with your work-from-home setup
Monthly $170 pre-tax stipend intended to cover your cellphone and WiFi bills
Yearly internal summit for all employees
Regular access to conferences, workshops, and meetups in the ecosystem
Preferred experience
You’ve designed systems under load, reasoned carefully about failure, and made your colleagues’ lives better by giving them something solid and well-understood to build on top of
We’re not looking for someone to write strategy documents; we’re looking for someone who writes the strategy and the code, and who has done exactly that before at scale
Experience defining requirements and driving technology choices across an engineering organization. You’ve been the person in the room who frames the decision correctly, not just the one who executes it
Kubernetes at operator depth. You know what happens inside the scheduler and the control loop when things go wrong, because you’ve been there. You’ve operated clusters under real load, not just deployed workloads onto them
You can draw the diagram, explain the failure modes at each node, and make a reasoned argument for which ones actually matter in a given context. NALSD thinking is how you naturally approach a new system design
Strong written and verbal communication. You can write a design doc that changes minds, and a postmortem that makes the organisation smarter. You’ve worked effectively in a globally-distributed team
You write strategy documents and then write the code that proves them out
Distributed systems depth, grounded in practice. You have a solid working model of how production systems fail — consistency and availability tradeoffs, failure cascades, backpressure, graceful degradation
Multi-cloud experience, not just multi-cloud exposure. You’ve made considered architectural decisions across AWS, GCP, and/or Azure — not just consumed managed services, but evaluated tradeoffs between them and lived with those decisions in production
You’ve been the person who made the call, and lived with the consequences
We’re looking for a Staff+-level engineer who has built production platform systems at scale before — not just consumed them
Strong Go proficiency. The platform team writes production Go. You should be fluent: you’ve built and shipped systems in it, and you have opinions about what good Go looks like
Experience working on a SaaS/PaaS product across multiple cloud providers
Experience with storage primitives at the system level — you’ve reasoned about when to reach for a relational store vs. an object store vs. something else, and you have real opinions informed by real failures
Familiarity with Apache Airflow or workflow orchestration systems
