Skip to content

Unacademy Interview Experience 2025–2026 — Real Candidate Stories

These write-ups reflect how Unacademy fresher interviews usually go — campus and off-campus. Patterns shift by year and role, so use this as a prep map, not a script.

Unacademy placement process includes: 1. Online Assessment (OA) - 90 minutes with 2-3 coding problems, 2. Technical Interview Round 1 - 45 minutes focusing on data structures and algorithms, 3. Technical Interview Round 2 - 45 minutes covering system design and technical deep dive, 4. Managerial Round - 45 minutes with behavioral and technical discussion, 5. HR Round - 30 minutes for general discussion. Total…

Most drives expect a clean academic record (often around 6.0–6.5+ CGPA with no active backlogs). Candidate-reported detail: Unacademy eligibility criteria for freshers 2026 include: Minimum Percentage of 70% or 7.0+ CGPA in 10th, 12th, and graduation. Degree required: B.Tech/B.E./M.Tech in Computer Science, IT, or related fields. Final year…

Fresher offers (candidate-reported) often land around eshers (2025-2026): Software Engineer: ₹12-18 LPA for new graduates, Senior Software Engineer: ₹20-30 LPA (2-. Treat numbers as directional — confirm on your offer letter.

RoundDurationWhat they test
Online Assessment90 minAptitude + coding
Technical Round45–60 minDSA basics + projects
HR20–30 minCulture, teaching/product mindset

Experience 1: SDE / Software Engineer (2025)

Section titled “Experience 1: SDE / Software Engineer (2025)”

Profile: B.Tech CSE, 7.8–8.4 CGPA, tier-2 college, 1 internship, decent DSA practice (150+ problems)

Online / written round

  • Focus stayed on problem-solving speed and clean code, not trick questions.
  • Cleared with full or near-full test cases; shortlist mail came in a few days.

Technical rounds

  • Coding: Two Sum / valid anagrams — approach used: hashing. Interviewer cared about complexity and edge cases.
  • Follow-up coding: Design a simple progress tracker (OOPs) — class design.
  • Domain discussion around live class infra and content delivery — they wanted practical trade-offs, not buzzwords.
  • Project deep dive: why you chose the stack, what broke in production/testing, what you would redo.

HR / managerial

  • Why edtech?
  • How would you use tech to improve learning?
  • Keep answers short and specific. Name the conflict, what you did, and the result.

Result: Selected What helped: Explaining approach before coding, admitting unknowns early, and linking project work to Unacademy’s domain (live class infra).

Experience 2: SDE / Software Engineer (2024–2025)

Section titled “Experience 2: SDE / Software Engineer (2024–2025)”

Profile: B.Tech IT / ECE, 7.2 CGPA, strong projects, average competitive programming

What differed

  • OA felt tougher on time; one medium-hard problem needed an optimised solution to clear the bar.
  • Second technical leaned more into user progress and system design basics (APIs, DB choice, failure modes).
  • Coding warm-up: SQL for course completion reports — aggregations.

Mistakes to avoid

  • Jumping into code without clarifying constraints
  • Treating HR as a formality — Unacademy still filters on communication and intent
  • Memorising system design jargon without a simple capacity / bottleneck story

Result: Selected after a managerial / HR round Takeaway: For Unacademy, consistent DSA plus a clear story on live class infra beats a perfect CGPA with weak explanation.

  1. Two Sum / valid anagrams — typically expects hashing
  2. Design a simple progress tracker (OOPs) — typically expects class design
  3. SQL for course completion reports — typically expects aggregations
  4. Discussion on live class infra and content delivery — capacity, failure modes, simple APIs
  5. Project deep dive — architecture, hardest bug, what you would change
  1. Why edtech?
  2. How would you use tech to improve learning?
  3. Work culture fit
  4. Relocation
  • Practise DSA under a timer. Clearing the OA matters more than polishing a perfect resume line.
  • For domain rounds, be ready to talk about live class infra in plain language — inputs, outputs, bottlenecks.
  • Revise OOPs and SQL; many Unacademy panels still open with fundamentals.
  • Keep HR answers concrete. One story with a clear result beats five buzzwords.
  • If you do not know something, say so and outline how you would find out. Guesswork wastes the round.

Last updated: August 2026