Work

How the problems were actually worked.

Three case studies, structured around the reasoning instead of the responsibilities. What the problem was, how it was approached, and what it produced.

Meta · Dublin: 2020–2022
Facebook Developer Circles · Nairobi: 2018–2020
VituMob · Nairobi: 2016–2020

Meta · Dublin
2020–2022
Dublin, Ireland
Operating between developers and everything that had to move for them
200+ escalations a month across six platforms, held at a 95% resolution rate. Built triage and routing systems instead of absorbing more volume.
App Review & Developer Support Specialist, later Project Manager
Read the case study
Facebook Developer Circles · Nairobi
2018–2020
Nairobi, Kenya
Running a 3,000-developer community as a volunteer, with a full-time job
One of Africa's largest Developer Circles chapters, built to run without me. At 3,000 people nothing person-dependent survives.
Community Lead
Read the case study
VituMob · Nairobi
2016–2020
Nairobi, Kenya
Taking over a production system in a language I did not write
An Android developer inheriting a JavaScript Chrome extension that connected Kenyan shoppers to US retailers, then owning it, extending it, and supporting the customers when it broke.
Software Developer & Product Support Specialist
Read the case study

What I take on

The problems behind the work

Operations that don't scale

The process worked at ten people and is quietly breaking at forty. Nobody decided to change it. It just stopped holding.

Execution that stalls

Work dies in the gaps between teams. Everyone is busy, nothing is landing, and nobody owns the handoff.

Technology you can't use

You bought the tools. Nothing is connected, the numbers disagree with each other, and nobody trusts the dashboard.

You are the bottleneck

Everything routes through you, because almost nothing is written down. Taking a week off would cost more than it's worth.

How we work together

Three things you can actually buy

Detail

Mission Control

Installed · fixed scope

You are the only person who knows what is actually happening.

Process automation

Fixed scope · built and handed over

One repeatable job is eating your team's week.

Build sessions

A few hours a week

You want the thing built, with your team in the room.

Background

Technical foundation and the record

I don't present myself as a full-time software engineer today. But I wrote production code for a decade, and it is why I can read an API, follow an architecture discussion, understand what a constraint costs, and tell a hard technical problem from an organisational one wearing a technical costume.

Worked in

Java · JavaScript · PHP · Laravel · SQL

Built across

Mobile development (Symbian, Android)
Browser extensions
Web scraping & third-party integrations
E-commerce systems : payments, checkout, logistics
Platform APIs & developer tooling
Data analysis & reporting

Roles, as held

Mobile development training
2010
eMobilis Technology Academy
Mobile development program
2012
mLab East Africa
Developer Intern
2013
Kubamba Krew
Software Developer & Product Support Specialist
2016–2020
VituMob
Community Lead
2018–2020
Facebook Developer Circles Nairobi
App Review & Developer Support Specialist → Project Manager
2020–2022
Meta
Business Operations
2024
TEEL Beauty
Operations & executive operations
2022–now
Independent

Taking on new builds.

Work is scoped and fixed-term. You get a system built and handed over, not a seat filled.

Start a conversation

Operating between developers and everything that had to move for them

Running a 3,000-developer community as a volunteer, with a full-time job

Taking over a production system in a language I did not write