Impact Analytics Data Analyst interview typically runs 2-3 rounds: technical screen, technical interview, and HR/managerial discussion. It usually wraps in 2-4 days and is quick, smooth, and structured.
$85K
Avg. Base Comp
$85K
Avg. Total Comp
4-5
Typical Rounds
2-4 days
Process Length
We've seen Impact Analytics lean toward candidates who can stay calm across a broad but very practical mix of questions. The recurring pattern in our candidate experience is that the bar is not about obscure algorithms; it’s about whether you can move cleanly through standard SQL mechanics like joins, nested queries, aggregates, LIMIT/OFFSET, and even a window function with COALESCE without getting lost. The Python and MCQ portions also suggest they care about comfort with implementation details and basic code reasoning, not just theory.
A second theme is how much they seem to value structured thinking in ambiguous prompts. One candidate called out a guesstimate about the number of fans in a college, and the emphasis was clearly on the reasoning path rather than the final number. We also noticed basic math, probability, permutation/combination, and puzzle-style questions showing up alongside resume discussion, which tells us they’re looking for someone who can connect analytical thinking to business conversations. The most telling signal is that the later discussion still mixed in technical checks and relocation fit, so clarity, composure, and practical problem-solving appear to matter as much as raw technical recall.
Synthetized from 1 candidates 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.
The process was pretty quick and surprisingly smooth. I got scheduled only a few hours in advance, and the whole thing wrapped up in about 2 to 4 days across two main rounds, plus an HR/managerial discussion at the end. The first round was a technical screen that felt like a mix of coding and aptitude. I had a 45-minute online assessment first, with 20 questions total, including one Python coding question, one SQL coding question, and a bunch of MCQs around code implementation and time-consuming aptitude problems. After that, the live technical interview stayed at a fairly basic level but covered a lot of ground: SQL joins, nested queries, aggregate functions, LIMIT/OFFSET, and even a window function with COALESCE. They also asked basic math, probability, permutation and combination, and a logic/programming sequence question. One of the more memorable parts was a guesstimate like how many fans are in my college, which they seemed to care about more for the thought process than the exact number.
The second round was more of an HR/managerial conversation, but it still had technical questions mixed in. They asked about my resume and also checked whether I was comfortable relocating to Bangalore. The interviewers were friendly and helpful, and the vibe was structured rather than intimidating. I also got a couple of puzzles in the later round, but nothing advanced or overly algorithmic. Overall, it felt like they were looking for someone who could reason clearly through standard SQL, basic Python, and aptitude-style questions instead of someone who had memorized tricky solutions. I ended up getting selected, and my main takeaway is to be ready for straightforward SQL, basic stats/probability, and guesstimates, with a clear explanation of how you think through each problem.
Prep tip from this candidate
Drill SQL joins, nested queries, aggregate functions, LIMIT/OFFSET, and at least one window-function question with COALESCE. Also practice explaining guesstimates and basic probability/aptitude problems out loud, since the interview leaned heavily on reasoning rather than hard coding.
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
Create top_ads with the top 3 ads and return the row counts for inner, left, right, and cross joins with ads
| Question | |
|---|---|
| Assumptions of Linear Regression | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Experiment Validity | |
| First to Six | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| First Touch Attribution | |
| 500 Cards | |
| Monthly Customer Report | |
| Bagging vs Boosting | |
| Lazy Raters | |
| Button AB Test | |
| Raining in Seattle | |
| Compute Deviation | |
| Download Facts | |
| Last Transaction | |
| Impression Reach | |
| Top 3 Users | |
| Network Experiment Design | |
| Random SQL Sample | |
| Subscription Overlap | |
| Month Over Month | |
| Prime to N | |
| Paired Products | |
| Upsell Transactions |
Synthesized from candidate reports. Individual experiences may vary.
The process began very quickly, with the candidate being scheduled only a few hours in advance. There was no long waiting period between stages, and the overall experience moved fast from first contact into the assessment and interview rounds.
The first formal step was a 45-minute online assessment with 20 total questions. It included one Python coding question, one SQL coding question, and several multiple-choice questions covering code implementation and time-consuming aptitude-style problems.
After the assessment, the candidate had a live technical screen at a fairly basic level but covering a wide range of topics. Questions focused on SQL joins, nested queries, aggregate functions, LIMIT/OFFSET, a window function with COALESCE, plus basic math, probability, permutation and combination, logic, and a guesstimate.
The experience suggests a second main round where the interviewer continued with practical reasoning questions rather than advanced algorithms. This round included additional puzzles and continued to emphasize clear thinking, structured problem solving, and comfort with standard SQL and basic Python concepts.
The last stage was an HR/managerial conversation that still mixed in some technical discussion. The interviewer reviewed the candidate’s resume, asked about willingness to relocate to Bangalore, and used the conversation to assess communication, fit, and overall readiness for the role.