Anna Sulkina has always been a traveler, and we’re lucky her travels have brought her to Airbnb. Anna is a Senior Director of Engineering…
Overview
Anna Sulkina, Senior Director of Engineering at Airbnb, shares her career journey from growing up in Eastern Ukraine during the collapse of the Soviet Union to leading Application & Cloud Infrastructure at Airbnb. The article covers her path through hardware diagnostics, frontend-to-backend engineering, nearly nine years at Twitter during its monolith-to-microservices transition, and her current role building developer platforms and infrastructure at Airbnb.
What You'll Learn
How an engineering leader transitioned from individual contributor to Senior Director of Engineering over two decades
Why designing for failure is essential when building resilient distributed systems
How to drive adoption of new technologies like GraphQL across a large engineering organization
How to build trust and alignment when leading a Developer Platform organization
Why aligning personal interests with company mission matters for long-term career satisfaction
Key Questions Answered
What does the Application & Cloud Infrastructure team at Airbnb do?
How did Twitter transition from a monolith to microservices architecture?
How was GraphQL adopted at Twitter?
How did Airbnb's Developer Platform team improve developer satisfaction?
What is the career path from individual contributor to Senior Director of Engineering?
What challenges do immigrant engineers face in the US tech industry?
Key Statistics & Figures
Technologies & Tools
Some links below are affiliate links. We may earn a commission if you make a purchase.
Key Actionable Insights
1When building distributed systems, design for failure rather than hoping to avoid it. The more complex a system becomes, the more likely it is to fail. Build resilience into your architecture from the start by assuming components will fail and planning accordingly.Anna learned this lesson during Twitter's transition from monolith to microservices, dealing with real incidents in the command center. This principle is referenced from the well-known paper 'How Complex Systems Fail.'
2When driving adoption of new technology within a large organization, start small with a proof of concept (such as a hack week project), then invest in building consensus across teams and leadership before scaling. The organizational work of convincing stakeholders is as important as the technical implementation.Twitter's GraphQL adoption started with two engineers during hack week and eventually replaced legacy REST services company-wide, accelerating velocity for all product feature teams.
3When taking over a new engineering organization, start by answering fundamental questions like 'Why are we here together?' and 'Where are we going?' before optimizing execution. Building internal alignment within your team and external alignment with stakeholders creates the foundation for sustained high performance.At Airbnb, Anna spent the first year or two focusing on organizational setup, coaching leadership, and building alignment, which resulted in a 10% year-over-year improvement in developer satisfaction.
4Measure developer experience quantitatively through regular surveys to track the impact of platform and tooling improvements. Building out developer satisfaction metrics provides objective evidence of your team's value and helps prioritize future investments.Airbnb's Developer Platform team built bi-annual DevX surveys that showed measurable improvements, helping earn trust from the engineers they supported.
5Consider leadership as a path if you notice the difference between teams with good leaders and those without. The transition from IC to manager doesn't have to be immediate — being pitched multiple times and trying it gradually can lead to a more informed and committed decision.Anna was pitched on leadership multiple times before accepting, and once she experienced coaching people and building high-performing teams, she knew it was the right path for her career.