Impetus Career Consultants Business Analyst Interview: Questions, Experience & Prep (2026)

Impetus Career Consultants is a consulting and staffing firm currently listing 2 open Business Analyst roles (as of July 2026, per knok jobradar). Across India, BA hiring is active: knok tracks 398 open BA positions, with Bangalore (53 openings), Delhi (48), and Mumbai (24) leading by volume.

Candidates report a process that typically spans two or three rounds: an initial HR call covering your background and salary expectations, a technical or case-based round testing your BA skills, and sometimes a final round with a senior manager or client lead. Because Impetus places BAs with client companies, interviewers focus heavily on communication, stakeholder management, and your ability to turn business problems into clear documentation.

Brush up on your process-mapping tools and be ready to walk through a real project end to end. The firm works across sectors including BFSI, retail, and logistics, so expect questions that test breadth over deep domain specialisation.

Candidates report these questions coming up frequently in Impetus Career Consultants BA interviews:

1. 'Walk me through a project where you were the primary BA. What exactly did you own?'
2. 'How do you gather requirements when stakeholders are not sure what they want?'
3. 'What is the difference between a BRD and an FRD? When do you use each?'
4. 'Describe a time you received conflicting inputs from two stakeholders. How did you resolve it?'
5. 'Which tools have you used for process mapping? Show me an example of a flow you created.'
6. 'How do you prioritise requirements when the team cannot build everything at once?'
7. 'What does Agile mean to you as a BA, and how does your role change in a Scrum team?'
8. 'How do you write a user story? Give a real example from a project you worked on.'
9. 'Tell me about a time project scope changed midway. How did you manage it?'
10. 'How do you verify that the delivered solution actually meets the original business requirement?'
11. 'What is UAT, and what is your specific role in that process?'
12. 'If a client says the current report is wrong but cannot explain why, what do you do first?'

Q: 'Describe a time you received conflicting inputs from two stakeholders. How did you resolve it?'

*Situation:* At my previous company, the sales head wanted a CRM dashboard showing all leads by region, while the finance team wanted the same screen to highlight overdue invoices. Both teams had equal project priority.

*Task:* I needed to produce requirements that satisfied both teams without doubling the development effort.

*Action:* I arranged a joint workshop with both stakeholders, mapped out their underlying goals (sales wanted conversion visibility, finance wanted risk visibility), and proposed a single dashboard with two configurable views. I documented both versions as separate user stories and got written sign-off from both heads in one meeting.

*Result:* The dashboard was built with a view toggle, development effort stayed within the original estimate, and both teams approved it during UAT without any change requests.

---

Q: 'How do you gather requirements when stakeholders are not sure what they want?'

*Situation:* I was brought onto a project for a logistics client where the ops head said, 'We just need something better than what we have,' with no further clarity.

*Task:* My job was to produce a concrete, signed-off requirements document within two weeks.

*Action:* I started with a process walkthrough: I sat with two ops executives, observed their current workflow, and noted every manual step and pain point. I then used the Five Whys technique to surface root causes rather than symptoms, and created an 'as-is' versus 'to-be' process map. I shared the map with stakeholders and asked them to validate or correct it section by section.

*Result:* I delivered a signed-off BRD with clear, prioritised requirements well within the deadline, and the project moved into design with no scope disputes in that phase.

---

Q: 'Tell me about a time project scope changed midway. How did you manage it?'

*Situation:* Midway through a retail analytics project, the client acquired a new brand and wanted its data included in the final reports. This was completely outside the original scope.

*Task:* I had to assess the impact and present options to both the client and my internal project manager.

*Action:* I documented the change request formally, estimated the additional data-mapping work with the tech lead, and presented three options: include the new brand in Phase 1 with a revised timeline, defer it to Phase 2, or build a connector as a separate deliverable. I kept both parties in sync through a shared change log updated after every discussion.

*Result:* The client chose Phase 2, the original delivery stayed on track, and the change was handled without conflict or cost overrun.

STAR (Situation, Task, Action, Result) is the most reliable structure for behavioural questions. Every answer should land on a concrete result, even if it is qualitative. Avoid ending on the Action; always state what actually changed.

