Staff Software Engineer, Astronomer

• Extensive, hands-on experience designing and building data infrastructure at scale — storage systems, retrieval and indexing infrastructure, data and/or streaming platforms that serve production traffic for multiple teams and products
• Strong proficiency in Go and deep, practical experience with Kubernetes at the operator level. You know what happens when things go wrong, because you've been there
• In-depth knowledge of the database and data systems landscape — relational, NoSQL, blob, timeseries, vector — and the hard-won experience to know when each is and isn't the right choice
• Deep understanding of distributed systems and Non-Abstract Large Systems Design: you can draw the diagram, explain the failure modes, and know which ones to actually care about
• Experience working across multiple cloud providers (AWS, GCP, Azure) — not just as a consumer, but as someone who has made considered choices between them and understood the trade-offs
• Experience defining requirements and making and justifying technology choices in cross-functional engineering organisations
• Strong written and verbal communication skills, with experience working in a globally-distributed team

Desirable

• We're looking for a Staff+-level engineer who has built serious data infrastructure before — not pipelines, not transformations, but the storage systems, retrieval infrastructure, and data platforms that sit underneath everything else and that other engineers build on top of
• You'll be joining our Platform Engineering team with a mandate to define and deliver this capability from the ground up, with the sponsorship and organisational backing to do it properly
• This is a foundational role at an interesting moment: your work will directly shape what Astronomer's products — Astro, Observe, and our IDE — are capable of over the next several years. This role reports directly to the VP responsible for delivering these platforms reliably
• Astronomer has a healthy and complex data estate spanning multiple cloud providers, a mix of managed and self-hosted systems, and an increasingly ambitious set of requirements as our products mature
• We have a clear sense of where we want 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
• We're not looking for someone to write data strategy documents; we're looking for someone who writes the strategy and the code, and who has done exactly that before at scale
• Blaze a Trail: Own and develop our data infrastructure strategy and practice, with 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