Job Summary
PRAGATI
JD
Business Analyst — Digital Engineering Engagement with a Sweden-based global top-tier manufacturing client · Multi-application transition and SAFe Agile delivery 1. Role purpose The Business Analyst is the bridge between the client’s Digital Product Owners and the HCLTech engineering pods delivering across a 100+ application portfolio for a Sweden-based global top-tier manufacturing client. The role converts business intent into well-formed, testable requirements, protects scope and traceability through the transition from Learn to Perform phase, and sustains a healthy, prioritised backlog once the pods move into steady-state delivery. The Business Analyst works across multiple technology stacks — Microsoft .NET, Java/JEE, SharePoint Online/M365, Mainframe and Data/BI — and is expected to build functional depth in the assigned sub-domains rather than act purely as a requirements scribe. 2. Role at a glance Attribute Detail Role title Business Analyst — Digital Engineering (Design & Development) Engagement Application transition and managed delivery for a Sweden-based global top-tier manufacturing client Reports to Group Project Manager — Digital Engineering, HCLTech Base location India (offshore) with Sweden (CET) time-zone overlap; onsite rotation as required Experience 8–12 years in business analysis within enterprise application delivery Band E3 — in line with the approved additional development capacity plan Engagement phase Transition (Learn → Perform) moving into steady-state Agile delivery 3. Key responsibilities Area Responsibilities Requirements engineering Elicit, analyse and document business and functional requirements; author user stories with clear acceptance criteria, non-functional requirements and definition of done. Maintain end-to-end traceability from business outcome to story to test case. Product backlog ownership Partner with the client Digital Product Owners to shape, refine and prioritise the backlog. Run refinement sessions, size demand with the pods and keep a ready-state backlog two to three sprints ahead. Transition & knowledge transfer Capture as-is process and functional flows during KT; validate understanding through reverse walkthrough and playback before the pod assumes delivery responsibility. Own functional sections of the run book and SOP set. Process & impact analysis Map as-is versus to-be processes, assess change impact across integrated applications and interfaces, and surface functional risk, dependency and technical-debt items into the transition risk register. SAFe Agile delivery Contribute to PI Planning, feature breakdown, dependency mapping and PI objectives. Support sprint ceremonies alongside the Scrum Master and ensure demos map back to committed business value. Testing & validation Define test scenarios and UAT scripts, support SIT and UAT execution, triage defects functionally and secure business sign-off ahead of release. Stakeholder engagement Work directly with the client DPO, DPAO, VSM and CSM community on scope, priorities and readiness reporting; present evidence-based status at governance and leadership forums. Documentation & reuse Maintain functional specifications, interface catalogues and glossaries as living assets; drive reusable templates and AI/Copilot-assisted documentation to reduce analysis toil. 4. Must-have skills and experience Skill area What we expect Business analysis Requirement elicitation, user-story writing, process modelling (BPMN/UML), gap and impact analysis, functional design documentation. Agile delivery Hands-on in a SAFe or Scrum environment — PI Planning, backlog refinement, sprint ceremonies, velocity and burndown interpretation. Technology literacy Working understanding of at least one stack in scope (.NET, Java/JEE, SharePoint Online/M365, Mainframe or Data/BI) and of API/integration-led architectures. Data & reporting SQL for data validation and ana
Key Responsibilities
4. Must-have skills and experience
Skill area What we expect
Business analysis Requirement elicitation, user-story writing, process modelling (BPMN/UML), gap and impact analysis, functional design documentation.
Agile delivery Hands-on in a SAFe or Scrum environment — PI Planning, backlog refinement, sprint ceremonies, velocity and burndown interpretation.
Technology literacy Working understanding of at least one stack in scope (.NET, Java/JEE, SharePoint Online/M365, Mainframe or Data/BI) and of API/integration-led architectures.
Data & reporting SQL for data validation and analysis; comfort with Power BI or Qlik-style reporting to evidence delivery and quality metrics.
ITSM & tooling ServiceNow, Jira or Azure DevOps for demand, incident and backlog management; Confluence or SharePoint for documentation.
Service transition Experience taking applications through transition into managed delivery, with structured KT, playback validation and readiness sign-off.
Communication Ability to hold a clear, evidence-led position with senior client stakeholders and to work effectively across distributed onsite–offshore teams.
5. Good to have
• Manufacturing, automotive or aftermarket domain background.
• Exposure to product lifecycle, parts management, warranty, service-contract or commercial-operations processes.
• CBAP, PMI-PBA, SAFe POPM or Certified Scrum Product Owner certification.
• AI and Copilot-assisted requirement drafting, backlog analysis and documentation generation.
• Familiarity with COTS and SaaS product landscapes alongside custom-developed applications.
6. Behavioural expectations
• Evidence-led — forms conclusions from data and documented process, not assumption.
• Documents as they learn; treats specifications and run books as living assets, not transition artefacts.
• Challenges vague demand constructively and drives scope to a testable, agreed definition.
• Coaches and cross-skills peers to remove single-analyst dependency risk.
7. Success measures — first 90 days
Window Expected outcome
Days 1–30 Complete KT for the assigned applications with sign-off; publish the validated functional landscape and interface map; establish working cadence with the client DPOs.
Days 31–60 Run a groomed, ready-state backlog two to three sprints ahead; deliver the first set of user stories through to UAT sign-off; close open functional clarifications from transition.
Days 61–90 Demonstrate independent delivery at Perform-phase entry — requirement quality (low rework and defect leakage), on-time PI objective delivery and a completed reverse walkthrough.
8. Interfaces
Client Digital Product Owner (DPO) and DPAO community, Value Stream Managers and Customer Success Managers; HCLTech Digital Engineering delivery leads, Solution Architects, Scrum Masters and engineering pods; QA and test teams; Change, Release and Problem Management; the incoming SRE pod