Backend & system development
The part users never see: APIs, databases, queues, background jobs, integrations and the servers they run on. This is my main job, in Python, Go, TypeScript, Java and C#.
What I can do
APIs and system design
REST APIs with clear contracts, permissions and tests, designed to grow without a rewrite.
Event-driven systems
RabbitMQ producers and consumers that keep systems in sync, released in a safe order.
Integrations and automation
Connecting CRMs, payment providers, trading servers, email, SMS and WhatsApp, and automating the manual steps between them.
Cloud and DevOps
Docker, AWS, Cloudflare and Linux servers, with CI, backups, monitoring and alerts.
Rescue and debugging
Finding out why production is slow, wrong or down, proving the cause and fixing it safely.
Technical advice
A second opinion on architecture, a build-or-buy decision or a vendor's proposal.
Proof, not promises
- CFI FinancialSenior Backend Engineer at CFI Financial: FastAPI services and RabbitMQ consumers across 7 services and shared libraries.
- SolveMYSolveMY's Go API: 235 endpoints and 1,006 test functions, running on Hetzner with Docker and Cloudflare.
- MT5 risk engineResolved a production data-integrity incident in an MT5 integration by tracing it to a thread-unsafe SDK.
How we would work
- 01
A short call
A no-obligation conversation about what you need, what exists already and what success looks like.
- 02
A written scope
What I will build, what I will not, the risks, and a fixed quote or a time-based estimate.
- 03
Small, visible releases
You see working software early and often, on a staging site you can click through.
- 04
Handover and support
Documentation, access and a clean handover, with ongoing support if you want it.
Questions
- Which languages and frameworks do you use?
- Python (FastAPI), Go, TypeScript (Node.js), Java (Spring Boot) and C# (.NET), on PostgreSQL, MySQL, Redis and RabbitMQ. I pick what fits your team and what you can hire for later.
- Can you take over a system someone else built?
- Yes. I start by reading the flows end to end and writing down how they work, then fix the riskiest parts first.
- Do you offer support after launch?
- We can agree ongoing support for fixes, updates and monitoring once the project is live.
Tell me what you are building.
A few lines are enough: what it is, who it is for, and when you need it. The form is just below, or email me if you prefer. I usually reply within two working days.