Solution architecture and technical leadership

The expensive mistakes in software are made early: the wrong data model, a service split that is not needed, security bolted on later. I make those decisions with you and write the trade-offs down before a line of code.

I have designed and built systems from a 15+ microservice streaming platform on Google Cloud to a fintech back office running KYC, banking and payouts over gRPC, and I led an engineering team that grew from 4 to 10 people.

What you get

Relevant work

Read the NOICE case study →

Read the Assure.co / Glassboard Tech case study →

Questions

Do you only advise, or also build?

Both. I can write the architecture and hand it to your team, or build it myself and lead the engineers who join.

Should we use microservices?

Usually not at the start. A well-structured monolith is cheaper to run and change. I split services only where scale, team ownership or isolation actually require it.

Book a free 30 minute call →View the full portfolio: 69 projects