Labs services
Six ways I help engineering teams.
Each engagement is scoped around one or two of these. Most start small, with a review or a single piece of work, and grow from there if it is useful.
Software engineering
Production software designed, built and shipped by an experienced engineer, in your repository and to your conventions, with the tests that keep it shippable.
- TypeScript, Node and NestJS
- Java and Python
- Testing and CI
Seen in TheCocoCard, Fixabee
Software architecture
Systems that scale with the business and stay understandable: service boundaries, data models and the trade-offs written down.
- Domain modelling
- Service boundaries
- Architecture reviews
Seen in TheCocoCard
Cloud architecture
Cloud foundations that are reliable, secure and sensibly priced, with infrastructure as code from the first day.
- AWS and GCP
- Kubernetes and serverless
- Terraform
Seen in Fixabee
APIs and integrations
Documented, versioned APIs for products and partners, and integrations that survive retries, rate limits and the other side's surprises.
- External and partner APIs
- Payments and messaging
- Third-party platforms
Seen in Fixabee, TheCocoCard
Backend systems
Event-driven backends, queues and workers, and the delivery pipelines that make shipping them safe.
- Event-driven systems
- Kubernetes migrations
- CI/CD pipelines
Technical leadership
An experienced voice when it matters: architecture reviews, technical due diligence, build-versus-buy decisions and fractional tech leadership.
- Due diligence
- Roadmap and build-vs-buy
- Fractional tech lead
Not sure which one you need?
Most conversations start with a problem, not a service name. Describe the problem and I'll suggest the smallest useful first step.