Engineer first. Everything else followed.
It started in 2013 with Enemy of the State and an unreasonable need to know how the technology worked. C came first, then Computer Science at KNUST. By 2014 I was writing production code, and I haven't really stopped.
what I care about
Systems should survive their worst day
Systems earn their keep when the queue backs up, the provider times out, and the retry storm starts. I design for that day first.
The gap between working and scaling is architecture
Boundaries, contracts, observability, and decision records that explain the why. Closing that gap is most of my job.
The team outlives the codebase
Being the strongest engineer in the room is easier than making the room strong. Past a certain headcount it stops being about mentorship and starts being about systems: how people get hired, how they get promoted, how decisions get recorded, and what happens when I am not in the meeting.
technical focus
Leading engineering
30+ engineers, directly and indirectly, across multiple concurrent clients. Hiring, mentoring, promotion frameworks, and the operating rhythm that keeps several teams shipping at once.
Strategy & engineering sales
Technical strategy for multi-year programmes, and the commercial side of engineering: scoping, work breakdown, fixed-price proposals, and delivery plans I then have to stand behind.
Backend architecture
Microservices, event-driven & domain-driven design, high-performance APIs built to take a hit and keep running.
Infrastructure & ops
AWS, Azure, Docker, CI/CD, and observability with ELK and Prometheus. Deliberately boring, which is the point.
Fintech & compliance
Money movement with exactly-once semantics, ISO 27001 led from inside an engineering team, central-bank licensing.
Security & governance
Dependency and vulnerability remediation across polyglot codebases, ASVS Level 2, SBOM generation, and delivery under separation-of-duties and reviewer-attestation requirements.
$ cat leadership.md
Things I have written for the org rather than the codebase.
- 01
A five-level career progression and promotion framework for an engagement-based consultancy, forking into IC and management tracks at L4.
- 02
I sit on our AI Training Committee, helping shape an internal AI Engineering programme for software engineers: foundation models, prompting, RAG, agents, evaluation and observability, plus the practical projects, coursework, CPD and study-group machinery that turns a curriculum into something engineers can actually apply.
- 03
I chair an engineering culture committee. Hackathons, demo days, meetups, and the unglamorous scheduling that makes them happen.
off the clock
I keep a running list of the books, videos, and people that shape how I think. Pushed straight from the command line, naturally.