Integration & Data Architect

VE3
City of London
2 months ago
Applications closed

Related Jobs

View all jobs

Enterprise Data Architect

Senior Data Architect

Data Architect

Data Architect

Data Architect

Data Architect

Integration & Data Architect

Location: City of London, England, United Kingdom


Role Purpose

The Technical, Integration & Data Architect will serve as the single technical authority evaluating shortlisted SaaS ERP platforms. The role will assess solution architecture, systems integration, security alignment, and data migration feasibility, ensuring reliable integration with the existing enterprise landscape, compliance with security and data‑sovereignty requirements, and safe, auditable migration of financial data from legacy systems.


Responsibilities

  1. Technical Architecture Assessment

    • Evaluate core technical architecture of shortlisted ERP platforms, including cloud‑native design, SaaS operating model, extensibility, configuration boundaries, scalability, resilience, and availability.
    • Assess alignment with enterprise architecture principles and cloud security best practices.
    • Identify architectural constraints, assumptions, and long‑term risks.


  2. Integration Capability and Tooling

    • Evaluate maturity and suitability of APIs (REST, event‑driven, bulk interfaces), ETL and data‑integration tooling, and middleware or iPaaS options.
    • Define and evaluate integration proofs of capability for key interfaces: exchange of financial journals, patterns for near‑real‑time vs batch, error handling, retries, reconciliation, monitoring, and operational support.


  3. Security, IAM, and Data Sovereignty

    • Assess alignment with security & compliance expectations: SSO, role‑based access, least privilege, encryption, key management, platform controls, logging, monitoring, auditability.
    • Confirm data‑residency and data‑sovereignty compliance, and identify risks and mitigations.


  4. Data Migration and Legacy Transition

    • Assess feasibility of migrating financial data (opening balances, historical transactions, reference and master data).
    • Review migration approaches: data mapping, transformation, validation, reconciliation, cutover strategy, rollback plan, and platform support.


  5. Proofs of Capability and Evidence Review

    • Define objectives and success criteria for integration and data proofs.
    • Evaluate vendor submissions against technical realism, operational robustness, prior use evidence, and challenge unsupported assertions.


  6. Scoring, Risk Identification, and Governance

    • Score candidate solutions against agreed criteria.
    • Document assumptions, exclusions, dependencies, risks.
    • Provide input into overall solution scoring and recommendation, and contribute to the System Selection Report with defensible technical rationale.



Key Deliverables

  • Technical architecture assessment inputs and scored evaluation matrices.
  • Defined integration proof and data proof criteria.
  • Assessment of integration feasibility and risks.
  • Data migration feasibility assessment and risk log.
  • Contributions to the final System Selection Report.

Required Skills and Experience

Essential



  • Proven experience as Technical Architect, Integration Architect, or Data Architect.
  • Hands‑on experience integrating SaaS ERP platforms with enterprise systems.
  • Expertise in API‑based and ETL‑based integration patterns.
  • Experience designing or assessing ERP data migration strategies.
  • Knowledge of cloud security, IAM, and data‑protection principles.
  • Objective evaluation and clear evidence documentation.

Desirable



  • Experience with Tier‑1 SaaS ERP platforms (Dynamics 365 Finance, SAP S/4HANA Public Cloud, Oracle Fusion, Unit4 ERPx).
  • Experience in regulated or security‑conscious environments.
  • Experience supporting formal system‑selection or procurement exercises.

Key Competencies and Behaviours

  • Technically rigorous – probes beyond surface architecture diagrams.
  • Evidence‑led – prioritises demonstrable capability over vendor claims.
  • Risk‑aware – identifies integration and data risks early.
  • Clear communicator – explains technical findings to non‑technical stakeholders.
  • Governance‑conscious – understands auditability and decision traceability.

Benefits

  • Work on cutting‑edge technologies and impactful projects.
  • Opportunities for career growth and development.
  • Collaborative and inclusive work environment.
  • Competitive salary and benefits package.

Referrals increase your chances of interviewing by 2x.


#J-18808-Ljbffr

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

How Many Data Science Tools Do You Need to Know to Get a Data Science Job?

If you’re trying to break into data science — or progress your career — it can feel like you are drowning in names: Python, R, TensorFlow, PyTorch, SQL, Spark, AWS, Scikit-learn, Jupyter, Tableau, Power BI…the list just keeps going. With every job advert listing a different combination of tools, many applicants fall into a trap: they try to learn everything. The result? Long tool lists that sound impressive — but little depth to back them up. Here’s the straight-talk version most hiring managers won’t explicitly tell you: 👉 You don’t need to know every data science tool to get hired. 👉 You need to know the right ones — deeply — and know how to use them to solve real problems. Tools matter, but only in service of outcomes. So how many data science tools do you actually need to know to get a job? For most job seekers, the answer is not “27” — it’s more like 8–12, thoughtfully chosen and well understood. This guide explains what employers really value, which tools are core, which are role-specific, and how to focus your toolbox so your CV and interviews shine.

What Hiring Managers Look for First in Data Science Job Applications (UK Guide)

If you’re applying for data science roles in the UK, it’s crucial to understand what hiring managers focus on before they dive into your full CV. In competitive markets, recruiters and hiring managers often make their first decisions in the first 10–20 seconds of scanning an application — and in data science, there are specific signals they look for first. Data science isn’t just about coding or statistics — it’s about producing insights, shipping models, collaborating with teams, and solving real business problems. This guide helps you understand exactly what hiring managers look for first in data science applications — and how to structure your CV, portfolio and cover letter so you leap to the top of the shortlist.

The Skills Gap in Data Science Jobs: What Universities Aren’t Teaching

Data science has become one of the most visible and sought-after careers in the UK technology market. From financial services and retail to healthcare, media, government and sport, organisations increasingly rely on data scientists to extract insight, guide decisions and build predictive models. Universities have responded quickly. Degrees in data science, analytics and artificial intelligence have expanded rapidly, and many computer science courses now include data-focused pathways. And yet, despite the volume of graduates entering the market, employers across the UK consistently report the same problem: Many data science candidates are not job-ready. Vacancies remain open. Hiring processes drag on. Candidates with impressive academic backgrounds fail interviews or struggle once hired. The issue is not intelligence or effort. It is a persistent skills gap between university education and real-world data science roles. This article explores that gap in depth: what universities teach well, what they often miss, why the gap exists, what employers actually want, and how jobseekers can bridge the divide to build successful careers in data science.