Cracking the Infosys Business Analyst Interview
Business Analysts (BAs) at Infosys serve as the critical bridge between global clients (often non-technical stakeholders) and the offshore development teams. The interview process focuses heavily on communication, requirement elicitation, Agile frameworks, and specific domain expertise.
Phase 1: The Core BA Skills Round
This round evaluates your fundamental understanding of the BA lifecycle.
- Requirement Gathering: "Walk me through your process for gathering requirements for a new feature." Expect follow-up questions on how you handle ambiguous or constantly changing requirements from a difficult client.
- Documentation: You must be proficient in writing User Stories, Acceptance Criteria, and Business Requirement Documents (BRDs). "How do you ensure a User Story is 'INVEST' (Independent, Negotiable, Valuable, Estimable, Small, Testable)?"
- Agile and Scrum: Infosys operates heavily on Agile methodologies. Be prepared to discuss your role in Sprint Planning, Backlog Grooming, and Sprint Reviews. "What is the difference between a Product Owner and a Business Analyst in your current setup?"
Phase 2: Domain Expertise Round (Crucial)
Infosys hires BAs specifically for their domain knowledge (e.g., BFSI, Retail, Healthcare, Manufacturing).
- Banking (BFSI): If you are applying for a banking project, expect questions on core banking (Finacle knowledge is a huge plus), payment gateways, SWIFT messaging, or KYC/AML processes.
- Retail/E-commerce: "Explain the order-to-cash lifecycle." You must understand supply chain logistics, inventory management, and CRM integrations.
- The Scenario: They will present a domain-specific problem. "Our retail client wants to implement a new loyalty program. What are the key technical and business requirements you would define?"
Phase 3: Managerial and Behavioral Round
Infosys needs BAs who can manage offshore teams and handle high-pressure client interactions.
- Conflict Resolution: "Tell me about a time when the client requested a massive feature change mid-sprint. How did you handle the client, and how did you communicate it to the development team?"
- Stakeholder Management: You will be evaluated on your ability to say "no" politely, manage scope creep, and prioritize the product backlog effectively using frameworks like MoSCoW (Must have, Should have, Could have, Won't have).
Top 3 Questions to Prepare
- Explain how you convert a high-level Business Requirement Document (BRD) into actionable User Stories for the development team.
- How do you manage scope creep when a client continuously adds new requirements during an active sprint?
- Walk me through a time when a project failed or missed a deadline due to misunderstood requirements. What did you learn?
