Product Thinking
Understanding the user problem behind the ticket.
Backend Engineer track
Junior
Write correct code, ship small changes safely, ask good questions.
- Edge CasesUnusual inputs and situations that break naive code.
- RequirementsWhat the software must do.
- User EmpathyRemembering a real person uses what you build.
Mid-level
Own a feature end to end without hand-holding.
Core: start here
- Product ThinkingUnderstanding the user problem behind the ticket.
3 more mid-level concepts
- DogfoodingUsing your own product.
- Functional vs Non-Functional RequirementsWhat it does vs how well it does it.
- Handling Support EscalationsInvestigating issues reported by customers.
Senior
Own a system, its failure modes, and its trade-offs.
- Build vs BuyDeciding whether to build something or use an existing product.
- Business MetricsRevenue, retention, conversion: what the business measures.
- Experimentation CultureTesting ideas with data before committing to them.
- Feature AdoptionWhether users actually use what you shipped.
- User ResearchLearning what users actually need.
Staff
Shape how many teams build, across systems.
- Cost of DelayWhat it costs to ship something later.
- North Star MetricThe single metric that best captures the value you deliver.
Principal
Set technical direction for the organization.
Nothing here yet.
Data Analyst track
Junior
Write correct SQL, build trusted dashboards, ask good questions.
- Business MetricsRevenue, retention, conversion: what the business measures.
- North Star MetricThe single metric that best captures the value you deliver.
Mid-level
Own an analysis end to end, from vague question to recommendation.
- Edge CasesUnusual inputs and situations that break naive code.
- Experimentation CultureTesting ideas with data before committing to them.
- Feature AdoptionWhether users actually use what you shipped.
- Product ThinkingUnderstanding the user problem behind the ticket.
- RequirementsWhat the software must do.
Senior
Own experimentation and metrics design; call out bad numbers.
Nothing here yet.
Staff
Shape how the organization measures and decides.
Nothing here yet.
Principal
Set measurement strategy across the company.
Nothing here yet.
Data Engineer track
Junior
Build and fix pipelines from clear specs; write correct SQL.
- Edge CasesUnusual inputs and situations that break naive code.
- RequirementsWhat the software must do.
- User EmpathyRemembering a real person uses what you build.
Mid-level
Own pipelines and models end to end, including their quality.
- DogfoodingUsing your own product.
- Functional vs Non-Functional RequirementsWhat it does vs how well it does it.
- Handling Support EscalationsInvestigating issues reported by customers.
- Product ThinkingUnderstanding the user problem behind the ticket.
Senior
Design the platform's storage, processing and modeling choices.
- Build vs BuyDeciding whether to build something or use an existing product.
- Business MetricsRevenue, retention, conversion: what the business measures.
- Experimentation CultureTesting ideas with data before committing to them.
- Feature AdoptionWhether users actually use what you shipped.
- User ResearchLearning what users actually need.
Staff
Shape how the whole organization produces and uses data.
- Cost of DelayWhat it costs to ship something later.
- North Star MetricThe single metric that best captures the value you deliver.
Principal
Set data strategy and architecture across the company.
Nothing here yet.
Frontend Engineer track
Junior
Build UI that works, ship small changes safely, ask good questions.
- Edge CasesUnusual inputs and situations that break naive code.
- RequirementsWhat the software must do.
- User EmpathyRemembering a real person uses what you build.
Mid-level
Own a feature end to end without hand-holding.
Core: start here
- Product ThinkingUnderstanding the user problem behind the ticket.
3 more mid-level concepts
- DogfoodingUsing your own product.
- Functional vs Non-Functional RequirementsWhat it does vs how well it does it.
- Handling Support EscalationsInvestigating issues reported by customers.
Senior
Own an app's architecture, performance, and failure modes.
- Build vs BuyDeciding whether to build something or use an existing product.
- Business MetricsRevenue, retention, conversion: what the business measures.
- Experimentation CultureTesting ideas with data before committing to them.
- Feature AdoptionWhether users actually use what you shipped.
- User ResearchLearning what users actually need.
Staff
Shape how many teams build, across apps.
- Cost of DelayWhat it costs to ship something later.
- North Star MetricThe single metric that best captures the value you deliver.
Principal
Set technical direction for the organization.
Nothing here yet.