Projects

Services and infrastructure I helped lead as a consultant.

Digital Assessment Service (opens in new tab)

Reception Baseline Assessment (RBA) · Standards and Testing Agency

Senior Developer, later Technical Lead

I helped build the digital platform behind the Reception Baseline Assessment for the Standards and Testing Agency. I started as Senior Developer and later became Technical Lead. I worked through the Item Validation Trial (IVT) and Technical Pre-Test (TPT). The RBA is an early maths and literacy assessment given in the first weeks of reception, and it’s the starting point for measuring progress through primary school.

The service covers the full school journey: registering pupils, preparing devices, pairing practitioner and pupil sessions, running the assessment, and producing narrative statements. Reliability and accessibility mattered as much as features. Schools need something that works in a real classroom, not just in a demo.

Scale showed up early. IVT covered about 1,500 pupils and around 9GB of event data. TPT covered about 3,000 pupils and generated about 30GB for item analysis. Each ran over a two-week September window, in different years. Those phases sat ahead of live national assessment (around 800,000 pupils).

We focused on secure Azure services, clear paths for schools and support staff, and engineering practices that could keep a national assessment moving as policy and tech changed.

Education Benchmarking and Insights (opens in new tab)

Financial Benchmarking and Insights Tool (FBIT)

Principal engineer, technical lead and technical architect

I led the ground-up build of this service. I set the technical direction across data, platform, and presentation: architecture, hands-on engineering, and the coordination needed to turn a broad data product into something schools could actually use.

It gives schools one place to manage and understand their financial data. Benchmarking lets them compare with similar schools. Insights help them dig into the numbers and spot better ways to plan. Practical evidence, not another spreadsheet pile.

The architecture splits ingestion, processing, APIs, and presentation. A Python pipeline loads CSV and Excel into Azure SQL. .NET Azure Functions expose REST APIs. An ASP.NET Core portal uses Vue and shared React/TypeScript charts. Infrastructure, migrations, pipelines, and ops analytics sit around that.

That split keeps processing repeatable, visualisations reusable, and ownership clear. School leaders, governors, and trustees get better information without having to assemble the analysis themselves.

Accessing Childcare Entitlement Checker (opens in new tab)

Principal engineer, technical lead and technical architect

I led the ground-up build of this service: architecture and delivery from early design through to something production-ready. The aim was a solid foundation teams could extend without painting themselves into a corner.

It helps parents and carers in England check eligibility for childcare support, including 15 and 30 hours of funded childcare and Tax-Free Childcare. Complex policy, turned into a journey people can actually follow.

We also put in automated integration and cross-browser testing, security scanning, technical docs, architecture decisions, and runbooks. That made the service easier to operate and evolve, and gave the team a shared view of the design and the risks.

Custom Checkov Policies (opens in new tab)

Technical lead for the infrastructure policy initiative

I led the work to shift infrastructure policy left. Compliance checks became part of delivery, not a late review. We codified expectations, wired them into CI, and gave teams feedback while they were still changing their infrastructure.

The repo has custom Checkov policies, examples, and CI integrations for scanning Azure infrastructure-as-code across Department for Education landing zones, including CIP and ELZ. Cloud security and platform rules, turned into automated checks teams can run consistently.

It gives policy rules, docs, and contribution practices a shared home. The roadmap extends that to more landing-zone rules, Bicep, and other artefacts like ARM templates, Dockerfiles, and workflow definitions.

Catching gaps earlier cuts rework. It also makes standards visible and testable, and easier to improve over time.