Infosys Software Engineer candidates commonly report an assessment followed by resume-led technical discussion; some paths add coding, managerial, system-design, or HR rounds. Expect fundamentals and clear project explanations alongside role-dependent coding depth.
$64K
Avg. Base Comp
$142K
Avg. Total Comp
3-4 rounds
Typical Rounds
4 months
Process Length
Infosys Software Engineer interviews reported here range from HackWithInfy and assessment-led routes to experienced-candidate paths, so the format is not uniform. The recurring pattern is a resume-led technical conversation paired with fundamentals: candidates were asked to walk through projects, explain listed technologies, describe architecture or implementation choices, and discuss challenges they solved.
Many candidates report an initial online assessment that can combine coding with aptitude, reasoning, English, or pseudocode. Coding depth varies substantially. Some candidates received string, linked-list, pattern-printing, or SQL tasks, sometimes written on paper; others faced medium dynamic-programming problems or higher-level system-design questions. Prepare to explain an approach and improve it when prompted, not only to produce a final answer.
Technical conversations repeatedly covered OOP, DBMS, SQL, operating systems, and networks, with Java, backend, or web-stack questions when those skills appeared on the resume. Project explanations can be as important as algorithms: be ready to describe the workflow, your own contribution, a limitation, and a technical decision. Several accounts then include HR or behavioral discussion, while some paths add a techno-managerial or second technical conversation.
The format is route-dependent. Build preparation around your actual resume and language stack, then rehearse concise explanations for core CS concepts, SQL reasoning, and one or two coding problems without relying on an editor.
Synthesized from 76 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 Infosys 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 Infosys
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Top 3 Users | |
| Find the Missing Number | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Normalize Grades | |
| Hurdles In Data Projects | |
| Ticket Agent Analysis | |
| Find Duplicate Numbers in a List | |
| Digitizing Student Test Scores | |
| Concurrent LLM Serving | |
| Swap Variables | |
| Check Matching Parentheses | |
| The Longest Journey | |
| String Palindromes | |
| Seller Type Modeling | |
| Cloud-Agnostic Deployments | |
| Safe Deployments | |
| Pipeline Transformation Failures | |
| Text Editor With OOP | |
| Testing Constraints | |
| Azure Kubernetes Infrastructure | |
| Relational Migration | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| ReLu vs Tanh | |
| Student Tests |
Synthesized from candidate reports. Individual experiences may vary.
Candidates commonly report a proctored or online assessment before interviews. Depending on the route, it may include coding alongside aptitude, reasoning, verbal or English questions, pseudocode, communication, or an essay. Some HackWithInfy candidates reported multiple coding questions or separate screening rounds.
Candidates report introductions followed by detailed questions about projects, internships, tools, architecture, workflow, responsibilities, and tradeoffs. OOP, DBMS, SQL, operating systems, networks, and language fundamentals may be discussed, particularly where they appear on the candidate's resume.
Some candidates report a dedicated coding round or several technical rounds. Reported tasks range from strings, linked lists, arrays, and SQL to dynamic programming, graphs, JavaScript, application performance, or system design. Paper-based coding and requests to optimize an initial approach also appear in individual accounts.
Candidates often report an HR or combined technical-HR conversation after technical screening. Reported questions include motivation, career plans, education, and behavioral examples; some candidates instead describe a techno-managerial project discussion before HR documentation.