Candidates report an Impact Analytics Data Analyst process that typically opens with an aptitude-focused screen, often including SQL. Technical rounds then add Python or pandas, guesstimates and puzzles. Candidates who advance describe a managerial or HR conversation.
$79K
Avg. Base Comp
$95K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Four candidates describe the Impact Analytics Data Analyst interview. They broadly agree that an aptitude-heavy screen comes first, often with SQL, followed by technical conversations. One candidate was selected and three did not receive offers. All four describe the difficulty as basic to moderate, and three describe the interviewers as friendly or supportive.
Guesstimates and puzzles come up across the reports, with guesstimates mentioned by all four candidates, including a question about how many fans are in a college. Two candidates say the interviewers cared more about how you structure your thinking than about the final number. One candidate who did not get an offer said guesstimates may have been the differentiator and wished they had practiced a framework.
SQL is the other recurring theme. Reported topics include joins, nested queries, aggregates, LIMIT/OFFSET, UNION versus UNION ALL, the order of query execution, and a window function with COALESCE. One candidate was asked to explain how RANK, DENSE_RANK and ROW_NUMBER differ on ties. Excel also appeared in two reports.
Python questions look practical rather than algorithmic. Two candidates mention a pandas condition that labels an ID as major or minor based on an age threshold. One of them also describes merging dataframes, finding outliers and handling nulls. Expect to explain resume projects in detail, and prepare basic probability and permutation and combination questions as well. One candidate was asked about relocating to Bangalore in the managerial round, so be ready to discuss location.
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.
The interview process was smooth and well-organized across three distinct rounds. The first round was an aptitude and SQL exam, testing my ability to write queries and reason through logical problems. The second round was a technical interview where the panel asked SQL, Python, and scenario-based questions. The interviewers were genuinely supportive and explained what they were looking for before each question, which made the experience feel collaborative. They also included guesstimate questions, which I found hard to approach systematically—I wasn't entirely sure what framework they expected. The third round was techno-managerial, focusing on logical reasoning, scenario-based decisions, SQL, and Excel.
Everything felt fair and professional. The interviewers were encouraging, and the questions tested solid fundamentals rather than exotic edge cases. The difficulty stayed moderate throughout. Despite the positive experience overall, I didn't receive an offer. Looking back, the guesstimate questions in particular felt like a potential differentiator—they seemed less about math and more about how you structure your thinking, which I could have prepared for better.
Prep tip from this candidate
The first round is an aptitude and SQL exam, so nail the SQL fundamentals before anything else. The later rounds introduce techno-managerial themes, so prepare to discuss technical decisions with business context—it's not just coding, but reasoning about trade-offs.
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 | |
|---|---|
| Valid Anagram | |
| Assumptions of Linear Regression | |
| Scalable Data Pipelines | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| First to Six | |
| Experiment Validity | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| First Touch Attribution | |
| 500 Cards | |
| Download Facts | |
| Monthly Customer Report | |
| Raining in Seattle | |
| Random SQL Sample | |
| Lazy Raters | |
| Subscription Overlap | |
| Compute Deviation | |
| Button AB Test | |
| Bagging vs Boosting | |
| Employee Salaries (ETL Error) | |
| Last Transaction | |
| Minimum Change | |
| Top 3 Users | |
| Lowest Paid | |
| Impression Reach |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates report an opening online test or exam. One describes a 45-minute assessment with 20 questions, including one Python and one SQL coding question plus MCQs. Another describes about 30 multiple-choice questions mixing aptitude and technical topics. A third describes an aptitude and SQL exam. Format likely varies by candidate.
Candidates report one or two technical rounds. Topics include SQL joins, nested queries, aggregates and window functions, plus pandas operations such as merging, outliers, nulls and conditional logic. Basic probability, puzzles and guesstimates also appear. Candidates describe the difficulty as basic to moderate.
One candidate reports being asked to walk through resume projects in detail. Another describes a techno-managerial round focused on logical reasoning, scenario-based decisions, SQL and Excel. You may need to explain your reasoning clearly in plain language.
Some candidates report a final HR or managerial conversation. It covers motivation for the role and resume questions. One candidate was asked about relocating to Bangalore, and technical questions or puzzles may still appear. One candidate in the evidence did not reach this stage.
