Winfred Kagendo / Engineering Lab - Nairobi
A software engineer with a frontend heart.
A working archive of systems I'm designing, assumptions I'm testing and products I'm shipping across frontend, backend and UX.
05+
Years building products
03
Active experiments
10+
Mentees
Product and Frontend Engineer in Nairobi. 5+ years shipping across AI, fintech, healthcare, and mobile. I care about the system and the human using it.
Learn More“How do I stop someone from abusing an API?”
Well... that escalated.
Case Studies
Token-First Design System — Audit Layer Planned
A frontend architecture case study for ComponentIQ: why the plan started as a docs-and-AI-assistant monorepo, why the shipped v1 became a token-first design system and component library instead, and what a future automated audit layer still needs from that foundation.
Read case studyReverse-Engineered Notion Architecture Study
An independent engineering case study explaining why caching a page is not the same as making it available offline, using Notion's offline architecture to reason about dependency guarantees, provenance, hierarchy reconciliation, and freshness.
Read case studyAI-Assisted Job Search — In Progress
A Next.js application that integrates Claude AI for resume tailoring and job fit evaluation. An exploration of what happens when you treat AI as a tool inside a real product instead of a standalone chat interface.
Read case studyPick a problem
Select a problem below and see how my thinking escalates.
“Why does every payment flow feel fragile?”
How do you build trust when money is on the line?
7 nodes in this path • Click any node to learn more
Payment UX
“She sees the relationship between the interface and the system underneath it.”
I'd rather understand why something works than memorize how to do it.
curiosity → fundamentals → depth
I'm increasingly convinced everything becomes a system if I zoom out far enough.
patterns → architecture → mental models
If I click a button, eventually I'm going to wonder where the state lives, where the request goes, and what happens when it fails.
UI → frontend systems → infrastructure
I don't think technically correct software is very useful if the person using it is confused.
system behaviour → interface → UX
If an architecture only works when everything behaves perfectly, I probably have more questions.
The interface is where product decisions, system behaviour, and human expectations eventually meet.
product → systems → humans
Sometimes the better engineering decision is removing the abstraction I was excited to build.
One question is rarely enough. Most of my rabbit holes start with "Wait... but what happens if?"
I'd rather understand why something works than memorize how to do it.
curiosity → fundamentals → depth
I'm increasingly convinced everything becomes a system if I zoom out far enough.
patterns → architecture → mental models
If I click a button, eventually I'm going to wonder where the state lives, where the request goes, and what happens when it fails.
UI → frontend systems → infrastructure
I don't think technically correct software is very useful if the person using it is confused.
system behaviour → interface → UX
If an architecture only works when everything behaves perfectly, I probably have more questions.
The interface is where product decisions, system behaviour, and human expectations eventually meet.
product → systems → humans
Sometimes the better engineering decision is removing the abstraction I was excited to build.
One question is rarely enough. Most of my rabbit holes start with "Wait... but what happens if?"
My Journey
Striking the balance between speed and engineering tradeoffs — how architectural decisions shape the user experience at scale.
Whether it's a full product build, a mobile app, or a tricky frontend challenge — I'm interested. I respond within 24 hours.
