Meta is a global leader in social media, virtual reality, and AI. It owns Facebook, Instagram, WhatsApp, and Reality Labs products used by billions worldwide. In India, Meta hires engineers for large-scale systems, machine learning, and product development.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Put measurable project impact near the top: latency improved, users reached, accuracy gained, cost saved - even campus-scale numbers beat vague “developed a web app.” Link GitHub only if the repo is readable. Mention languages you will use in CoderPad. Contest ranks help as secondary signal; they do not replace Meta-tag practice.
If you have Instagram/WhatsApp/Facebook project clones, be ready to discuss real trade-offs you made - interviewers have seen a thousand clones and will poke storage and fan-out choices.
Academic requirements
Marks: No strict official cutoff published for all India roles; many campus JDs and student reports cite 7.0+ CGPA or 70% across 10th, 12th, and graduation
Degree: B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields
Year of Study: Final-year students and recent graduates (within about 1 year)
Backlogs: No active backlogs at application / joining verification
Branch & skills
Branches: CS, IT, ECE, EE, and closely related streams on most drives
Programming: Strong DSA in Python, C++, or Java
Experience: Freshers and early careers for E3; deeper design for E4+
On-campus Meta JDs are where students most often screenshot a 7.0 / 70% line across academics. Off-campus posts may omit a hard number and still filter through resume + OA. Either way, clearing a printed floor only gets you into the funnel - phones and onsite decide offers.
Class 12 questions students ask: if your JD lists 10th/12th/grad together, treat them as a package. A spike downward in one year is explainable once; three inconsistent stories across forms is not. If your college uses percentage while Meta form asks CGPA, convert carefully and keep evidence.
“Is 6.8 enough?” Sometimes a recruiter will still talk if coding signal is elite (contests, prior finals, strong internship). Do not bank on exceptions. Build the coding case first, then ask the placement cell or recruiter with facts - not hopium.
Production Engineer / other tracks: PE and adjacent roles can appear with overlapping DSA expectations plus stronger systems/ops flavor. Read the JD. This hub’s E3 SWE map is the default fresher path most students mean by “Meta placement.”
Meta CGPA criteria (candidate-reported): treat 7.0 / 70% as a common shortlisting floor when a campus JD prints it - not as a guarantee. Meta does not publicly pin one India-wide number that never moves. Always verify the exact line on your drive notice or careers post.
| Academic Level | Typical floor (candidate-reported) | Notes |
|---|---|---|
| Graduation | Often 7.0+ CGPA / 70% when listed | Confirm on campus JD |
| 10th / 12th | Often aligned when JD lists all three | Consistency matters |
| Backlogs | Usually none active | Checked again at offer stage |
Selection chances by CGPA band (rough student framing):
| Band | What it usually means |
|---|---|
| Around 7.0 | Meets many printed floors; OA must be strong |
| 7.5+ | Competitive shortlist band with solid projects |
| 8.0+ | Strong academically - still must clear coding rounds |
2025 and 2026 eligibility talk is the same story: no separate year-tagged CGPA FAQ needed. If your CGPA is slightly under a printed floor but you have contest ranks, strong internships, or Meta Hacker Cup signal, ask the recruiter / placement cell - exceptions are rare and never replace interview skill.
Good fit: You can finish two medium DSA problems in 45 minutes while explaining trade-offs; you have STAR stories with real impact numbers; you are okay with product design conversations about feeds, messaging, and ranking. Internships help, but a clean CoderPad habit helps more.
Harder path: You only practiced with LeetCode Run + autocomplete; you cannot talk without reading notes; you treat behavioral as “HR fluff.” Meta interviews mix values into technical slots. Silent grinders who cannot narrate impact stall late.
Branch myth: ECE/EE candidates clear Meta every year when DSA is real. Branch does not get you a discount on graphs and hash maps.
Campus vs off-campus eligibility feel: On-campus JDs are where the 7.0/70% line shows up most often in writing. Off-campus and referral paths may soft-pedal a printed CGPA number, then still crush you on OA and phones. Do not assume “no number on the post” means “academics irrelevant forever” - background checks still exist - but do assume coding decides shortlists once you are in the funnel.
Internships and PPOs: High-performing Meta interns sometimes convert without replaying the entire fresher OA story. That path still expects strong coding and values alignment during the internship. If you are a final-year candidate without an internship, the open loop above is your main map - do not wait for a PPO rumor season.
Documents students forget: keep mark sheets ready, be consistent about graduation month, and do not invent CGPA rounding stories. Recruiters notice resume vs portal mismatches quickly.
Download 2026 Meta placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Meta papers are not a service-company aptitude bank. Previous-year sets mainly train OA stamina (3-4 timed DSA problems) and the themes that later appear in phone screens: arrays/strings, trees/graphs, hash maps, and light product design prompts. Think of them as simulators for speed and correctness under a clock - Meta reuses families of problems more than exact clones.
| Stage | What previous-year practice trains |
|---|---|
| OA | 3-4 coding problems; all tests pass mindset |
| Phone screen | 2 problems / 45 min; spoken approach |
| Onsite coding | Medium DSA with follow-ups |
| Design | News feed / messenger / Stories style prompts |
| Behavioral | Values stories with measurable impact |
Across recent candidate notes and year packs:
Related problems to practice (use this instead of memorizing one PDF):
| Theme you saw | What to drill next |
|---|---|
| Longest unique substring / window | Anagram windows, at-most-K distinct |
| Tree LCA / paths | DFS with backtracking, diameter variants |
| Graph BFS layers | Shortest path in unweighted graphs, multi-source BFS |
| Hash frequency maps | Prefix sums, two-sum family, grouping problems |
| Merge / interval style | Sweep line thinking, sorting + pointers |
How to use one paper set in a sitting: time 60-90 minutes for 3-4 problems; ban running code on the first pass; mark every guess; rewrite the weakest solution cleanly; spend 20 minutes listing the pattern you missed (two-pointer, BFS layering, prefix map, etc.). Three reviewed sets beat ten skimmed PDFs.
Meta OA problems rarely need exotic libraries. They stack:
If you can narrate “what the pointer means right now,” you are practicing phone-screen survival too. If you only recognize the problem title from memory, a small twist will break you.
Meta hires through campus drives, careers portal / off-campus, referrals, internship conversions, and contest visibility (for example Meta Hacker Cup). After the OA, most fresher loops are virtual. The technical bar does not drop because the venue is online.
Campus recruitment
Placement-cell coordinated PPTs and registrations at participating colleges. Season-aligned windows are common; follow your TPO mail exactly for OA links.
Off-campus / careers
Apply on Meta Careers for Software Engineer and related roles. Recruiter screens and OA invites follow resume shortlists.
Referrals, internships, contests
Employee referrals and PPO conversions are real paths. Meta Hacker Cup can create signal - still prepare the same interview loop afterward.
Background, motivation, Why Meta?, logistics. Rough filter before burning interviewer time. Have a crisp story: products you used thoughtfully, projects with metrics, and role level (E3 vs experienced). Ask clarifying questions about timeline - Meta loops can move fast once OA is cleared.
Usually 3-4 DSA problems. Topics: arrays, strings, trees, graphs, hash maps. Most Meta OAs do not include DP. Expect an online platform; all test cases generally need to pass for shortlisting.
| Focus | Typical ask | Student tip |
|---|---|---|
| Arrays / strings | Windows, parsing, uniqueness | Clarify constraints early |
| Trees / graphs | Traversal, connectivity | Draw the graph before coding |
| Hash maps | Counts, prefixes | Watch off-by-one on windows |
| Complexity | Time/space talk later | Still write correct first |
Time box many students use: scan all problems (3-4 min) → lock an easy/medium first → leave the hardest for last with a partial plan written. Do not burn 40 minutes on problem 1 while problem 2 is a giveaway.
| Minute band | Action |
|---|---|
| 0-5 | Read all; pick order |
| 5-25 | Problem A (sure clear) |
| 25-50 | Problem B |
| 50-70 | Problem C / stretch |
| 70-75 | Edge-case pass and cleanup |
Two coding problems per round in CoderPad: no autocomplete, no execution. You must explain approach, clarify requirements, and discuss complexity. This is where IDE-only practice dies. If you cannot dry-run your own loops, say so early and fix the habit before onsite.
Use these as 20-minute whiteboard drills, not as memorized speeches:
For each: users → API → data model → bottlenecks → one cache idea → one failure mode. Stop before naming every AWS service you have heard of.
Typical mix:
Treat every coding round as also a mini-behavioral: interviewers listen for how you handle ambiguity and feedback.
Compensation, joining date, location, and remaining logistics. By this point the technical bar is mostly cleared - do not invent conflicting stories about notice periods or location.
If you only remember three numbers: ~5 stages, OA often 60-90 minutes with 3-4 problems, E3 fresher TC commonly discussed around ₹50-65 LPA (candidate-reported). Everything else is execution.
After a strong loop, recruiters may run team matching. Narrow “only Instagram ML in Bangalore, remote forever” constraints can stretch weeks. Rank two or three acceptable teams/locations before matching calls. Ask thoughtful questions about on-call, stack, and mentorship - Meta interviewers remember candidates who sound like teammates, not tourists.
| Phase | Duration | What happens |
|---|---|---|
| Recruiter / resume | Days to a week | Screen + process overview |
| OA | 1 day window | 3-4 coding problems |
| Phone screen(s) | Few days to 1 week | Live CoderPad |
| Virtual onsite | 1-2 weeks scheduling | Coding + design + behavioral |
| Team match / HR | Days to longer | Offer details; matching can stretch |
| Total | Often 2-4 weeks | Off-campus can run longer |
| Item | Typical Meta fresher OA |
|---|---|
| Duration | 60-90 minutes |
| Questions | 3-4 coding |
| DP | Usually absent |
| Pass bar | All / nearly all tests |
| Next step | Phone screen in CoderPad |
Waiting-week anti-patterns: opening five new YouTube design playlists; rewriting your entire resume the night before; doomscrolling “Meta layoff” threads; skipping spoken practice because “I’ll be fine live.” Protect sleep and one mock per day max.
Record yourself once. Most students discover they go silent for thirty seconds at a time - that silence reads worse than a slower correct approach.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Meta invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Meta sits around ₹50-65 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Meta does not publish one official India CGPA PDF. From student reports and campus JDs, a common baseline is 7.0+ CGPA or 70% across 10th, 12th, and graduation, but strong coding and interview performance matter more. Degrees: B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields. Final-year students and recent graduates (within about 1 year). No active backlogs. Maximum about 1 year gap commonly reported. Full-ti.
What you are training for: Typical fresher path: Resume & Recruiter Screen (20-30 min) → Online Coding Assessment (60-90 min, 3-4 DSA problems, most Meta OAs avoid DP) → Technical Phone Screen(s) (1-2 rounds, 45 min, 2 coding problems in CoderPad) → Virtual Onsite (3-4 rounds: coding, system/product design, behavioral) → HR/Offer. Total often 2-4 weeks; team matching can stretch after yes.
Short version of the prep split: Split time roughly 50% DSA (Meta-tag LeetCode, timed 2-problem/45-min mocks), 20% system/product design (news feed, messenger, Stories), 20% Meta values STAR stories, 10% communication and light aptitude. Practice CoderPad-style coding with no autocomplete and no code execution. Use timed previous papers on this site.
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Meta previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Meta drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Meta usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Meta?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Meta-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Meta story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Meta papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Meta papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Meta-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Meta paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Meta. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Meta, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Meta mistakes, you are collecting content, not preparing.
Sit one more mixed Meta set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
Figures below are candidate-reported as of August 2026 (total annual package bands). Treat them as ranges, not offer letters.
| Level | Experience | Base (approx.) | Total Package | Typical background |
|---|---|---|---|---|
| E3 (Software Engineer) | New Grad | ₹38-48 LPA | ₹50-65 LPA | Fresh graduates, strong campus/off-campus loops |
| E4 (SWE 2) | 2-5 years | ₹60-75 LPA | ₹80-100 LPA | Deeper ownership + design |
| E5 (Senior SWE) | 5-8 years | ₹90-130 LPA | ₹1.2-1.7 Cr | Senior scope |
| E6+ | 8+ years | ₹1.7 Cr+ | ₹2.2 Cr+ | Staff+/architect tracks |
| Role | Level | Total Package | Notes |
|---|---|---|---|
| Production Engineer | Entry | ₹38-55 LPA | Strong CS + systems ops flavor |
| QA / Automation | Entry-Mid | ₹28-45 LPA | Testing depth |
| Product Manager | Mid-Senior | ₹65-95 LPA | Product sense + tech |
| Data Scientist | Mid | ₹55-85 LPA | ML / analytics |
Hybrid policies vary by team, health coverage, RSUs as a real slice of fresher TC, learning stipends/internal training, and global mobility on some orgs. Read the offer for vesting cliffs and joining bonus separately from the headline LPA tweet.
How to read an E3 letter: base, bonus, and RSU are different levers. Compare total first-year cash + stock assumptions carefully against peer offers (Google / Amazon / Microsoft). Location and team can move you inside the band.
Growth students ask about: E3 → E4 is the early ladder people discuss; promotion timing depends on impact evidence, not vibes. Internal mobility across Meta products is a real talking point - if you care about working on Instagram vs infra vs AI-adjacent teams, say that in matching conversations with specifics.
Negotiation tone that does not backfire: know your competing offer math, ask clarifying questions about vesting and joining bonus, and avoid inventing exploding offers. Meta HR has seen every script. Clarity beats theater.
Hiring shape 2026
Virtual OA + interview loops remain the default for many India candidates. Product/system design questions show up earlier for stronger levels.
Process constants
OA still leans non-DP coding. CoderPad without execution is still the phone-screen reality. Values/behavioral stays mandatory.
Access paths
Hacker Cup, referrals, and internship PPOs remain useful side doors - none replace loop prep.
Company context
Instagram, WhatsApp, AI, and Reality Labs work still show up in “Why Meta?” answers - pick a specific product story, not a generic metaverse speech.
Net for 2026 prep: do not wait for a rumor that “Meta stopped asking graphs.” Double down on timed Meta-tag DSA, dry-run discipline, and STAR stories with metrics. Faster offers happen for some candidates; team matching can still stretch if you constrain offices too hard.
Also expect virtual-first logistics to stay normal for many India candidates. That means your home network, webcam setup, and ability to draw a design on a tablet/whiteboard tool are part of prep - not afterthoughts the morning of onsite. If your college finally gets a Meta PPT, treat it as a real shot; the bar does not drop because the PPT slide deck looks friendly.
Signal vs noise in 2026 chatter: Hacker Cup placements, AI team rumors, and “Meta is freezing” tweets will keep circulating. Your controllable inputs remain the same - Meta-tag patterns, CoderPad tracing, values stories with numbers, and honest location prefs.
Typical fresher path: Resume & Recruiter Screen → Online Coding Assessment (60-90 min, 3-4 DSA problems) → Technical Phone Screen(s) on CoderPad → Virtual Onsite (coding + design + behavioral) → HR/Offer. End-to-end often 2-4 weeks, with possible team-matching delay after a hire signal.
About five stages: recruiter, OA, phone screen(s), onsite loop (usually 3-4 interviews), HR. Phone screens may be one or two. Onsite commonly includes two coding rounds, one design, and one values/behavioral.
Yes. Free Meta placement papers PDF and previous-year practice (2024-2026) with solutions are on this site - including the 2026 PDF and year pages. No registration for core downloads.
Usually 60-90 minutes, 3-4 coding problems, focus on arrays/strings/trees/graphs, DP uncommon, and a high bar on test cases. After OA, expect live coding without running code.
No single official India-wide CGPA PDF. Student reports and many campus JDs cite 7.0+ / 70% across 10th, 12th, and graduation as a baseline. Degrees: B.Tech/B.E./M.Tech/MCA in CS/IT/ECE-related fields. Final year or ~1 year recent grad. No active backlogs. ~1 year max gap commonly reported. Coding performance outweighs a perfect transcript. Same substance as 2025 - verify your notice.
Candidate-reported (August 2026): E3 ≈ ₹50-65 LPA total (base often ₹38-48 LPA). E4 bands often cited around ₹80-100 LPA total. Figures include base/bonus/RSU assumptions people share publicly - always trust your letter.
E3 is the common new-grad SWE level. E4 expects stronger ownership and deeper system/product design. Compensation jumps accordingly. Interview design difficulty scales with level - do not prep E3 like a Staff interview, but do not skip design entirely either.
Rough split: 50% DSA, 20% design, 20% values STAR, 10% comms/CS review. Practice Meta-tag problems under timers and CoderPad constraints. Use preparation guide for week plans.
Python, C++, and Java are the usual choices. Pick one and stay consistent from OA through onsite. Speed and clarity beat language prestige.
Shared editor without autocomplete and without code execution in many technical rounds. You clarify, code, and manually prove correctness. Practice tracing on paper or a plain text buffer until it feels normal.
Prepare STAR stories for Move Fast, Focus on Impact, Be Bold, and Build Awesome Things, plus teamwork/conflict. Expect follow-ups. Values questions appear even in technical rounds - prepare aloud, not only in a notes app.
Meta’s competitive programming contest. Strong performance can help recruiting visibility. It is optional signal - you still need OA/interview prep afterward. Do not confuse contest rating with loop readiness.
Most Meta OAs avoid DP. Interviews may still touch DP-adjacent thinking occasionally, but do not center OA prep on classic DP drills at the expense of arrays/graphs/hash maps.
Rough fresher framing (candidate-reported): Meta E3 ≈ ₹50-65 LPA, product/values heavy, social/AI/VR context. Google fierce algorithms + design, strong brand. Microsoft competitive packages with many teams known for comparatively steadier WLB. Pick on team, offer math, and work you want - not Twitter rankings.
Many fresher offers assume an India hub / hybrid policy by team. In recruiter and HR chats, state location prefs honestly. Extremely narrow “remote-only” constraints can slow or block team matching even after a strong loop.
Drill Meta-tag problems under a 45-minute two-problem clock, then re-trace without running code. Add one spoken STAR story per week. Speed plus clear impact language beats random Hard-problem collecting.
After a hire signal, you may speak with teams about projects, stack, and location. Preferences that are extremely narrow can stretch timelines. Rank a few acceptable options and ask concrete questions about mentorship and on-call.
Candidate reports expect no active backlogs. A gap of about one year is commonly discussed if explained cleanly. Longer gaps need a coherent story and still do not replace OA/interview performance.
An April 2024 remote E4/L4 candidate recounted a LinkedIn recruiter chat, then a multi-round online onsite spanning coding, system design, and behavioral questions, finishing with: “I received a call 8 days later and they are proceeding with an offer for E4/L4” (GeeksforGeeks). Even for experienced hires, Meta’s process still hinges on timed coding clarity plus structured design storytelling.
What juniors should copy: once a recruiter thread opens, keep a working CoderPad-ready environment (language muscle memory, quiet room, stable network). Experienced loops still look like fresher loops with harder design - do not skip narration practice because “I have YOE.”
A verified Meta L3 SWE report from 2026 on Exponent described a roughly one-month process: because they had reached finals before, Meta skipped the OA and opened with a recruiter call plus phone screen, then a final loop of three technical interviews and one behavioral. They stressed that “you cannot run your code, so you have to manually trace it and prove it works,” and noted recruiters warn that team matching can still stretch if office/team preferences are narrow.
Practical takeaway: dry-run discipline is non-negotiable. Students who only ever trust the Run button discover the hard way that Meta phones are a different sport. Also build calendar slack for matching - a “yes” is not always an immediate team assignment.
Write-ups collected on this site and peer groups often follow: clear OA with all tests → recruiter schedules phone screen → two-problem CoderPad → virtual onsite with coding + design + values → HR → possible team match. Patterns repeat more than exact questions. Keep a personal log of which Meta value each mock interviewer stressed - you will spot weak stories quickly.
Common failure modes candidates admit later: finishing code that fails a obvious edge case they never traced; design diagrams with no API contracts; values answers that stay abstract (“I always move fast”) without a metric; arguing with the interviewer instead of collaborating on a hint.
What to steal: practice proving code without Run; budget calendar time for matching; read fuller notes on Meta interview experiences; and treat every public write-up as a vibe check, not a fixed question paper. Return to timed mocks on this site for the actual reps.
Also keep exploring the linked practice pages when you need drills - this hub is the map, not the entire gym. Juniors who only reread hubs without timed coding rarely clear phones.
