Technical Business Analyst – APIs & Systems Integration
Turn complex ideas into solutions teams can build. Join the insurance sector for our client and make an impact from day one, with a clear 90-day journey from learning key systems to leading feature analysis and helping shape MVP scope.
What is in it for you:
- Salaried: $72-82 per hour.
- Incorporated Business Rate: $83-93 per hour.
- Hybrid schedule, 37.5 hours per week.
Responsibilities:
- Learn how systems interact end to end, including services, APIs, integrations, data handoffs, and related business processes.
- Draft sequence diagrams with architects and engineers showing interactions, call order, payloads, and agreed behaviours for errors, timeouts, and retries.
- Raise unresolved design questions for architects and engineers to address.
- Help define data contracts, including fields, formats, required and optional elements, validation rules, and examples.
- Build and maintain workflow diagrams, including swimlanes, documenting decision points, handoffs, and exception paths for active features.
- Work with the Product Owner and architects to break features into user stories with clear Given, When, and Then acceptance criteria.
- Capture non-functional requirements, including performance, security, and auditability, as testable criteria based on targets established by architects and risk and security partners.
- Identify gaps, assumptions, dependencies, and risks early, and maintain traceability from business needs through stories and tests.
- Help the Product Owner, architects, and engineers identify the smallest scope that delivers the product outcome.
- Recommend thin, end-to-end slices, explain trade-offs, and document work deferred to later releases once scope is agreed.
- Flag MVP shortcuts that may create technical debt or conflict with the target architecture.
- Participate in refinement, sprint planning, design reviews, and demos.
- Run discovery sessions and walkthroughs and document decisions.
- Help QA translate acceptance criteria into test scenarios and answer developers' questions during sprints.
What to expect in your first 90 days:
- First 30 days: Learn the systems, build working relationships with the Product Owner and architects, and map one key end-to-end flow.
- By 60 days: Own analysis for a feature, from architecture walkthrough to sequence diagrams, data contracts, and sprint-ready stories reviewed by the Product Owner.
- By 90 days: Lead analysis for an agreed feature stream, including helping scope its MVP.
What you will need to succeed:
Required qualifications
- 3+ years of experience as an IT Business Analyst, Systems Analyst, or in a similar role on software delivery teams.
- 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 using tools such as draw.io, Lucidchart, Visio, Miro, PlantUML, or Mermaid.
- Comfort reading and drafting request and response payloads, such as JSON, and field-level data definitions.
- 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.
Preferred qualifications
- Experience with REST APIs, event-driven or message-based systems, or microservices.
- Exposure to API specifications, such as OpenAPI or Swagger, basic SQL, or logs.
- Familiarity with UML or BPMN, Jira, and Confluence.
- Experience in banking, financial services, or another regulated industry.
- Experience with products delivered across web and native mobile platforms, including iOS and Android.
Soft skill
Why Recruit Action?
Recruit Action (agency permit: AP-2504511) provides recruitment services through quality support and a personalized approach. As part of the screening process, some applications may be reviewed using artificial intelligence tools. Only candidates who meet the hiring criteria will be contacted.