Technical Business Analyst

Our financial services client is seeking a Technical Business Analyst (3+ years) to translate architecture and business requirements into delivery-ready stories using sequence diagrams, data contracts, and workflow diagrams- 17450

Join an engineering-embedded role supporting two squads delivering banking initiatives across web, Android, and iOS. You will close the gap between architecture and development by turning designs and business requirements into clear sequence diagrams, workflow diagrams, data contracts, and sprint-ready user stories. Work day-to-day with architects, developers, QA, and the Product Owner to keep scope focused and delivery unblocked. This is a 6-month contract with an option to renew.

Location: Toronto/Hybrid - 3 Days a Week on Site

Duration: 11/24/2026 to 06/23/2027

Hours: 37.5 Hours Per Week

Must Haves

• 3+ years as an IT Business Analyst or Systems Analyst on software delivery teams
• user stories and acceptance criteria authored with Given/When/Then formats
• sequence diagrams and workflow diagrams created in draw.io, Lucidchart, Visio, Miro, or PlantUML/Mermaid
• request/response payloads (e.g., JSON) and field-level data definitions
• incremental releases scoped with clear dependencies and trade-offs

Nice to Have

• Experience with REST APIs, event-driven or message-based systems, or microservices
• Exposure to API specs (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)

Responsibilities

• Map end-to-end system interactions across services, APIs, integrations, and data handoffs
• Draft sequence diagrams with architects and engineers specifying call order, payloads, and error/timeout/retry behavior
• Define data contracts including fields, formats, required/optional flags, validation rules, and examples, with architect/engineer sign-off
• Build workflow diagrams with swimlanes covering decision points, handoffs, and exception paths
• Break features into user stories with clear Given/When/Then acceptance criteria
• Capture non-functional requirements (performance, security, auditability) as testable criteria
• Recommend thin, end-to-end slices for MVP and document scope deferred to later releases