Meta Data Analyst Career Ladder
Every level of Meta's data analyst ladder from IC3 to IC6 — typical timelines, what changes at each level, why analysts get stuck, and how promotions actually work.
Last updated: 2026-04-01
Aiming for your next level at Meta?
Get a personalized promotion plan with AI coaching.
Level Overview
| Level | Title | Typical Years | Median TC | Terminal? |
|---|---|---|---|---|
| IC3 | Data Analyst | 1–3 yr | $148K | No |
| IC4 | Data Analyst | 2–3+ yr | $176K | Yes |
| IC5 | Senior Data Analyst | 2–4+ yr | $235K | Yes |
| IC6 | Staff Data Analyst | 3–5+ yr | $296K | Yes |
Promotion Cycle
Frequency
Twice yearly (typically H1 and H2 review cycles)
Decision Maker
hybrid
Manager-driven with calibration. Your manager writes a promotion case based on your self-review, peer reviews, and demonstrated impact. The case goes through calibration with other managers and directors. Meta emphasizes demonstrated impact over tenure — you need to show you're already operating at the next level.
Key Details
- •Performance reviews happen twice yearly with promotion decisions tied to the review cycle
- •Manager writes the promotion narrative based on your impact documentation
- •Peer reviews from cross-functional partners (PMs, engineers) carry significant weight
- •Meta uses a 'performing at the next level' standard — you must demonstrate next-level work before promotion
- •Impact is the primary criterion — scope and complexity of problems you solve matter more than tenure
- •Calibration sessions normalize ratings across teams to prevent grade inflation
- •Data Analysts are evaluated on how their analysis changes product decisions, not just analytical quality
- •Cross-functional influence (working with PMs, engineers, designers) is expected at IC5+
- •PSC (Performance Summary Cycle) is the formal review process
IC3 — Data Analyst
Junior / Entry-LevelEntry point for new grads and early-career analysts. You execute analysis tasks, write SQL queries, build dashboards, and support your team's data needs. Your manager or senior analysts scope the work for you.
Typical Time at Level
1–3 years (typical: ~2 years)
Total Compensation (US)
$130K–$170K (median: $148K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Only responding to data requests instead of identifying what to analyze
- •Weak SQL or Python skills limiting your ability to handle complex datasets
- •Not understanding the product or business context behind the metrics you track
- •Dashboards that report numbers without surfacing actionable insights
IC4 — Data Analyst
Mid-LevelYou own analysis end-to-end for your product area. You define the right questions, design experiments (A/B tests), and present findings to product and engineering leads. Your analysis directly informs feature decisions and roadmap priorities.
Typical Time at Level
2–3+ years (typical: ~3 years)
Total Compensation (US)
$155K–$200K (median: $176K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Doing solid IC4-level work but not demonstrating IC5-scope impact
- •Analysis that's technically correct but doesn't change product direction
- •Not running or designing A/B tests — staying in descriptive analytics only
- •Weak cross-functional relationships with PMs and engineers
- •Not mentoring IC3 analysts or sharing analytical best practices
- •Manager not actively sponsoring your promotion case
- •Impact limited to a single product surface rather than broader product area
- •Generic peer feedback that doesn't demonstrate next-level behaviors
IC5 — Senior Data Analyst
SeniorProduct-area analytical leader. You define the measurement strategy for your product area, own key metrics, and your analysis shapes product strategy. You mentor IC3/IC4 analysts, lead cross-functional data reviews, and are the go-to person for analytical decisions in your area.
Typical Time at Level
2–4+ years (typical: ~4 years)
Total Compensation (US)
$200K–$275K (median: $235K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Operating at product-area scope instead of driving org-level analytical impact
- •Reacting to requests from product leaders instead of proactively shaping the data agenda
- •Not creating reusable frameworks, metrics, or tools that scale beyond your team
- •Doing all the analysis yourself instead of enabling others and delegating
- •Limited cross-team influence — IC6 requires impact across multiple product areas
- •Insufficient visibility with directors and VPs who make promotion decisions
IC6 — Staff Data Analyst
StaffOrg-wide analytical authority. You define measurement strategy across multiple product areas, create analytical frameworks adopted company-wide, and influence Meta's product direction through data. You set the standard for how analysis is done in your organization.
Typical Time at Level
3–5+ years (typical: ~5 years)
Total Compensation (US)
$260K–$350K (median: $296K)
Source: Levels.fyi
Why Engineers Get Stuck Here
- •Impact limited to a single product area rather than spanning the organization
- •Not shaping analytical culture or setting standards for the broader data team
- •Lacking executive visibility and sponsorship from senior leadership
- •No evidence of growing the analytical talent pipeline through hiring and mentoring IC5s
Additional Context
Meta's Data Analyst role sits at the intersection of product, engineering, and business teams. Analysts are expected to be deeply embedded in their product areas and drive decisions through experimentation and metrics. The role emphasizes SQL, Python, and statistical rigor, with A/B testing being a core skill at IC4+. Meta's performance culture means that analysts who only report numbers without driving action tend to plateau at IC4.
Data sourced from Levels.fyi (compensation figures, last verified March 2026), Team Blind, and Reddit. Meta does not publish a public DA-specific ladder; levels mirror the standard IC track (IC3–IC6 for DA scope).