Responsibilities

• Extract data from legacy source systems under the direction of the Migration Lead, working to agreed extraction schedules and formats across all in-scope data tracks.
• Profile source data to identify quality issues, missing fields, duplicates, and format inconsistencies, and document findings clearly for review by the Migration Lead.
• Maintain source-to-target data mapping documentation, keeping it up to date as configuration decisions are made in MX.3 or as source system data changes.
• Liaise with legacy system owners and data custodians to understand data structures, resolve extraction questions, and obtain data samples needed for mapping and testing.

• Write and maintain SQL scripts, Shell scripts, and Python routines for data extraction, transformation, cleansing, and loading tasks across assigned migration tracks.
• Execute migration loads into MX.3 staging environments using MxML Exchange import workflows and bulk loading utilities, following the runbook and escalating errors to the Migration Lead.
• Monitor migration job execution, capture error logs, and investigate failed records — categorising issues by root cause and either resolving them directly or escalating with a clear summary.
• Implement data transformation logic as defined in mapping specifications, including cleansing rules, format conversions, defaulting logic, and enrichment from reference data.
• Maintain migration control tables and audit logs to track record-level load status, error counts, and resolution outcomes across each batch run.

• Run reconciliation checks between migrated MX.3 data and source system records at each migration milestone — trade counts, notional values, market values, P&L figures, and static data attributes.
• Investigate reconciliation breaks, trace them back to their source (mapping error, transformation gap, MX.3 configuration issue, or source data problem), and document findings with proposed fixes.
• Apply data quality validation rules within the migration pipeline to catch records that fail business rule checks before they are loaded into MX.3.
• Support the interface reconciliation workstream by validating that data arriving in MX.3 from external systems (nostro, cash positions, collateral) is correctly received, mapped, and represented in MX.3 — noting that these flows are owned by the Integration workstream, not migrated directly.
• Keep the reconciliation log and issues tracker up to date, flagging unresolved breaks to the Migration Lead with enough context for them to make a call.

• Write and execute migration-specific test cases for SIT and UAT, covering record-level accuracy, referential integrity, and MX.3 module behaviour after loading.
• Log, triage, and track defects through to resolution, coordinating with the relevant functional workstream where the fix sits outside the migration pipeline.
• Support business users during UAT migration validation — responding to data queries, pulling validation extracts, and providing root-cause analysis when loaded data doesn’t match expectations.
• Participate in migration dress rehearsals, executing assigned tasks within the cutover runbook and recording timing and outcomes accurately for post-rehearsal review.

• Keep mapping specifications, transformation logic documentation, and data dictionaries accurate and current throughout the programme.
• Contribute to the migration runbook by documenting the steps, inputs, outputs, and known risks for the tasks you own within the cutover sequence.
• Attend daily stand-ups, design reviews, and workstream planning sessions, flagging blockers early and providing clear status updates on assigned tasks.
• Support knowledge transfer activities at the close of the programme, ensuring documented procedures are clear enough for the client’s internal team to follow without needing you in the room.

Requirements

• 5–8 years of experience in data migration, data analysis, or ETL delivery roles within capital markets or financial services, with at least some exposure to Murex MX.3 programmes.
• Hands-on experience working with MX.3 data structures — instruments, counterparties, portfolios, books, trade records — either through migration, configuration, or reporting work.
• Practical experience writing SQL queries for data extraction, validation, and reconciliation; familiarity with Sybase or Oracle in a Murex context is a clear advantage.
• Experience working with ETL pipelines or data transformation scripts in Python or Shell, even if not as the primary developer.
• Some exposure to MxML Exchange import workflows or Murex bulk loading processes is preferred but not mandatory — willingness to learn the detail quickly matters more.

• Bachelor’s degree in Finance, Information Technology, Computer Science, Business Analytics, or a related discipline.
• Formal Murex training in data model or migration-related modules is an advantage.

• SQL (Sybase and/or Oracle) — comfortable writing queries for data validation, reconciliation, and diagnostic analysis without needing to look up syntax.
• Python and/or Shell scripting for data processing, transformation, and batch monitoring tasks.
• Familiarity with the Murex MX.3 data model and FIN schema at a working level — enough to understand what you’re loading and where it will land in the system.
• Experience with scheduling tools (Control-M, AutoSys, or equivalent) for monitoring and executing batch migration jobs.
• Excel proficiency for reconciliation, validation, and ad-hoc analysis tasks; VBA is a plus.