Contract architect · backend · ERP · data
I design and build backends in Go for domains that are genuinely complicated — accounting, inventory, logistics, multi-tenant platforms. Decisions get written down before code, so the system can be handed to someone else without archaeology.
What I do
All four share one thing: they need someone who can hold the whole system in their head and write the decisions down. If your problem is adding screens to an app that already works, you want a team, not me.
Services in Go with a clean domain layer, explicit invariants and predictable behaviour under load.
Document flow, finance, inventory, procurement, pricing — modelled as one coherent system rather than a pile of CRUD screens.
Systems that exchange data without losing it, and without silence when something breaks.
Nine of my years are in data before they were in backend. Query plans and schema, not "add more RAM".
Case studies
These are systems I designed and built, not projects I consulted on from a distance. One client is under NDA, so that one is described by its engineering rather than its name — I would rather say so plainly than invent a logo wall.
ERP · multi-tenant platform
Multi-tenant ERP as a modular monolith: domain modules in one codebase, gRPC inside, a GraphQL gateway outside, PostgreSQL as the source of truth, Kafka for events and Elasticsearch for search.
10+domain modules in production
Architecture recorded in a C4 model and a body of ADRs; module boundaries enforced by CI, not by convention.
Logistics · microservices
Eight scalable microservices behind a central API gateway, replacing a process that had been partly manual. Go on the backend, Nuxt 3 operator panel, MS SQL Server, centralised logging through Vector into Elasticsearch.
16 h → 9 mincore process turnaround
The number is the whole point: same work, same people, two orders of magnitude less waiting.
Retail · allocation engine
Decides how much of each article goes to each store, what returns to the warehouse and what moves between stores — with a readable explanation for every decision. Client under NDA; the domain is a retail chain.
3 pipelinesforward, reverse, redistribution
Sales velocity on a smoothed EMA, demand with seasonality and safety stock, every run snapshotted against a job id so results stay reproducible.
Earlier work, for context
Before contracting I spent years inside larger organisations: a cancer research centre (grant and financial flows, laboratory data, regulated pharmaceutical accounting — all calculations at the database level), a tier-one bank (trading system integration, MxML to FIXML transformation), and a gaming holding (data warehouse across MS SQL, PostgreSQL and ClickHouse; migrating ETL from SSIS to Apache Airflow). Delivered as part of contractor teams and directly.
Engagement
You are hiring someone you have not met, in another country, for work that is hard to evaluate from outside. So the first step is deliberately small and produces something you keep either way.
Two to three weeks, fixed price. The output is a document set, not a proposal.
from $2,0002–3 weeks, fixed
Scope agreed per sprint, demoed at the end of each one.
from $4,500per two-week sprint
You have a team. You do not have someone who owns the shape of the system.
from $2,400per month, part-time
Contract and paymentUSD / EUR
The contracting party is Didenko Maksim Sergeevich, a sole proprietor registered in Russia (OGRNIP 324190000021130, TIN 245735477632). Invoices are issued in USD or EUR and settled by bank transfer to an account outside Russia; exact banking details are agreed before signing. I am happy to sign an NDA before we discuss anything specific.
Prices on this page are starting points, not an offer. Final scope, cost and schedule are fixed in the contract.
Working with me
Every one of these will surface in week two anyway. Better you know them before you pay.
"You are one person. What happens if you disappear?"
The repository is yours from day one, not on delivery. The C4 model, the ADRs and the migrations are written as the work happens. Handing the project to another Go engineer is a few days of reading, not an excavation — that is the entire reason the decisions are written down.
"How much can you actually take on?"
One substantial project at a time, plus a retainer. I do not subcontract architecture, and I will tell you when a piece of work needs a team rather than pretending otherwise. If your deadline needs five engineers, I am the wrong call.
"Time zones?"
I work at UTC+7. That gives four to six overlapping hours with Central Europe every day, and early mornings only with the US East Coast. For the US West Coast, daily synchronous work is not realistic — asynchronous, with written decisions, is.
"What about English?"
I work in English in writing and on calls. Architecture decisions, trade-offs and scope I put in writing regardless of language — that is how I work anyway, and it happens to remove the ambiguity that accents introduce.
Questions
Not covered here? Ask directly — a straight question gets a straight answer.
A modular monolith gives clean domain boundaries without the operational cost of a distributed system. I split a service out when a domain has its own load profile, its own ownership and its own release cycle — not before. Most teams pay the distributed-systems tax years before they get any benefit from it.
You do. Work is committed to your repository from the first day, infrastructure is provisioned in your accounts, and rights transfer under the contract. There is no platform licence and no dependency on me continuing.
Yes, and that is often the better first step. I start with an architecture review, record the findings as ADRs, and set up the CI gates that stop the system degrading further. Sometimes the outcome is "this is fine, here are three things to fix" — you get that answer too.
For discovery, yes — that is why it is fixed. For a full build, only after discovery, because a fixed price on an unexamined problem is either padded or a future argument. Sprints with agreed scope are usually the honest middle.
A call to understand the domain and constraints, read-only access to the existing system if there is one, then written work: the system map, the risk register, the decisions that need making. You see drafts as they appear, not a reveal at the end.
Contact
I reply within one business day. If the work is not a good fit for me, I will say so directly and, where I can, point you somewhere better.