No invented metrics
When an exact figure is confidential or unavailable, I describe the technical change instead of manufacturing a percentage.
Engineering case studies / 01—03
Engineering decisions, shown in context.
Three close accounts of systems I worked on: what was brittle, what I changed and what became easier to run. Company names stay private. The technical scope does not.
00 / NOTE
P01 P02 P03
Work worth explaining.
A stack list tells you very little. These case studies focus on the decisions behind the code, the constraints around them and the result that could be supported in day-to-day use.
Decisions before tools
The technology matters, but only after the problem and the trade-off are clear.
Names withheld, work intact
Organisations and commercial details are omitted. The engineering scope is kept specific.
All case studies01—03
CASE / 01
AI workflow platform cloud migration.
A multi-component document-processing platform relied on environment-specific deployments. I moved its infrastructure and delivery model to reusable Terraform, GKE and managed Google Cloud services.
CASE / 02
Archival workflow management.
I built a Spring service and React microfrontend around a Camunda process so operators could manage archival sessions, packages and workflow state in one focused slice.
CASE / 03
Retail ERP maintenance and evolution.
I worked across SQL Server, .NET and the frontend of a business-critical retail ERP, improving performance, integrations and day-to-day reliability as one connected system.
Have a system that needs a clearer path forward?
Bring the difficult part. We can work through the architecture, delivery plan and first useful release together.