Lead/Senior Business Analyst - Multiple Domains
EPAM Systems, Inc. (company site, opens in a new tab)7–15 yrsJaipurOn-siteDirect career pageEst. 25–45 LPA
Posted on 1 Sept
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Reach people at EPAM Systems, Inc.
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at EPAM Systems, Inc. you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Lead requirement gathering and documentation activities including BRD and FRD across BFSI, Healthcare, Insurance, and Lifesciences domains.
- Facilitate Agile ceremonies (Scrum, Kanban, SAFe) and integrate AI tools to enhance Business Analyst/Product Owner productivity and decision-making.
- Collaborate with stakeholders and technical teams on business-IT alignment, UI/UX design support, data processes, API integrations, and automation of recurring BA/PO tasks.
Minimum Requirements
- 7-15 years of IT experience with proven Business Analysis or Product Ownership track record.
- Experience in BFSI, Healthcare, Insurance, and Lifesciences domains.
- Proficiency in requirement gathering (BRD, FRD), stakeholder management, Agile methodologies (Scrum, Kanban, SAFe).
- Technical skills required: SQL, API, Data/ETL technologies, familiarity with AI tools for BA/PO activities, UI/UX design and mockup creation.
Ideal Candidate Profile
- Practitioner comfortable operating across multiple domains and collaborating with diverse stakeholders and technical teams.
- Experienced in blending Agile frameworks and AI-assisted approaches to improve BA/PO output and project execution.
- Skilled in translating complex business needs into actionable user stories, acceptance criteria, and technical integrations.