Integration Technical Analyst

Expected Integration Documentation

Depending on the integration, the analyst should be capable of producing or maintaining:

• Integration requirements specifications
• Epics, features and user stories
• Acceptance criteria
• Context and integration flow diagrams
• Interface catalogues
• API/interface specifications
• Event/message definitions
• Source-to-target data mapping specifications
• Transformation and translation rules
• Reference-data and code mappings
• Business validation rules
• Error and exception matrices
• Retry and recovery requirements
• Reconciliation requirements
• Non-functional requirements
• Security and access requirements
• Logging, monitoring and alerting requirements
• Dependencies, assumptions, constraints and outstanding questions
• Requirements traceability

Inputs And Access Required

To perform the role effectively, the analyst will require appropriate access to existing technical information and environments. This should include, where available:

• Documentation for existing integrations
• System manuals, vendor documentation and training materials
• Technical architecture information covering servers, databases, services and integration components
• Details of relevant user and service accounts
• Access to suitable non-production or replica environments
• Access to relevant source code, configuration and implementation artefacts
• Appropriate access to secrets, certificates, API keys and credentials where required for authorised analysis or testing
• Access to APIs, databases, message queues, topics, file locations and other integration endpoints
• Access to logs, monitoring dashboards and diagnostic information
• Representative and appropriately controlled test data
• Existing interface specifications, schemas and data dictionaries
• Vendor and third-party support contacts
• Named technical owners and system owners for each participating platform
• A defined escalation route where documentation, system behaviour or vendor support is insufficient

Typical Deliverable Standard

The expected outcome is not simply a high-level statement such as:

"Student attendance data must be transferred from System A to System B."

The analyst should be able to take that requirement through to sufficient detail to establish:

• what business event initiates the integration;
• which system is authoritative for each piece of data;
• what message or interface is invoked;
• what data is extracted;
• how source attributes map to the target;
• which transformations or translations are applied;
• what validation occurs;
• how reference data is resolved;
• what constitutes successful processing;
• what constitutes a business rejection;
• what constitutes a technical failure;
• what is retried automatically;
• what requires manual intervention;
• how failures are surfaced and supported;
• how processing can be reconciled;
• and how the completed integration can be objectively accepted and tested

The role therefore requires an analyst who is comfortable moving continuously between business process, requirements, data and integration technology rather than handing technical definition entirely to a downstream development team.

Requirements

The successful candidate should have strong experience of integration analysis rather than solely general-purpose business analysis.

Essential experience includes:

• Requirements elicitation with both business and technical stakeholders
• Writing detailed user stories and testable acceptance criteria
• Producing source-to-target data mappings
• Analysing APIs, database structures, messages, files and other integration interfaces
• Defining transformation, translation and validation rules
• Documenting business and technical exception scenarios
• Understanding asynchronous and synchronous integration patterns
• Familiarity with Enterprise Service Bus (ESB), canonical data models and event-driven integration
• Understanding concepts such as publish/subscribe, request/reply, queues, topics, message routing, correlation, retries and dead-letter handling
• Ability to analyse existing implementations rather than relying solely on greenfield requirements
• Ability to read and interpret technical documentation, API definitions, database schemas, configuration and logs
• Confidence working directly with integration developers, solution architects, infrastructure teams and application specialists
• Ability to communicate technical concepts clearly to business stakeholders and business requirements clearly to technical teams

Higher Education Experience

Experience within Higher Education would be highly desirable, particularly integrations involving systems or processes such as:

• Student Records Systems
• Timetabling and scheduling
• Attendance and engagement monitoring
• Virtual Learning Environments / Learning Management Systems
• Student portals and mobile applications
• Identity and access management
• Admissions and enrolment
• Module and programme data
• Student, staff and organisational data
• Assessment and results
• Learning analytics
• Room and resource management

The analyst should ideally understand that Higher Education integrations frequently involve shared entities such as students, staff, modules, programmes, academic periods, teaching activities, locations, enrolments and attendance events, with ownership of individual data domains distributed across several systems.