Product Business Analyst

Start free →

Or apply yourself on the official page →

About the role

About us SFG20 is the industry standard for building maintenance. Providing services and pioneering technologies that empower people to create and sustain safer buildings. Our mission is to make buildings better using our standard, software and expertise. Our vision is to become the leading authority for built environment maintenance that protects and enhances quality of life. About the role The Product Business Analyst bridges the gap between business needs and engineering delivery, turning ideas, requests and requirements into clear, actionable work. By bringing clarity to ambiguity, connecting work across Product and Platform Engineering and making sure teams have the information they need, the role helps reduce rework, improve delivery and build better software for our customers. Key Responsibilities Discovery and shaping • Work with stakeholders to explore ideas, requests and feedback, clarifying the underlying problem, business need and intended outcome before work is defined • Explore the reasons behind requests before work is defined, ensuring relevant context and requirements are understood. • Challenge assumptions constructively, identify gaps and surface conflicting needs or unanswered questions early. • Identify and engage the right stakeholders to provide the information and decisions needed to shape clear requirements. Turning needs into actionable work • Translate business needs into clear epics, features, user stories and acceptance criteria that give engineering teams sufficient context to progress work effectively. • Break down defined or moderately complex initiatives into clear, deliverable increments, working with Product and Engineering colleagues and seeking support on more complex work where needed, • Maintain accurate requirements and supporting context in Jira, including agreed scope, relevant decisions and material changes. • Keep requirements current as understanding or scope develops, working with relevant Product, Engineering and project colleagues to capture what has changed and why. Question resolution during delivery • Remain closely involved during delivery as a point of contact for requirements-related questions and clarification. • Investigate ambiguity, work with the right stakeholders to resolve requirements questions and escalate more complex issues where needed so engineering teams can continue with clear direction. • Participate in refinement and planning discussions where business analysis input is needed to clarify scope, requirements or agreed decisions. • Maintain traceability from the original business need through agreed requirements and material changes to what is ultimately delivered. Integrating product and platform work • Maintain awareness of relevant work across Product and Platform Engineering and identify dependencies, overlaps or potential impacts between teams. • Help shape requirements where product and platform changes need to work together, ensuring relevant dependencies and constraints are understood. • Flag where teams may be addressing the same problem, where proposed changes could conflict, or where work in one area creates an impact elsewhere. • Support effective handovers and cross-team working by ensuring teams have the requirements context and documentation they need. Stakeholder engagement • Build constructive working relationships across Product, Engineering, QA, customer-facing teams and the wider business. • Translate engineering questions and constraints into clear language for business stakeholders. • Translate business needs and agreed intent into precise, actionable requirements for engineering teams. • Help stakeholders understand what has been agreed from a requirements perspective, what remains unresolved and where further inpu

View the official posting →