Dev Ops Engineer

My Money Matters is a leading financial health platform on a mission to help public sector workers make the most of their salary - through education and products like pension top-ups, on-demand pay and automated savings.

Right now, 72% of public sector workers are just one bad month away from financial difficulty. We exist to change that. Through innovative financial products, education, and our digital money coach, we help people take control of their financial future, whether that’s buying their first home, boosting their pension, or planning for retirement. Already trusted by major organisations including the NHS, we’re growing quickly and building a team of ambitious, commercially minded people who want their work to genuinely matter.

We are looking for a hands-on Dev Ops Engineer to build the operational backbone that lets our platform scale with confidence. This is a high-impact, ground-floor opportunity to shape how we monitor, deploy and run our services - putting in place the observability, automation and reliability that turn a fast-growing platform into a resilient one. There is genuine momentum and investment behind this work, and the freedom to make a visible difference quickly.

You will own observability, CI/CD, and the day-to-day reliability of our cloud estate - making releases safe, repeatable and reversible, making the platform’s health visible in real time, and building the automation that lets our engineers ship with confidence. You will also be a key player in our migration off the legacy platform, where a reliable pipeline and solid environments are the foundation everything else depends on.

This is a pragmatic, build-it role for someone with a strong bias to action. You will see the gaps, prioritise the ones that reduce risk fastest, and close them - not write strategy decks about them.

Our Tech

Our systems are built using Web technologies (React, Node.js), with a React Native mobile app published to Android and iOS, deployed on Google Cloud (with Firebase). We use Playwright as our test automation technology, GitHub for source control and GitHub Actions for CI/CD, SonarQube for static analysis, and GCP Vertex for agentic AI. Test maturity varies across the estate - our newer mobile app has strong coverage, while parts of the platform have little or none yet - so there is real scope to raise the bar. We hold ISO 27001 and Cyber Essentials, so reliable, evidenced quality matters here.

What You’ll Do

• Make the platform observable. Build and own monitoring and observability across the estate - metrics, logging, tracing, dashboards and meaningful alerting - so that we detect and diagnose issues before our customers do.
• Set SLOs that matter. Define and own service-level objectives (SLOs) on our critical journeys - starting with the AVC application and payroll - and the alerting that protects them.
• Make releases safe and repeatable. Establish consistent, automated CI/CD pipelines across all repositories: changes pass automated checks, are traceable to source control, deploy predictably, and are reversible. Move us towards safe, near one-click deployments.
• Codify the infrastructure. Bring our infrastructure under Terraform so the environment is reproducible, reviewable, versioned and testable - removing manual, tribal deployment steps.
• Build real environments. Stand up proper local, ephemeral and staging environments with production parity and seeded non-production data, so engineers can build and test with confidence.
• Bake in security. Implement cloud-native secrets management and secrets scanning, and embed SAST, software composition analysis and container/image scanning into the pipeline.
• Make incidents manageable. Establish an incident process that works - detection, ownership, escalation, clear comms, and blameless post-incident reviews - supported by runbooks and operational documentation.
• Prove we can recover. Validate that our backups actually restore, and that our RTOs and RPOs hold up, through regular restore and disaster-recovery testing.
• Underpin the migration. Be a key contributor to the migration off the legacy Ruby on Rails platform, where the CI/CD pipeline, test infrastructure and environments are the first things that must be in place.
• Enable the team. Champion guardrails and automation so that engineering can move quickly and safely without needing manual sign-off for every routine change.
• Work as one team. Be an active, engaged member of the cross-functional agile team - contributing in standups, refinement, planning and retros, and championing quality throughout.