Technical Business Analyst (ITBA)
JOB SUMMARY
This role is part of Engineering, embedded with the engineering team, reporting through engineering leadership, and working alongside architects, developers, and QA every day, in close partnership with the product owner. The position supports 2 squads working on banking initiatives, across web, Android, and iOS. This role bridges the gap between architecture and business requirements, identifying the smallest technical scope that meets product goals, and making complex systems clear enough for everyone to understand. It ensures that details are not lost between the architect's design and the stories developers pick up, closing gaps that might otherwise lead to rework, defects, or stalled work. The role supports online banking systems across Web, iOS and Android platforms, sitting between Solution Architects and Developers, bridging the gap between solution design and development. It is responsible for understanding user stories, end-to-end system interactions and data flows, and translating them into technical documentation, with a focus on sequence diagrams, workflows, technical user stories, API specifications and data contracts. This is a stepping stone towards architectural work.
Key Responsibilities
• Learn how our systems interact end to end: services, APIs, integrations, data handoffs, and the business processes around them.
• Draft sequence diagrams with architects and engineers that show who calls whom, in what order, with which payloads, and the agreed behavior for errors, timeouts, and retries.
• Raise unresolved design questions for decision.
• Help scope and define data contracts: fields, formats, required vs. optional, validation rules, and examples.
• Build workflow diagrams, including swimlanes, that show decision points, handoffs, and exception paths.
• Keep diagrams for the features you support current while that work is active.
• Work with the product owner and architects to break features into user stories with clear Given / When / Then acceptance criteria.
• Capture non-functional requirements (performance, security, auditability) as testable criteria.
• Find gaps, assumptions, dependencies, and risks early, and keep requirements traceable from business need to story to test.
• Help the product owner, architects, and engineers identify the smallest scope that delivers the product outcome.
• Recommend thin, end-to-end slices and explain the trade-offs.
• Document what moves to later releases once scope is agreed with the Product Owner and architects.
• Flag when MVP shortcuts might create technical debt or conflict with the target architecture.
• Take part in refinement, sprint planning, design reviews, and demos.
• Run discovery sessions and walkthroughs, and record decisions so the team doesn't have to repeat old discussions.
• Help QA turn acceptance criteria into test scenarios and answer developers' questions during the sprint.
• Independently create sequence diagrams and system workflows.
• Understand system interactions, integrations and data flows.
• Document technical requirements for development teams.
• Interpret existing API documentation and draft technical API specifications, including OpenAPI specs.
• Identify the appropriate type of diagram required for a particular solution.
Required Qualifications
• 3+ years as an IT Business Analyst, Systems Analyst, or in a similar role on software delivery teams.
• The ability to read a system or integration flow and explain it step by step, in plain language.
• Hands-on experience creating sequence diagrams and workflow diagrams in tools such as draw.io, Lucidchart, Visio, Miro, or PlantUML/Mermaid.
• Comfort reading and drafting request/response payloads (for example, JSON) and field-level data definitions.
• A track record of writing user stories and acceptance criteria that developers can build from and QA can test against.
• Experience breaking features into incremental releases and explaining scope recommendations, dependencies, and trade-offs to product and engineering partners.
• Clear writing and facilitation skills.
• Comfort working inside an engineering team.
• Curiosity to keep asking "and then what happens?".
• Strong diagramming skills.
• End-to-end solution understanding.
• Technical user story writing.
• Understanding of REST APIs, API calls, GET/PUT operations and API documentation.
• Technical background (prior development experience is ideal; alternatively, strong experience working closely with developers and architects).
• Self-starter who can work independently with minimal guidance.
Preferred Qualifications
• Experience with REST APIs, event-driven or message-based systems, or microservices.
• Some exposure to API specs (for example, OpenAPI/Swagger), basic SQL, or logs.
• Familiarity with UML or BPMN, and with Jira and Confluence.
• Experience in banking, financial services, or another regulated industry.
• Experience on products delivered across web and native mobile (iOS/Android).
• Mobile application transformation experience.
• Experience working on or delivering MVPs.
• Familiarity with Lucidchart or Mermaid for diagramming.