What I build in EdTech & Learning Platforms

Multi-source data consolidation

Learner records sit across VLEs, e-portfolio platforms, internal databases, and SharePoint spreadsheets. Bringing them into a single coherent view, without forcing every consuming system to know about every source, is harder than it looks.

Ofsted and compliance readiness

Inspections move faster than software roadmaps. EdTech platforms need to surface progress, off-the-job hours, and supervisor visibility in time for inspection windows, not the next major release.

Apprenticeship progress calculation

Period-based benchmarks, off-the-job hours, e-portfolio assessments, and breaks all feed into RAG status. The calculation logic is more product than plumbing, and it has to match what tutors and clients already see in their existing reports.

Legacy VLE integration

Established VLEs were not built for deep linking, modern SSO, or partial UI takeovers. Integrations have to respect what the VLE owns and avoid forking workflows that staff already rely on.

Authentication across systems

Learners, tutors, and supervisors typically authenticate against separate identity providers. SAML, OIDC, and Auth0 have to be wired together so users do not lose context as they move between dashboards and underlying tools.

Real-time vs batch data freshness

Some data sources expose APIs, others only ship overnight CSVs. Designing the platform so the user experience does not silently suffer when a feed is a day stale is a recurring product question, not just a technical one.

Apprenticeship Platforms

Apprenticeship learner dashboards and progress engines

I have designed and led the build of greenfield apprenticeship platforms covering learner dashboards, progress engines, and integrations with OneFile, internal LMS platforms, and legacy VLEs. The work spans architecture, data mapping across multiple sources, and the period-based progress calculations that drive RAG status for tutors, supervisors, and clients.

VLE Integration

VLE and e-portfolio integration

Most learning platforms outlive the technology they were originally built on. I integrate with Drupal-based VLEs, OneFile, and bespoke learner record systems through SAML SSO, deep linking, and database-backed adapters, so newer dashboards can sit alongside older systems without a rip-and-replace migration.

Multi-Service Development

.NET Aspire for learning platform teams

Learning platforms typically end up as a small constellation of services: dashboards, progress engines, ingestion jobs, and cached data. I use .NET Aspire to give teams a true F5 development experience across the whole ecosystem, including SQL, Blob storage, and Redis, so developers can run the platform locally as one piece rather than mocking half of it.

AI-Augmented Discovery

Claude Code-led discovery and delivery

Greenfield EdTech projects often start with several unfamiliar third-party platforms and a tight inspection deadline. I use Claude Code through discovery to reverse-engineer APIs, derive component libraries from design screenshots, and produce data mappings the team can verify before any production code is written, and continue using it through the delivery itself.