Unacademy startup-style loops: coding for SDE, strong communication for other tracks. Breadth helps; unfinished resume projects hurt.
What actually rejects people
Thin projects and no ownership examples.
First round: Unacademy coding / role interviews
Time split that matches how candidates report outcomes (not a marketing pie chart):
DSA 45%
Projects 25%
Culture 20%
Mocks 10%
Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.
Stage
Time
What they check
OA / screen
timed
Coding or aptitude
Interviews
multiple
Tech + culture
Data Structures & Algorithms (40% time) - Master arrays, hash maps, trees, graphs, and dynamic programming
System Design (30%) - Learn video streaming, CDN, content delivery, and learning platforms
Coding Practice (20%) - Solve 100+ medium-hard problems on LeetCode, HackerRank
Technical Concepts (10%) - Review databases, APIs, microservices
One timed block that matches Unacademy’s first round (coding + culture)
Log misses: topic + why you failed (speed, concept, carelessness)
Re-solve yesterday’s misses cold
Twice a week: 10 minutes of resume/project narration out loud
Week
Focus
Exit criteria
1-2
DSA fundamentals
Clean easy/medium solves
3-4
Projects + ownership stories
Resume bullets measurable
5-6
Mocks + culture
Explain trade-offs under pressure
7-8
Weak topics + HR
No unfinished ‘hero’ projects on resume
Order problems by confidence after a 3-4 minute skim
Passing test cases beats a brilliant half-solution
Invent edge cases before submit; watch timeboxes
Restate → brute force → optimize → code → test
Show ownership; unfinished resume projects get punished.
Tie CS answers to a project when it strengthens the point
Why Unacademy, why this team/role, location flexibility
STAR with a metric; pick 2-3 real company values and prepare proof
DSA for SDE
Product/edtech stories if relevant
Working code in one language
Projects you actually shipped
Ownership stories
Product sense lite
Breadth across stack claimed on resume
Full-length mock every other day
Light revision only - no new rabbit holes
Sleep, ID proofs, machine/network checklist for test day
30 days out: weekly full OA-style mocks; close weak DSA patterns; draft STAR stories.
7 days out: alternate mock / review days; re-solve misses cold; no new patterns.
Day before: skim notes, check machine/network/ID logistics, sleep.
Thin projects and no ownership examples - fix this first
Preparing only interviews while failing Unacademy’s first round
Collecting notes without timed mocks
Listing five frameworks on the resume and defending none
Changing language/stack one week before the drive
Listing half-built side projects as production
BYJU’S · Google · Amazon · Microsoft · TCS · Infosys
Next step: Run one timed mock this week that matches Unacademy’s first round (coding + culture), then build the weeks around your weakest section - not around what is most fun to study.