MoSCoW for prioritisation questions. When asked how you prioritise requirements, walk the interviewer through Must Have, Should Have, Could Have, and Won't Have. Give a real example of something you moved to 'Won't Have' and why the business accepted it. This signals commercial judgment, not just process knowledge.

As-Is vs To-Be for process questions. When describing how you approach a new project, frame it as: 'First I document the current state, identify gaps, then define the future state.' This shows structured thinking without jargon.

Five Whys for root-cause questions. If asked how you handle unclear problems or 'the report is wrong' scenarios, explain that you ask why repeatedly until you reach the actual cause, not the symptom. Keep the example short and specific.

RACI for stakeholder questions. When discussing multiple stakeholders, mention how you map Responsible, Accountable, Consulted, and Informed so no one is surprised by decisions. Interviewers at consulting-adjacent firms respond well to this because it shows you can manage client relationships in a structured way.

Impetus Career Consultants places BAs with client companies, which means every interviewer is asking one underlying question: 'Can I put this person in front of a client?'

Clear communication. They watch how you explain your past projects. If you rely on technical jargon or take several minutes to reach the point, that is a concern signal. Practice explaining your best project in under two minutes before the interview.

Structured thinking. BA work is about organising ambiguity. Interviewers present vague scenarios on purpose to see whether you ask the right clarifying questions or jump straight to assumptions.

Ownership of outcomes. Saying 'the team delivered X' is weaker than 'I owned the requirements, and the team delivered X.' Take clear credit for your specific contributions without overstating them.

Tool familiarity. Candidates report direct questions about JIRA, Confluence, Visio, MS Excel, and basic SQL. You do not need expert-level command of all of them, but be honest about what you know and give a real example for each tool you claim.

Comfort with ambiguity. Consulting-style BA roles rarely start with a well-defined problem. Show that you can take a vague brief and produce structured documentation without constant hand-holding from a manager.

One week before the interview:

Pick your three best projects and write out a STAR story for each. Cover at least one story about stakeholder conflict, one about scope change, and one about a tool or process you improved. Rehearse these out loud, not just in your head.

Process and documentation basics:

Review how to write a user story (as a [user], I want [goal], so that [reason]), the structure of a BRD versus an FRD, and the difference between functional and non-functional requirements. If you have not written one recently, draft a one-page sample BRD for a fictional app to rebuild the habit.

Tools check:

Open your JIRA, Confluence, or Visio and pull up real work you did. Being able to say 'here is a flow I created for a past project' is far more convincing than 'yes, I have used Visio.'

Research Impetus Career Consultants:

Check their LinkedIn page and any recent job descriptions they have posted. Note the sectors and tools mentioned repeatedly. Candidates report the HR round typically opens with 'tell me about yourself' and moves quickly to 'why Impetus?' Have a specific, honest answer prepared.

Day before:

Prepare two or three questions for the interviewer. Good options: 'What does the first three months look like for a BA in this role?' or 'What tools does the client team use today?' Asking nothing signals low interest.

If you are still searching for the right opening while you prepare, knok checks 150+ job sites nightly, applies to roles that match your resume, and messages HR for you, so your job hunt keeps moving while you focus on interview prep.

Saying what the team did instead of what you did. In BA interviews, your personal contribution matters. Replace 'we gathered requirements' with 'I facilitated the workshops and documented the outputs.'

Skipping the result. A STAR answer without a result is just a story. Even a partial outcome counts: 'the project shipped on time' or 'the client accepted the BRD with only two revision cycles.'

Claiming tools you cannot back up. If JIRA, Visio, or SQL appears on your resume, expect a follow-up question. Only list tools where you can walk through a real example on the spot.

Being vague about salary expectations. Because Impetus is a placement firm, the HR round often includes a direct CTC discussion. Know your current CTC and expected CTC before the call. Saying 'I am flexible' without any number tends to slow down the placement process.

Not asking about the client or project. Since Impetus places you with a client company, asking nothing about the end organisation or the project signals low interest. Prepare at least one informed question about the role or sector.

Over-explaining technical details to an HR interviewer. Match your depth to your audience. In the HR round, keep answers concise and high-level. Save the detailed process walkthrough for the technical round.