Meta hub
Meta Online Assessment
Overview
Meta online assessment (OA) is the first hard filter for many fresher and lateral engineering drives. This page covers format, sample Meta OA questions, an 8-week prep plan, and mistakes that sink strong candidates.
Patterns are from student reports for 2025-2026. Confirm your invite.
Meta hiring flow after the OA
| Stage | What candidates report | What you must show |
|---|---|---|
| 1. Online assessment | Timed coding OA with strict tests | Correctness + reasonable complexity |
| 2. Technical interviews | Multiple DSA interviews | Explain approach and edge cases |
| 3. Later rounds | Behavioral / team matching; HR logistics | Depth + communication |
| 4. HR / offer | Role, location, CTC | Consistency with resume |
Meta Online Assessment format
| Component | From student reports details |
|---|---|
| Platform | HackerRank / CodeSignal / Meta-hosted (confirm invite) |
| Duration | Often 60-90 minutes for coding OA variants |
| Question mix | 1-2 medium-hard coding problems |
| Languages | C++, Java, Python |
| Scoring | Automated tests; efficiency matters |
| Advance rate | Highly selective |
What makes Meta OA feel distinct
- Hard DSA bar similar to other top product companies
- Clean code and complexity analysis expected
- Follow-ups in interviews dig into optimization and edge cases
- Behavioral / Meta values appear after technical screens
Question types
Core
- Graphs, trees, heaps
- Arrays/strings/sliding window
- DP and recursion
- Design-lite coding occasionally
Secondary
- Clear problem narration practice for later loops
- Edge-case inventiveness
Usually not in OA
- Long aptitude batteries
- Designer take-homes for pure SWE OA
Sample Meta Online Assessment questions
Question 1: clone graph
Question 2: binary tree vertical order
Question 3: subarray sum equals k
Question 4: k closest points to origin
Question 5: decode string
Question 6: accounts merge
8-Week prep plan
| Weeks | Focus | Exit criteria |
|---|---|---|
| 1-2 | Arrays, hashing, two pointers | 40+ clean easy/medium |
| 3-4 | Trees/graphs/heaps as relevant | Implement BFS/DFS cold |
| 5-6 | Domain-flavored drills for Meta | Timed section comfort |
| 7 | Full mocks at OA duration | Finish required problems with tests |
| 8 | Weak-topic repair | Re-solve misses in 48 hours |
Daily loop
- One timed medium problem
- Write complexity + 3 edge cases before coding
- Log misses by pattern
- Weekly full mock
Common mistakes
- Brute force only with n too large
- Unreadable code you cannot explain
- No timed mocks at OA duration
- Ignoring behavioral prep until too late
- Overfitting to leaked questions
Day-of checklist
- Skim all problems for 3-4 minutes and order by familiarity
- Submit a correct simpler solution before over-optimizing if time is tight
- Invent edge cases the samples omit
- Do not leave a problem fully blank if a partial tested approach can score
- After the test, write down every problem from memory for interview prep
Interview transition plan (48 hours after OA)
- Re-solve your OA problems cleanly
- Prepare STAR stories (ownership, conflict, failure, impact)
- Revise OOPs, DBMS, OS one-pagers
- Rehearse a 2-minute project narration