Backend & APIs
A server that keeps up with growth and doesn’t fall over on a Friday night.
- Architecture and data model
- REST and gRPC APIs
- Queues, background jobs, integrations
Fullstack Engineer
The systems nobody sees. The interfaces everybody feels.
3+ years shipping products — from architecture to interface
From the first schema to the last pixel — one engineer for the whole product.
A server that keeps up with growth and doesn’t fall over on a Friday night.
Live data on the user’s screen in milliseconds.
A fast, polished front end that sells the product.
Architecture in motion
Web, mobile, desktop — thousands of clients, each sending a stream of small, impatient requests.
A gateway terminates TLS, checks tokens, rate-limits and routes traffic before it reaches anything that matters.
Small services call each other when they need an answer now — and publish events when they don't. NATS, Kafka, RabbitMQ: the bus fits the job, not the other way around.
Live state is pushed back to clients over persistent WebSocket connections. Milliseconds, not page reloads.
PostgreSQL for transactions, MongoDB for documents, Cassandra for heavy writes, ClickHouse for analytics, Redis for speed — plus object storage, vectors, search and graphs where they belong.
Every hop is measured, logged and traced. When it works, nobody notices. That is the whole point.
The server side of an online game with complex gameplay logic — stateful requests, background processing, analytics and real-time delivery, built to stay fast under load.
A fast, predictable backend for an automation platform — event-driven services, background jobs, semantic search and real-time updates in the UI.
A personal site that shows invisible systems at work — an isometric 3D architecture scene driven by scroll, a live terminal backdrop, two themes and two languages, with a perfect Lighthouse score on mobile.
Latency budgets, back-pressure and load tests come before the launch, not after the incident.
Every service explains itself with metrics, traces and errors you can actually act on.
Proven tools, simple deploys, reproducible environments. Excitement belongs in the product.
Decisions follow numbers: user behavior, product metrics, performance regressions.
The tools I reach for every day — and the ones I pick up when a project needs them.
Have a product or a feature in mind? Tell me what you need — I’ll get back to you with a plan.
vladamirov1980@gmail.com