Candidates describe an Infosys Software Engineer process that usually starts with an online coding assessment, then moves to technical interviews on DSA, SQL, and core CS, and in some reports finishes with an HR conversation.
$78K
Avg. Base Comp
$95K
Avg. Total Comp
3 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Infosys Software Engineer interview as a coding assessment followed by technical conversations that range well beyond algorithms. Most reports begin with an online test. One candidate had an online coding round with three questions followed by an offline coding round with four. Another reports a four-question assessment with three easy-to-medium problems and one hard one. Reported topics include dynamic programming, arrays, strings, greedy, matrix problems, balanced brackets, hashmap questions, rotating an array by k steps, and an LRU cache.
The technical rounds lean on resume depth and core computer science. Candidates report SQL queries written from simple to hard, query optimization, DBMS, and SOLID, along with basics such as deadlocks and TCP versus UDP. Stack-specific questions follow whatever the candidate listed: Java and REST APIs, React and JavaScript, or Salesforce. One candidate who received no offer could not go deeper on a listed JavaScript certification and its projects. That candidate also lost points when the time complexity they stated for a paper problem was judged wrong despite sound logic.
Expect some unevenness. One final interview ran about an hour and a half and leaned heavily on DBMS, while the no-offer candidate describes a session of roughly three hours. System design comes up in some reports. Two candidates mention RAG or other AI questions, so be able to explain a pipeline and any AI project you list. A closing HR conversation is described as covering package details and communication.
Across the accepted reports, the common thread is being able to explain your approach and complexity out loud, then talk comfortably about SQL and your own projects.
Synthesized from 409 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 | |
| Size of Joins | |
| P-value to a Layman | |
| Normalize Grades | |
| Ticket Agent Analysis | |
| Hurdles In Data Projects | |
| Find Duplicate Numbers in a List | |
| Digitizing Student Test Scores | |
| RAG Strict Source Control | |
| Concurrent LLM Serving | |
| Swap Variables | |
| Check Matching Parentheses | |
| The Longest Journey | |
| Seller Type Modeling | |
| String Palindromes | |
| Cloud-Agnostic Deployments | |
| Blob Indexing | |
| Safe Deployments | |
| Pipeline Transformation Failures | |
| Text Editor With OOP | |
| Scalable Data Pipelines | |
| Testing Constraints | |
| Client Solution Pushback | |
| Azure Kubernetes Infrastructure |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically report starting with an online assessment. Reports include a three-question online coding round and a four-question set covering arrays, strings, DP, and greedy, with three easy-to-medium problems and one hard. Another candidate describes a very tough test heavy on dynamic programming, with matrix and array questions mixed in.
Some candidates describe a second coding step done offline or in person. One candidate had an offline round with four questions. Another qualified in an online assessment and then a second, in-person assessment before receiving an interview email.
Candidates report one or two technical rounds covering DSA, SQL, DBMS, and sometimes system design. Examples include writing SQL queries from simple to hard, query optimization, SOLID principles, deadlocks, and TCP versus UDP. One no-offer candidate wrote two medium problems on paper. One final interview of about an hour and a half leaned heavily on DBMS and core CS.
Several candidates say interviewers questioned the projects and skills on their resume. Depending on the stack, this may include Java and REST APIs, React and JavaScript, or Salesforce, plus explaining a RAG pipeline or an AI project you list. One candidate also had a virtual AI-based interview on React, Node.js, and past projects. Listing a technology you cannot discuss in depth can hurt, as one no-offer report shows.
Some candidates describe a closing HR discussion. One in-person HR round lasted about an hour and covered benefits and package details, and another touched on communication. One candidate heard from others that the HR side can be inconsistent.
