- Salary
- C$82 – C$92/hr
- Location
- Toronto, Ontario
- Type
- Contract
- Department
- IT
- Seniority
- Mid
- Closing date
- Today
Description
Job Title: Technical Business Analyst (ITBA)
Location: Toronto, ON
Estimated Duration: 7 Months
Description:
Technical Business Analyst (ITBA)
About the role
You turn architecture and business requirements into stories engineering can build, help identify the smallest technical scope that meets product goals, and make complex systems clear enough for everyone to understand.
Where you'll sit and why this role exists
This role is part of Engineering. You'll be embedded with the engineering team, report through engineering leadership, and work alongside architects, developers, and QA every day, in close partnership with the Product Owner. You'll support 2 squads working on banking initiatives, across web, Android, and iOS.
On many teams, details get lost between the architect's design and the stories developers pick up: integration details, data contracts, edge cases, and "what happens when this call fails?" questions. They come back later as rework, defects, or stalled work. You'll close that gap.
Ownership is clear. The Product Owner owns the what and the why, including priorities. Architects own the solution design. You make both buildable: you document how the system works, suggest options, flag gaps, and turn agreed decisions into clear diagrams, data contracts, and stories.
What you'll do
Map how systems work
Location: Toronto, ON
Estimated Duration: 7 Months
Description:
Technical Business Analyst (ITBA)
About the role
You turn architecture and business requirements into stories engineering can build, help identify the smallest technical scope that meets product goals, and make complex systems clear enough for everyone to understand.
Where you'll sit and why this role exists
This role is part of Engineering. You'll be embedded with the engineering team, report through engineering leadership, and work alongside architects, developers, and QA every day, in close partnership with the Product Owner. You'll support 2 squads working on banking initiatives, across web, Android, and iOS.
On many teams, details get lost between the architect's design and the stories developers pick up: integration details, data contracts, edge cases, and "what happens when this call fails?" questions. They come back later as rework, defects, or stalled work. You'll close that gap.
Ownership is clear. The Product Owner owns the what and the why, including priorities. Architects own the solution design. You make both buildable: you document how the system works, suggest options, flag gaps, and turn agreed decisions into clear diagrams, data contracts, and stories.
What you'll do
Map how systems work
- 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 their decision.
- Help scope and define data contracts: fields, formats, required vs. optional, validation rules, and examples. Architects and engineers sign off on the final contract.
- 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. Architects and risk/security partners set the targets.
- 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. Once scope is agreed with the Product Owner and architects, document what moves to later releases.
- 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.
- 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, and the curiosity to keep asking "and then what happens?"
- 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. We don't expect expertise, and we'll support you as you learn.
- 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).
- 30 days: Learn our systems, build working relationships with the Product Owner and architects, and map one key end-to-end flow.
- 60 days: Own analysis for a feature, from architecture walkthrough to sequence diagrams, data contracts, and sprint-ready stories reviewed by the Product Owner.
- 90 days: Lead analysis for an agreed feature stream, including helping scope its MVP. Architects and engineers stay available for design decisions and validation, and the Product Owner and QA review stories.
- Developers start stories with the flows, data contracts, and acceptance criteria they need.
- Architects trust you to represent their designs accurately, and the Product Owner sees their intent in what gets built.
- Fewer stories bounce back mid-sprint for missing details, and fewer defects trace back to unclear requirements or contracts.
Skills
SQLJiraConfluenceiOSAndroidRESTMicroservices