About · Engineering profile
An engineer who builds systems, and has actually run them.
I’m Kennedy Mutisya, a CTO, systems engineer and software architect based in Nairobi. For more than ten years I have designed, scaled and evolved the platforms underneath products that people depend on: communication infrastructure, marketplaces and payments, data and intelligence systems, and the internal tooling that keeps them operable.
What I care about is engineering judgement under real constraints. Systems that are already in production. Businesses that cannot pause. Data that has to move. Failure that has to be survived rather than avoided.
01What I build
Six kinds of systems.
Distributed Systems
Systems that continue working as workloads and complexity grow.
Data-Intensive Applications
Pipelines, analytics systems, data stores and intelligence platforms.
Financial Infrastructure
Payments, wallets, marketplaces, BNPL and transaction systems.
Multi-Tenant SaaS
Systems designed around isolation, scalability and operational reliability.
Communication Infrastructure
High-volume email, SMS and notification systems and asynchronous processing.
Developer Platforms
Internal tools that make complex systems easier to operate and develop.
02How I think
Principles learned by getting them wrong first.
01
Find the bottleneck
Don't rewrite the system because one component is struggling.
02
Make expensive work asynchronous
Queues are not merely an implementation detail. They are a scalability boundary.
03
Give data the right home
MySQL isn't ClickHouse. Redis isn't MySQL. Elasticsearch isn't your source of truth.
04
Design for failure
Providers fail. Workers die. Networks disappear.
05
Evolve instead of rewrite
The best architecture is often the architecture you can introduce without stopping the business.
03Environments
Where I have operated.
2019 to present
Chief Technology Officer · CoAmana
Technical leadership for the platforms CoAmana builds for businesses across Africa: architecture, infrastructure, the engineering team, and the evolution of systems that are already in production.
2014 to 2019
Senior Software Engineer · Untapped Global
Senior engineering role designing and shipping production systems and the practices that keep them running.
Platforms I have architected serve 500K+ users across Africa.
04Problems I enjoy
The shape of work I say yes to.
- A mature system that has started to bind under load nobody planned for.
- Work that is synchronous and needs to become asynchronous without changing what customers see.
- Data living in the wrong store: analytics in the OLTP database, coordination state in tables, truth in a search index.
- Multi-tenant products where isolation, throughput and cost pull in different directions.
- Money moving between parties and providers that fail, retry and report late.
- Teams that need tooling to operate a system they cannot hold entirely in their heads.
05The story
How I got here.
I’ve always been more interested in how things work than in simply using them.
When I was seven, I took apart my family’s first computer to find out what was happening inside. By high school, that curiosity had turned into building software. The pattern has stayed remarkably consistent ever since: understand the system, find the constraints, and figure out how to make it better.
Early in my career, I co-led the development of a SaaS platform that changed how businesses across Africa engaged with their customers. Since then, I’ve worked across product engineering, architecture, infrastructure, and technical leadership, often in systems that were already complex, already serving real users, and couldn’t simply be rewritten.
That experience shaped how I approach engineering.
I care less about whether a technology is fashionable and more about whether it is appropriate for the problem. I think about what should be synchronous and what should become asynchronous. Where data should live. Where the bottleneck will appear next. What happens when a dependency fails. And, perhaps most importantly, what not to change.
Today, as CTO of CoAmana, I work across the boundary between product and infrastructure, building financial, data, and intelligence systems while thinking about the architecture, reliability, and operational decisions that allow them to grow.
I’m particularly drawn to difficult systems problems: high-volume workloads, distributed processing, multi-tenant platforms, data pipelines, developer tooling, and systems that have to keep working when things inevitably go wrong.
I still take things apart to see how they work.
The difference is that these days, I usually put them back together better.
Contact
Building something difficult?
I’m interested in hard engineering problems, ambitious products, and systems that need to work at scale.
Get in touchkenmsh@gmail.com