EXL campus loops split between software-engineering fundamentals and analytics problem-solving. This page synthesizes SE and Analytics tracks into round tables, outcome notes, and prep traps.
Round-wise process at a glance
Round
Typical format
What clears you
Written / OA
~40 MCQs in 45–60 min (quant, LR, verbal); CoCubes-style sectional cutoffs on some drives
Sectional accuracy; do not over-invest one section
~45 min / 60 Q mix: aptitude, reasoning, verbal, OS, DBMS, networking, OOP (pattern from recruitment notes)
Technical 1
Basic questions on preferred language (C++)
Stack and Queue fundamentals
Showcase knowledge calmly under short duration
Technical 2 (~1 hour)
Interest in projects → live demo on laptop
Quant/reasoning: matrices, vectors
Paper coding: arrays, strings, linked lists (interviewer helped while candidate thought aloud)
Family background; willingness to join testing vs development passion (honest + cooperative answer)
Full form of OTT (movie web-app project)
Final result: Selected (email ~1 week later)
Key takeaways: Paper coding + project demo matter; answer testing questions without dismissing the work.
Takeaways
What decided it: Calm Tech-1 fundamentals, then a live laptop project demo, paper coding with think-aloud, and a cooperative answer on testing vs development
Common fail: Refusing testing roles outright, or a project you cannot demo when asked to open the laptop
How to practise: Paper-code arrays/strings/LL once weekly; rehearse a 5-minute demo; prepare an honest testing-willingness answer
Why EXL; hobbies (sports deep-dive); room elaboration timed; more puzzles
Final result: Selected on successful Set 3 account
Key takeaways: Analytics EXL scores structured estimation and SQL as much as coding.
Takeaways
What decided it: Clearing CoCubes sectional cutoffs, then SQL/normalisation plus structured puzzles (make 24, chessboard squares) and a clear Why EXL
Common fail: Failing one sectional cutoff despite strong totals, or blanking when Neo4j/sports hobbies become deep grills
How to practise: Timed CoCubes sections; 1-3NF + joins on paper; speak assumptions on one market-size guesstimate; prune undefended resume lines
Puzzle and guesstimate round - Analytics campus (composite)
Puzzle / guesstimate interview
Candidate profile: Campus analytics/BPM track. Pattern from public placement write-ups (Tpoint Tech, GeeksforGeeks analytics sets) where a dedicated puzzle round sits between OA and deep technical.
After written shortlist
Candidate cleared ~40-question aptitude (20 quant, 10 LR, 10 verbal reported on one drive)
Next stage was not resume-based coding - it was open-ended estimation and puzzles
Questions reported
Estimate two-wheelers or cars in a major Indian city - interviewer wanted decomposition (population → households → ownership rate → commercial fleet)
Logic puzzle: form 24 using digits 8, 8, 3, 3 with standard operators
Triangle division puzzle; count squares on a chessboard (classic IndiaBix-style prompts reused in HR on some drives)
“Real-life rollout” planning with population arithmetic (vaccination or product rollout framing in GFG Set 2 accounts)
Outcome
Candidates who spoke assumptions before multiplying passed even with rough final numbers
Those who stayed silent and guessed a single integer were pressed until structure appeared - or rejected
Key takeaways: Treat puzzles as communication tests. Write assumptions on paper if virtual; say what you would sanity-check against real data.
Technical interview experience 3 - EXL Analytics Set 2 (on-campus)
Analytics technical depth
Candidate profile: B.Tech with Java + SQL on resume; Neo4j mentioned in one project. Source: GeeksforGeeks EXL Analytics Interview Experience | Set 2 (On-Campus).
Written (CoCubes pattern)
English 10 + Reasoning 10 + Aptitude 20 in 45 minutes with sectional cutoff
Emphasis on syllogism, data interpretation, probability in prep tips bundled with the experience
Technical prompts
Favourite language deep-dive - interviewer walked through a Java calculator the candidate had written
Database design: 1NF–3NF on a schema the candidate proposed; JOIN types; SQL with AND/OR precedence
Graph DB vs RDBMS because Neo4j appeared on the CV - when graph storage wins vs when relational reporting wins
SQL functions in practice: UCASE, LEN, AVG; case-insensitive search patterns
Puzzle: divide an equilateral triangle into smaller equal parts (visual reasoning)
HR overlap
Why EXL; hobbies with follow-up (sports rules tested in depth on one account)
Timed “describe this room” observational prompt
Key takeaways: Anything on your resume - Neo4j, sports, side projects - can become a 10-minute grill. Remove lines you cannot defend.
Technical interview experience 4 - EXL Service (off-campus 2020, composite)
Off-campus software engineer
Candidate profile: Off-campus applicant; GeeksforGeeks EXL Interview Experience (On-Campus 2020) and related SE reports combined for round shape.
Round 1 - Online / written
Aptitude-heavy filter; large applicant pool with steep drop after first stage (exact counts vary by drive - do not treat forum numbers as official)
Mix of quant, reasoning, verbal; some drives add OS, DBMS, networking, OOP MCQs for engineering
Technical
C++ fundamentals if listed as primary language
Stack vs queue behaviour; where each fits in a project
Paper coding on arrays, strings, linked lists - candidate reported interviewer coaching while they thought aloud
Project demo on laptop for a web-app style project (including acronym checks like OTT for a streaming-themed build)
HR
Standard motivation and location questions
Selected candidates received email roughly one week after final round in the SE GFG account
Key takeaways: Off-campus loops mirror campus SE shape: aptitude gate → fundamentals → demo. Paper coding practice matters as much as IDE speed.
Pattern (multiple GFG / campus posts): First round is the steepest filter - not because questions are PhD-level, but because sectional timing and accuracy under pressure eliminate most applicants before any interview.
Engineering add-ons: CS fundamentals MCQs; Analytics add-ons: basic stats/SQL/Python MCQs on some drives
What fails people
Spending too long on one section and missing sectional cutoff on another
Guessing randomly on quant instead of skipping and returning
Ignoring easy verbal questions while chasing hard puzzles
Prep that helped selected candidates
Two timed full papers per week with a log of topic and reason for each miss
Sectional drills: 20 quant in 25 minutes, then review formulas - not endless untimed problem sets
Key takeaways: Clearing OA only means you join a smaller interview pool; treat the written test as a scored sport with a clock, not a syllabus to finish.
HR interview experience
HR interview experience
Candidate profile: Selected SE / Analytics (composite of GFG analytics HR sections and campus HR reports)
Core HR prompts
Tell me about yourself (short - not a repeat of the entire technical project story)
Why EXL and why analytics/BPM as an industry - not interchangeable with “Why IT?”
Strengths and weaknesses with examples
Relocation to Noida, Gurugram, Bengaluru, or Hyderabad; shift flexibility for client go-lives
Salary expectations and notice period; other offers if any
Non-standard prompts
Timed observational tasks (“describe this room in two minutes”)
Light puzzles repeated from earlier rounds to test composure, not new difficulty
Hobbies with deep follow-up (rules of a sport, recent match) - reported on Analytics Set 3
Outcome signal
HR is usually the last gate before offer documentation
Inconsistent answers vs technical round (dates, project ownership, “Why EXL”) can stall approval even after strong tech
Key takeaways: Prepare a specific Why EXL answer on the HR page. Stay calm on odd timed prompts - structure beats perfection.
Sample answers for high-frequency questions
Technical
Q. Willing to work in testing? A. Affirm quality ownership; tie testing to product reliability; state long-term development interest without refusing testing work.
Q. Guesstimate cars in Bangalore? A. Population → households → car ownership rate → adjust for commercial; state assumptions aloud. Example: ~13M people ÷ ~4 per household ≈ 3.25M households; apply tiered car ownership (low/middle/high income) and add fleet vehicles; sanity-check against registered vehicle statistics and name the sensitive assumption (household size or ownership rate).
Q. Make 24 from 8, 8, 3, 3? A. Work systematically: try combining two eights (8+8, 8×8, 8−8…) then use 3 and 3 on the result. One valid line is 8/(3 - 8/3) which evaluates to 24. Interviewers care that you show operator trials on paper, not that you memorised a single trick.
Q. SQL join without WHERE? A. Yes via JOIN ... ON; CROSS JOIN produces a cartesian product - use only when intentional. WHERE filters rows; join condition belongs in ON for outer joins so you do not accidentally turn a LEFT JOIN into an inner join by filtering the right table in WHERE.
Q. Normalisation 1NF–3NF on a student-course table? A. Split repeating course columns into a separate Enrollments table with (student_id, course_id); ensure no partial dependency of non-keys on part of a composite key (2NF) and no transitive dependencies like student_id → dept → dept_location without moving dept_location to a Departments table (3NF).
Q. Graph DB vs RDBMS (Neo4j on resume)? A. Graph stores excel at relationship traversal (fraud rings, recommendations); relational stores excel at aggregated reporting and strict ACID reporting pipelines. Mention what you stored in Neo4j and what still landed in SQL for BI.
HR
Q. Why EXL? A. Analytics/operations + digital transformation for insurance, healthcare, and banking clients; map your SE or analytics strength to the exact role title in the drive mail. Add one sentence on learning client governance of data - not only building models.
Q. Why analytics instead of product engineering? A. Show you prefer structured client problems, SQL/Excel/stats daily work, and explaining metrics - without insulting software roles.
Common questions checklist
OA
Sectional cutoffs (CoCubes-style on some drives); ~40 MCQs in 45–60 min
These links are research inputs used to map EXL SE vs Analytics loops - not copied page mirrors. We reorganized them into process tables, outcome notes, and prep takeaways.
Confirm role name (Service SE vs Analytics) against the drive mail.
