
No company-specific verbatim questions are publicly documented for IBM Philippines BA interviews; this question is grounded in confirmed general topics such as requirements gathering and stakeholder communication. IBM seeks BAs who can navigate ambiguity and align diverse perspectives within global delivery teams, demonstrating collaboration and conflict resolution.
Use the STAR format to show a specific instance. Emphasize your role in bridging gaps, the techniques you used (e.g., prioritization, prototyping), and the win-win outcome. Avoid blaming stakeholders or sounding like you simply obeyed orders.
Start by grounding the conflict in a specific project, and name the stakeholders only by their roles so you keep the story professional. Say plainly that you first listened to each side separately, without taking sides, because that lets people speak candidly and gives you the full context behind their requirements. Then explain that you mapped their needs onto business value and feasibility, using simple criteria like impact, cost, and timeline, and that you brought the data back to them in a joint session. Present this as a neutral facilitator, not a judge, and show that you used a visual aid such as a matrix or a simple prototype to make the trade-offs concrete. This matters in the Philippine workplace where hierarchy can silence junior voices, so emphasize that you invited everyone to react to the evidence rather than defer to rank. Close by noting how you aligned the group on a shared goal, got a documented sign-off, and delivered something that met the core needs of both sides. Avoid saying you simply compromised or followed the senior stakeholder, instead show that you turned disagreement into a decision everyone owned.
Many Filipino candidates, especially in Philippine BPO settings, fall back on saying, 'Inayos ko na lang po yung requirements based sa kung sino mas mataas yung position' (I just followed the stakeholder with the higher position). This indicates a passive approach. Instead, demonstrate proactive facilitation and evidence-based decision-making regardless of hierarchy.
Situation
In my previous role as a junior business analyst for a retail mobile-app project, the marketing team wanted a flashy, feature-rich checkout flow to boost engagement, while the legal and compliance team demanded a strict, minimal-step process to reduce liability. Both stakeholders were adamant and deadlines were tight.
Task
I had to elicit, prioritize, and reconcile these conflicting requirements into a single set of functional specifications that both sides would sign off on.
Action
First, I scheduled separate one-on-one interviews with each stakeholder to fully understand their underlying concerns and non-negotiables. Using MoSCoW prioritization, I categorized each requested feature as Must, Should, Could, or Won't have. Then I organized a joint workshop where I presented a compromise user flow that included the essential compliance steps but still allowed some marketing-driven personalization elements, backed by data from a mini competitor analysis and a quick prototype usability test with 5 internal users.
Result
Both sides agreed to the hybrid design after two rounds of iteration. The final solution reduced checkout drop-off by 12% in the first month while passing all compliance audits. It also fostered a more collaborative relationship between the two teams going forward.
Facilitating structured dialogue and using a transparent prioritization framework turns conflict into consensus.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.