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, software engineer in Nairobi
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

Every product, a different bottleneck.

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

Nyumbani homepage
Case 01

Nyumbani

Product & engineering lead · Elixir / Phoenix

Helping Kenyans abroad find their way back home.

Problem
Kenyans born or raised abroad had no single place to learn where their family comes from or plan a trip back.
Built
Taken from idea to launch: personal profiles, a library of heritage stories, a diaspora community directory and homecoming trips.
Result
Live in production, shaped and built end to end.
ElixirPhoenix LiveViewPostgreSQL
Visit nyumbanixp.com →
Sema homepage
Case 02

Sema

Full-stack build · Elixir / Phoenix

Online therapy that doesn't feel clinical.

Problem
Booking a therapist felt confusing and cold for people who were already struggling.
Built
Virtual session booking, intake flows for individuals, couples and companies, and a resource library.
Result
A live therapy platform serving individuals, couples and organisations.
ElixirPhoenix LiveViewPostgreSQL
Visit semawebapp.com →
EazyRent homepage
Case 03

EazyRent

Product & platform build · Elixir / Phoenix

Rent collected, every shilling accounted for.

Problem
Landlords tracked rent across spreadsheets, M-Pesa messages and paper receipts.
Built
One system that bills tenants, takes M-Pesa, card and bank payments, and matches every payment automatically.
Result
Month-end reports in one click instead of days of reconciling.
ElixirPhoenix LiveViewPostgreSQLPaystack
Visit eazyrent.biz →
Hopewell Learning homepage
Case 04

Hopewell Learning

Product & platform build · Elixir / Phoenix

One calm home for running online learning.

Problem
Organisations ran webinars across scheduling tools, spreadsheets and scattered video links.
Built
Organisation workspaces, facilitator management, a public session calendar and registration.
Result
Registrations, attendance and payouts tracked in one place.
ElixirPhoenix LiveViewPostgreSQL
Visit hopewelllearning.semawebapp.com →
Asake Kenya homepage
Case 05

Asake Kenya

Ticketing platform · Elixir / Phoenix

Concert ticket sales that held up on launch day.

Problem
When a big show goes on sale, everyone buys at once, and that's exactly when checkout tends to break.
Built
Multiple ticket tiers, live availability and a payment flow built for rush-hour demand.
Result
Checkout stayed reliable through the sales rush.
ElixirPhoenixJavaScript
Visit asakekenya.com →
Kabeberi Sevens homepage
Case 06

Kabeberi Sevens

High-availability system · Mwamba Rugby

Zero downtime when the whole crowd shows up.

Problem
Thousands of fans hit the site in the short window before kickoff.
Built
A ticketing system designed for that spike, with instant digital tickets.
Result
Zero downtime under match-day traffic.
ElixirPhoenixJavaScript
Visit mwambarugby.com →
Chartely homepage
Case 07

Chartely

Product & platform build · Elixir / Phoenix

From charter request to firm quote, without the phone tag.

Problem
Pricing a private flight meant phone calls and back-and-forth before anyone saw a number.
Built
Pick a route and see a rough price instantly, send a request, get a firm quote with the aircraft and timing, then pay and fly.
Result
Customers see a price in seconds and get a firm quote without chasing anyone.
ElixirPhoenix LiveViewPostgreSQL
Visit chartely.victormbashia.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, or book a short call. 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.