Work map
Projects grouped by what they prove.
This is not only a timeline. The point is to show the kinds of systems I can understand, repair, extend, and own, and why those examples matter for future backend work.
Reading order
Start with the proof closest to the job.
Current target
STS is the strongest proof for modern .NET backend roles: clean ownership, domain rules, auth, tests, and deployment.
Hard-system experience
UCCP shows work inside a large legacy system where the useful skill was making progress without ideal architecture or ideal deadlines.
Public-sector repairs
Government Services groups smaller but important work: migrations, auth fixes, framework updates, and a data-leak fix.
Case studies
Different systems, different proof.
Unified Contact Center Platform
A large emergency-service platform where the useful work was making a difficult system buildable, extendable, and shippable under real constraints.
Proves: Legacy modernization, pressure handling, and extending a large public-service system without clean-room conditions.
State Probation Service
A from-scratch backend for a public-service assessment system, with versioned tests, JSON scoring rules, explicit errors, auth, and deployment ownership.
Proves: Modern backend ownership: architecture, domain rules, tests, auth, deployment, and explicit failure contracts.
Government Services
Backend rescue work across public-sector services: project-template migration, auth stabilization, framework upgrades, and a data-leak fix.
Proves: Practical rescue work in systems already in motion: migration, stabilization, framework updates, and scoped security fixes.