Alex Ndungu

Co-Founder + CTO

Let's talk
HomeAboutExperienceProjectsSkillsContact
Let's talk
HomeAboutExperienceProjectsSkillsContact

Alex Ndungu

Backend systems, machine learning retrieval, and clean product-minded engineering for teams that care about reliability.

GitHubLinkedInLeetCodealexmeta517@gmail.com
Portrait of Alex Ndungu
About

Engineering with system clarity, product intent, and durable architecture.

I care about building software that earns trust in production: systems with clean boundaries, understandable behavior, and room to evolve.

I'm a founder, software engineer, and machine learning engineer with experience across informatics systems, fintech workflows, and applied ML projects that focus on retrieval, recommendation, and operational intelligence. I run CodePinion as Co-Founder and CEO, and serve as Co-Founder and CTO of Harlem Manage. Building both has deepened how I think about multi-tenant architecture, product strategy, and the realities of shipping a real operating system for a domain instead of a narrow feature set.

My work spans production informatics at Savannah Informatics, financial backend workflows from fintech environments like E&M Tech, and proptech system design through Harlem Manage. That mix has shaped a strong bias toward reliability, access control, financial correctness, and software that respects the operational context it lives in. I'm currently learning Elixir and Phoenix, drawn to the BEAM for exactly those concurrency and fault-tolerance properties.

Both companies are built on the same conviction: that African software and property teams deserve infrastructure designed for how they actually operate, not a Western product with a local coat of paint. That shows up in the architecture — M-PESA as a native payment rail rather than a bolt-on, and AI built as a governed, role-aware execution layer inside the product rather than a chat box beside it. I am building both to last.

Education

BSc Computer Science

Dedan Kimathi University of Technology

Engineering philosophy

Systems thinking

I design software by tracing how data, infrastructure, and user needs move through a system end-to-end before writing implementation detail.

Engineering philosophy

Scalability by default

From API boundaries to schema design, I favor decisions that keep complexity manageable as products, teams, and traffic grow.

Engineering philosophy

Data-driven design

I like systems that are observable, measurable, and explainable so product decisions can be grounded in how the software actually performs.