Technical Business Analyst

About Us

At Resonate, we're on a mission to embed intelligent, connected technology into the operational fabric of railway operations, driving performance, efficiency, and innovation across the network. Our vision is bold yet clear: to be the trusted partner, leading the modernisation of railway operations through purposeful innovation. We're not just building technology; we're building the future of how railways run. We measure our success by the "Resonate Test", the moment when every Route and Operations Team says, "We couldn't run the railway without Resonate" and "Have you asked Resonate?"

becomes the go-to question for technology solutions. That's the impact we're striving for, and we're looking for talented individuals who share our passion for making it happen. If you're ready to be part of something transformative, where your work directly enables safer, smarter, and more efficient rail operations, we'd love to hear from you.

The Technical Business Analyst role, embedded within Software Development requires strong analytical thinking, a good understanding of software delivery and excellent communication and focus. You will take ownership of turning complex operational and technical needs into clear, build-ready specifications, working closely with Product, Design and Development teams. The focus of this role is not strategy definition, but technical clarity, traceability, and execution quality.

• Requirements are complex, interdependent and evolving
• Functional and non-functional considerations are equally critical
• Technical trade-offs must be made explicitly and documented clearly
• Delivery quality has real operational consequences

This role is suited to candidates who are comfortable working at detail level, owning requirements end-to-end and ensuring development teams can build with confidence.

2. Translation of Business Needs into Technical Narratives

3. Analysis, Root Cause & Problem Solving

4. Specification & Delivery Enablement

5. Traceability, Change Control & Quality

• Requirements Ownership & Technical Definition
• Create and own the requirements capture for software development, working closely with product, stakeholders and development teams to align development with business priorities
• Apply a range of elicitation techniques, including interviews, workshops, site visits, surveys and storyboards to build a deep understanding of operational and technical needs
• Take accountability for the quality, completeness and clarity of requirements throughout the delivery lifecycle
• Translate business and technical requirements into clear, detailed project narratives, ensuring shared understanding across engineering and product functions
• Define and document the who, what and why of each requirement, including acceptance criteria, information flows, business processes and data structures
• Ensure both functional and non-functional requirements are explicitly captured and understood
• Conduct structured root cause analysis on complex problem areas, identifying underlying issues rather than treating symptoms
• Engage cross-functional teams throughout the project lifecycle to gather insight, validate understanding and shape effective technical solutions
• Refine project narratives into comprehensive technical specifications, using appropriate techniques such as:
• Use cases
• Behaviour‑Driven Development (BDD) scenarios
• Process and data flows
• Business rules and data definitions
• Ensure specifications are sufficiently precise to support incremental development, testing and release with minimal rework
• Maintain clear traceability between business objectives, requirements and delivered functionality
• Manage change effectively, ensuring impacts are understood, documented and agreed
• Support delivery teams by responding quickly to clarification needs and ensuring analysis remains aligned to delivery goals

• Strong critical and analytical thinking capability, with the ability to systematically deconstruct complex challenges, including functional and non‑functional requirements, dependencies and downstream impacts
• Demonstrable experience owning…