Abc Software Engineer candidates report an aptitude or online screen, one to several technical rounds on DSA, OOP, SQL and project deep-dives, then an HR conversation. Reports vary widely in length and format.
$125K
Avg. Base Comp
$150K
Avg. Total Comp
2-5 rounds
Typical Rounds
3 weeks
Process Length
Candidates describe the Abc Software Engineer interview as mostly fundamentals-driven, but the format varies a lot from person to person. Several report an online aptitude test or DSA assessment as the first filter, and one candidate says the aptitude round ended their process before any technical interview.
In the technical rounds, candidates report array, string and linked-list problems. Specific questions include converting a string into a number, 3Sum, rain water trapping and two-sum variations. One candidate was asked about graph and dynamic programming concepts. Another reported easy-to-medium DSA plus a question on JDK, JRE and JVM. A third was asked to write Java 8 stream code and a Spring configuration question. A different candidate reported Kubernetes, Terraform and Dockerfile questions, so the stack can lean toward DevOps depending on the team.
Project discussion comes up repeatedly. Candidates were asked to explain what they personally built and the problems they solved, so prepare to separate your contribution from the team's.
Candidates also mention an HR or managerial round covering self-introduction, why Abc should hire you, notice period, pressure scenarios and salary expectations. One candidate reported a three-hour final panel with three interviewers, and the same candidate said the whole process took about three weeks.
Practice medium-level DSA, review OOP, SQL and OS basics, and have specific project stories and a clear reason for choosing Abc.
Synthesized from 38 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 Abc process.
I interviewed at Abc for a Junior Software Engineer role and found the experience refreshingly well-organized. The recruiter discovered my resume on Naukri.com and reached out promptly to schedule the interview. The entire process felt smooth and efficiently handled, which set a positive tone from the start.
The interview itself began with a written component, followed by a viva round where they asked academic questions about my major, minor, and university projects. They wanted to understand my educational foundation and what I'd actually built in school — not just grades, but real learning. The next stage brought me in front senior leadership, including the MD, who focused on whether I could articulate why they should hire me and how I'd describe my work and myself. The tone was conversational rather than confrontational; they were gathering information about my thinking and communication skills alongside technical knowledge. One question that stuck was about the pillars of object-oriented programming — a conceptual check rather than a code-writing exercise. The staff was professional and welcoming throughout, and I appreciated their strong security protocols, which gave me confidence in how they operated.
After the final interview, the company extended an offer and began the onboarding process. The whole experience felt like they were genuinely interested in whether there was a fit, not just running through a checklist. It was a chance to explore myself as much as to be evaluated.
Prep tip from this candidate
Be prepared to discuss your university projects in concrete detail and articulate why you're a good fit for the role — they want to hear your reasoning, not a generic answer. Brush up on OOP fundamentals, but expect the emphasis to be on how you think and communicate rather than coding under time pressure.
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 Abc
Given a dictionary consisting of many roots and a sentence, write a function to stem all the words in the sentence with the root forming it.
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| loc vs iloc | |
| Find the Missing Number | |
| Binary Tree Validation | |
| Bootstrapping Samples | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Top 5 Turnover Risk | |
| Random SQL Sample | |
| Merge Sorted Lists | |
| Upsell Transactions | |
| Top 3 Users | |
| Longest Streak Users | |
| Rolling Bank Transactions | |
| String Shift | |
| Customer Orders | |
| Largest Salary by Department | |
| Scrambled Tickets | |
| Find Bigrams | |
| Comments Histogram | |
| Payments Received | |
| Slacking Employees Salaries | |
| Last Transaction | |
| Get Top N Frequent Words |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an early screen, either an online aptitude test or a DSA assessment of easy-to-medium problems. One candidate was rejected at the aptitude stage, so it may act as a real filter. Not every candidate describes this step, so treat it as common but not guaranteed.
Candidates report between two and five technical rounds. Reported topics include strings, arrays, linked lists, 3Sum, OOP, SQL and language-specific questions such as Java streams. Difficulty is mostly described as easy to medium, though one candidate found the DSA bar high. Questions may change with the team.
Several candidates report being asked to introduce themselves and walk through their projects, including what they personally did and the decisions they made. Preparing concrete examples for each resume project is typically worthwhile, since this discussion appears in both technical and HR rounds.
Candidates describe HR or managerial conversations covering why they should be hired, notice period, pressure scenarios and salary expectations. One candidate reported a roughly three-hour panel with three interviewers followed by a 30-minute behavioral discussion. Offers and rejections were both reported after this stage.
