Infosys Business Analyst interviews reported by candidates range from two to four rounds and commonly test resume depth, project judgment, communication, and assignment-relevant technical knowledge.
$91K
Avg. Base Comp
$107K
Avg. Total Comp
2-4 rounds
Typical Rounds
1-2 months
Process Length
Infosys Business Analyst candidates describe a process that can range from two to three rounds, with the exact mix varying by hiring route and assignment. Your resume and project history are the center of gravity. Candidates report detailed follow-ups on recent work, business processes, project decisions, domain knowledge, tools, and the outcome of their work. Prepare a concise walkthrough that makes your role, approach, stakeholders, and results easy to follow.
Technical depth is role-specific rather than uniform. Reported discussions include SQL, data modeling, Dynamics 365, cloud topics, and other tools listed on the candidate’s resume. Review the tools and claims you present, then connect them to practical business use. Several accounts also describe situation-based prompts: handling changing requirements, difficult stakeholders or clients, conflict, deadline pressure, and project challenges.
Expect communication and motivation questions alongside the work discussion. Candidates mention introductions, knowledge of Infosys, Business Analyst responsibilities, skills, career direction, and long-term goals. The evidence is assignment-dependent, so use it to prepare adaptable examples rather than expect one fixed format. Be ready to explain the business need behind a project, the standards or process you followed, your individual contribution, and the resulting output.
Synthesized from 13 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 interview was more straightforward than I expected, but it was very closely tied to my background. Rather than spending much time on abstract questions, the interviewers worked through my resume and asked more than ten questions about the projects I had listed. The main discussion centered on my current project, and I was expected to explain it thoroughly: what I had worked on, the standards I followed, the business need, and the output I achieved. Because the role involved Dynamics 365, they also tested my knowledge of standard D365 processes and how those processes applied to my project work.
A large part of the conversation was scenario based. I had to describe past projects and explain how I would respond to situations resembling active client work. One question focused on a difficult client I had dealt with and how I approached that relationship. The important part was not just identifying the conflict, but clearly describing what I focused on and what result came from my actions. They also covered core business analysis concepts and looked for alignment between my previous experience and the responsibilities of the job.
Overall, I thought the questions were manageable because they came directly from my resume and the standard D365 product, though that also meant there was nowhere to hide if I could not explain a project in detail. The interview felt background specific, with an emphasis on being able to contribute to the type of project already underway. The experience itself was good, and I ultimately received an offer, but I declined it. My biggest takeaway is to know every project and claim on your resume well enough to discuss the process, standards, client challenges, and measurable output without relying on vague descriptions.
Prep tip from this candidate
Prepare a detailed walkthrough of every resume project, especially how you applied standard Dynamics 365 processes and what output you achieved. Also rehearse a concrete difficult-client example that explains both your approach and the result.
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 | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Size of Joins | |
| P-value to a Layman | |
| Hurdles In Data Projects | |
| Digitizing Student Test Scores | |
| Covariance vs Correlation | |
| Classification and Regression | |
| Ticket Agent Analysis | |
| Swap Variables | |
| Addressing Data Quality Issues | |
| Seller Type Modeling | |
| String Palindromes | |
| Merchant Dashboard Design | |
| Safe Deployments | |
| Scalable Data Pipelines | |
| Testing Constraints | |
| Client Solution Pushback | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| Relational Migration | |
| Singly Linked List | |
| Student Tests | |
| Empty Neighborhoods | |
| Customer Orders | |
| Prime to N |
Synthesized from candidate reports. Individual experiences may vary.
Some candidates report an initial profile screen or campus aptitude assessment covering quantitative aptitude, logical reasoning, and verbal questions. This is not described in every account, so candidates should confirm their route while preparing a clear introduction and concise explanation of their background.
Candidates commonly report detailed discussion of projects, BA concepts, business processes, and the skills on their resume. Depending on the assignment, reported topics include SQL, data modeling, ERP tools, Excel, Jira, cloud, or application technologies; prepare to explain how you used your own tools in context.
Candidates report scenarios about changing requirements, stakeholder or client conflict, deadline pressure, and project challenges. A case-study or managerial discussion may ask how you structure a response, communicate trade-offs, and relate prior experience to the role.
Candidates report HR-style conversations about motivation, career goals, location or relocation, availability, role expectations, and compensation. Some accounts place this after technical or managerial discussion, while others describe it as part of a panel or final round.
