Data report · Updated 2026
The 2026 Tech Interview Report — 28 roles, one dataset
Use this dataset to estimate your interview loop, see what your role will test, and jump straight to the right prep guide. We broke the process for 28 tech roles — rounds, time-to-offer, competencies, and comp — into one comparable view, built on the same hand-curated research behind our per-role guides.
Key findings
What that means for how you prep:
- If your loop is 7+ rounds, expect 6–8 weeks and at least one behavioural round — that's the senior/leadership shape (see Staff Software Engineer or Director of Engineering interview prep).
- Targeting Staff+ or manager roles? System design and strategy outweigh coding — drill design and stakeholder stories, not LeetCode (see Engineering Manager interview prep).
- Mid-level IC loops are the leanest — around 5 rounds and coding-led (see Software Engineer interview prep).
- Product and data roles swap LeetCode for product sense or applied ML/SQL (see Product Manager and ML Engineer interview prep).
What tech interviews actually test
Share of the 28 roles whose interview includes each competency area. The surprise: a behavioural component is universal, but only 43% are coding-led — most senior, leadership, product and data roles are evaluated on design, strategy or product judgement instead. The emphasis shifts up the ladder.
Find your role — loops, comp & why candidates fail
Jump to your track, see your loop length, what it tests, time-to-offer and comp — then read the single most common reason strong candidates get rejected at that bar, and open the round-by-round prep guide to drill the fix. (We don't publish made-up “fail rates”; no one can source those per role and per stage honestly.)
Software Engineering
Software Engineer roles · IC2 → IC6 · 6–7 rounds
| Role & prep guide | Level | Rounds | Main test focus | Time to offer | Base | Equity / yr | Bonus |
|---|---|---|---|---|---|---|---|
| Staff Software Engineer interview prep | L6 / IC5 | 7 | System design | 5–8 weeks | $200–240k (SF/NYC) | $300–500k/yr | 20–25% |
| Principal Software Engineer interview prep | L7 / IC6 | 6 | Strategy / leadership | 8–12 weeks | $240–290k (SF/NYC) | $700k–1.5M/yr | 25–30% |
| Senior Software Engineer interview prep | L5 / IC4 | 6 | Coding + system design | 4–6 weeks | $155–185k (SF/NYC) | $80–150k/yr | 15–20% |
| Software Engineer interview prep | L3 / IC2 | 6 | Coding + system design | 3–5 weeks | $120–155k (SF/NYC) | $30–80k/yr | 5–15% |
Why Software Engineering candidates lose the offer
Describing technical work without org-level impact. The Staff bar is about how a 30+ person org operated differently because of you — not whether you shipped a hard system. Frame every story around what shipped at the org level, not the project level.
Being too tactical. Principal interviewers expect strategic and capital-allocation thinking — multi-year bets, executive influence, where to invest $10M of engineering. Strong Staff IC answers will get you downleveled here.
Treating system design as a Q&A. The signal at L5 is whether you DRIVE the conversation — propose, justify, evolve under pressure. Senior candidates who wait passively for the interviewer to lead get marked down hard, even with technically correct answers.
Coding in silence. Even with the correct answer, interviewers grade your thought process out loud. Narrate trade-offs, edge cases, and complexity as you go — that's the bar at L3 / IC2.
Engineering Management
Manager and leadership roles · M1 → VP · 6–8 rounds
| Role & prep guide | Level | Rounds | Main test focus | Time to offer | Base | Equity / yr | Bonus |
|---|---|---|---|---|---|---|---|
| Director of Engineering interview prep | M3 / M4 | 8 | Strategy / leadership | 8–14 weeks | $300–380k (SF/NYC) | $400–800k/yr | 25–30% |
| VP of Engineering interview prep | VP | 7 | Strategy / leadership | 12–24 weeks | $400–480k (SF/NYC) | $1M–3M/yr | 30–40% |
| Engineering Manager interview prep | M1 / M2 | 6 | Strategy / leadership | 4–6 weeks | $180–220k (SF/NYC) | $60–150k/yr | 15–20% |
| Senior Engineering Manager interview prep | M2 / M3 | 6 | Strategy / leadership | 5–8 weeks | $220–270k (SF/NYC) | $150–300k/yr | 20–25% |
Why Engineering Management candidates lose the offer
Walking in without a 90-day plan. Most Director rounds explicitly ask 'how would you operate in your first 90 days here?' — many candidates haven't drafted one. Bring a written outline tailored to the company; expect to defend each priority.
Underestimating CEO and board fluency. VP rounds are political as much as technical. Practising executive communication — concise updates, strategic recommendations, comfort with ambiguity — matters more than technical depth at this level.
Showing you still want to be an IC. EM interviewers worry first-time managers will neglect people work for coding. Make explicit you've made the transition: you might miss IC work occasionally, but you don't regret the move and have specific people-management wins to point to.
Speaking only about your direct team. The bar at this level is org-level: how you grow first-line EMs, calibrate performance across multiple squads, shape hiring across teams. Direct-team examples sound junior at this level.
Data & ML
Data Science, ML, and Data Engineering · IC3 → IC4 · 5–7 rounds
| Role & prep guide | Level | Rounds | Main test focus | Time to offer | Base | Equity / yr | Bonus |
|---|---|---|---|---|---|---|---|
| Senior Data Engineer interview prep | L5 / IC4 | 7 | System design | 5–7 weeks | $180–215k (SF/NYC) | $150–300k/yr | 15–20% |
| Senior Data Scientist interview prep | L5 / IC4 | 7 | Product sense | 5–8 weeks | $180–220k (SF/NYC) | $150–280k/yr | 15–20% |
| Senior Machine Learning Engineer interview prep | L5 / IC4 | 7 | Coding + system design | 5–7 weeks | $190–230k (SF/NYC) | $200–400k/yr | 15–20% |
| Data Engineer interview prep | L4 / IC3 | 5 | Coding + system design | 3–5 weeks | $145–175k (SF/NYC) | $50–110k/yr | 10–15% |
| Data Scientist interview prep | L4 / IC3 | 5 | Product sense | 4–6 weeks | $150–180k (SF/NYC) | $60–120k/yr | 10–15% |
| Machine Learning Engineer interview prep | L4 / IC3 | 5 | Coding + system design | 4–6 weeks | $155–185k (SF/NYC) | $80–150k/yr | 10–15% |
Why Data & ML candidates lose the offer
Describing pipeline-level work without platform-level framing. Senior DE interviews calibrate against multi-team platforms, schema-evolution decisions, and cross-team data contracts. Strong L4 "I built this pipeline" stories will get you downleveled if you don't frame them around the platform decisions that mattered.
Answering at the same depth as a mid-level. Senior DS rounds need strategic framing on top of technical fluency: priorities across bets, decisions enabled by the work, cross-functional influence stories. Strong IC3-level answers will get you downleveled here.
Describing model wins without production trade-offs. Senior MLE interviews are calibrated against latency budgets, retraining cost, monitoring, on-call. Strong L4 "model AUC" stories will get you downleveled if you don't frame them against the production constraints that shaped the design.
Under-investing in system design. Many candidates with strong SQL get filtered because they treat the pipeline design round as a casual chat instead of a 60-minute structured discussion. Practise the design framework: ingestion → schema → transformation → storage → monitoring, with explicit trade-offs at each step.
Prepping only for SQL when the loop has a Python or combined round. Many candidates with strong analysis skills get caught off-guard when the technical screen asks for pandas data manipulation or a simple algorithm in Python. Confirm the round breakdown with your recruiter and prep both.
Treating it like a DS interview. The MLE coding bar is closer to SWE than DS, and the system design round expects production thinking (latency, monitoring, retraining) not just modelling. DS-style answers focused on offline metrics get downleveled here.
Mobile
iOS and Android engineering · IC3 → IC4 · 5–6 rounds
| Role & prep guide | Level | Rounds | Main test focus | Time to offer | Base | Equity / yr | Bonus |
|---|---|---|---|---|---|---|---|
| Senior Android Engineer interview prep | L5 / IC4 | 6 | System design | 4–6 weeks | $185–220k (SF/NYC) | $180–350k/yr | 15–20% |
| Senior iOS Engineer interview prep | L5 / IC4 | 6 | System design | 4–6 weeks | $185–220k (SF/NYC) | $180–350k/yr | 15–20% |
| Android Engineer interview prep | L4 / IC3 | 5 | Coding + system design | 3–5 weeks | $150–180k (SF/NYC) | $80–150k/yr | 10–15% |
| iOS Engineer interview prep | L4 / IC3 | 5 | Coding + system design | 3–5 weeks | $150–180k (SF/NYC) | $80–150k/yr | 10–15% |
Why Mobile candidates lose the offer
Describing implementation work as architecture work. Senior Android interviews calibrate against the choices you made, not the features you shipped. Strong L4 "I built X at scale" stories will get you downleveled if you can't articulate the architectural trade-off behind X.
Describing implementation work as architecture work. Senior iOS interviews calibrate against the choices you made, not the features you shipped. Strong L4 "I built X at scale" stories will get you downleveled if you can't articulate the architectural trade-off behind X.
Treating Android coding rounds as algorithm tests. The interviewer is grading whether you write Kotlin like a production Android engineer — lifecycle-aware scopes, Compose state handling, process-death survival. Algorithmic correctness without that layer reads as a backend engineer playing Android.
Treating iOS coding rounds as algorithm tests. The interviewer is grading whether you write Swift like a production iOS engineer — value semantics, weak-self, MainActor, the lifecycle hooks. Algorithmic correctness without that layer reads as a backend engineer playing iOS.
Infrastructure
SRE and Platform Engineering · IC3 → IC4 · 5–7 rounds
| Role & prep guide | Level | Rounds | Main test focus | Time to offer | Base | Equity / yr | Bonus |
|---|---|---|---|---|---|---|---|
| Senior SRE / Platform Engineer interview prep | L5 / IC4 | 7 | System design | 5–7 weeks | $195–235k (SF/NYC) | $200–400k/yr | 15–20% |
| Site Reliability Engineer interview prep | L4 / IC3 | 5 | Coding + system design | 4–6 weeks | $160–195k (SF/NYC) | $80–160k/yr | 10–15% |
Why Infrastructure candidates lose the offer
Describing service-level reliability work without platform-level framing. Senior SRE interviews calibrate against organisational impact (services adopting your platform, error-budget policy you enforced, incidents that didn't recur because of process you changed). Strong L4 "I fixed this incident" stories will get you downleveled if you don't frame them around platform decisions.
Under-investing in the coding round. Many candidates from DevOps backgrounds have great infra skills but get filtered at the coding screen because they assumed SRE = bash + Terraform. The coding bar is closer to SWE than DevOps; drill LeetCode mediums for 4+ weeks.
Product
Product manager roles · IC2 → VP · 6–7 rounds
| Role & prep guide | Level | Rounds | Main test focus | Time to offer | Base | Equity / yr | Bonus |
|---|---|---|---|---|---|---|---|
| Senior Product Manager interview prep | PM3 / IC4 | 7 | Product sense | 5–8 weeks | $170–210k (SF/NYC) | $120–250k/yr | 15–20% |
| VP of Product interview prep | VP | 7 | Strategy / leadership | 12–24 weeks | $380–460k (SF/NYC) | $1M–3M/yr | 30–40% |
| Director of Product interview prep | PM4 / M3 | 6 | Strategy / leadership | 8–14 weeks | $280–340k (SF/NYC) | $300–600k/yr | 25–30% |
| Product Manager interview prep | PM2 / IC2 | 6 | Product sense | 4–6 weeks | $140–175k (SF/NYC) | $50–120k/yr | 10–15% |
Why Product candidates lose the offer
Not having a strategic point of view on the company. Senior+ PM interviews assume you've researched their business deeply — top-3 strategic moves, ranked, defended. Generic frameworks fail at this level.
Underestimating CEO and board fluency. VP rounds are political as much as product-strategic. Practising executive communication — concise updates, strategic recommendations, comfort with ambiguity — matters more than product depth at this level.
Walking in without a written 90-day plan. The director-track interview is fundamentally executive — you need a clear plan you can present and defend, with reasoning tied to the company's actual product, market, and team.
Reciting frameworks without judgment. Walking through 'CIRCLES' or 'AARM' on autopilot makes you sound junior. Show that you know the framework, then bring opinion: pick a target user, defend the choice, name the trade-off you accepted.
Solutions
Sales Engineering and Cloud Solutions Architecture · IC3 → IC4 · 6–7 rounds
| Role & prep guide | Level | Rounds | Main test focus | Time to offer | Base | Equity / yr | Bonus |
|---|---|---|---|---|---|---|---|
| Cloud Solutions Architect interview prep | L4 / IC3 | 7 | Coding + system design | 5–8 weeks | $150–185k (SF/NYC) | $60–120k/yr | Variable: $20–60k OTE on-target |
| Senior Cloud Solutions Architect interview prep | L5 / IC4 | 7 | Strategy / leadership | 6–10 weeks | $190–240k (SF/NYC) | $200–400k/yr | Variable: $30–80k OTE on-target |
| Senior Sales Engineer interview prep | L5 / IC4 | 7 | Strategy / leadership | 4–6 weeks | $160–200k (SF/NYC) | $60–150k/yr | Variable: $100–160k OTE on-target |
| Sales Engineer interview prep | L4 / IC3 | 6 | Strategy / leadership | 3–5 weeks | $130–160k (SF/NYC) | $30–80k/yr | Variable: $60–100k OTE on-target |
Why Solutions candidates lose the offer
Treating the architecture review as a system-design interview. Cloud SA architecture rounds are about customer-engagement design — discovery first, requirements before solution, cost as a first-class constraint. Strong system-design answers without the customer-centric framing read as SWE candidates playing SA.
Describing tactical architecture work as strategic. Senior Cloud SA interviews calibrate against the customer relationship and multi-year planning, not the technical artefact. Strong L4 "I designed this reference architecture" stories will get you downleveled if you can't articulate the enterprise-customer politics and cost-strategy work behind them.
Describing tactical deal work as strategic. Senior SE interviews calibrate against the insights you brought, not the deals you closed. Strong L4 "I worked the deal hard" stories will get you downleveled if you can't articulate the strategic shape behind the work.
Treating SE interviews as technical interviews with customer fluff. The technical depth is necessary but not sufficient. The customer-centric framing — discovery first, problem before solution, composure under objection — is what separates strong SE candidates from strong engineers playing SE.
Found your role?
The tables above are the market average. To prep for your actual interview, open your role's guide for the round-by-round breakdown — or paste a specific JD into a free scan and get predicted questions, a comp benchmark, and (with your CV) your experience gaps for that exact company.
How to use this report
- Find your role in the family tables above (or jump via your track).
- Note your loop shape — round count, main test focus, and time-to-offer tell you how long to plan and what to drill first.
- Open your prep guide for the exact round-by-round process, sample questions, level calibration, and where strong candidates still lose the offer.
Methodology
- Source. 28 tech roles, each researched and hand-curated for our per-role interview-prep guides — not scraped or AI-generated. The aggregates on this page are computed directly from that dataset at build time.
- Round counts include the recruiter screen and every formal evaluative round through the final loop. Informal chats, team match calls, and references are excluded.
- Main test focus & competency mix reflect which evaluation areas each role's interview includes — coding, system design, strategic/leadership, product sense, behavioural — taken directly from each role's tagged question set, not inferred from round names. A role counts once toward an area whether it tests it in one round or several.
- Role families use the same grouping as our interview-prep hub, so the two pages always agree on which roles belong together.
- Compensation targets the 50th percentile at major US tech employers (SF/NYC calibration), in USD. London, Berlin and Singapore typically run 30–50% lower in base; equity ratios vary by company stage. Use the figures as relative benchmarks between roles, not absolute local quotes.
- Updated. Published 2026-06-03. Figures track the 2026 hiring market; see what changed in tech interviews in 2026 for the shifts behind them.
Reusing this data? It's free under CC BY 4.0 — please credit Calibrd with a link to this page.
Prep for your actual role
The dataset is the average. Your interview isn't.
Paste a real LinkedIn, Greenhouse, or Lever JD and Calibrd predicts the questions for that company and level, benchmarks the comp to the role and location, and (with your CV) flags your specific experience gaps. Then practise out loud: record your answer, get it transcribed, and have your AI coach calibrate it — on every predicted question. PDF emailed. Free to install; full reports from $3.99.
Free to install · Preview every posting · Paid plans from $3.99