PLATFORM RELIABILITY01
A platform with a lot riding on it.
Keeping a large online platform running across Nigeria, the UK, and Ireland.
165+services supported
Hello, I’mSRE · DevOps · Platform · Cloud
CLOUD · PLATFORM · RELIABILITY
Good systems.
Quiet nights.
I build the systems that keep your business moving.
And make life a little calmer for the people behind them.
Cloud & platform engineerSoftware engineer. Cloud builder. Problem solver.▶ Meet me in 43 seconds
FIG. 01 — A DATA PLATFORM, IN MINIATURE
Less firefighting. More forward motion.↓
Experience across
real-world complexity.
Automotive
Telecommunications
Online platforms
Geospatial systems
IN MY OWN WORDS
A face.
A voice.
A way of working.
Meet the person behind the platform. A short introduction to the work, the thinking, and what comes next.
The story follows the page as you scroll. Sound is your choice.
A quick introduction43 SEC
0:00 / 0:43
The systems behind the tools — and the engineer behind the systems.
Recovery footage is illustrative · Pause or dismiss at any time
01 / SELECTED WORK
Complex underneath.
Simple where it matters.
A few things I’ve helped build and keep running.
The outcome first. The engineering one click deeper.
SOFTWARE THAT REACHES PEOPLE02
Built for the people on the other side.
Turning customer needs into software and platforms people can rely on.
100k+users served by applications
CLOUD & INFRASTRUCTURE03
A stronger foundation. Fewer surprises.
Operating cloud infrastructure with repeatable environments and reliable recovery practices.
50+AWS EC2 instances managed
Scale figures from my professional experience. Context and scope are included in each technical story.
02 / A SMALL DEMONSTRATION
Things break.
The next part matters.
A good system notices. A better system recovers.
See the idea in action, in under ten seconds.
All services healthyINTERACTIVE SIMULATION
Field data FlowingPlatform HealthyReports Up to date
Go on. Give it a little chaos.This is the idea: systems that can look after themselves.
Scripted demonstration of a recovery pattern. No live services are interrupted.
03 / GO A LITTLE DEEPER
The story.
Behind the system.
Some work belongs in a conversation. Ask for a guided walkthrough of the problem, the architecture, and the decisions along the way.
Private material is shared only with permission. Repository access comes after we’ve spoken.
Personal access · 72-hour links when a tour is available04 / WHEN THE PLAN CHANGES
Calm is an
engineering practice.
How I think through a difficult day.
Illustrative scenarios, explained in plain English.
A release goes wrong.
A new release fails its health check. Customers could lose access if traffic reaches it. Keep traffic on the healthy version and roll the release back. Add the failed condition to release checks.
Demand suddenly spikes.
Traffic outgrows the available capacity. People wait longer, and some requests time out. Restore capacity while checking the actual bottleneck. Test realistic demand and alert before saturation.
A backup needs to work.
A service loses access to its primary data. Recovery time becomes time the business cannot operate. Follow the recovery plan and verify the restored data. Rehearse restoration instead of trusting a green backup job.
05 / THE HUMAN PART
Good with systems.
Here for the people.
My work has taken me from virtual infrastructure and internal applications to customer systems and large cloud platforms. The thread through it all: understanding what people need, then building something they can rely on.
01
Make the complex understandable.Experience working with clients, product owners, architects, and technology leaders.
02
Share what you learn.Mentoring engineers, documenting decisions, and building shared ownership.
03
Build for the whole lifecycle.From the first requirement to deployment, support, and the next improvement.
LET’S BUILD SOMETHING THAT LASTS.
Your next chapter.
My next good problem.
Tell me what you’re building. I’ll bring the engineering.
Choose your role. Get the relevant experience.