Academic snapshot
Marks: 6.5+ CGPA / 65% (candidate-reported)
Degree: B.Tech / B.E. / M.Tech / MCA (tech); MBA/grad for BD
Backlogs: None active preferred
Year: Final-year and recent grads
BYJU'S Placement Papers 2026
BYJU’S is a major Indian ed-tech company offering digital learning programs for school and competitive exam preparation. Its technology teams have historically hired for product engineering, content platforms, and learning experience roles supporting apps used by millions of students.
HQ: Bengaluru, India
Employees: Variable (restructuring era)
Revenue: Ed-tech (private)
Website: byjus.com ↗
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
BYJU’S eligibility & CGPA (2026)
Who this hub is for
- For: Students targeting Software Engineer / product-engineering roles that used to (and occasionally still) appear under the BYJU’S brand - content platforms, student progress, recommendations.
- Also in scope: Business Development / sales / associate roles. Different filter: communication and case/role-play, more flexible academics.
- Not a 2021 time machine: Peak-era campus volume is gone. This page keeps historical patterns so you can prep if a drive or posting is real - not so you assume one will show up at your TPO office.
- Experienced hires: Lateral loops may skip OA and go straight to product/manager chats. Use fresher sections as a base only.
Check the job exists before you grind
On-campus vs off-campus vs bd
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus (when it happens) | Batch OA window, PPT, college CGPA list | Coding/communication bar for that role |
| Careers portal / referral | Resume screen volume; posting may be silent on CGPA | You still need the skills the JD lists |
| Tech SWE | OA + DSA interview | Project story + ed-tech vocabulary |
| Business Development | Case / role-play instead of coding | Why ed-tech, communication, joining logistics |
If your CGPA sits near 6.5, spend energy on mocks (or a BD pitch), not on hunting a mythical lower cutoff blog post.
Degree, projects, and “is 6.5 enough?”
Is 6.5 CGPA enough? It matches the commonly reported floor for tech. Selection still hinges on OA correctness (or BD communication). A 6.6 with clean timed coding beats an 8.5 that cannot explain a progress-tracker schema. BD roles historically flexed more on marks and heavier on talk.
Branches: CS/IT/ECE dominate tech shortlists. MBA and non-engineering grads show up on BD/product-associate posts. Read the notice - do not apply a coding OA plan to a sales JD.
Gaps and backlogs: Active backlogs are the usual blocker at offer time. A gap is easier to explain with a skills story than silence. Do not invent “I always wanted to work in ed-tech” if you cannot name one product surface.
What helps the resume screen: One project you can defend (stack, hardest bug, metric), any internship with ownership language, and - for this company - a sentence on how software changes a learner’s week. Certificates are optional. See certifications after fundamentals.
Branch & skills
Preferred (tech): CS / IT / ECE and related
Languages: Java, Python, JavaScript
Focus: DSA, aptitude, ed-tech product solving
Differentiator: Content delivery, progress tracking, recommendations
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 6.5+ CGPA / ~65% across 10th, 12th, graduation | BD historically more flexible; verify every posting |
| Degree | B.Tech / B.E. / M.Tech / MCA (tech) | MBA / other grads on BD posts |
| Branch | CS, IT, ECE (tech) | Adjacent branches with strong DSA on some drives |
| Year | Final year + recent grads | Peak-era intern conversions are not a 2026 default |
| Backlogs | No active backlogs preferred | Clear them before paperwork |
| Coding languages | Java, Python, JavaScript | Stick to one for OA + interviews |
BYJU’S CGPA criteria
Minimum CGPA required (candidate-reported): 6.5+ CGPA / 65% is the commonly cited floor for technical roles. Treat it as a shortlisting filter when printed. Clearing CGPA only gets you into the funnel - OA or BD communication decides the rest.
BYJU’S does not publish one universal India cutoff. Your placement cell mailer or the live JD always wins.
BYJU’S placement papers - last few years
Download 2026 BYJU'S placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What BYJU’S previous year papers actually train
BYJU’S does not publish one permanent official paper set. “Previous year papers” on this site are pattern trainers for the first filter and early technical rounds - not leaked live assessments. Use them if you have a live invite; they still transfer to other ed-tech / product OAs.
| Round (typical) | What to practice |
|---|---|
| Online assessment | Timed accuracy on BYJU’S Online Assessment (~90 min): aptitude + 1-3 coding |
| Technical interview | Live coding narration + OOP/SQL + one project |
| Design / domain | Content delivery, recommendation, attendance/progress tracking |
| Managerial / HR | Why ed-tech?, learning outcomes, relocation, integrity |
| BD path | Case/role-play, communication, sales aptitude - not LeetCode |
Themes that keep repeating (2024-2026)
- 2024 cycles: Practice sets and campus-style notes still show 2-3 DSA problems in a ~90-minute window (level-order trees, hashing, two pointers). Aptitude appears on mixed invites. Students who only collected “BYJU’S PDFs” without a timer lost easy marks. Hiring volume was already thinner than peak years.
- 2025 loops: Write-ups that exist still emphasise DSA + project and personalized learning / content platform talk. SQL aggregations for completion reports show up as a warm-up. Do not treat 2025 as a return to 2021 mass hiring.
- 2026 prep expectation: Assume low volume. If you get an invite, keep easy-medium DSA (arrays, strings, hashing, BFS level-order) and one progress-tracker OOP design warm. Treat PDF packs as pattern catalogs. Own
GROUP BY+ a null-student edge case, not the exact “SQL for completion reports” story. If no invite appears by the time other product OAs start, do not wait - the same hashing/SQL week still pays off at Unacademy and similar bars.
How to use one paper set in a single sitting
- Timed: run a full ~90-minute mock (aptitude + coding) in the language you will use on test day.
- Untimed review: rewrite the cleaner solution; list three edge cases (empty class roster, one student, all incomplete).
- Map each coding miss to a theme (hash / two pointers / BFS / OOP) and pull two cousins from coding questions.
- Spend 15 minutes explaining student progress tracking or content delivery out loud like a teammate.
- Log one STAR story (ownership under a broken demo, conflict on a content deadline).
Related problems to practice
| Theme you saw in a set | What to drill next | Why BYJU’S asks it |
|---|---|---|
| Two Sum / anagram | Hash map variants | Matching, lookup, clean edges |
| Merge sorted lists | Two pointers | Combining ranked content / scores |
| Level-order tree | BFS queue | Hierarchical courses / modules |
| Kadane / max subarray | Running sum reset | Streaks, score windows |
| Progress-tracker OOP | Classes, ownership of state | Attendance, completion, retries |
| SQL completion reports | GROUP BY, HAVING, NULLs | “How many students finished module X?” |
2024 PDFs often drill “binary tree level order.” Own the BFS-by-level template - drain size, collect values, enqueue children - then drill a related problem (zigzag, right-side view). That transfers; memorising the tree in the PDF does not.
BYJU’S placement process, round by round
When hiring is active, BYJU’S historically hired through campus cells, the careers portal, and referrals. After resume screen, tech looks like a product-company filter: timed OA, then coding + ed-tech interviews, then managerial/HR. BD skips most of the coding.
Application methods
Campus recruitment
Through college placement cells - PPT, then OA and interviews - if the company is on your calendar this year.
Online applications
Apply on byjus.com careers for early-career / fresher roles; follow the invite mailer for platform and duration.
Referrals
Employee referrals improve visibility. You still need passing OA code (tech) or a clear BD pitch.
1. Resume / eligibility screen
Placement cell or recruiter checks degree, CGPA floor when printed (6.5+ / 65% commonly reported), backlogs, and year of passing. Projects help when volumes are high. This is a gate - the OA or BD interview is the filter.
2. Online Assessment - BYJU’S Online Assessment (~90 min)
Candidate reports commonly describe a ~90-minute assessment mixing aptitude with coding. Some 2024-style notes describe a coding-heavy block (2-3 problems). Treat the table as a working map.
| Section (typical) | Questions (reported range) | Time feel | Focus |
|---|---|---|---|
| Aptitude / reasoning | ~15-20 | ~30-45 min | Quant, logic, verbal |
| Technical MCQs | ~8-15 (when present) | ~20-30 min | CS / light product |
| Coding | 1-3 problems | ~25-45+ min | Arrays, strings, hashing, BFS |
Languages: Java, Python, JavaScript (C/C++ also appear). Platforms: HackerRank and similar - confirm in the invite.
Pass bar in practice: Fully passing solutions beat a clever half-answer. Aptitude, when present, punishes slow calculation.
Student tip: Skim all coding prompts in 3-4 minutes. Bank the solvable one. Invent two edge cases (empty roster, single student) before submit.
Example timing for a 90-minute OA
| Minute | Move |
|---|---|
| 0-5 | Skim full paper / all coding statements; mark easy wins |
| 5-35 | Aptitude / MCQ block if present - skip sticky puzzles |
| 35-70 | Coding: restate → brute → optimize → code → sample tests |
| 70-85 | Second coding prompt or harden edges on the first |
| 85-90 | Flagged aptitude items only - no new hard DSA rabbit hole |
Deeper OA notes: BYJU’S Online Assessment.
3. Technical / business interview (~45-60 min)
For SWE: 1-2 DSA problems plus a project warm-up. Patterns candidates report: Two Sum / anagram (hashing), merge sorted lists, level-order BFS, simple progress-tracker OOP design, SQL aggregations for completion reports.
You should:
- Clarify constraints (null rosters, duplicate students, time windows)
- Narrate brute force → bottleneck → target complexity
- Code without syntax stalls
- Walk edge cases and complexity
Example narration (progress tracker): “I’d model Student, Module, and Attempt. Completion is a derived flag from last successful attempt, not a boolean you set by hand.” For ‘how many finished module X?’ I’d aggregate attempts with a unique student count and treat NULLs as not started.” That is fresher depth - enough.
4. Managerial round
Why ed-tech (not “famous brand”), how tech improves learning outcomes, working with content/ops ambiguity. They may walk a tiny product prompt: “A student drops off after video 3 - what do you measure?” Answer with a metric and a simple experiment, not a 12-service diagram.
5. HR (~20-30 min)
Relocation to Bengaluru / Mumbai / Delhi NCR, joining vs exams, strengths with proof. Know the ₹4-8 LPA historical band so you are not shocked - and ask what this year’s letter actually says.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | OA (aptitude + coding) | ~90 min | Timed accuracy |
| 2 | Technical / Business | 45-60 min | Code or case + projects |
| 3 | Managerial | ~30-45 min | Product / ed-tech fit |
| 4 | HR | 20-30 min | Location, logistics, CTC |
Some fresher write-ups merge managerial into HR and report three stages. Count the mailer.
Bd / sales-oriented loop
Historically: aptitude or business-case screen → business interview (role-play, objection handling, “sell this course”) → HR. Coding is usually absent. Prep a 60-second pitch, one story about persuasion with integrity, and a honest take on the ed-tech market in 2026 - interviewers can smell 2021 growth slogans.
Role-play shape students report: interviewer plays a parent who already paid for two unused apps. Your job is not a louder pitch. Ask what failed last time, name one metric you would check (login streak, first-week video completion), and offer a 7-day plan instead of a discount speech. That is closer to how later managerial rounds talk about learning outcomes.
What BD still shares with tech: Why ed-tech?, relocation, joining vs exams, and a resume story you can defend. What it does not share: LeetCode mediums. If the mailer never mentions coding, do not spend the week on binary trees.
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | Many campuses have no 2026 slot |
| OA → shortlist | Few days common when active | |
| Interview loop | ~1-2 weeks | Tech → managerial → HR |
| Offer / paperwork | Days after final round | Written offer wins |
| End to end | ~2-4 weeks when campus batches ran | Off-campus can stretch or stall |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Aptitude / logic | Speed + accuracy | Timed mock quiz |
| Coding Q1-Q2 | Hashing, two pointers, BFS, OOP | Two timed easy-mediums |
| Domain follow-ups | Progress, content, recommendations | Explain one flow in 3 minutes |
| HR / managerial | Why ed-tech in 2026 | Two STAR stories + honest industry take |
| BD path | Case + pitch | One role-play with a friend |
What’s on the BYJU’S test & where to practice
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
Where your BYJU’S prep time should go
If a BYJU’S invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for BYJU’S sits around ₹4-8 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): BYJU’S eligibility for freshers 2026 is candidate-reported. Common baseline: 6.5+ CGPA / 65% in 10th, 12th, and graduation; B.Tech/B.E./M.Tech/MCA in CS, IT, or related fields for tech roles; MBA/graduate degrees for Business Development and product roles; no active backlogs at application. Always verify the specific posting - hiring volumes have been uneven since 2023.
What you are training for: When a tech drive is active, candidate-reported loops commonly run: Online Assessment (~90 min, aptitude + 1-3 coding) → Technical/Business interview (DSA + projects, ~45-60 min) → Managerial round → HR. Business Development roles often skip coding for case-study or role-play rounds. Campus batches historically finished in about 2-4 weeks.
Short version of the prep split: First confirm an active opening. Then split time roughly: 50% DSA/aptitude (arrays, strings, hashing), 20% ed-tech product (content delivery, progress tracking, recommendations), 15% CS + projects, 15% behavioral. For BD roles, swap most DSA time into communication, case practice, and sales aptitude. Languages: Java, Python, JavaScript.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the BYJU’S previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most BYJU’S drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at BYJU’S usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why BYJU’S?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a BYJU’S-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the BYJU’S story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 BYJU’S PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed BYJU’S papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many BYJU’S papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in BYJU’S-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed BYJU’S paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why BYJU’S. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
BYJU’S compensation & benefits
Figures below are historical candidate-reported India bands. Restructuring means current letters can look different. Treat this as context, not a promise.
Bands students ask about
| Band | Typical CTC (historical, candidate-reported) | Notes |
|---|---|---|
| Software Engineer / Analyst (fresher) | ₹4-8 LPA | Peak/mid-era reports; verify 2026 letter |
| Business Development (fresher) | Often similar band, more variable | Incentive language matters - read the offer |
| Mid-level / specialist | Wide spread | Outside default fresher campus scope |
Confirm base, variable, and any incentive or clawback language on the written offer. Do not treat blog midpoints as guarantees.
Benefits students actually care about
Policies varied by year and BU. Candidates commonly cared about:
- Health insurance
- Learning / content access (role-dependent)
- Hybrid or office norms in Bengaluru / Mumbai / Delhi NCR
- Relocation - ask, do not assume
How to talk CTC in HR without sounding lost
Know the ₹4-8 LPA historical context, then ask how this package splits (fixed vs variable). Clarify joining date vs exams. One calm question beats arguing 2021 Glassdoor screenshots.
What’s changed in BYJU’S hiring lately
- Volume is the story. Post-2023 restructuring cut campus density. 2026 is not 2021.
- When a tech loop exists, DSA after resume screen is still the filter; aptitude still appears on mixed OAs.
- Domain awareness for content delivery and progress tracking shows up in managerial chats.
- JavaScript remains more welcome than at many banks - still pick one language and stay.
- BD vs tech split is still the first fork: do not mix prep.
- Treat ₹4-8 LPA as a historical reported band, not a 2026 guarantee.
- BD vs tech remains the first fork on any live JD - coding OA prep is wasted on a sales posting, and a pitch deck is wasted on a DSA loop.
- Historical campus PDFs still train OA patterns; they are not a 2026 hiring forecast. Always re-check careers the week you sit the test.
Common questions about BYJU’S hiring
Process & papers
Is BYJU’S actively hiring freshers in 2026?
Volumes have been significantly reduced and inconsistent since 2023. Check BYJU’S careers and LinkedIn for live openings before a long prep sprint. This hub keeps patterns for when a drive exists - it is not a promise your campus will see one.
What is the BYJU’S placement process for freshers?
When active, typical tech path: Online Assessment (~90 min) → Technical/Business interview → Managerial → HR. Campus batches historically finished in about 2-4 weeks. BD often skips coding for case/role-play. Confirm on your invite.
How many interview rounds does BYJU’S usually have?
Historically 2-4 depending on role. Some fresher tech write-ups report OA + technical + HR. Count the mailer.
Can I download BYJU’S placement papers PDF for free?
Yes. Free BYJU’S placement papers PDF and 2024-2026 style practice sets are on this site - pattern trainers with solutions, not leaked live papers. Start with the 2026 PDF or the paper archive.
What does the BYJU’S Online Assessment look like?
Candidate-reported OA is often ~90 minutes with aptitude and 1-3 coding problems. Some 2024 notes describe coding-heavy 2-3 problem sets. Languages: Java, Python, JavaScript. Verify your invite.
Eligibility & offer
What eligibility / CGPA do fresher drives usually expect?
Commonly reported floor: 6.5+ CGPA / 65%, CS/IT-related degrees for tech, final-year or recent grads, no active backlogs preferred. BD historically more flexible on marks. Your posting overrides this page.
What is BYJU’S fresher salary in India?
Historical candidate-reported CTC often landed around ₹4-8 LPA. Restructuring means 2026 letters may differ. The written offer is the only number that matters.
Do I have to relocate?
Bengaluru is HQ; Mumbai and Delhi NCR appear in older notes. HR usually checks relocation. Be honest early.
Prep & BYJU’S-specific
How should I prepare for BYJU’S?
Confirm a live role. Then split tech time roughly 50% DSA, 20% ed-tech product, 15% CS/projects, 15% behavioral. Clear timed OA mocks first. Details: preparation guide.
Which programming languages are allowed?
Java, Python, and JavaScript are the usual set (C/C++ also appear). Confirm on the invite. Do not switch the week of the drive.
Are tech and Business Development the same process?
No. Tech includes OA coding and DSA. BD historically uses case/role-play and communication, with more flexible academics. Prep to the JD.
What ed-tech topics should I revise?
Content delivery, student progress / attendance, recommendations, and SQL completion reports at fresher depth: APIs, data, bottlenecks, failure modes in plain language.
How is BYJU’S different from Unacademy for freshers?
Both are ed-tech product bars when they hire. BYJU’S 2026 story is lower volume and more uncertainty after restructuring; Unacademy (and other product companies) may be the more active calendar item. Prep DSA once; customise the “why this product” story.
What certifications help before joining?
For campus SWE, DSA + OA mocks + one strong project beat certificate stacks. See certifications.
Any pro tip that actually changes outcomes?
Confirm the job is open. Then bank solvable OA problems, keep an error log, and rehearse one progress-tracker explanation. For BD, a honest 2026 market take beats a 2021 growth speech.
Where can I read real interview experiences?
Start with BYJU’S interview experience on this site, then cross-check recent community write-ups. Patterns shift - use them as maps, not scripts.
What recent candidates reported
Fresher SWE loops (2024-2025)
Profile patterns that got selected: B.Tech CSE/IT/ECE, roughly 7.2-8.0 CGPA in write-ups (floor was 6.5), tier-2 mix, one internship or a strong project, steady DSA rather than last-week panic.
Online assessment: Timed coding on HackerRank or similar. Clean, fully passing solutions beat partial cleverness. Shortlist mail often arrived in a few days.
Technical rounds: Coding such as Two Sum / valid anagram (hashing), merge sorted lists, level-order BFS. Warm-up: simple progress-tracker OOP and SQL for completion reports. Domain chat around content platform and student progress - plain explanations worked better than buzzwords. Project deep dive: stack choice, hardest bug, what you would rebuild.
HR / managerial: Why ed-tech? How tech improves learning outcomes? Relocation? Keep answers short: situation → what you did → result.
Takeaway candidates repeated: clear DSA plus a coherent content-platform story beats a high CGPA with weak explanation. Talking through the approach before coding mattered as much as the final snippet.
What hurt other candidates: coding before clarifying constraints; treating HR as a formality; system-design jargon without a simple bottleneck; 2021-style “we will 10x learning” with no metric; freezing on a SQL GROUP BY.
How to read 2026 reports
Public fresher write-ups are thinner than for banks or FAANG. If you find a 2026 post, check date, role (tech vs BD), and whether an offer actually arrived. Older PDFs still train the OA; they do not prove your campus will see a drive.
A practical filter for old posts: if the story assumes weekly campus drives, a large Bengaluru campus hire class, or 2021-style CTC negotiations, treat it as pattern history, not a 2026 calendar. The useful bits still transfer: hashing + a progress-tracker OOP design + SQL completion counts. The volume promise does not.
If you are prepping “just in case”: keep the same DSA list and run Unacademy / other product OAs on the same calendar. One error log can serve both. Drop BYJU’S-only slogans until a live mailer exists. A 2026 “Why BYJU’S?” that ignores restructuring sounds unprepared - name what you still want to build (content, progress, recommendations) and that you checked a live posting.
More narratives: BYJU’S interview experience.