Lead engineer at Tutorful

Hi, I’m Kim.
I build software.

I help businesses solve problems with software. Tell me what’s getting in the way and I’ll find the simplest fix.

Need a specialist? Laravel is my home ground, with Vue and Flutter alongside. And I build with AI coding agents every day.

  • Laravel
  • Flutter
  • Vue
  • Stripe
  • APIs
  • Testing
  • AI
Plates & Plans · Flutter + Laravel

Selected work

Things I’ve worked on.

Lead Software Engineer · 2018–now

Tutorful

Hands-on engineering on a live tutoring marketplace.

Booking, pricing, Stripe billing, messaging, onboarding, APIs and the admin tools behind them. Lead since 2021.

  • Laravel
  • Vue.js
  • MySQL
  • Stripe
Visit Tutorful

Laravel backend · Fitness app

Strong Girl Society

Took over and stabilised the backend of a fitness app.

Training programmes, recipes, community features, plus Strava and RevenueCat integrations. Finished half-built features and made the whole thing dependable.

Backend only. The React Native app was built by the mobile team.

  • Laravel
  • PHP
  • Integrations
  • Debugging
View the app

Flutter + Laravel · Meal planning

Plates & Plans

Built most of a meal-planning app, front to back.

Flutter screens from supplied designs, Laravel APIs and product logic, and RevenueCat subscriptions.

Screenshots show the released app, which may include changes after handover.

  • Flutter
  • Laravel
  • RevenueCat
  • APIs
View the app
Kim Ward

About me

I like making things simpler.

My favourite part of the job is finding the straightforward way through something complicated.

Laravel is home. I love its conventions, its ecosystem, and how a few well-chosen lines can do a proper job.

Day job: Tutorful, improving a product people use every day. The rest of the time: small tools, side projects and whatever’s caught my attention.

Lately I’ve gone deep on AI. I use coding agents in my daily work and build tools that keep their output small, tested and easy to review.

How I work

Three things I come back to.

Understand it first.

What’s actually needed, how it works today, and what would make a real difference.

Keep it simple.

Use the patterns that fit. Build what’s needed. Leave it clear for the next person.

Care about the finish.

Small, reviewable changes. Useful tests. Check the real thing, not just the green tick.

Get in touch

Got a problem to solve? Let’s chat.

[email protected]