APIs and services
REST and event-driven services in Python (FastAPI), Java (Spring Boot), Node or Go, with typed contracts and versioning.
Users judge a product by its interface and abandon it because of its backend. I design APIs, data models and infrastructure that stay fast, observable and boring under load, which is exactly what a backend should be.
For startups that need a first senior engineer, and teams whose backend has outgrown the decisions made in its first month.
01/What you get
Data that holds up
PostgreSQL schemas, migrations, indexing and caching designed around the queries the product really makes.
Infrastructure as code
Terraform, Docker and Kubernetes on AWS, GCP or Azure, with CI/CD pipelines that make releases routine.
Observability
Logs, metrics, traces and alerts, so problems are found by a dashboard before they are found by a customer.
02/How it works
- Step 1
Read the system
Code, schema, infrastructure and incidents, to find where the real risk sits.
- Step 2
Fix the foundation
The few structural changes that unblock everything else, made in small, reversible steps.
- Step 3
Build forward
New features on solid ground, with tests and reviews your team keeps after I leave.
- Step 4
Document and hand over
Architecture notes and runbooks written for the next engineer, not for me.
03/Proof
04/Questions
Can you join as a contractor on our existing team?+
Yes, full time or part time, directly or through Andela's talent network, with working hours that overlap Europe and the US East Coast morning.
Do you also do frontend and design?+
Yes. I wireframe and prototype in Balsamiq and Figma, and build interfaces in Next.js and React. Most of my recent work is backend and AI, but I design the screens the backend serves rather than leaving them to chance.
Can you lead a team rather than code alone?+
Yes. I have led technology for a logistics company end to end, and I can act as a fractional tech lead until you hire one full time.
Related writing