Skip to content

BYJU'S Interview Experiences

How BYJU’S fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.

For fresher tech roles, BYJU’S usually runs Online Assessment (90 min), Technical Round (45-60 min), HR (20-30 min). Campus and off-campus patterns differ slightly, trust the drive college placement email over older PDFs.

Eligibility (from student reports): 6.5+ CGPA in 10th, 12th, and graduation.

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

Experience 1: software engineer loop (published write-up, pre-2023)

Section titled “Experience 1: software engineer loop (published write-up, pre-2023)”

The one reasonably detailed public engineering account describes a genuinely hard loop - the questions were product-company grade, not edtech-lite.

  • Coding round: a Base62 string encoding problem, and the classic minimum-number-of-jumps array problem.
  • Round 1 (with a VP of Engineering): a dynamic-programming question framed as trains and platforms - given ~1500 trains and ~2000 platforms, find the minimum number of changes to get from one location to another. Then: convert a binary tree to a binary search tree. The candidate offered the standard in-order-traversal-plus-sort approach; the interviewer pushed for an O(1) extra-space solution using a linked list and quicksort.
  • Round 2: low-level design - design a chess system.
  • Result: rejected after Round 2.

What this tells you: the bar in the engineering loop was LeetCode-medium-to-hard plus LLD, with interviewers pushing past the first correct answer for a better space complexity. Do not assume an edtech company means an easy DSA bar.

Experience 2: the BDA / sales track, which is what actually recruits at volume

Section titled “Experience 2: the BDA / sales track, which is what actually recruits at volume”

This is the role most BYJU’S campus and off-campus drives have advertised, and where nearly all recent public accounts sit. It is a sales role, and the process reflects that.

  • Group discussion is common at campus drives - groups of roughly 20 students, topic assigned on the spot (one reported example: “should India go cashless”). Speaking clearly and letting others finish matters more than winning the argument.
  • Telephonic / screening round: why this role, what you know about the company, and whether you are comfortable in a fast-paced target-driven environment.
  • A role-play or case task is widely reported - you are asked to sell the product to the interviewer, or walk through how you would handle a hesitant parent. Preparation means knowing the product and the objection, not knowing an algorithm.
  • Later rounds are a panel and then a senior/executive conversation on career goals and fit.
  • Multiple accounts note that academic percentage weighs less here than communication and persuasion. That cuts both ways: it is an accessible role to clear, and an intense one to do.

Sources for this section

  1. Two Sum / valid anagram. Usually expects hashing
  2. Simple progress-tracker OOPs design. Usually expects class design
  3. SQL for completion reports. Usually expects aggregations
  4. Discussion on content platform and student progress, bottlenecks, failure modes, simple APIs
  5. Detailed project discussion, architecture, hardest bug, what you would change
  1. Why edtech?
  2. How tech can improve learning outcomes
  3. Culture fit
  4. Relocation
  • Clear the screening round first. Timed practice beats last-minute topic hopping.
  • For domain questions, explain content platform in plain language, inputs, outputs, what breaks at scale.
  • OOPs and SQL still open a lot of BYJU’S 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.

After technical rounds, BYJU’S 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.

Unacademy · Amazon · Flipkart · Google · Microsoft · TCS