Staff Software Engineer, Platform Infrastructure

Astronomer•New York, NY

1d•$275,000 - $377,000•Hybrid

About The Position

Astronomer empowers data teams to bring mission-critical software, analytics, and AI to life and is the company behind Astro, the industry-leading unified DataOps platform powered by Apache Airflow®. Astro accelerates building reliable data products that unlock insights, unleash AI value, and powers data-driven applications. Trusted by more than 800 of the world's leading enterprises, Astronomer lets businesses do more with their data. 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. We’re looking for a Staff+-level engineer who has built production platform systems at scale before — not just consumed them. 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. You write strategy documents and then write the code that proves them out. You’ve been the person who made the call, and lived with the consequences. 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.

Requirements

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

Nice To Haves

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.
Experience working on a SaaS/PaaS product across multiple cloud providers.
Familiarity with Apache Airflow or workflow orchestration systems.

Responsibilities

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 directly involved in deciding what we work on and how we work on it. Make promises, and keep them.
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.
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.