Principal Engineer - Customer Engagement Platform

Position

Principal Engineer – Dynamics, Power Platform, Workflow & Colleague Experience Engineering at Scale

Hours:

35 hour per week

Closing Date:
Fri, 24 Apr 2026

Skipton is the fourth largest building society in the UK, proudly mutual, owned by our members not shareholders. We aim to do the right thing for our customers and colleagues. People say Skipton is a great place to work and it is recognized as the happiest place to live in Great Britain.

The Customer Engagement Platform (CEP) powers how Skipton understands, supports, and communicates with its members and colleagues. It underpins our Dynamics 365 CRM, Power Platform solutions, case management, workflow automation, marketing capabilities, and the suite of colleague‑facing tools that enable thousands of interactions every day. As a Principal Engineer for CEP, you will set the engineering tenets, patterns and paved roads that enable these systems to operate with high performance, high reliability and high trust, ensuring colleagues can serve members with clarity, confidence and speed.

CEP enables the CRM, workflow and marketing automation that shape thousands of interactions every day. As these journeys scale in complexity and ambition, Skipton needs an engineering system capable of delivering fast, safe, frequent change while ensuring the platform remains resilient, compliant and deeply reliable. The Principal Engineer owns the physics of delivery: low lead time, high deployment frequency, low change‑failure rate and rapid recovery.

By defining tenets, paved roads and guardrails, you allow teams to move with speed and confidence, turning high‑performance delivery into a normal, repeatable capability that compounds over time.

• Define and standardise the Golden Path for CEP: establish secure‑by‑default, policy‑as‑code CI/CD for Dynamics and Power Platform solutions, set patterns for progressive delivery and automated rollback/forward‑fix, and provide reusable service blueprints and deployable modules that make fast, safe delivery repeatable across squads.
• Architect for reliability, observability and flow: codify API/event contracts, workflow orchestration patterns and dependency baselines; instrument release‑linked observability with deployment annotations, traces and golden signals; embed SLOs/error budgets to guide Value‑Flow‑Quality improvements.
• Make on‑demand environments & data the default: champion ephemera ls, production‑like environments and data‑on‑demand (masked/synthetic/seeded), enforce parity and drift detection, expose environment readiness signals so CRM, workflow and low‑code changes can ship in small, safe batches with confidence.
• Shift‑left quality and security: embed contract, performance, resilience and security tests in CI; enforce push‑protection, SAST/SCA/DAST and SBOM provenance; evolve compliance‑as‑code guardrails that balance speed with safety across Dynamics 365, Power Apps and Power Automate solutions.
• Lead the CEP modernisation roadmap: drive decoupling, core refactoring, resilience uplift and tech‑debt retirement, clarify versioned boundaries and platform contracts, enabling product teams to move independently while the platform remains coherent, reliable and easy to consume.
• Operational excellence and recovery: run failure‑mode testing and recovery drills; tighten MTTR via playbooks and telemetry; ensure incident/problem management generates audit‑ready evidence and lasting improvements across CEP’s stacks.
• Coach, multiply and raise the bar: mentor Staff/Senior engineers, lead Communities of Practice, publish reusable CEP templates, shape the hiring bar, use decision narratives to improve clarity and judgement across engineering and platform teams.
• Work backward from colleagues and members: use journey data, case telemetry and colleague feedback to invent on their behalf, ensuring CRM, workflow and automation capabilities feel simpler, faster and more human.