I lead DevOps and Platform Engineering initiatives, shaping architecture and delivering solutions that scale.
My work helps organisations improve delivery confidence, reduce operational drag, and build stronger foundations for change. Hands-on where needed, architectural where it matters.
Tooling in context
Tools are only useful when they support a delivery model. This is the stack I tend to group around the platform outcomes a team actually needs.
Account, network, platform, and runtime foundations that teams can build on without reinventing the baseline.
Infrastructure and release paths that make changes easier to review, promote, recover, and explain.
Signals, scripts, and service patterns that help teams own what they ship after deployment.
Delivery Lifecycle
This is usually the shape of the work: clarify the problem, design the right solution, build the platform foundations, automate the delivery path, and leave teams with something they can run confidently without crossing their fingers first.
How I Help
The technical work matters, but the commercial point is simpler: improve delivery speed, reduce avoidable platform friction, and leave teams with foundations they can keep using after the project has stopped being everybody's favourite topic in Slack.
Platform Strategy and Architecture
Shape cloud and platform decisions that balance speed, resilience, governance, and the reality of how delivery teams actually work.
Cloud Foundation Delivery
Build reusable AWS and GCP foundations that reduce setup overhead, standardise delivery, and make new environments faster to stand up and easier to operate.
DevOps Improvement and CI/CD Enablement
Improve pipelines, release paths, and delivery controls so teams can ship more confidently without turning every deployment into a group trust exercise.
Platform Standards and Team Enablement
Introduce reusable patterns, operating guardrails, and clearer ways of working that improve developer experience without losing sight of risk, supportability, or cost.
Selected projects
These projects reflect the blend I work in most often: DevOps and Platform Engineering with clear ownership across leadership, architecture, and delivery, so the result is not just well designed but commercially useful, adopted by teams, and actually shipped.
Tier 1 Bank Platform Enablement
Led DevOps and Platform Engineering direction for a complex banking environment through reusable patterns, stronger standards, and a more coherent path from architecture to delivery, reducing duplication across teams and improving release consistency.
Outcome: one shared Terraform and Kubernetes delivery baseline, adopted across multiple delivery teams, with DORA metrics brought into the delivery conversation.
Remittance/Fintech Start Up Cloud Foundation and EKS Build-Out
Architected and delivered AWS platform foundations for cloud transition work, balancing solution design, DevOps control points, and a delivery model that helped product teams move faster on a stronger baseline.
Outcome: delivered 4 core AWS building blocks, VPCs, EKS, transit gateways, and peering, to give product teams a usable platform foundation faster.
Telecommunications Company Data Platform and Self-Service Tooling
Combined platform architecture and self-service DevOps tooling to reduce operational drag and make infrastructure rollout more scalable, repeatable, and easier for teams to own without constant intervention from the same few people.
Outcome: improved 3 delivery layers at once, data workflows, monitoring, and self-service deployment tooling, so rollout work became more repeatable and less manual.
Sector Reach & Platform Capability
The environments have varied, but the pattern is familiar: take a delivery problem that is part architecture, part platform, part DevOps, and turn it into something teams can actually operate, scale, and justify commercially without needing a sacrificial spreadsheet and a hopeful Slack thread.
Sector map
Delivery experience across regulated, high-change, consulting-led, and pharmaceutical environments where platform decisions need to balance speed, controls, and a realistic path for teams to work well.
Platform Capability Matrix
The markers show where I typically operate: helping shape direction, defining the architecture, building the thing properly, and leaving teams with working patterns rather than another well-meaning slide deck.
Cloud
I typically work across the full cloud lifecycle here: shaping landing zones, defining account structure, and helping delivery teams build on something that is stable rather than improvised.
Experience Timeline
The progression moves from core DevOps automation into broader Platform Engineering, solution architecture, and delivery leadership, with each role carrying more responsibility for direction, commercial outcomes, and execution. Fewer shell scripts, more strategic decisions, but still plenty of shell scripts.
Capco | Senior DevOps Engineer / DevOps Lead
London | Jul 2021 to present
Led DevOps and Platform Engineering direction for delivery teams by strengthening engineering standards, reusable patterns, and the architecture behind change-to-release workflows, helping teams deliver more consistently at scale.
WorldRemit | DevOps Engineer
London | Apr 2020 to Jul 2021
Built core AWS foundations and helped shape a DevOps and Platform Engineering delivery model where platform controls and solution design supported faster, safer change and reduced environment setup drag for product teams.
Accenture | DevOps Engineer / Consultant
London | Jan 2019 to Apr 2020
Worked across consulting engagements with a consistent focus on clarifying architecture, improving platform usability, and creating DevOps delivery approaches that teams could sustain, adopt quickly, and get commercial value from.
Capgemini | DevOps Engineer
Telford | Apr 2017 to Jan 2019
Built early infrastructure and automation foundations that introduced more structured DevOps thinking, stronger platform habits, and more repeatable delivery practices with less manual overhead.
Recognition, Certifications & Education
A few concrete credibility markers alongside the hands-on work: industry recognition, current cloud certifications, and the formal computer science foundation behind the delivery experience.
Computing DevOps Excellence Awards 2025 Finalist
Finalist for DevOps Rising Star of the Year, recognising delivery impact, platform leadership, and the kind of DevOps work that leaves teams with a calmer platform and fewer pipeline dramas.
Education
BSc (Hons) Computer Science
Additional certification
AWS Solution Architect Associate
Google Associate Cloud Engineer
Certification aligned with practical GCP delivery work across infrastructure, services, and operations.
AWS Certified Cloud Practitioner
Foundational AWS certification covering core cloud concepts, platform services, and operating principles.
AWS Certified AI Practitioner
Foundational AWS AI certification covering practical AI concepts, services, and responsible adoption.
Useful links and shareable profile
If you are here for the quick version, start with the public profile. If you want the fuller story, LinkedIn is the best place to continue the conversation. I keep the complete CV off the open internet, but the essentials are still easy to review, share, and follow up on.
Public resume
The polished, shareable version: who I am, the platform problems I solve, and the delivery strengths that usually matter before a first conversation.
Full CV by request
The complete version is available for relevant roles and proper conversations. I prefer to share the detailed timeline when there is useful context, not leave it floating around forever.
GitHub
A look at the hands-on side: public repositories, experiments, infrastructure work, and the occasional reminder that tidy engineering usually starts with untidy problems.
The broader professional picture: role history, sectors, recommendations, and the easiest route to start a sensible conversation without guessing which inbox I am watching.