What you’ll own
- A technical domain, not a single service. You’ll be the engineer who knows how a slice of Data Cloud works end-to-end – and where it’s going next.
- Architecture and strategy. Drive multi-quarter technical roadmaps: what we build, what we retire, and what we stop doing. Author the RFCs that matter.
- Cross-team decisions. Partner with two or three engineering teams, Product, and Data Science to make the right technical trade-offs – especially the ones no single team can make alone.
- Quality of the whole. Reliability, performance, cost and security for your domain. When an incident touches your area you’re part of the postmortem.
- Engineering standards. Set the bar for design reviews, API contracts, testing and operability – and teach it, so it sticks.
- Hands-on work. We expect you to still ship code – typically the hard bits, the de-risking prototypes, and the reference implementations others build on.
- Mentorship at scale. Grow Seniors into the next Staff engineers. Coach Engineering Managers on technical direction. Be generous with your time.
Must-haves
- Deep experience building and running production systems in Python on AWS – typically 8+ years of engineering, with at least a couple of those operating at a Staff/Principal scope.
- A track record of leading systems, not just features. You can point to platforms or services you designed whose decisions still hold up under load, change and time.
- Strong judgement on trade-offs. Cost vs. latency, build vs. buy, consistency vs. availability, velocity vs. debt – and you can explain your reasoning in a room of non-engineers.
- Demonstrable technical influence across teams, not just within one. RFCs, guilds, shared libraries, architecture forums – something that shows your reach.
- A mentoring habit. Named engineers whose careers moved because of your input. You already enjoy this work.
- Excellent written communication. Your docs, RFCs and postmortems teach people things. This matters as much as your code.
