asman.malikov_ RU

Experience

Senior backend engineer and team lead. I design and operate distributed systems in Go and Python — event-driven microservices over Kafka and gRPC, a real-time ClickHouse analytics stack, and money-critical flows made safe with idempotency and observability. I currently lead a team of four on a B2B payments platform, turning product ideas into production-ready systems.

Download PDF ↓ Resume as Markdown ↓

2022-07 — Present · Cyprus (remote)

Backend Team Lead / Senior Backend Engineer (Go / Python) — Korvax

Backend architecture and technical leadership for a B2B payments platform — distributed microservices, event-driven integrations, and a real-time analytics stack. Korvax delivers custom digital products and business systems for clients across multiple industries, including financial services.

  • Led a team of 4 backend engineers — owned architecture direction, set code-review and testing standards, and mentored the team to ship independently.
  • Architected billing, notification, and crypto-payment microservices in Go (Gin) and Python (FastAPI), using gRPC for synchronous calls and Kafka for event streaming between services.
  • Made money-critical flows safe under retries and duplicate delivery with idempotency keys and a producer outbox → consumer inbox dedup pattern — eliminating double-processing of payment events.
  • Designed a dedicated ClickHouse reporting service that ingests payment events via Kafka, isolating analytics from the transactional PostgreSQL path and cutting report generation from ~30s to under 2s as volume grew past 1M+ events/day.
  • Optimized PostgreSQL and ClickHouse for analytical workloads — connection pooling, partitioning, and pre-aggregation — keeping reporting fast as data grew.
  • Instrumented production observability with OpenTelemetry tracing, Prometheus metrics, and Grafana SLO dashboards, cutting incident MTTR from ~20 to ~5 minutes.
  • Hardened services for reliability — graceful shutdown with in-flight draining, end-to-end context propagation/cancellation, and Redis for cache-aside, task queues, distributed locks, and rate limiting.

Delivered a distributed, fault-tolerant microservice platform with a real-time analytics layer — and a team that ships it independently.

GoGingRPCPythonFastAPIKafkaClickHousePostgreSQLRedisDockerOpenTelemetryPrometheusGrafana

2020-02 — 2022-10 · Remote

Backend Developer — Amit agency

Built custom web and backend solutions for SMB clients, focusing on CRM systems, third-party integrations, and business process automation. Amit agency is a software development agency building custom web platforms, CRM systems, and SaaS integrations for small and medium-sized businesses.

  • Migrated a monolithic e-commerce platform to microservices (FastAPI, PostgreSQL, Redis) incrementally with an expand/contract approach — each service proven in production before the next cut, keeping the platform at ~100% uptime throughout.
  • Built a custom CMS for the e-commerce platform hodoor.com, powering catalog and content for international expansion.
  • Designed an automated translation pipeline for 30+ languages on Celery task queues and Yandex Cloud Translate — localizing content continuously with human spot-checks instead of manual translation.
  • Set up CI/CD on GitLab (Docker + Swarm) and Sentry error monitoring — turning manual deploys into repeatable releases and surfacing production errors before users reported them.
  • Built ETL pipelines to migrate data from legacy systems without downtime.
  • Designed authentication and UGC modules (chats, reviews) with real-time delivery over WebSocket.
  • Configured edge infrastructure with Traefik, Cloudflare, and Yandex CDN for fast global delivery.

Delivered a scalable, fault-tolerant, internationally-ready platform — migrated live, without halting delivery.

PythonFastAPICeleryPostgreSQLRedisDockerDocker SwarmGitLab CISentryTraefikCloudflareWebSocket

Education

ITMO University — BSc, Programming in computer systems (2016–2020)

Skills & technologies

GoPythongRPCPostgreSQLClickHouseKafkaRedisMicroservicesDistributed SystemsEvent-Driven ArchitectureIdempotency & Outbox patternSystem DesignObservability (OpenTelemetry)KubernetesCI/CDTechnical LeadershipAI-assisted engineeringLLM integrationsRAG pipelines

AI-assisted engineering practice

I run an AI-native development workflow: custom agent plugins, skills, and hooks; token-optimized tooling; structured review rituals; and AI-readable project knowledge bases. AI is a multiplier in my engineering process, not a replacement for engineering judgment.

AI-readable record →

Work style

Outcome-first scoping, small reviewable increments, honest status reporting, tests and verification before claims of done. I document decisions so the team and the tools can reuse them.

[+]Projects that are a fit

  • Backend/platform contracts: APIs, integrations, internal platforms, reliability work.
  • AI automation projects: agent workflows, LLM integrations, document and data pipelines.
  • AI development culture: plugins, workflows, review rituals, team enablement.
  • Quality and knowledge systems: QA gates, evaluation loops, AI-readable documentation.
  • Technical leadership: tech lead, CTO, or fractional CTO for small teams.

[–]Projects that are not a fit

  • Pure frontend/design projects with no backend or systems component.
  • ML research or training models from scratch.
  • Staff augmentation without ownership of outcomes.
  • Projects that need promises of guaranteed delivery dates before scoping.