Academic snapshot
Floor: Often 6.0 / 60%
Degrees: Engineering + listed graduates
Backlogs: None active
Year: Final year / recent grad
EXL Placement Papers 2026
EXL is an analytics-led operations and digital transformation company serving insurance, healthcare, and banking clients worldwide. Founded in 1999, it hires engineers across Noida, Bengaluru, Hyderabad, and Chennai to build data platforms, automation, and decision systems.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
EXL fresher eligibility for campus drives
EXL does not publish one universal CGPA cutoff for every India campus drive. Analytics, operations, and developer JDs differ. Treat numbers below as candidate-reported (as of August 2026).
Who this hub is for
- For: Students targeting analyst / BA / analytics operations roles where the first filter is aptitude and the interview is SQL + guesstimates + communication. Main India stories: Noida, Gurugram, Bengaluru, Hyderabad.
- Not the same track: Assuming EXL is “another Infosys coding paper.” Many campus tests are 40 aptitude MCQs, not 2 LeetCode mediums. Developer/.NET posts exist - read the JD.
- Experienced hires: SQL depth, domain (US healthcare/insurance), client communication, notice period. Use fresher sections as a base.
Degree, projects, and “is 6.0 enough?”
Yes - 6.0 / 60% meets the commonly reported floor. It is not a selection guarantee. A 6.3 who finishes 20 quant questions accurately and can join two tables beats an 8.4 who panics on probability.
Projects that help: any dashboard, SQL-heavy internship, Excel model with a decision, a small Python ETL. A “machine learning” title with no metric and no data-cleaning story is weak.
What a strong EXL resume line looks like
Weak: “Worked on machine learning and data analytics.”
Stronger: “Built a 4-table Excel/SQL model of 2,000 mock claims; flagged 12% duplicates; presented a one-page summary to a faculty mentor.”
You do not need a Fortune 500 internship. You need a grain (what one row was), a mess (what was dirty), and a decision (what changed). Interviewers in ops-analytics smell certificate stacks immediately.
If you are a core-branch student switching to analytics, write one paragraph on why process data interests you more than a shop-floor role. The GFG BA HR round asked exactly that. Silence or “better package” is a weak answer; “I like structured exceptions in messy tables” is a real one.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus | Batch OA, PPT, printed CGPA | Aptitude bar |
| Careers / off-campus | Role-specific tests (SQL, .NET, typing) | Communication still graded |
| Referral | Resume visibility | OA still happens |
Off-campus developer posts (e.g. Chennai backend) can look more like a coding + Azure loop. Do not prep only RS Aggarwal if the mailer says C#. Conversely, do not disappear into LeetCode Hard if the mailer is a 40-Q aptitude link. The same company runs both funnels; your invite is the syllabus.
Communication is a scored filter, not a personality contest. US healthcare and insurance stakeholders will hear you on calls. If you cannot explain a join result in plain English, practise that more than a fourth Python library. HR will notice filler words. Record one 90-second project pitch this week and listen to it once - most students never do, and it shows. If you hear five “basically”s, rewrite the pitch on paper and record again the next day. That loop is more useful than a seventh mock test you will not review. Same for guesstimates: one recorded attempt with a friend interrupting you beats five silent notebook estimates.
Documents and portal hygiene
- Keep marks consistent - BV catches typos.
- Screenshot invite: 45 vs 60 minutes changes strategy.
- If the drive is BA vs “Associate Application Development,” prep stacks differ.
- Be ready to discuss shifts for US processes.
- Clear active backlogs before joining.
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 6.0+ / ~60% | Some analytics drives run higher informally |
| Degree | B.E./B.Tech/M.Tech/MCA or graduates as listed | BA drives sometimes take non-CS |
| Branch | CS/IT/ECE + analytics-friendly streams | Developer posts may restrict CS |
| Year | Final year + recent grads | Drive-dependent |
| Backlogs | None active preferred | Clear before offer |
| Tools | SQL, Excel, Python | Match the JD |
| Shifts | Possible for US healthcare/insurance | Ask HR early |
Skills & focus
Primary: Timed aptitude
Secondary: SQL + guesstimates
First filter: EXL Online Test
Differentiator: Clear client-facing English
Selection feel by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| Below 6.0 | Often filtered on-campus | Off-campus only if JD allows |
| 6.0-6.5 | Meets many floors | Need quant accuracy + SQL talk |
| 6.5-8.0 | Common shortlisted band | OA still decides |
| 8.0+ | Comfortable academically | Communication still a filter |
EXL placement papers - last few years
Download 2026 EXL placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What EXL previous year papers actually train
EXL does not publish one permanent official paper. “Previous year papers” on this site are pattern trainers for aptitude, SQL, and interview themes - not leaked live tests.
| Round (typical) | What to practice |
|---|---|
| Online test | 40-Q speed: 20 quant, 10 LR, 10 verbal |
| Puzzle / guesstimate | Structured estimation, not a lucky number |
| Technical | SQL, projects, sometimes stats |
| HR | Why EXL, shifts, location, communication |
Themes that keep repeating (2024-2026)
- 2024 cycles: Campus write-ups (including a GFG BA experience) describe 40 questions / ~60 minutes, quant hardest, ~200+ students → ~80 after OA. Next: technical with guesstimates (metro riders in Lucknow) and a puzzle, then HR with stats/probability and team stories.
- 2025 loops: Analytics interviews keep asking SQL joins, case when, CTEs. Operations tracks stay aptitude + English. Developer off-campus posts add .NET / Azure / Python - do not mix those into a BA plan.
- 2026 prep expectation: Keep quant speed and 15 SQL queries warm. Add one insurance or healthcare process sentence for Why EXL. Treat PDFs as pattern catalogs.
How to use one paper set in a single sitting
- Timed: 40 questions in 45 minutes (stricter than 60 so test day feels easier).
- Untimed review: every quant miss → formula or DI misread?
- Write 5 SQL queries on a tiny claims/orders schema.
- One guesstimate out loud (8 minutes).
- Log one STAR story (messy data, tight deadline, stakeholder).
Related problems to practice
| Theme you saw | What to drill next | Why EXL asks it |
|---|---|---|
| Probability / SI-CI | 12-min timed sets | Quant section |
| DI tables | 2 sets / day | Time sink |
| Syllogisms / puzzles | LR 10-Q bursts | OA Section |
| SQL joins | 10 query variants | Technical |
| Case when / group by | Claims-style tables | Analytics |
| Guesstimate | 3 frameworks | BA round |
2025 PDFs often drill “20 quant in 45 minutes shared with verbal.” Triage: bank easy arithmetic, skip ego probability, return later.
Free practice packs. Full archive: previous year question papers.
EXL hiring rounds in 2026
EXL hires freshers through campus placement cells, exlservice.com careers, and referrals. After resume screen, campus analytics looks like: timed aptitude, then case/SQL/puzzles, then HR.
Application methods
Campus recruitment
PPT → online test → interviews on a batch timeline. One GFG BA drive finished interviews within ~15 days.
Online applications
Apply on EXL careers. Follow the invite - aptitude vs SQL vs coding.
Referrals
Better resume visibility. You still sit the assigned assessment.
1. Resume / eligibility screen
6.0+ / 60% when printed, backlogs, year of passing. Internships with Excel/SQL help. This is a gate - the 40-Q test is the filter.
2. Online Assessment - EXL online test (~45-60 min)
The most repeated campus pattern:
| Section | Questions (reported) | Time feel | Focus |
|---|---|---|---|
| Quantitative aptitude | ~20 | Most of the paper | Arithmetic, DI, probability |
| Logical reasoning | ~10 | Moderate | Puzzles, syllogisms, blood relations |
| Verbal ability | ~10 | Easier | RC, grammar, vocab |
| Total | ~40 | 45-60 min | Speed + accuracy |
Analytics drives may add SQL MCQs or a take-home flavour - confirm the mailer. Developer drives may replace this with coding.
Pass bar: Quant accuracy. Verbal is usually easier; do not let it steal minutes from DI.
Student tip (from campus notes): Attempt quant first. Leaving it for the end causes panic.
Example timing for a 45-minute test
| Minute | Move |
|---|---|
| 0-2 | Skim; mark easy quant |
| 2-28 | Quant 20 - skip 2 hardest |
| 28-38 | LR 10 |
| 38-45 | Verbal + flagged quant |
Deeper notes: EXL Online Assessment.
Quant first is not optional advice. The GFG BA candidate who sat with 200+ people said the same thing: verbal is easier, quant is where the clock dies. A practical rule: if a probability question needs more than 90 seconds, mark it and leave. DI tables are usually higher expected value than a cute clock-calendar trap.
What “cleared OA” looked like in that drive: about 80 of 200+ moved on. That is a 40% pass-through, not a participation certificate. Timed mocks that you score at 60% untimed will not survive this. You need a 45-minute score you can repeat twice in a week.
3. Technical / puzzle / guesstimate (~30-45 min)
Campus BA example (GFG): project chat, geopolitics (candidate-specific), guesstimate (Lucknow metro daily riders), then a puzzle. Analytics laterals: SQL joins, case when, optimisation, CTEs.
You should:
- Clarify guesstimate constraints (city, weekday vs IPL Sunday)
- Break into factors (population × trips × metro share)
- Compute on paper; sanity-check the order of magnitude
- For SQL: state the grain of the table before writing joins
Worked mini-guesstimate - metro riders in a tier-2 city:
- Population ~3.5 million.
- Working-age ~60%.
- Maybe 8-12% use metro on a weekday if the network is small.
- 2 trips/day.
- Land in a range, not a fake-precise 4,17,332.
4. HR (~15-25 min)
Why EXL (insurance claims, healthcare ops, banking processes - pick one), night shifts, Noida vs Bengaluru, strengths/weaknesses, a team conflict. One GFG HR also asked probability of three heads and a simple average - stay awake for light quant.
Know the ₹5-9 LPA band so you do not look shocked, and so you do not invent a 12 LPA demand with no market anchor.
Puzzle rounds, when they appear, are less about the “right” trick and more about whether you stay structured when you do not know. Say what you know, try a small case, and narrate. Freezing for four minutes is worse than a wrong path you can defend. The GFG BA candidate said they had no idea on the puzzle and still cleared by trying.
| # | Round | Duration | What they check |
|---|---|---|---|
| 1 | Online test | 45-60 min | Aptitude speed |
| 2 | Technical / case | 30-45 min | SQL, guesstimate, projects |
| 3 | HR | 15-25 min | Communication, shifts, fit |
Timeline from application to offer
| Phase | Typical duration | Notes |
|---|---|---|
| Apply / campus register | Drive-dependent | PPT then OA |
| OA → shortlist | Same day to a few days | Large drop after 40-Q |
| Interviews | ~1-2 weeks | Sometimes same week |
| Offer | Days after HR | Written letter wins |
| End to end | ~1-3 weeks campus | Off-campus 2-4 weeks |
OA pattern cheat-sheet
| Component | Focus | Prep move this week |
|---|---|---|
| Quant 20 | Speed | Daily 20-Q timed |
| LR + verbal | Accuracy | Mock quiz |
| SQL | Joins / group by | 10 queries on paper |
| Guesstimate | Structure | One 8-min drill |
| HR | Why EXL, shifts | Two STAR stories |
Practice map for EXL placements
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.
What to practise before a EXL drive
If a EXL 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 EXL sits around ₹5-9 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, SQL. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): EXL eligibility for freshers 2026 is candidate-reported: often 60% or 6.0+ CGPA; B.E./B.Tech/M.Tech/MCA or other graduates depending on the track (analytics vs operations); final-year students and recent graduates; no active backlogs preferred. Always verify the campus JD or exlservice.com careers post.
What you are training for: Campus analytics/BA loops commonly run: Online aptitude test (often ~40 questions in 45-60 minutes: quant, LR, verbal) → technical or puzzle/guesstimate round → HR. Some drives add a SQL/case interview. Backend/tech roles may include a coding or .NET/Azure assessment. Timeline is often 1-3 weeks for campus batches.
Short version of the prep split: Split time roughly: 40% aptitude speed (quant-heavy), 25% SQL + Excel, 20% guesstimates/puzzles/cases, 15% communication and Why EXL (insurance/healthcare/banking ops). Languages: SQL, Python, Excel. Coding-heavy DSA is secondary unless your JD is a developer role.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the EXL 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 EXL 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 EXL 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 EXL?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. 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 EXL-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 EXL story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 EXL 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 EXL 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 EXL papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in EXL-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 EXL 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 EXL. 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.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For EXL, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three EXL mistakes, you are collecting content, not preparing.
Extra drill block (1)
Sit one more mixed EXL set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
What EXL pays freshers (candidate-reported)
Figures are candidate-reported (as of August 2026). Role and city move the number.
| Band | Typical CTC (candidate-reported) | Notes |
|---|---|---|
| Campus analyst / BA / ops | ₹5-9 LPA | Primary band for this hub |
| Some backend associate estimates | ~₹4.5-7 LPA | City and role dependent |
| Lateral analyst | Higher, wide spread | Not campus default |
Confirm fixed vs variable, joining location, and shift allowance on the written offer.
Benefits students actually care about
- Health insurance
- Shift / transport support when nights exist
- Learning budget (manager-dependent)
- Hybrid vs office in NCR vs Bengaluru
- Relocation - ask, do not assume
How to talk CTC in HR
Know ₹5-9 LPA, ask fixed vs variable, and clarify joining vs exams. One calm question beats a demand with no anchor.
What’s changed in EXL hiring lately
- Aptitude 40-Q papers remain the campus workhorse.
- SQL is louder on analytics interviews than in 2016-style pure puzzle rounds.
- Developer off-campus (.NET/Azure/Python) is a different funnel - read the JD.
- US healthcare/insurance language shows up in HR; shifts are not a rumour.
- Treat ₹5-9 LPA as a reported campus band, not a promise.
- Multi-city India delivery (Noida, Gurugram, Bengaluru, Hyderabad, Chennai) means location flexibility is a real HR question.
Common questions about EXL hiring
Process & papers
What is the EXL placement process for freshers?
Typical campus analytics path: 40-Q aptitude test (45-60 min) → technical/guesstimate/SQL → HR. Some drives add a separate puzzle round. Developer JDs differ. Campus often finishes in 1-3 weeks.
How many interview rounds does EXL usually have?
Most freshers report 3-4 stages. Count the mailer.
Can I download EXL placement papers PDF for free?
Yes. 2024-2026 style practice is on this site. Start with the 2026 PDF or the archive.
What does the EXL online test look like?
Commonly ~40 questions in 45-60 minutes: 20 quant, 10 LR, 10 verbal. Quant is the usual bottleneck. Confirm your invite.
Eligibility & offer
What eligibility / CGPA do fresher drives usually expect?
Commonly 6.0+ CGPA / 60%, relevant degree, no active backlogs. EXL does not publish one universal cutoff.
What is EXL fresher salary in India?
Candidate-reported campus CTC often ₹5-9 LPA (as of August 2026). Some associate tech posts cite lower. Written offer wins.
Do I have to do night shifts or relocate?
Possibly. US-facing processes and multi-city hubs are real. HR will ask. Be honest.
Prep & EXL-specific
How should I prepare?
40% aptitude, 25% SQL/Excel, 20% guesstimates, 15% HR - unless the JD is developer. Details: preparation guide.
Which tools / languages are expected?
SQL, Excel, sometimes Python for analytics. C#/.NET or Java for some dev posts. Match the JD.
Does EXL ask SQL and guesstimates?
Often yes on BA/analytics tracks. Operations may stay aptitude + English. Prepare both if unsure.
EXL vs Genpact vs Mu Sigma?
EXL: analytics-led ops in insurance/healthcare/banking. Genpact: broader ops. Mu Sigma/Fractal: heavier analytics branding. Compare offer, shifts, and work type.
Any pro tip that actually changes outcomes?
Quant first on the 40-Q paper. Keep 15 SQL queries fluent. Practise guesstimates aloud. Why EXL needs a domain sentence.
Where can I read interview notes?
EXL interview experience and campus blogs (e.g. GFG BA write-up). Maps, not scripts.
Is EXL a coding company like TCS NQT?
Not on most BA/analytics campus papers. Those are aptitude-first (often 40 MCQs). Developer JDs can add coding or .NET. Read the invite. Preparing only NQT-style advanced coding for a quant paper is a common miss.
Will I work only in Noida?
No. Gurugram, Bengaluru, Hyderabad, and Chennai also appear. HR asks location flexibility. Pick a preference and a backup city you can actually join.
Real EXL interview notes from candidates
Campus business analyst
EXL visited in November. Round 1: 40 questions / 60 minutes - LR easy-moderate, verbal easy, quant moderate-hard. Suggestion from the candidate: attempt quant first. ~200+ sat; ~80 cleared. Round 2: technical - projects, a guesstimate (Lucknow metro riders), a puzzle. Round 3: HR - Why analytics vs core, probability of three heads, averages, stats (candidate could not solve all), team conflict, family, strengths. Takeaway: OA is a numbers game; interviews mix structured thinking and calm English.
Analytics laterals
AmbitionBox-style notes repeat SQL joins, case when, CTEs, query optimisation. If you cannot write a left join on a whiteboard, do not claim “advanced SQL” on the resume.
What hurt people: leaving quant for last; unstructured guesstimates; no domain sentence for insurance/healthcare; refusing shifts after applying; treating HR as a chat with zero STAR examples.
More notes: EXL interview experience.
Sample technical / case follow-ups you should rehearse
- Write a query: claims in the last 30 days by state, with a
CASEfor high/medium/low amount. - Inner join vs left join - when does a left join explode row counts?
- Guesstimate: daily UPI transactions at a Bengaluru metro station.
- A stakeholder wants a dashboard tomorrow; your data is dirty - what do you do first?
- Explain a pivot table as if the listener is a process manager, not a CS professor.
- Probability: three coins, all heads - HR has asked this.
Answer out loud. Silent SQL that only works in your laptop will not survive a whiteboard.
Offer-stage discipline
If you clear HR:
- Read shift, joining city, and variable pay
- US healthcare/insurance processes often mean unsocial hours - confirm before you celebrate
- Do not resign until the written letter lands
- Background verification expects consistent marks
Keep the email thread. Verbal “Noida, 6.5 LPA” is not an offer.
One more mock template (45 minutes)
| Minute | Action |
|---|---|
| 0-2 | Skim; mark easy quant |
| 2-28 | Quant 20 - skip two ego items |
| 28-38 | LR 10 |
| 38-45 | Verbal + flagged quant |
Then immediately: one 8-minute guesstimate on paper. That is the campus combo.
Domain sentence bank
- Insurance: claims cycle time, fraud flags, first-notice-of-loss - you want to sit close to that data.
- Healthcare: US payer ops, eligibility checks, denial reasons - you can explain a messy table.
- Banking: KYC refresh, credit-card disputes - you like structured exceptions, not generic “analytics.”
If you cannot finish one sentence without “synergies,” rewrite it.