What Experimentation Engineers Actually Build
Experimentation engineering spans from infrastructure to analysis.
Experiment Infrastructure
Running experiments:
- Assignment service — Random user allocation
- Feature flags — Experiment configuration
- Exposure logging — Tracking who saw what
- Guardrail metrics — Safety monitoring
- Experiment lifecycle — Start, stop, ramp
Statistical Analysis
Making valid conclusions:
- Power analysis — Sample size planning
- Statistical tests — Significance testing
- Sequential testing — Early stopping
- Metric development — Defining success
- Variance reduction — CUPED and similar
Platform Development
Self-serve experimentation:
- Experiment UI — Configuration interface
- Results dashboard — Analysis visualization
- Documentation — Methodology guides
- Automation — Automated decisions
- Integration — Product team workflows
Experimentation Technology
Platforms
| Platform | Use Case |
|---|---|
| Optimizely | Feature experimentation |
| LaunchDarkly | Feature flags |
| Statsig | Full-stack experimentation |
| Eppo | Warehouse-native |
| Custom | Large companies |
Statistical Methods
- Frequentist: t-tests, chi-squared
- Bayesian: Posterior distributions
- Sequential: Group sequential testing
- Variance reduction: CUPED, stratification
Skills by Experience Level
Junior Experimentation Engineer (0-2 years)
Capabilities:
- Implement experiment features
- Support experiment setup
- Generate experiment reports
- Debug experiment issues
- Document processes
Learning areas:
- Statistical depth
- Experiment design
- Platform architecture
- Advanced analysis
Mid-Level Experimentation Engineer (2-5 years)
Capabilities:
- Design experiment systems
- Implement statistical methods
- Build analysis tools
- Handle complex experiments
- Work with data scientists
- Mentor juniors
Growing toward:
- Architecture decisions
- Methodology development
- Technical leadership
Senior Experimentation Engineer (5+ years)
Capabilities:
- Architect experiment platforms
- Lead methodology development
- Design scalable systems
- Handle organizational adoption
- Drive experimentation culture
- Mentor teams
Curiosity & fundamentals
Independence & ownership
Architecture & leadership
Strategy & org impact
Interview Focus Areas
Technical Skills
- "Explain p-values and statistical significance"
- "How do you determine sample size for an experiment?"
- "What's the multiple testing problem?"
- "Design an experiment assignment system"
Statistical Knowledge
- "When would you use Bayesian vs frequentist analysis?"
- "How do you handle experiments with low traffic?"
- "Explain variance reduction techniques"
Platform Engineering
- "Design an experimentation platform for a product company"
- "How do you ensure experiment assignment is deterministic?"
- "How do you handle experiment interactions?"
Common Hiring Mistakes
Hiring Pure Data Scientists
Experimentation engineering requires platform skills: building infrastructure, APIs, real-time systems. Pure data scientists may lack engineering depth.
Ignoring Statistics
Basic statistical understanding is essential. Engineers who don't understand p-values, power, or confidence intervals build misleading platforms.
Underestimating Platform Complexity
Experiment platforms at scale are complex: deterministic assignment, network effects, metric computation. Evaluate for systems experience.
Missing Product Sense
Experiments exist to drive product decisions. Engineers who don't understand product context build tools nobody uses.
Where to Find Experimentation Engineers
High-Signal Sources
Experimentation engineers typically come from data-driven tech companies with strong experimentation cultures. Netflix, Airbnb, Microsoft, Spotify, and Booking.com alumni have direct experimentation platform experience. Also look at experimentation platform companies like Optimizely, LaunchDarkly, and Statsig.
Conference and Community
CIKM (Conference on Information and Knowledge Management) features experimentation papers. KDD includes applied experimentation content. The experimentation community on Twitter and engineering blogs from top companies share best practices.
Company Backgrounds That Translate
- Experimentation pioneers: Netflix, Airbnb, Microsoft, Booking.com—XP platforms
- Experimentation tools: Optimizely, LaunchDarkly, Statsig, Split—commercial platforms
- Data-driven companies: Spotify, Uber, DoorDash—experiment culture
- Large tech: Google, Meta, Amazon—massive experimentation scale
- Feature flagging: Companies that have built flag management into experimentation
Statistical Background
Experimentation engineers often have quantitative backgrounds—statistics, applied math, or quantitative social science. Look for understanding of causal inference, not just engineering skills.
Recruiter's Cheat Sheet
Resume Green Flags
- Experimentation platform experience
- Statistical methods knowledge
- A/B testing infrastructure
- Metric development experience
- Data engineering skills
Resume Yellow Flags
- No experimentation experience
- Only using experiment tools
- Cannot discuss statistics
- No platform building experience
Technical Terms to Know
| Term | What It Means |
|---|---|
| A/B test | Controlled experiment |
| Statistical power | Ability to detect effect |
| p-value | Probability under null hypothesis |
| MDE | Minimum Detectable Effect |
| CUPED | Variance reduction technique |
| Guardrail | Safety metric |