Reported EXL Data Scientist interviews emphasize project discussion, technical fundamentals, applied case reasoning, and, in some three-round processes, a final people-focused conversation.
$126K
Avg. Base Comp
$140K
Avg. Total Comp
3 rounds
Typical Rounds
2-4 weeks
Process Length
EXL Data Scientist candidates most consistently describe interviews that test how well they can explain their own work and apply technical judgment. Project depth matters: reported discussions covered a candidate’s role, model selection, feature engineering, and evaluation metrics. Prepare a clear account of the problem, data, decisions, trade-offs, and results behind each project on your resume.
Technical questions in these reports included Python, SQL, statistics, machine learning, forecasting, and regression assumptions. One candidate was asked about ARIMA, stationarity, covariance, and linear-regression assumptions. Another reported Type I and Type II errors and t-test versus z-test. Coding examples included a basic Python question, a frequency-counting task, and reports of SQL or Python screening. Practice explaining concepts aloud, then translating that understanding into a simple, readable solution.
Applied reasoning also appears in the evidence. Candidates described business-oriented case work involving data cleaning, exploratory analysis, feature engineering, class imbalance, model selection, and metric choice. In a reported three-round process, the final conversation covered experience, career plans, compensation expectations, and notice period. Focus your preparation on project explanations, core technical foundations, and a structured approach to practical problems.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Exl process.
I interviewed with EXL for a Data Scientist role and experienced about three rounds. The first technical discussion covered my current project, including my role, model selection, feature engineering, and evaluation metrics. I was also asked questions on Python, SQL, statistics, and machine learning, including a small Python frequency-counting problem.
A later technical discussion focused on a practical business problem. We talked through data cleaning, exploratory analysis, feature engineering, class imbalance, model selection, and evaluation metrics. The final conversation covered my experience, projects, reason for switching, career plans, salary expectations, and notice period.
Overall, the process was more practical than theoretical. Be ready to explain the decisions behind your projects and to work through an applied data-science approach clearly.
Prep tip from this candidate
Prepare concise project walkthroughs and practice explaining Python, SQL, statistics, model choices, and evaluation metrics in the context of a business problem.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Exl
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Bagging vs Boosting | |
| Size of Joins | |
| P-value to a Layman | |
| Type-ahead Search | |
| Precision and Recall | |
| Three Zebras | |
| Hurdles In Data Projects | |
| Target Indices | |
| Fine-Tuning VS RAG | |
| Transformer Encoder Layer | |
| Assumptions of Linear Regression | |
| Duplicate Rows | |
| RAG Strict Source Control | |
| Type I and II Errors | |
| Swap Variables | |
| Data Preparation for Imbalanced Data | |
| Overfit Avoidance | |
| Multicollinearity in Regression | |
| SARIMA in Retail Forecasting | |
| Credit Card Fraud Model | |
| Explaining Linear Regression to Different Audiences | |
| Random Forest from Scratch | |
| Google Earth Storage | |
| Your Strengths and Weaknesses | |
| Correlation in Regression | |
| Branch Sales Pivot | |
| Linear vs Logistic Regression | |
| Designing a Fraud Detection System |
Synthesized from candidate reports. Individual experiences may vary.
Candidates reported technical conversations that began with introductions or project deep-dives. Topics included project role, model selection, feature engineering, evaluation metrics, forecasting concepts, regression assumptions, statistics, machine learning, Python, and SQL.
Reported exercises included a basic Python question and a Python frequency-counting task. Candidates also described practical case work that moved through data cleaning, exploratory analysis, feature engineering, imbalance handling, model selection, and evaluation metrics.
One candidate’s reported third round was conversational and covered experience, projects, reason for switching, career plans, salary expectations, and notice period. Prepare concise examples that connect your past work to the role.
