Software engineer, Nairobi

I'm the engineer founders call when a product needs to actually happen.

I work as an embedded technical and product partner to founders and business owners: understanding the problem, making the calls, building what matters, and staying accountable until it ships.

Victor Mbashia
VM

Working with

  • Founders shaping a product from a rough idea
  • Teams stuck on a technical bottleneck
  • Businesses that need someone to just own it
Currently: partnering on a therapy-booking platform, an event-ticketing system built for zero downtime, and a heritage platform for the diaspora.

What I actually do

Not just someone who writes code.

Most engineers wait to be told what to build. I sit closer to the business, understanding why a decision matters, weighing the trade-offs with you, and taking ownership of moving the product forward, not just the ticket in front of me.

4
Years in production
20+
Products shipped
15+
Founders partnered with
4
Technical essays published

How I work

The same four steps, every engagement.

This is the order I actually work in, not a values poster. Skipping the first two is how products end up technically correct and strategically wrong.

01

Understand

Sit with the business logic, the users, and the constraints before touching a line of code.

02

Decide

Make the technical and product calls so you're not refereeing every detail yourself.

03

Build

Ship the smallest thing that actually moves the goal, not the most impressive one.

04

Own it

Stay accountable for the outcome, watch what breaks, and fix it before you have to ask.

Selected work

Four products, four different bottlenecks.

A short note on each: the problem I was brought in to solve, and what I actually did about it.

Case 01

Nyumbani

Product & engineering lead · Elixir / Phoenix

Nyumbani is a heritage-led platform reconnecting second and multi-generation Kenyans in the diaspora with Kenya: its culture, its stories and its people. I worked on this from the concept stage, shaping the product before building the MVP end to end. A personalised profile, a curated library of heritage and contemporary stories, a directory for diaspora communities and events, a homecoming experiences layer, and a section connecting the diaspora to opportunities back home.

ElixirPhoenix LiveViewPostgreSQL
Visit nyumbani.victormbashia.com →
Case 02

Sema

Full-stack build · Elixir / Phoenix

Sema needed a way to connect people with licensed therapists: individuals, couples and organisations, without the booking process feeling clinical or confusing. I built the platform end to end: virtual session scheduling, tailored intake flows for different needs, and a resource library, all designed to hold up under real emotional weight, not just look good in a demo.

ElixirPhoenix LiveViewPostgreSQL
Visit semawebapp.com →
Case 03

Asake Kenya

Ticketing platform · Elixir / Phoenix

An event-ticketing and artist-promotion platform where the real risk wasn't the UI. It was checkout failing under real demand. I built multiple ticket tiers, live availability tracking, and a payment flow that stays reliable when a lot of people try to buy the same thing at the same time.

ElixirPhoenixJavaScript
Visit asakekenya.com →
Case 04

Kabeberi Sevens

High-availability system · Mwamba Rugby

A ticketing system for Mwamba Rugby's events, where thousands of fans hit the site in a short window before kickoff. I built for that specific failure mode: zero downtime under a traffic spike, instant digital tickets, and a checkout that doesn't buckle when everyone shows up at once.

ElixirPhoenixJavaScript
Visit mwambarugby.com →

Who this works for

Best said plainly.

Good fit

This works well when:

  • You have a real business problem and need someone who can turn it into a working product.
  • You want a technical partner who pushes back, not just a pair of hands.
  • You're comfortable trusting decisions to someone who takes ownership of the outcome.
Not a fit

This isn't the right fit if:

  • You already have a fixed spec you want followed exactly, with no input.
  • You're looking for the cheapest hourly rate rather than a partner who cares about getting the right outcome.

Get in touch

Tell me what you're building.

Email me directly. A couple of lines on the problem you're facing is enough to start. I'll read it properly and reply myself.

What happens next

  1. I read your email and reply within a day or two, usually with a couple of questions.
  2. We get on a short call to talk through the problem and whether I'm the right fit.
  3. If it makes sense for both of us, we agree on scope and I get to work.