Selected work

Evidence from systems that needed to become stronger.

Anonymised examples of senior engineering work. Client and system identifiers are withheld where confidentiality requires it; the outcomes and technical work remain specific.

Email Farolum

What these engagements had in common

A real production or delivery constraint
A measurable technical or operational outcome
A controlled path from diagnosis to change
Evidence that could guide the next decision

API performance under real load

A production API had severe latency spikes during peak traffic, expensive database paths and limited visibility into regressions.

Established an APM and log baseline before changing the critical path
Optimised queries, cache strategy and background jobs
Added service-level dashboards and actionable alerts
Outcome: core endpoint P95 moved from approximately 1.8 seconds to below 450ms, with stable errors and visible regressions

Legacy PHP modernisation

A business-critical PHP platform had fragile domains, manual releases and unclear ownership. Delivery could not pause for a big-bang rewrite.

Mapped domains, dependencies and release risk
Introduced incremental migration boundaries and tests
Moved critical paths through controlled release phases
Outcome: critical modules were isolated and monthly high-risk batches became smaller, safer weekly releases

Mobile release reliability

A React Native product experienced crash spikes after releases and slow startup on older devices.

Analysed crash clusters and release history
Profiled startup paths and removed bottlenecks
Strengthened instrumentation and the release checklist
Outcome: crash-free sessions moved from roughly 96% to above 99%, with repeatable release checks

Next step

Your system deserves a diagnosis before a promise.

Tell us what is at risk. We will help identify the most sensible place to start.

Confidential by default. We reply within two business days.

Explore next

Technical assessment Application performance Software modernisation