Lead Business Analyst

EPAM Systems is seeking a Lead Business Analyst to oversee the requirements layer for migrating a Windows desktop application to a cloud-native SaaS platform. This role involves leading a team, partnering with stakeholders, and translating business needs into actionable specifications while ensuring clarity and consistency throughout the migration process.

Responsibilities:

• Take ownership of the end-to-end requirements layer for the migration initiative, ensuring clarity and consistency across all deliverables
• Lead a small team of business analysts, providing guidance, mentorship, and quality oversight across their work
• Partner with product, engineering, and business stakeholders to shape a shared understanding of scope, priorities, and desired outcomes
• Analyze the current desktop application to document existing workflows, functional behaviors, and underlying business rules
• Translate business needs into detailed user stories, acceptance criteria, and functional specifications suitable for engineering delivery
• Facilitate structured workshops and discovery sessions with business users, subject matter experts, and technical teams to gather requirements
• Coordinate the review, validation, and sign-off of requirements with stakeholders across technical and non-technical audiences
• Support the engineering team throughout implementation by clarifying requirements, resolving ambiguity, and refining scope as needed
• Plan and orchestrate user acceptance testing activities, aligning them with release milestones and business timelines
• Track progress, dependencies, and risks across the requirements workstream, escalating and resolving issues as they arise

Requirements:

• 5 or more years of experience as a Business Analyst on software delivery projects, including at least one legacy migration or modernization engagement
• At least 1 year of experience in people management or team leadership, overseeing a team of 5 or more FTEs
• Background contributing to financial services, regulatory, or compliance-domain projects, with familiarity in audit trail requirements, deadline-driven workflows, and examiner-facing data quality
• Experience working embedded within an Agile engineering team, writing stories and acceptance criteria consumed directly by developers
• Proven ability to facilitate requirements workshops and UAT sessions with non-technical end users
• Strong skills in requirements elicitation and documentation, including user stories, acceptance criteria, and functional specifications for API-backed workflows
• Business process modeling expertise, with the ability to decompose AS-IS desktop workflows and design TO-BE cloud equivalents
• Solid gap analysis capability, including feature scoping across large application surfaces and distinguishing between carry-forward, retire, and redesign scenarios
• Experience with entitlement and role modeling, defining access control rules such as admin, user, report preparer, and read-only as implementable business rules
• Understanding of multi-tenant SaaS concepts, including institution-scoped data, per-institution onboarding, and role inheritance models
• Strong stakeholder management skills across technical and non-technical audiences at the same time
• REST API literacy, with the ability to read OpenAPI specs, validate endpoint contracts, and identify mismatches between specification and implementation
• Proven experience planning and facilitating UAT under filing-deadline pressure
• Fluent English communication skills at a B2 level or higher, both written and verbal
• Domain knowledge of FDIC Call Report and FFIEC CDR filings and processes
• Familiarity with SAML, OIDC, and SSO concepts sufficient to document federation flows and institution onboarding steps independently of engineering support
• Basic SQL skills for validating data migration outputs and spotting tenant scoping issues
• Awareness of SOC 2 Type II requirements, with the ability to document audit trail and access control needs as BA artefacts
• Prior experience applying the Strangler Fig migration pattern, including parallel-run periods, feature flag rollout, and institution-by-institution cutover
• Background in change management and user adoption, supporting end-user transition from desktop to web-based platforms