
Indium Software Data Analyst interviews focus on SQL (joins, GROUP BY, window functions) in most reports, with individual reports adding Python, machine learning basics, estimation problems, and a group discussion or HR round.
$96K
Avg. Base Comp
$125K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Indium Software's Data Analyst interviews center on SQL in most reports. Three of the four candidates described questions on joins and GROUP BY aggregations, and two mentioned window functions; one was also asked about query execution order and the LAG function. One candidate was asked directly how confident they felt in SQL versus Python before the interviewer calibrated question difficulty accordingly, suggesting the bar can flex to match a candidate's stated strengths rather than follow one fixed script. Beyond core SQL, the process has included different adjacent topics depending on the candidate. One report described two technical rounds that touched on RAG pipelines, basic data structures, aptitude problems, and a maximum-salary-per-department query, followed by an HR interview. Another described a full-day process opening with a group discussion, followed by a machine learning fundamentals round and a tougher estimation question asking the candidate to size daily Uber ride volume in India with clearly stated assumptions. A separate candidate described a first technical round with SQL joins, basic Python, and aptitude questions that skipped window functions despite advance advice to prepare them. Their second round was shallow, focused on HAVING versus WHERE and basic joins, and paired with a product metrics case about a 50% metric drop, followed by weeks of silence from HR after the final interview. Because the available reports describe different combinations of rounds, applicants should prepare broadly for SQL fundamentals and stay flexible for either a collaborative, project-driven conversation or a more unpredictable process depending on the interviewer.
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 Indium Software 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 Indium Software
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Top Three Salaries | |
| Lowest Paid | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| First to Six | |
| Monthly Customer Report | |
| Experiment Validity | |
| Download Facts | |
| First Touch Attribution | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Compute Deviation | |
| Find the Missing Number | |
| Largest Salary by Department | |
| Button AB Test | |
| Employee Salaries (ETL Error) | |
| Size of Joins | |
| 500 Cards | |
| Paired Products | |
| Raining in Seattle | |
| Bagging vs Boosting | |
| Last Transaction | |
| Subscription Overlap | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
One candidate reports clearing an initial online assessment before being invited to technical interviews. Other candidates did not mention this step, so it may not be part of every hiring pipeline for this role at Indium Software, but applicants should be ready for a screening test early on.
In three of the four reports, a technical round focused on SQL fundamentals, mainly joins and GROUP BY aggregations, with window functions and query execution order appearing in some accounts, along with basic Python. One candidate noted the interviewer asked how confident they felt in SQL versus Python and adjusted question difficulty accordingly. Another candidate found the depth inconsistent, with window functions skipped entirely despite being told in advance to prepare them.
One candidate described starting a full-day interview with a group discussion. This was followed by a technical round covering machine learning fundamentals at a conceptual level and logical brainteasers such as 'how can you write 5 in 5 moves.' Other candidates did not mention this format, so it may not apply to every applicant.
The same candidate described a noticeably harder second round built around an estimation question: sizing how many Uber rides get booked in India in a day. The interviewer probed assumptions and factors like weather, seasonality, and economic conditions. Candidates facing this stage should be ready to think aloud and structure assumptions clearly rather than aim for a precise number.
One candidate described a final HR interview following two technical rounds, while another mentioned a product-sense question about a metric dropping 50% mixed into later technical conversation. Post-interview communication varied widely: one candidate received an offer, while another reported weeks of silence despite multiple follow-up emails to HR after the final interview.