1.

Can you walk me through a project where you acted as a bridge between business
and technical teams?
→ Assesses your experience as a solution provider and your communication clarity
across domains.

2. How do you gather requirements from stakeholders who are not clear about what
they need?
→ Tests your facilitation skills, probing techniques, and experience running
workshops.

3. Tell me about a time when you prioritized conflicting stakeholder requirements.

How did you handle it?
→ Evaluates your stakeholder management, negotiation, and prioritization
capabilities.

4. Describe a business process you improved or redesigned. What tools did you use?
→ Looks for BPMN, Visio, Lucidchart, and actual process improvement experience.

5. How do you ensure the solution you propose aligns with both customer and
business needs?
→ Focuses on your analytical mindset, gap analysis, and documentation accuracy.

6. Have you worked on a transformation or change request? What was your approach?
→ Directly related to the job’s change management planning responsibilities.

7. What is your approach to documenting business and functional requirements?

→ Helps interviewers assess your BRD, FRD, and user story documentation style.

8. How do you validate that a solution works before it's handed over to BAU?
→ Checks your coordination with QA/UAT, test case mapping, and closure approach.

9. How do you manage risks and dependencies during a project? Can you give a real
example?
→ Aligns with the JD’s focus on risk identification, mitigation, and reporting.

10. Explain a situation where you used SQL or other tools to analyze data or
resolve a root cause.
→ Measures your data analysis ability—especially for issue resolution in finance.

11. What challenges have you faced working on financial systems like Oracle or
reporting platforms?
→ Evaluates your hands-on experience with tools like Oracle EBS and how you
troubleshoot/report issues.

12. Have you ever trained end users or created user documentation? How did you
approach it?
→ Ties into your role in preparing training docs, user manuals, and running
sessions.

Special migration answer:

Example: At Citi, I identified regulatory gaps in ISO 20022 message mapping and
initiated a change to align SWIFT messages with updated compliance requirements.

✅ Resume Bullet (TCPWave – Citi Bank)

Led end-to-end change management for ISO 20022 migration initiative, including
impact analysis, change control, and stakeholder alignment across compliance,
payments, and core banking teams.
Created and maintained change impact assessments, updated BRDs/FRDs to reflect
SWIFT message formatting changes, and ensured traceability in JIRA through epics
and linked change requests.

Facilitated approval cycles through Change Control Board (CCB) meetings, managed
sign-offs, and collaborated with QA to update test plans and UAT scripts.

Enabled smooth transition by conducting training sessions, stakeholder

walkthroughs, and post-implementation reviews, minimizing change-related defects
and ensuring compliance with regulatory deadlines.

🎯 Interview Scenario (STAR Method)

S – Situation:
At Citi, we were required to adopt ISO 20022 for cross-border payments. This change
impacted our payment gateway validations and message formatting for SWIFT MX.

T – Task:
As the Senior Business Analyst, I was responsible for managing the change end-to-
end — from gathering revised regulatory requirements to ensuring updated message
schemas were properly implemented without affecting downstream systems.

A – Action:
I conducted impact assessments with SMEs, identified affected processes, and raised
change requests via JIRA. I facilitated multiple stakeholder sessions to align
operations, tech, and compliance teams. I then updated the BRD and message mapping
specifications, managed approvals via the Change Control Board, and worked closely
with QA to modify regression and UAT test cases.

R – Result:
The changes were implemented two weeks ahead of the SWIFT deadline with zero post-
production issues. This also improved our STP (straight-through processing) rates
by 11%, as validations were more accurate.

Change Management scenario for “Moving Core Banking Legacy System to Citi Cloud
Systems”, ideal for your Senior Business Analyst interview and resume:

✅ Resume Bullet (TCPWave – Citi Bank)

Spearheaded change management activities for migrating Citi’s legacy core banking
platform to Citi-owned private cloud, impacting over 20 downstream systems
including payments, fraud, and regulatory reporting.

Conducted end-to-end impact analysis, identified risks, updated integration

touchpoints, and managed documentation across BRDs, FRDs, and system interface
specs.

Facilitated cross-functional alignment via workshops with infrastructure, security,

operations, and business teams, ensuring cloud readiness without disruption to BAU
operations.

Managed the Change Control lifecycle through CCB coordination, JIRA change tickets,
and stakeholder approvals, resulting in a zero-defect migration across two release
waves.

🎯 Interview Scenario (STAR Format)

S – Situation:
Citi Bank initiated a strategic initiative to migrate its legacy core banking
system to Citi's private cloud infrastructure. This was a high-impact change,
touching everything from customer account processing to real-time fraud analytics
and compliance reporting.

T – Task:
As the Senior Business Analyst, my responsibility was to manage the business-side
change impact and ensure a smooth transition across functional units, without
affecting ongoing operations or customer SLAs.

A – Action:
I started by conducting a detailed impact analysis across all integrations (over 20
downstream systems), including payment gateways, ledger entries, and fraud
platforms. I updated the BRD and FRD to reflect cloud-specific architectural
shifts, and ensured new interface contracts were documented. I facilitated joint
working sessions with infrastructure, cybersecurity, and business users to address
access control, latency risks, and failover requirements.

I used JIRA to log and track change requests, created traceability matrices, and
managed all approvals via the Change Control Board. For UAT, I coordinated test
case updates to reflect the new cloud-based execution paths and helped design
rollback plans for critical components.

R – Result:
The migration was successfully executed in two phases, with zero production issues
and no unplanned downtime. Post-migration performance improved by 18%, and audit
compliance scores increased due to better logging and access control capabilities
in the cloud environment.