HR interview questions
Common Unacademy HR questions, sample answer frames, and STAR tips.
Unacademy Interview Experiences
How Unacademy fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat 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 detailed technical discussion, 4. Managerial Round - 45 minutes with behavioral and technical discussion, 5. HR Round - 30 minutes for general discussion. Total duration: 3-4 weeks from application to offer.
Eligibility (from student reports): 7.0+ CGPA in 10th, 12th, and graduation.
Fresher package ballpark (from student reports): ₹12-18 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90 min | Aptitude + coding |
| Technical Round | 45-60 min | DSA basics + projects |
| HR | 20-30 min | Culture fit, product mindset |
Real interview experiences
Section titled “Real interview experiences”These are rewritten from public candidate write-ups, not invented composites. Unacademy hires mostly off-campus and through referrals or platforms like Instahyre, so the accounts skew towards applicants with some experience rather than pure campus drives - there is no standardised OA-then-interview funnel the way there is at a mass recruiter.
Experience 1: Software Engineer, off-campus
Section titled “Experience 1: Software Engineer, off-campus”Source: Unacademy Interview Experience - GeeksforGeeks
- Phone screen: short, mostly about previous work.
- Round 1 - Coding: longest palindromic substring, then counting the occurrences of every element in a list.
- Round 2 - Project discussion (~45 min): entirely on the candidate’s own projects. The write-up describes the interviewer as genuinely interested and going deep - this round is as long as the coding ones, so a shallow project story is a real risk.
- Round 3 - DSA: graph questions, ending with number of islands via DFS.
- Round 4 - Behavioural / managerial.
- Outcome: Selected.
Experience 2: Software Engineer - Android, off-campus (2022)
Section titled “Experience 2: Software Engineer - Android, off-campus (2022)”Source: Unacademy Interview Experience for Software Engineer-Android (Off-Campus) 2022 - GeeksforGeeks
Applied via Instahyre, shortlisted on resume - no online assessment at all. Five rounds, each about 60 minutes.
- Round 1 - DSA + Android: an easy Android coding question, questions about the candidate’s career switch, Android fundamentals, and a palindrome check first for strings and then adapted for numbers.
- Round 2 - System design + Android: deep-dive on a previous internship project (a short-video sharing app), scaling a followers/following feature, and “how will you create a ViewModel which can globally handle the user response such as likes on different screens?”
- Round 3 - Problem solving + design: pros and cons of Jetpack Compose, debouncing, Coroutine use cases, then “implement a search recommendation system like Google search”, extended to handling misspelled keywords using longest common subsequence.
- Round 4 - Hiring manager: behavioural questions, plus product thinking - what features would you improve on Unacademy, and native vs hybrid frameworks.
- Round 5 - HR: culture fit and working in a fast-moving environment.
- Outcome: Selected.
Common thread: Unacademy loops are long and conversational rather than screen-heavy. Expect a full round dedicated to your own projects, at least one open-ended design question tied to a real product surface (search, feeds, live sessions), and product-opinion questions in the manager round - having a considered view on the app itself is treated as a signal, not small talk.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Two Sum / valid anagram. Usually expects hashing
- Simple progress-tracker OOPs design. Usually expects class design
- SQL for completion reports. Usually expects aggregations
- Discussion on live class infra and content delivery, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why edtech?
- How tech can improve learning outcomes
- Culture fit
- Relocation
Practical tips for Unacademy
Section titled “Practical tips for Unacademy”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain live class infra in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Unacademy panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, Unacademy usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.