Infosys Business Analyst interview typically runs 3 rounds: screening, technical, and managerial/HR. It usually takes a few days to a few weeks and is mostly resume-driven and straightforward.
$58K
Avg. Base Comp
$93K
Avg. Total Comp
3
Typical Rounds
1-2 weeks
Process Length
Our candidates report that Infosys is less interested in trick questions than in whether your background cleanly maps to the role you’re claiming. Across experiences, the strongest signal was resume fluency: interviewers repeatedly pulled from recent projects, listed tools, and day-to-day responsibilities, then asked candidates to explain what they actually did and why. Even when the conversation touched technical topics, it stayed grounded in practical work rather than abstract theory, which means vague claims on a CV tend to get exposed quickly.
A recurring theme is breadth over depth. We’ve seen candidates asked to connect core Java, Java 8 streams, collections, multithreading, Spring, Hibernate, MySQL, and microservices into a coherent picture of how a real application works. That tells us Infosys is checking for working familiarity across the stack and for the ability to describe tradeoffs in plain language. The non-obvious make-or-break factor is not memorizing definitions; it’s being able to walk through a project, name the hurdles, and show how you handled them without drifting into generic answers.
The managerial conversations also seem to reward clarity and consistency more than polish. Multiple candidates described fairly direct discussions about strengths, weaknesses, role fit, and why they wanted to join, with the same underlying expectation: can you communicate your experience in a way that feels credible and relevant? In our view, the candidates who do best here are the ones whose stories line up tightly with their résumé and who can speak confidently about the work they’ve already done, not the work they wish they had done.
Synthesized from 3 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.
The process was straightforward and mostly centered on whether my background matched the Business Analyst role. I first went through an initial screening, where the discussion covered my profile and general suitability. The next round was technical, but it was not especially difficult or algorithmic. Instead, the interviewer focused on my previous and most recent work experience, the skills I had developed, and how I approached problems in my past roles. Most of the questions were grounded in my resume, so the conversation felt fair and predictable rather than like a test of obscure concepts.
The final stage was a managerial or HR discussion. We talked about role expectations, my availability, and compensation. Overall, the process felt easy, with the main evaluation based on how clearly I could explain my experience and connect my skills to the position. I received and accepted the offer. My biggest takeaway is to know every part of your resume well, especially your recent projects and responsibilities, because those details drive most of the interview. It is also worth getting clear confirmation about next steps and timelines after HR, since communication after selection may not always be consistent.
Prep tip from this candidate
Prepare concise explanations of your recent work experience, the skills you used, and how you solved problems in those roles. Also be ready to discuss salary, availability, and expectations during the HR round.
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 | |
| Top 3 Users | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| P-value to a Layman | |
| Retailer Data Warehouse | |
| Hurdles In Data Projects | |
| Digitizing Student Test Scores | |
| Covariance vs Correlation | |
| Classification and Regression | |
| Ticket Agent Analysis | |
| Swap Variables | |
| Seller Type Modeling | |
| String Palindromes | |
| Safe Deployments | |
| Testing Constraints | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Relational Migration | |
| Student Tests | |
| Empty Neighborhoods | |
| Customer Orders | |
| Prime to N | |
| Cumulative Distribution | |
| Button AB Test | |
| Paired Products | |
| Employee Salaries | |
| Rolling Bank Transactions | |
| 500 Cards |
Synthesized from candidate reports. Individual experiences may vary.
The first conversation is a screening focused on your profile and overall fit for the Business Analyst role. Interviewers use this stage to confirm that your background, experience, and communication style align with the position.
This round is technical but generally not highly difficult or algorithm-heavy. The discussion is mostly resume-driven, covering your recent projects, work experience, core skills, and how you approach problems; in some cases, it also includes basic technical questions relevant to the stack, such as Java fundamentals, Java 8 streams, collections, or related application concepts.
The final stage is a managerial or HR discussion. This round covers role expectations, availability, compensation, and behavioral questions, along with how you handled challenges in past projects and how you communicate your experience.