Frontend Engineer Hub

Frontend Engineer at Meta: Levels, Comp, and the React-Stewardship Culture (2026)

In short

Meta is the company that shipped React (since 2013) and continues to steward its core development. React 19, Server Components, Suspense, Hermes (the JS engine), Relay (GraphQL client), and ComponentKit (legacy iOS) all originated here. Frontend engineers at Meta work on Facebook, Instagram, WhatsApp, Threads, Messenger, Workplace, and the React open-source project itself. Levels run E3 (junior) through E9+ (rare distinguished tier) with senior E5 total comp $360,000-$520,000 and staff E6 $530,000-$780,000 per levels.fyi 2026. The interview is FAANG-standard with a frontend-specific UI build round. Meta's engineering blog at <a href="https://engineering.fb.com/" rel="noopener noreferrer" target="_blank">engineering.fb.com</a> is the canonical reference.

Key takeaways

  • Meta ships React. React 19, Server Components, Suspense, the React Compiler, the Hermes JS engine, Relay GraphQL client, and React Native all originated at Meta. Frontend engineers at Meta who work on the React open-source project itself sit on the React core team.
  • Levels at Meta: E3 (junior) → E4 (mid) → E5 (senior) → E6 (staff) → E7 (principal) → E8 (Senior Principal / Distinguished). Total comp at E5 commonly $360k-$520k, E6 commonly $530k-$780k, E7 commonly $700k-$1.2M+ per levels.fyi 2026 (levels.fyi/companies/facebook).
  • Meta's frontend stack is internal infrastructure, not Next.js. The company has built and maintains its own React-shipping infrastructure: a custom build pipeline, custom component frameworks (legacy Yoga + ComponentKit on mobile; modern React for web), custom GraphQL with Relay, internal design system. Next.js is not used at Meta.
  • The interview is FAANG-standard with a frontend-specific UI build round. The format: 1 phone screen + 4 onsite (2 coding, 1 product design / UI build, 1 behavioral) + bootcamp + team-match post-offer. The coding rounds emphasize React + JavaScript with the standard FAANG algorithmic bar.
  • Meta's frontend hiring bar in 2026 emphasizes React + JavaScript depth, algorithmic-coding fluency, and cross-functional partnership. The bar is comparable to general-SWE Meta hiring with a frontend-specific UI build round added. Hello Interview's FAANG Job Levels post (hellointerview.com/blog/understanding-job-levels-at-faang-companies) is the canonical leveling reference.
  • Meta has invested heavily in the React Compiler (released beta with React 19) — internal Meta surfaces are increasingly compiler-optimized. Senior+ frontend engineers at Meta are expected to be fluent with the React Compiler's tradeoffs.

What frontend engineering at Meta actually looks like

Meta's frontend organization is enormous and structured around product surfaces:

  • Facebook web. The largest frontend surface — facebook.com. React + Relay (GraphQL) + custom build infrastructure. Hundreds of frontend engineers across the news feed, profile, groups, marketplace, and ads-related surfaces.
  • Instagram web. instagram.com. Smaller than Facebook web but still a substantial frontend surface; React + Relay.
  • WhatsApp web / Messenger / Workplace. Each has its own frontend team and stack variant.
  • Threads. Newer surface (launched 2023), React-heavy.
  • React open-source. The React core team — the engineers who ship React 19, the Compiler, Server Components stable, Suspense improvements. The team is small (10-30 engineers as of 2026) and includes some of the most senior frontend engineers in the industry.
  • Hermes JS engine. Meta's internal JS engine for React Native (and increasingly other surfaces). Substantial systems-engineering work.
  • Internal infrastructure. Meta's frontend platform team — the build pipeline, the design system, the dev-tools, the perf platform. Senior+ work.

The team structure: very large (~5,000-10,000+ frontend engineers as of 2026 across all of Meta per public disclosures). The engineering culture emphasizes data-driven decisions, A/B testing, structured perf-management, and the internal-tooling-as-leverage philosophy. Meta's engineering blog (engineering.fb.com) covers ongoing technical work.

The interview at Meta: format and what's tested

The Meta interview process per public Hello Interview reports, Glassdoor data, and Meta's careers page (metacareers.com):

  1. Recruiter screen. 30 minutes.
  2. Technical phone screen. 45-60 minutes. Algorithmic-coding round in any language; the standard FAANG algorithmic bar applies. LeetCode-medium-style problems on graphs / trees / strings / DP.
  3. Onsite — Round 1: Coding. 45 minutes. Algorithmic-coding round.
  4. Onsite — Round 2: Coding / Product Design. 45 minutes. Either a second algorithmic-coding round or a product-design / UI build round depending on the role specialty. Frontend engineers typically get a UI build round here — implement a small interactive component (e.g., a typeahead search, a custom dropdown with keyboard handling).
  5. Onsite — Round 3: System Design / Architecture. 45-60 minutes. For mid+ candidates. Frontend-flavored system design — design the data-fetching layer for a news-feed-scale product, design the comment thread for a high-traffic page, design the offline-first sync for a chat product.
  6. Onsite — Round 4: Behavioral. 45 minutes. Conversation about past work, leadership, conflict-resolution. Meta uses a structured behavioral rubric.
  7. Bootcamp + team-match post-offer. Distinctive to Meta. New hires spend 4-6 weeks in a bootcamp learning Meta's internal tooling and meeting teams; team-match happens at the end of bootcamp. Hello Interview's FAANG Job Levels post (hellointerview.com/blog/understanding-job-levels-at-faang-companies) covers the bootcamp-and-team-match pattern in detail.

