Four candidates describe Indium Software's Software Engineer-track interviews: aptitude or coding screens, SQL and Python questions, project discussion, group discussion, and an HR round. Their experiences differ, so prepare for fundamentals.
$112K
Avg. Base Comp
$131K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
The four candidate reports for Indium Software differ in format, so prepare for a range of rounds. The most consistent theme is SQL and Python fundamentals rather than extreme algorithm difficulty. One candidate describes a first-round assessment with SQL and Python multiple-choice questions, two DSA coding problems and two SQL query questions. Another recalls basic Python tasks such as prime checks, arrays, strings, lists and tuples, plus SQL joins.
Several candidates also report conversational rounds. One was asked to walk through projects, especially AI or ML work. Another had a Python interview built around resume questions. Be ready to explain what you built, why you made your choices, and how you solved problems.
One candidate reports a design-oriented question about building a traffic signal execution system with Java OOP, so practice structuring classes and managing state. The same candidate describes a round on software design and SDLC, including how testing fits into a project.
The process is not uniform. Reports mention a group discussion on topics such as AI and social media, and HR rounds covering background, motivation and communication. One candidate reports harder LeetCode-style and system design questions, followed by weeks of silence after being shortlisted. Expect the format to vary by role and hiring channel, and follow up politely on timing.
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.
I went through three rounds at Indium Software for a Software Engineer role, and it was a mix of technical depth and behavioral assessment that really tested both my coding skills and how I communicate under pressure. The first round was a technical assessment with multiple-choice questions on SQL and Python fundamentals, followed by two DSA-focused coding problems and two SQL query questions. This round felt fairly standard but covered a lot of ground — they wanted to see if I could handle both theoretical concepts and practical problem-solving. The second round went deeper into software design and SDLC principles, with questions around system architecture and development lifecycle practices. They asked me to think through how different testing approaches fit into the broader context of a project, which was more nuanced than I expected. The final round was the HR and behavioral component, where they explored my background across companies, how I handle team dynamics, and my problem-solving approach. One question that stood out was building a traffic signal execution system using Java OOP concepts — it wasn't just about writing code, but demonstrating how I'd structure classes, manage state, and think about real-world constraints. The entire process felt like they were assessing not just technical chops but also how I'd fit into their team and think through problems systematically. Confidence and clear, stable answers really made the difference across all three rounds.
Prep tip from this candidate
Prepare for both DSA coding problems and SQL query questions in the technical rounds, and practice designing systems like traffic signal execution using OOP principles — that blend of algorithms, database work, and object-oriented design thinking was the core of their assessment.
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 | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Find the Missing Number | |
| Largest Salary by Department | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Size of Joins | |
| Comments Histogram | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Retailer Data Warehouse | |
| Minimum Change | |
| Flight Records | |
| Upsell Transactions | |
| Level Of Rain Water In 2D Terrain | |
| P-value to a Layman | |
| Download Facts | |
| Cumulative Distribution |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an early screen that may include aptitude questions, SQL and Python multiple-choice items, and basic coding. One describes two DSA problems and two SQL queries; another describes simple Python tasks with arrays, strings, lists and tuples, plus SQL joins.
Two candidates report a group discussion. One recalls open-ended topics such as AI's benefits and social media, which appeared aimed at communication and the ability to explain a position. Not every report includes this stage, so it may depend on the role or hiring channel.
Technical interviews are described as conversational and resume-based. Candidates report project walkthroughs, Python questions, and in one case software design, SDLC and testing discussion plus a Java OOP traffic signal system question. One candidate instead reports LeetCode-style and system design questions.
Three candidates describe a final HR-style conversation about background, motivation, team dynamics, communication and fit. Prepare concise, stable answers about your experience, how you solve problems and how you work with others. Outcomes were mixed: one offer was reported and three candidates reported no offer.
