Integration Technical Analyst
Role Overview
Analyse, define and document data integrations between enterprise systems.
Work between business analysis and integration or solution analysis, partnering with business SMEs and technical teams.
Take integrations from business requirements through implementation-ready specifications.
Key Skills for This Role
Full Job Posting
Location and engagement
- Remote work with occasional travel to High Wycombe.
- Three-month engagement starting as soon as possible.
- Pay rate is £450–£500 per day; outside IR35.
About PACT Solutions
Specialist consultancy supporting UK higher education institutions with strategy, digital transformation and operational change.
Role purpose
Analyse, define and document data integrations between enterprise systems.
Work between business analysis and integration or solution analysis, partnering with business SMEs and technical teams.
Take integrations from business requirements through implementation-ready specifications.
Key responsibilities
- Facilitate workshops and interviews with business and technical stakeholders, system owners and vendors.
- Elicit functional and non-functional requirements; write implementation-ready user stories and acceptance criteria.
- Analyse existing integrations, system configuration, documentation and implementation artefacts; document end-to-end flows.
- Define requirements for APIs, messaging, queues, files, databases and other integration mechanisms.
- Create source-to-target mappings covering fields, attributes, formats, defaults, transformations, translations, validation and filtering.
- Define event and message behaviour, dependencies, sequencing, correlation, idempotency and retries where applicable.
- Specify exception handling, errors, reconciliation, recovery, logging, monitoring, alerting, operational support and security requirements.
- Resolve ambiguity with developers and integration engineers; support test preparation and defect triage.
- Maintain traceability between business requirements, specifications, mappings and delivered functionality.
Expected documentation
May produce or maintain integration specifications, epics, features, user stories, acceptance criteria, flow diagrams and interface catalogues.
Documentation may include API and event definitions, data mappings, transformation and translation rules, validation rules and exception matrices.
Other expected artefacts include recovery, reconciliation, non-functional, security, access, monitoring and traceability requirements, plus dependencies, assumptions and open questions.
Inputs and access
- Requires access to available integration documentation, system manuals, vendor documentation, training materials and technical architecture information.
- Access should include relevant user and service accounts and suitable non-production or replica environments.
- Where required and authorised, analysis or testing may need access to source code, configuration, implementation artefacts, secrets, certificates, API keys and credentials, as well as APIs, databases, queues, topics and file locations.
Apply for this job in 1 click
Skip the repetitive application forms
Install the Base Career Chrome Extension and autofill job applications across major job boards with your profile.
Trusted by over 500,000 job seekers on Base Career