Interview experience
EXL interview experiences covering Online Assessment, Technical Interview 1, Technical/Case Interview 2, Managerial round (some drives), +1 more. Round-wise notes, common questions, and what candidates report clears each stage.
EXL Interview Questions and Answers (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: Interview experience · HR interview questions · Overview · Placement papers · Preparation guide
Overview
EXL runs a single online assessment into a role-dependent split: engineering candidates get a DSA/CS-fundamentals loop, while analytics/BPM candidates (EXL’s larger core business) get SQL, Excel, statistics, and case-style guesstimates.
HR interview questions
EXL HR interview questions with sample answer frameworks - motivation, relocation, STAR stories, and culture-fit prompts.
EXL interview process at a glance
| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 45-60 min | ~40 MCQs on aptitude, reasoning, verbal ability (+ CS fundamentals or SQL/Python/stats depending on role) |
| Puzzle / guesstimate (some analytics drives) | 20-30 min | Market sizing, logic puzzles, structured estimation - not always a separate slot; may fold into Technical 2 |
| Technical Interview 1 | 20-30 min | Programming basics/DSA (engineering) or SQL/Excel/stats (analytics) |
| Technical/Case Interview 2 | 30-45 min | Project walkthrough or live demo, guesstimates, case studies |
| Managerial round (some drives) | 20-30 min | Team fit, business-line understanding, role alignment |
| HR Round | 15-20 min | Fit, motivation, why EXL/why analytics |
EXL online assessment: quick answers
These answers are compiled from public candidate reports, not from an official EXL notice, and drives differ. The instruction screen of your own test is the final word.
| Question | Answer |
|---|---|
| How many questions and how long? | About 40 MCQs in 45 minutes. A GfG campus report and HitBullseye’s pattern page both give the split as 20 quantitative aptitude, 10 verbal and 10 logical reasoning. Some drives add SQL, programming or statistics questions; one 2023 campus report had aptitude, SQL and C programming in the first round. |
| Does it have negative marking? | Not published, and candidate reports do not mention one. Check the instruction screen. |
| Is there a sectional cutoff? | On some drives, yes. Candidate reports describe a separate cutoff for each of the aptitude, logical reasoning and English sections, so a weak section can eliminate you on its own. |
| How much is the cutoff? | No overall score cutoff is published; shortlists are relative to the batch. Reported eligibility is usually 60% in 10th, 12th and graduation; one 2023 campus report cites 75% with no current arrears. |
| Which platform is it on? | Not published, and we found no recent report naming one. Your invite names the vendor. |
| Is there coding? | Usually not in the OA, though one 2023 campus drive included C programming and SQL questions. Engineering roles get basic DSA in the technical interview; analytics roles get SQL and Excel instead of coding. |
| Is there a puzzle or guesstimate round? | On many analytics drives, yes - either as its own slot or folded into the second technical round. One campus report says about 1 in 5 candidates cleared that round. |
EXL interview questions by role
Questions below are ones candidates report in GfG and other public campus write-ups for each EXL hiring route. They show the level and style, not a fixed list.
| Role | Reported questions and topics |
|---|---|
| Analytics (Business Analyst, Analytics Associate) | SQL joins and GROUP BY on a claims-style table, second-highest salary per department, VLOOKUP vs INDEX-MATCH, correlation and p-values, guesstimates such as two-wheelers in Bengaluru, and a project walk-through with the formulas you used. 2025 analyst reports describe a resume-led interview on SQL joins and basics plus puzzles and guesstimates; one Nov 2025 reporting-analyst candidate also got deep learning, DSA and advanced SQL questions. |
| Engineering (software, digital and platform teams) | Basic DSA: arrays, strings, sorting, searching, stacks and queues. Binary search complexity, OS, DBMS, networks and OOPs, plus core language fundamentals for the language on your resume. |
| Operations and BPM roles | Mostly HR and communication: strengths, why EXL, why analytics or operations, and whether you are comfortable with process work and shifts. |
Asked across every role: tell me about yourself, why EXL, why data analytics, and your compensation expectations and notice period. One campus candidate believed a very high CGPA counted against them on retention grounds; that is one person’s view, not an EXL policy.
Online Assessment
A single timed test (~40 MCQs, 45-60 minutes) covering quantitative aptitude, logical reasoning, and verbal ability for all applicants, with the technical component branching by role - CS fundamentals for engineering roles, SQL/Python/statistics for analytics roles. Some drives use sectional cutoffs (English, reasoning and quant each have their own cutoff); missing one section’s cutoff eliminates you even with a strong overall score.
Common questions
- Quantitative aptitude - percentages, ratios, time-speed-distance, probability, data interpretation
- Logical reasoning, syllogism, and data sufficiency
- SQL/Python MCQs or basic statistics questions (analytics-track applicants)
- Basic CS fundamentals MCQs - OS, DBMS, networks (engineering-track applicants)
Candidate reports on public forums describe steep attrition after this stage - practice timed sectional papers, not only untimed topic drills.
Technical Interview 1
Branches hard by track. Engineering candidates get language basics and simple DSA; analytics candidates get SQL, Excel, and statistics fundamentals.
Common questions
- Basic DSA - arrays, strings, sorting, searching (engineering track)
- Write a SQL query using joins and GROUP BY (analytics track)
- Explain a statistical concept you’ve used in a project - correlation, hypothesis testing, distributions (analytics track)
- Core language fundamentals in whichever language your resume lists
Technical/Case Interview 2
A project walkthrough or live demo, paired with guesstimates and case-style reasoning - most pronounced for analytics/BPM roles, where this round often decides the offer.
Common questions
- Walk us through a project you built, including a live demo if asked
- Estimate the number of X in a given city or market (guesstimate)
- A case-style question built around a past data project: what formulas or approach you used and why
- Explain a business-process or data-quality problem you solved and how you validated the fix
Round-by-round breakdowns are on the EXL interview experience page.
Managerial round (some drives)
Where run as a separate stage, this checks fit for the specific team and business line rather than testing new technical material - understanding of the role, past project experience, and expectation alignment.
Common questions
- What do you understand about the team/business line you’re being considered for?
- Walk me through a project outcome you’re proud of and your specific role in it
- Are your expectations on role scope and location aligned with what we’re offering?
HR Round
The closing 15-20 minute conversation on fit, motivation, and compensation. Interviewers explicitly probe for a genuine “why EXL, why analytics/BPM” answer rather than a generic one.
Common questions
- Tell me about yourself
- Why EXL, and why the analytics/BPM industry specifically?
- Compensation expectations and notice period
- Are you comfortable with the process/BPM nature of some roles versus pure product engineering?
Sample answer frameworks for each of these are on the EXL HR interview questions page.
EXL Analytics vs EXL engineering and operations roles
EXL hires freshers into very different jobs under one brand. Analytics roles - its larger core business in insurance, healthcare, banking and finance analytics - are judged on SQL, Excel, statistics and guesstimates. Engineering roles on EXL’s digital and platform teams are judged on basic DSA and CS fundamentals. Operations and BPM roles focus on communication and process fit, often with shift work.
The online assessment is shared, but the interviews split by role, so preparing for the wrong one is the most common mistake. This page covers the analytics and engineering campus routes. Check which role your invite names before you prepare.
Common technical interview questions and answers
Q: Write a SQL query using a join and GROUP BY to find total claim amount per policy type.
A typical answer is SELECT p.policy_type, COUNT(c.claim_id) AS claim_count, SUM(c.amount) AS total_amount FROM policies p LEFT JOIN claims c ON c.policy_id = p.policy_id GROUP BY p.policy_type ORDER BY total_amount DESC; LEFT JOIN matters here because policy types with zero claims still need a row - an INNER JOIN would silently drop them. Note that COUNT of a column ignores NULLs, so a policy type with no claims correctly shows zero, whereas COUNT(*) would wrongly count the NULL-padded row as one. Every non-aggregated column in the SELECT list must appear in GROUP BY, which PostgreSQL enforces strictly and MySQL enforces when ONLY_FULL_GROUP_BY is on.
Q: What is the difference between WHERE and HAVING?
WHERE filters individual rows before grouping happens, so it cannot reference an aggregate function. HAVING filters the groups that GROUP BY produced, so aggregates are allowed there. In a claims query you would use WHERE to keep only claims filed this year, and HAVING to keep only policy types whose total claim amount exceeds a threshold. Putting a plain row condition in HAVING still returns the right answer but does more work, because rows are grouped first and then thrown away; putting an aggregate in WHERE is simply invalid. The logical order of evaluation is FROM, WHERE, GROUP BY, HAVING, SELECT, ORDER BY, LIMIT - which also explains why a SELECT alias cannot be used in WHERE but can be used in ORDER BY.
Q: What does a correlation coefficient of 0.8 actually tell you?
Pearson’s r of 0.8 means a strong positive linear relationship: as one variable rises the other tends to rise, and about 64 percent of the variance in one is explained by the other, since r squared is 0.64. It says nothing about causation - a lurking third variable or reverse causation produces the same number. It also captures only linear structure: a perfect parabola can have r near zero, which is why you plot the data before trusting the coefficient. Pearson’s r is sensitive to outliers, so one extreme claim value can move it substantially; Spearman rank correlation is the robust alternative when the relationship is monotonic but not linear.
Q: What is a p-value, and what does a significance level of 0.05 mean?
A p-value is the probability of observing data at least as extreme as what you got, assuming the null hypothesis is true. If it falls below the chosen significance level - conventionally 0.05 - you reject the null and call the result statistically significant. It is not the probability that the null hypothesis is true, and it is not the probability that your finding is a fluke; that is the most common mistake candidates make. A 0.05 threshold means accepting a 5 percent chance of a Type I error, rejecting a null that was actually true, and testing many hypotheses at once inflates that risk unless you correct for it. Statistical significance is also not practical significance: a huge sample can make a commercially meaningless difference significant.
Q: What is the difference between VLOOKUP and INDEX-MATCH in Excel?
VLOOKUP searches for a value in the leftmost column of a range and returns a value from a column a fixed number of positions to the right, so it cannot look leftward and it breaks when someone inserts a column, because the column index is hard-coded. INDEX-MATCH splits the job: MATCH finds the row position of the lookup value in one column, and INDEX returns the value at that position from any other column, in either direction. Because both arguments are references to real columns rather than an offset number, INDEX-MATCH survives column insertion and is generally faster on large sheets, since it scans two columns rather than the whole table. Always pass 0 or FALSE as the final argument for an exact match; in newer Excel versions XLOOKUP replaces both.
How would you approach a guesstimate such as estimating the number of two-wheelers in Bengaluru?
Work top-down from population to households to vehicle ownership, stating each assumption out loud - the interviewer is checking structure, not precision. Start from a population base of roughly 13 million, convert to households using an average size of about 4, giving around 3.25 million households. Segment by income - say 20 percent low, 60 percent middle, 20 percent high - and assign two-wheeler ownership rates such as 0.3, 1.2 and 0.8 per household, since high-income households often substitute cars. That gives roughly 0.2 plus 2.3 plus 0.5, about 3 million, then add a commercial-fleet allowance for delivery riders. Sanity-check the answer against a known reference point and say which assumption your estimate is most sensitive to.
Q: What is the time complexity of binary search, and when can you not use it?
Binary search runs in O(log n) time and O(1) space iteratively, because each comparison halves the remaining search space - a million sorted elements need at most about 20 comparisons. It requires the data to be sorted and randomly accessible by index, so it works on an array but not on a linked list, where reaching the midpoint is already O(n). If the array is unsorted and you only need one lookup, sorting first at O(n log n) is worse than a single linear scan at O(n); sorting pays off only when many searches follow. Two classic bugs are computing the midpoint as (low + high) / 2, which can overflow - use low + (high - low) / 2 - and getting the loop-termination condition wrong so it never converges.
Q: What is the Central Limit Theorem and why does it matter in analytics work?
The Central Limit Theorem states that the sampling distribution of the sample mean approaches a normal distribution as sample size grows, regardless of the shape of the underlying population, provided that population has finite variance. Its standard deviation, the standard error, is the population standard deviation divided by the square root of n - so quadrupling the sample size only halves the error. This is why confidence intervals and t-tests work on skewed real-world data such as claim amounts or call-handling times, which are nowhere near normal themselves. A rule of thumb is that n of about 30 suffices for mildly skewed data, though heavily skewed distributions need considerably more.
Q: How do RANK(), DENSE_RANK(), and ROW_NUMBER() differ in SQL?
All three are window functions that order rows within a partition. ROW_NUMBER() assigns a unique sequence with no ties - use it when you need exactly one row per group (for example picking the latest row per customer). RANK() gives tied rows the same rank then skips the next rank (1, 2, 2, 4). DENSE_RANK() also ties but does not skip (1, 2, 2, 3). For “second highest salary per department,” ROW_NUMBER() or DENSE_RANK() in a CTE is the portable pattern; RANK() can return multiple “second” rows if salaries tie.
Q: Write SQL to find the second-highest salary per department.
One idiomatic pattern: WITH ranked AS (SELECT department, salary, DENSE_RANK() OVER (PARTITION BY department ORDER BY salary DESC) AS dr FROM employees) SELECT department, salary FROM ranked WHERE dr = 2; Alternatives include ROW_NUMBER() with dr = 2 or a correlated subquery with MAX and NOT IN - state which engine you assume and whether ties should return one row or all tied seconds.
Q: What happens in EXL’s puzzle or guesstimate round?
On some analytics campus drives, candidates report a dedicated stage between the written test and deep technical interviews: market-sizing (vehicles in a city, rollout coverage), classic logic puzzles (make 24 from four digits, chessboard square counts), and short observational prompts. Interviewers score structured assumptions and sanity checks, not decimal precision. If your drive mail lists only three rounds, guesstimates may still appear inside Technical Interview 2 instead of as a separate slot.
Q: What is normalization to 3NF, in plain language?
First normal form removes repeating groups - one row per fact, no “Course1, Course2” columns. Second normal form removes partial dependencies: every non-key column must depend on the whole primary key, not just part of it in a composite key. Third normal form removes transitive dependencies: if A determines B and B determines C, move B and C to their own table so non-keys depend only on the key. EXL analytics interviews often ask you to normalize a schema you propose for a mini project.
Frequently asked questions about EXL interviews
Does the EXL online assessment have negative marking?
Not published. Public EXL candidate reports and HitBullseye’s pattern page describe the 40-question, 45-minute test without mentioning a penalty, and EXL issues no official pattern, so read the instruction screen before guessing. Some drives do apply sectional cutoffs, which matter more than any penalty.
Is there a sectional cutoff in the EXL online test?
On some drives, yes. Candidate reports describe aptitude, logical reasoning and English sections that each have their own cutoff, so missing one section eliminates you even with a strong total. No overall score cutoff is published. Reported eligibility is usually 60% in 10th, 12th and graduation (HitBullseye lists B.Tech CSE, ECE or IT), though one 2023 campus report cites 75% with no current arrears.
What is the EXL interview process for freshers?
EXL typically runs 3-4 rounds: 1. Online Assessment (45-60 minutes) - around 40 MCQs on quantitative aptitude, logical reasoning, verbal ability, and sometimes CS fundamentals or SQL/Python/statistics depending on the role. 2. A first Technical Interview (20-30 minutes) - basics of your programming language plus simple DSA for engineering roles, or SQL/Excel/stats for analytics roles. 3. A second Technical/Case Interview (30-45 minutes) - project walkthrough or live demo, along with guesstimates, case studies, and quant-reasoning questions, especially for analytics/BPM roles. 4. HR Round (15-20 minutes) - fit, motivation, and culture questions. Some drives combine the two technical rounds into one.
What questions are asked in EXL interviews?
For engineering roles, expect basic DSA (arrays, strings, sorting, searching, stacks, queues) and CS fundamentals (OS, DBMS, computer networks, OOPs). For analyst/BPM-analytics roles, EXL leans heavily on SQL, Excel formulas, statistics, and past-project or guesstimate/case-study questions, plus a direct ‘why EXL, why analytics/BPM’ question that interviewers use to filter out candidates who seem unsure about the industry.
How many rounds are there in the EXL interview?
Most candidates go through 3-4 rounds: an online aptitude/technical assessment, one or two technical or case interviews, a managerial round for team/role fit, and a final HR round. Attrition is steep at the technical/case round - candidate reports describe large drop-offs between the written test and the interview stage.
How should I prepare for EXL interviews?
Practice basic-to-medium DSA and brush up OS/DBMS/networks fundamentals if you’re applying for a tech role. For analytics/BPM roles, get comfortable with SQL joins/aggregations, Excel formulas, and structured case/guesstimate thinking (market sizing, profitability-style questions), and prepare a clear, specific answer for ‘why EXL’ and ‘why analytics/BPM’ rather than a generic response - interviewers explicitly probe for genuine interest in the industry.
Is EXL’s process different for engineering roles versus analyst/BPM-analytics roles?
Yes. EXL hires for both software engineering roles (product/platform teams) and analytics/BPM roles (its larger, core business - insurance and healthcare analytics, business process management). Engineering roles run a more DSA/CS-fundamentals-heavy loop closer to a typical product company. Analyst/BPM roles lean on SQL, Excel, statistics, guesstimates, and case-style discussion of past data projects, with less emphasis on classic coding-interview DSA.
What does EXL’s managerial round check for?
The managerial round (where run as a separate stage) focuses on overall fit for the specific team, understanding of the business line you’re joining, past project experience, and role-expectation alignment - it’s less about testing new material and more about confirming you and the team are a match before the closing HR/compensation conversation.
What interviewers score
| Stage | Strong signal | Weak signal |
|---|---|---|
| Aptitude OA | Speed + accuracy on quant/logical under ~45-60 min | Untimed puzzle practice only |
| Technical / case | SQL (joins, HAVING vs WHERE, window ranks) + project story | Memorised second-highest salary with no filter-order reasoning |
| Guesstimate / case | Structured metric → hypotheses → data → caveat | Random number with no structure |
| HR | Why analytics ops + Noida/Gurugram/Bengaluru logistics | Generic “data is the new oil” |
EXL panels reward business-aware SQL more than LeetCode Hard. Explain why the filter order matters.
Red flags that kill EXL offers
- Cannot write a JOIN or explain GROUP BY/HAVING without Stack Overflow
- Freezing when asked “so what should the VP do?” after a chart
- Treating HR salary talk as the first question
- Claiming Power BI/Python depth you cannot demo on a blank screen
- No questions about training, client domain, or first project type
How to prepare for EXL interviews
- Loop map: Online Assessment; Technical Interview 1; Technical/Case Interview 2; Managerial round (some drives). Confirm timings from the drive mail.
- Technical depth: Drill the Q&A section until answers are spoken, not read. Know every resume project cold.
- Experiences: Study round-wise notes on the interview experience page - real prompts beat generic lists.
- HR: Three STAR stories + a specific “Why EXL?” on the HR page.
A practical EXL prep plan
Use this as a default four-week loop before a EXL drive. Adjust to your invite timeline.
- Week 1: 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: 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: 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: Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
10-day crash version: Days 1-4 timed DSA, days 5-7 resume projects + CS fundamentals, days 8-9 mock interviews out loud, day 10 HR STAR stories on the HR page.
Compensation notes
Candidate-reported fresher/early-career packages for EXL often cite ₹5-9 LPA campus band. Treat forum numbers as ranges, not guarantees - confirm the written offer letter for your team and location.
Sources
Interview process details and sample questions on this site are editorially organized from public candidate reports and hiring write-ups, with round structure, prep notes, and company-specific framing added by our team. For round-by-round stories, see the EXL interview experience page. For OA papers and coding drills, use EXL on placementpapers.app. OA quick answers and role-wise questions draw on a GfG EXL campus interview experience (test split and round-by-round shortlist numbers), HitBullseye’s EXL test pattern page, EXL Glassdoor interview snippets (2023-2025) seen via search, and the candidate reports already summarised on this page.