
Candidates describe a fast Impact Analytics Data Scientist process, about two weeks in two accounts. Reports mix SQL, Python, statistics, a business case such as clustering or forecasting, and managerial and HR conversations.
$135K
Avg. Base Comp
$160K
Avg. Total Comp
3-5 rounds
Typical Rounds
2 weeks
Process Length
Three candidates who interviewed for Data Scientist roles at Impact Analytics describe a fast process, and two of them put it at about two weeks. Their accounts differ in structure, so treat the stages below as a range, not a fixed sequence. One reports five stages, while the others describe about three.
SQL and Python come up in every account. Candidates mention medium-difficulty queries, SQL questions tied to retail use cases and pandas data manipulation. Logic puzzles and probability questions appeared in at least two accounts, including a phone screen, so do not prep only on coding.
The applied case is the other recurring theme. One candidate was asked to build a clustering solution for a clothing brand and justify feature selection and algorithm choice. Another faced a forecasting case study and SQL questions tied to retail scenarios. A third reports a small business case in a managerial round. Statistics topics reported include normal distribution, probability and linear regression.
Later rounds look more conversational. Candidates describe walking through past projects, discussing team leadership and explaining why they wanted to join. One candidate's final round was in person at the Bangalore office. Outcomes varied: one was rejected without feedback, one declined an offer and one accepted. Prepare one project you can explain end to end, with the reasoning behind your modeling choices.
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 Impact Analytics process.
I got the call from the recruiter and was told the whole process would move fast—they weren't kidding. From that first call to final decision was roughly two weeks. The first round was a phone screening covering the basics: they asked me about a couple of projects I'd worked on, threw a SQL question or two at me, had me solve a simple Python problem, and finished with a logic puzzle. Nothing too deep, but enough to gauge if I knew what I was doing. The second round was the interesting part—they gave me a clustering assignment to work through. The task was to implement a clustering solution for a clothing brand, which meant thinking about feature selection, picking an algorithm, and justifying my choices. It felt like a real business problem rather than a coding drill, so I tried to structure my thinking accordingly. The third round was with a lead from their team. We talked through my past projects in detail, and he asked about my experience leading teams and what drew me to Impact Analytics specifically. The conversation went smoothly—I felt like I connected well and could speak intelligently about my work. Then came the rejection email. They said they were moving forward with another applicant. No feedback, no explanation, and when I tried following up with the recruiter, they ghosted. Radio silence after that.
Prep tip from this candidate
Be ready for a real-world clustering case study in the second round—they'll expect you to think beyond just coding the algorithm and justify your choices on feature engineering and model selection. Also, refresh window functions and SQL fundamentals before round one; those showed up consistently across the process.
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 Impact Analytics
Given a list of integers, and an integer N, write a function to find all combinations that sum to the value N.
| Question | |
|---|---|
| Size of Joins | |
| Valid Anagram | |
| Assumptions of Linear Regression | |
| Scalable Data Pipelines | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| First to Six | |
| Subscription Overlap | |
| Experiment Validity | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| First Touch Attribution | |
| 500 Cards | |
| Download Facts | |
| Monthly Customer Report | |
| Upsell Transactions | |
| Raining in Seattle | |
| Random SQL Sample | |
| Lazy Raters | |
| String Shift | |
| Compute Deviation | |
| Button AB Test | |
| Bagging vs Boosting | |
| Job Recommendation | |
| Employee Salaries (ETL Error) |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report either a phone screen or an online assessment first. The phone screen covered past projects, a SQL question or two, a simple Python problem and a logic puzzle. The online assessment covered aptitude, SQL and Python. Expect fundamentals more than deep theory at this stage.
One candidate describes two technical interviews with medium-difficulty SQL and pandas problems plus probability and logic puzzles. Another reports retail-flavored SQL questions and questions on linear regression and normal distribution. Review medium-level SQL queries and pandas data manipulation before this stage.
Candidates report business-style cases. One had a clustering assignment for a clothing brand, requiring feature selection, algorithm choice and justification. Another had a forecasting case study. Interviewers appear to care about how you reason through a realistic problem, not only whether the code runs.
Candidates describe a resume-focused round with a manager or team lead. Topics included past projects in detail, experience leading teams, why Impact Analytics, and in one account a small business case. Have a specific project ready, with your decisions and results.
Some candidates report a final HR round, and one combined HR with a final technical round covering ML concepts and more SQL. One candidate says the last round required an in-person visit to the Bangalore office, so confirm logistics with your recruiter early.