Job Title: Product Business Analyst
Department: Product
Location: Hybrid (split between Kingston Upon Thames office and home-working)
Country: UK
Level: Individual Contributor
Reports to: VP Product
Contract Type: Permanent / Full-time
Contracted Hours/Days: 37.5 hours / 5 days per week
About Us
At Reveal, passion meets purpose. Our body-worn video solutions are more than just technology; they're a testament to our commitment to safety, innovation and change. Rooted in the UK, we've become a trusted ally for many police forces, local authorities, retailers and private organisations; helping to pioneer and drive the application of body-worn video in settings and geographies where we can see exciting potential. With an influence now spanning over 40 countries, our mission to make a positive impact continues to gain momentum.
Purpose of the Role
The purpose of the Product Business Analyst role is to strengthen the Product function by translating customer needs, product strategy, and technical requirements into clear, testable documentation for software, firmware, and QA teams. The role ensures that product behaviour, workflows, and requirements are well understood across teams, supporting consistent delivery and helping maintain high product quality.
Key Responsibilities
The following outlines the principal responsibilities of the role. This list is not exhaustive and may be updated to reflect business needs, provided it remains aligned with the overall purpose of the position.
Requirements & User Stories (Software & Firmware)
- Ensure backlog items are well‑defined, prioritisation‑ready, aligned to product goals and meet agreed definitions of readiness before entering development.
- Break down high‑level product initiatives into epics, user stories, and clearly scoped deliverables.
- Lead the creation of detailed user stories and acceptance criteria for software and camera firmware development.
- Translate hardware PRDs and system constraints into supporting software and firmware requirements.
- Define functional and non‑functional requirements, including edge cases and error handling.
Development & Testing Collaboration
- Work closely with Software Development and QA teams to clarify requirements and resolve questions.
- Support test planning by ensuring acceptance criteria are clear, complete, and testable.
- Assist with defect triage by documenting expected behaviour and reproduction steps.
Product Documentation
- Document existing (“as‑is”) and future (“to‑be”) product behaviour.
- Produce workflow diagrams, state flows, and interface descriptions to support development and testing.
- Act as a central point of reference for product behaviour and feature definitions.
- Help draft release notes ensuring they accurately reflects delivered functionality and known limitations.
- Maintain clear records of behavioural changes across product versions.
Customer Feedback & Service Delivery Interface
- Support the collection and analysis of customer feedback and customer experience insights for incorporation into structured requirements.
- Work with Service Delivery to triage support issues and log defects requiring development.
Team Relationships
- Work under the direction of the VP Product, supporting product strategy and delivery.
- Collaborate closely with Software Development and Testing teams.
- Interface with Sales Engineering to understand customer usage patterns and feedback.
- Support cross‑functional alignment by ensuring shared understanding of product behaviour.
Health and Safety
- Comply with all company Health & Safety policies and procedures.
- Support product safety activities through accurate documentation and requirement definition where applicable.
Learning and development
- We encourage continuous professional development and support learning through on-the-job experience, feedback and access to relevant training opportunities. You are expected to take ownership of your development and maintain up-to-date knowledge of sector trends, technology and best practice relevant to your role.
Qualifications, Skills and Experience
Essential
- 3–5 years’ experience as a Business Analyst or Product/Technical BA within a SaaS or technology-led environment
- Demonstrable experience writing high-quality user stories and acceptance criteria for software delivery teams
- Proven ability to translate high-level product strategy into detailed, structured requirements
- Experience working in Agile/Scrum environments with cross-functional engineering and QA teams
- Experience documenting both functional and non-functional requirements
- Strong ability to break down complex problems into clear, structured deliverables
- Comfortable working across Product, Engineering, QA, Sales Engineering and Service Delivery
- Able to manage upwards effectively by providing clarity, progress updates and structured recommendations
- Works effectively with developers and testers to ensure shared understanding
- Strong communication and interpersonal skills, with the ability to build effective working relationships.
- Demonstrates a growth mindset, with adaptability, curiosity and a commitment to continuous improvement.
- Strong emotional intelligence, including self-awareness, empathy and sound judgement.
Desirable
- Bachelor’s degree in Business, Computer Science, Information Systems or related discipline
- Experience working with hardware-software integrated products
- Familiarity with compliance-driven or regulated environments
- Experience using tools such as Azure DevOps
- Exposure to firmware or embedded systems environments
Key Metrics for Success
The key metrics to be successful in this role are:
1. Requirements Quality & Readiness
- % of backlog items meeting agreed Definition of Ready before entering development
- Reduction in requirement-related rework or clarification during sprint execution
- Low incidence of requirement-related defects post-release
2. Delivery Effectiveness
- Stories delivered within sprint without requirement-driven blockers
- Acceptance criteria consistently testable and aligned with QA outcomes
- Clear documentation available ahead of development start
3. Cross-Functional Alignment
- Positive feedback from Engineering and QA on clarity and completeness of requirements
- Reduced ambiguity and fewer clarification cycles during development
- Strong working relationships across Product, Engineering and Service Delivery
4. Product & Customer Impact
- Structured incorporation of customer feedback into documented requirements
- Improved traceability between customer need, requirement and delivered feature
- Accurate release notes reflecting delivered functionality
5. Continuous Improvement
- Ongoing refinement of documentation standards and templates
- Contribution to improved Product processes and backlog hygiene
- Maintenance of clear records of behavioural changes across product versions