I help product teams build and modernise PHP products that have to keep working for years.

Problem

An all-in-one fundraising platform for non-profits needed new CRM and automation features, built by a team of 5 to 10 engineers on a codebase that had to stay reliable and easy to change. CI builds took 30 to 60 minutes.

Why it mattered

Non-profit staff were updating contact records by hand, and the CRM only tracked individual donors, not the businesses that give. Slow CI held up every merge and deploy for the whole team.

What I did

• +Primary backend developer for Workflows, which automates the contact data updates staff were doing by hand. Designed it with the team from product's brief.
• +Primary backend developer for Company Contacts, so customers can track businesses as donors, not just individuals.
• +Split the test suite into parallel runs to cut GitHub Actions build times.
• +Proposed coding standards and vertical slice architecture. The team adopted some of the standards.
• +Fixed critical issues in the import system.
• +Reviewed pull requests, demoed delivered features to stakeholders, and wrote automated tests.

Result

Workflows and Company Contacts shipped to production, backed by tests. CI builds went from 30 to 60 minutes to under 10, so merges and deploys moved faster and CI costs dropped.

Problem

A Fortune 500 company's regulated loan application only worked through its own interface. Banks wanted to integrate with it and use the main loan origination flow directly.

Why it mattered

Regulated financial software cannot ship broken. The API had to open the core loan flow to outside banks without putting the live product or its releases at risk, and business analysts and product owners needed to see progress as it happened.

What I did

• +Led a team of 3 developers and 2 QA engineers on the project, and planned and split the work.
• +Designed the REST API that lets banks use the main loan origination flow.
• +Reported progress and presented delivered work to business analysts and product owners.
• +Built features, fixed bugs, and supported production releases on the main application.

Result

The project was on schedule when I handed it over before launch.

Problem

The existing platform was too old to keep building on. The team was rewriting it from scratch and needed the new API layer, external integrations, and a consistent user interface.

Why it mattered

A rewrite only pays off if the new base is one the team can keep building on. The APIs shipped with tests from day one, and the component library gave the front end one set of building blocks.

What I did

• +Designed and shipped REST and GraphQL API features for the new platform.
• +Integrated third-party APIs.
• +Wrote unit and feature tests using TDD.
• +Designed and built the reusable UI component library for the front end.

Result

The rewritten platform launched on REST and GraphQL APIs covered by unit and feature tests, with a reusable UI component library for the front end.

Problem

An iGaming platform needed features and improvements to reach launch, integrations with third-party services, and a way to show players' crypto wallet balances in the app.

Why it mattered

The platform had a launch date to hit. The team needed to ship quickly without copying the same integration code and business rules into several places.

What I did

• +Built features, improvements, and bug fixes that helped the product ship.
• +Built internal packages from scratch for third-party integrations and shared domain logic, reused across the codebase.
• +Integrated blockchain and Web3 services to show players' crypto wallet balances in the app.
• +Suggested architectural and conceptual improvements to the codebase.
• +Wrote automated tests.

Result

The platform launched. Integrations and shared business rules live in internal packages the team reuses, and players see their crypto wallet balances in the app.

Problem

Most developer education teaches demos, not how to build and maintain software that lasts.

Why it mattered

Engineers who only learn from demos ship code that falls over on contact with real users and real time. I wanted a place that teaches the other part of the job: keeping a product working for years.

What I did

• +Set the product direction: what to build, what to cut, and the pricing model.
• +Chose the stack, built the platform, and run it in production.
• +Lead and mentor a team of 1 to 2 engineers, and review their code.
• +Decide the curriculum and write the courses, learning paths, and articles.

Result

The platform is live and in active development, with courses, learning paths, and articles published.

Problem

A new delivery and logistics product needed a dispatcher ERP for the office and an API for the drivers' mobile app, built from scratch.

Why it mattered

Both apps would keep growing after the first release. The structure set at the start decides whether that growth needs a rewrite later.

What I did

• +Chose the stack for the ERP and the driver app API.
• +Set up the project structure for both apps.
• +Built ERP features, front-end features, and the mobile app API.
• +Mentored interns in the team's practices.

Result

Both apps kept growing on the structure I set up, without a rewrite.

Problem

A video platform with millions of daily users was redesigning the tools creators use to upload and publish their videos.

Why it mattered

Creators supply the platform's content. If uploading and publishing does not work, millions of viewers have nothing new to watch.

What I did

• +Designed and built the REST API behind the redesigned creator upload and publishing tools.
• +Worked with the client on scope and requirements, and fed back on the designs.
• +Fixed release and production bugs so the live platform kept running while the redesign was built.
• +Refactored code for performance and readability.

Result

The API for the redesign was in place when I left, and the redesigned creator tools launched after that.