Technical Business Analyst

The Technical Business Analyst translates business needs into specifications that developers and QA can implement and test. The role covers stakeholder discovery, task decomposition, process modelling, API and data contracts, and user stories with Given—When—Then acceptance criteria. The analyst understands how the platform, databases, and integrations work well enough to discuss feasibility with engineering.

Required skills:

Data and databases:

• Understand RDBMS concepts: tables, keys, relationships, constraints, and transactions.
• Explain the difference between SQL and NoSQL: when each is used, consistency versus flexibility, and typical use cases.

• General Transact-SQL: SELECT, filters, joins, and aggregations — enough to validate data and support analysis.

   

APIs and data formats:

• REST principles: resources, HTTP methods, status codes, and request/response contracts.
• General knowledge of SOAP: envelopes, WSDL/XML messages, and when SOAP is still used in enterprise integrations.
• Read and describe JSON and XML structures used in APIs.
• Document field-level payloads, including mandatory versus optional fields, validations, and error responses.
• Inspect API calls in a tool such as Postman.

Authentication and security (analyst level):

• General knowledge of authentication protocols and patterns: sessions, Basic authentication, OAuth 2.0, tokens/JWT, and SSO concepts.

Software architecture (general view):

• High-level understanding of how a product is built: client, API/services, database, integrations, and identity.
• Ability to discuss system boundaries and the impact of a change.

Requirements engineering:

• Active listening and structured note-taking.
• Task decomposition: breaking initiatives into epics and user stories.
• User stories with acceptance criteria in GWT format (Given / When / Then).

 Modelling and documentation:

• UML and/or BPMN (or equivalent) to illustrate business and system flows.
• Sequence diagrams (or equivalent) for integrations, authentication, and similar end-to-end flows.

Nice-to-have knowledge and skills:

• UI/UX principles: information architecture, form validation, empty and error states, and accessibility at a basic level.
• Figma: read designs, comment on gaps, and share feedback with the team.
• Domain experience in lending or fintech.
• Jira and Confluence for backlog management and requirements documentation.

Responsibilities:

• Run discovery sessions with internal and external stakeholders: listen, take structured notes, and turn discussions into a structured backlog.
• Decompose initiatives into feasible tasks.
• Write user stories with testable Given—When—Then acceptance criteria, covering the happy path, edge cases, and failure paths.
• Illustrate business and system flows using BPMN, UML, or equivalent diagrams.
• Analyse and document REST integrations and, where relevant, SOAP integrations: endpoints, methods, payloads, status codes, error handling, and data mapping.
• Use T-SQL to inspect and validate data when needed.
• Specify authentication and authorisation behaviour for features and integrations, including sessions, tokens, and roles.