Winfred Kagendo.

Senior Frontend & Product Engineer.

I architect scalable frontend, mobile, and AI product systems that turn ambiguous business problems into maintainable software.

Based in Nairobi · Frontend architecture, product engineering, AI integrations

About Me

I own product surfaces where frontend architecture, business constraints, and user experience meet.

Winfred Kagendo

I am a Product and Frontend Engineer based in Nairobi with 5+ years across AI, fintech, healthcare, SaaS, and mobile. My work spans React, Next.js, TypeScript, React Native, design systems, performance, accessibility, and AI integrations, with the emphasis on engineering decisions that help teams ship durable products.

Learn More

Experience

My Journey

Experience

Frontend & Mobile Engineer

Supernomics

Jan 2026 – Present

Contributed to monorepo-based AI product architecture, using shared package boundaries to keep web, mobile, and product workflows maintainable as the system expands.
Delivered a React Native and Expo mobile delivery decisions where cross-platform parity, release speed, and API integration quality mattered more than isolated screens.
Owned a shared component library to reduce repeated UI implementation and make product surfaces easier for engineers to extend consistently.
Translated Figma requirements into production web and mobile interfaces while clarifying API contracts and interaction edge cases before they reached implementation risk.

React.jsReact NativeTailwind CSSExpoMonorepos

Mobile Engineer

Nesti

Aug 2025 – Jan 2026

Delivered mobile UI implementation quality by turning Figma specifications into production interfaces with attention to platform constraints and interaction detail.
Owned an Alipay mini app to production, balancing mini-app platform limitations with the product requirement for a complete mobile experience.
Integrated product APIs across mobile flows, tightening frontend and backend expectations around data shape, loading states, and error handling.

React NativeAlipay Mini AppFigmaAPI Integration

Frontend Engineer

Leja

Jul 2024 – Oct 2025

Chose server-side rendering for business-critical pages where faster perceived loading, indexability, and retention mattered more than a purely client-rendered implementation.
Owned a Safaricom mini app by aligning Ant Design Mini patterns with product requirements, API contracts, and the commercial need to support sales workflows.
Converted Figma systems into responsive React and MUI interfaces while preserving reusable patterns instead of one-off page implementation.
Raised frontend security quality by accounting for XSS and CSRF risks in the browser layer before sensitive flows reached production.
Improved SEO readiness through rendering and metadata decisions that made product pages more discoverable and easier to maintain.

React.jsNext.jsMUIAnt DesignSEO

Frontend Engineer

Oaknet Business

2023 – 2024

Owned frontend implementation for a SaaS monitoring and evaluation system, coordinating UI requirements with backend teams so product workflows mapped cleanly to data contracts.
Improved the investment appraisal experience by translating complex domain workflows into clearer interface states and interaction paths.
Used Vue 3 and Pinia to keep state management explicit in data-heavy flows where predictable updates were more important than local component convenience.
Integrated GraphQL APIs in ways that aligned query shape with screen-level needs, reducing unnecessary frontend data handling complexity.

Vue3.jsPiniaGraphQLJavaScript

Frontend Developer

Pathology Network

May 2023 – May 2024

Owned creation of reusable React interface patterns that reduced development time by 30% and improved team efficiency by 20% across repeated healthcare product workflows.
Used React Query for server-state heavy screens where caching, loading states, and refetch behavior needed clearer ownership than component-local state.
Balanced Tailwind CSS and Material UI implementation choices to preserve design consistency while keeping delivery practical for the team.
Clarified requirements with cross-functional partners during Agile delivery so healthcare features shipped with fewer late-stage interpretation gaps.

React.jsTailwindCSSReact QueryMaterial UI

Case Studies

Projects

View all

Reverse-Engineered Notion Architecture Study

Offline-First Engineering

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 study