Vladimir K.

Your Golang backend is slow, flaky, or hard to change? I join existing codebases, find what hurts and ship fixes to production. I'm a senior Go (Golang) backend engineer based in Germany (CET): 12 years in backend development, Go in production since 2018. Most of my work is on existing production services: event processing, payments and statuses, third-party integrations, observability and infrastructure. Available 30+ hours/week. WHAT I'M HIRED FOR • Event-driven backends: Kafka, NATS, Pub/Sub, background jobs, delayed and duplicate events, reconciliation. • Integrations: Google Play subscriptions, push and scheduled notifications, logistics and tax-authority APIs, LLM chatbots via MCP servers in Go. • Performance and stability: slow queries, database deadlocks, unreliable sync between systems. • Observability: tracing, metrics and alerting with OpenTelemetry, Prometheus, Grafana, Datadog and Sentry. • Infrastructure code: Kubernetes tooling in Go, Ansible, Docker. • Monolith → services migrations. HIGHLIGHTS • AI creator platform (Yodayo, now Moescape): notifications, content filtering, Google Play subscriptions and an FFmpeg-based video-processing service in Go. Shipped to production and supported after release. • AI assistant integration (CHECK24): built a Go MCP server exposing internal geographic and experience search to the company's AI chatbot; LLM-based mapping of provider booking questions to internal CRM fields. • Courier payouts (large e-commerce retailer): fixed delayed and duplicate delivery events processed across multiple service instances and built reconciliation for deliveries missing from payout calculations. Any 15-minute outage meant a huge queue, so correctness and recovery were the main job. • Delivery tracking (marketplace, around a million active deliveries): took part in the team's redesign of status processing — webhooks instead of polling, optimized status tables, fewer provider API calls. • IoT platform (tens of thousands of sensors across the US): added trace IDs and Datadog tracing to sync services, sped up dimension-table writes, fixed Kafka reconnection and panic reporting to Sentry, shipped targeted deadlock fixes. • Monolith migration: helped design and implement a staged move from a NestJS monolith to Go microservices with NATS and gRPC; built service templates and protobuf contracts; the first migrated services went to production. STACK Go, PostgreSQL, MySQL, Kafka, NATS, Redis, Elasticsearch, gRPC, REST, Docker, Kubernetes, Google Cloud, AWS, Ansible; also PHP and TypeScript. HOW I WORK Small PRs that are easy to review, regular status updates, and an early heads-up when a task turns out bigger than planned. Comfortable with both legacy code and greenfield. Message me with 2–3 lines about your setup and your biggest backend headache. I'll tell you honestly whether I can help and how I'd start.