The Meta bar is FAANG-standard algorithmic-coding plus a frontend UI build round. The UI build round is graded on: correctness, accessibility (keyboard handling, ARIA), code quality, edge-case coverage, and the conversation about trade-offs.

Compensation: real bands at Meta

Total comp at Meta by level (US, per levels.fyi 2026):

LevelBaseTotal comp
E3 (junior)$140k-$190k$210k-$290k
E4 (mid)$170k-$220k$280k-$400k
E5 (senior)$200k-$260k$360k-$520k
E6 (staff)$240k-$300k$530k-$780k
E7 (principal)$280k-$360k$700k-$1.2M+
E8 (senior principal)$320k-$420k$1.0M-$2.0M+

Meta is a public company; equity is RSU-based. The reference is levels.fyi/companies/facebook (levels.fyi/companies/facebook). The compensation premium for React core team members is partly cosmetic (E5 pays the same to a React core engineer as to a Facebook product engineer) but the org-level scope and external visibility is materially higher.

What's load-bearing at Meta: the cultural and technical signals

Three signals to demonstrate, drawn from Meta's engineering blog (engineering.fb.com), Hello Interview's FAANG coverage, and the public Meta careers content:

  • Algorithmic-coding fluency. Meta's coding bar is FAANG-standard. Engineers who can solve LeetCode-medium problems in 30 minutes consistently pre-screen well. Frontend specialty does not exempt you from the algorithmic-coding bar.
  • React + JavaScript depth. Meta is React's home; senior+ frontend engineers at Meta are expected to read and write React internals fluently. The interview's UI build round tests modern React (hooks, Suspense, context, custom hooks, error boundaries). The React Compiler integration is a 2026 senior-plus expectation.
  • Cross-functional partnership. Meta runs on PM-engineering-design partnership at every level. Senior+ frontend engineers are expected to partner with PM and design fluently and to articulate trade-offs in PM-readable language. The behavioral round tests this directly.

What's NOT load-bearing at Meta: Next.js depth (Meta uses internal infra, not Next.js), pure design-tooling fluency (Figma's territory), pure backend / distributed-systems experience (separate Meta organizations).

Frequently asked questions

Is React 19 stewardship still at Meta in 2026?
Yes. The React core team at Meta continues to ship React's major releases. React 19 (December 2024) was led by Meta with substantial Vercel collaboration on Server Components stability. The React Compiler released beta with React 19 was authored at Meta. The team is small (10-30 engineers as of 2026) and is one of the most prestigious frontend roles in the industry.
Do I need GraphQL / Relay experience for Meta?
Helpful at senior+. Meta uses Relay (their internal GraphQL client) extensively across Facebook, Instagram, and most product surfaces. Engineers without prior Relay experience can ramp up post-hire (Meta's bootcamp covers it), but engineers with prior Relay or GraphQL depth pre-screen favorably. The Relay docs (relay.dev) are the canonical reference.
Is Meta hiring frontend engineers in 2026?
Yes per public job postings at metacareers.com as of early 2026. Meta has continued hiring after the 2022-2023 reductions; the AI-features expansion (Llama-integration across Meta surfaces, Threads growth) supports sustained hiring. Senior+ frontend with React depth and algorithmic-coding fluency is the dominant hiring profile.
Can I work remotely at Meta?
Limited. Meta has implemented a return-to-office policy for most engineering roles. Some roles are remote-eligible per the careers page (metacareers.com), but the dominant pattern is hub-based work at Menlo Park, Seattle, NYC, London, or other Meta offices.
What's the React core team interview like?
Public information is sparse — the React core team is small and most hires are internal transfers from product teams. External hires happen but are rare. The interview includes substantial deep-dives on React internals (reconciliation, Fiber, hooks-rules, the compiler), open-source contribution patterns, and architecture trade-offs. Andrew Clark and Sebastian Markbåge (formerly at Vercel) are public-facing React core engineers; their writing is the closest public reference.
How important is the bootcamp + team-match for new hires?
Distinctive to Meta. New hires (E3-E5) spend 4-6 weeks in bootcamp learning Meta's internal tooling and meeting teams. Team-match happens at the end of bootcamp; engineers get to express preferences but don't always get the team they wanted. The pattern is described in Hello Interview's FAANG Job Levels coverage. The team-match outcome materially shapes the early career trajectory at Meta.
What's the difference between Meta's frontend roles and React Native roles?
React Native specialists work on the cross-platform mobile surface (Facebook mobile, Instagram mobile, Messenger mobile). The interview shape is similar but with mobile-specific UI build rounds and React Native architecture conversations. Cross-platform-mobile is a distinct specialty within Meta's frontend org. The hiring rubric is similar.

Sources

  1. Meta Careers — official job postings.
  2. Meta Engineering Blog — React, Hermes, infrastructure writing.
  3. React.dev — React 19 release notes (December 2024). Meta-led release.
  4. levels.fyi — Meta comp by level (public-company RSU).
  5. Relay — Meta's open-source GraphQL client. Internal Meta product surfaces use Relay extensively.
  6. Hello Interview — Understanding FAANG Job Levels. Canonical Meta E3-E8 leveling reference.

About the author. Blake Crosley founded ResumeGeni and writes about frontend engineering, hiring technology, and ATS optimization. More writing at blakecrosley.com.