Artem Vasilyev

Senior Go Backend Engineer / Platform Engineer

I help build the backend foundation of digital products: domain models, APIs, integrations, diagnostics, releases, and technical manageability — so systems can handle load, changing requirements, and new product scenarios.

@avslyv

Senior Go Backend Engineer / Platform Engineer

Experience4+ years of commercial Go backend development

Focuscomplex business logic · clear APIs · integrations · service resilience

Domainstelecom · eCommerce · EdTech · geospatial · engineering education

Go · GraphQL · gRPC · Kafka · Kubernetes · PostgreSQL · Redis

Open to strong engineering challenges

backend platforms · architecture · technical leadership

Download CV

3 520days in code

ENGINEERING FOCUS

A strong backend platform is a business system: domain, APIs, data, integrations, and ownership of the outcome.

ContractsDomainScaleDiagnosticsOwnership

Experience in Product Systems

Domains where I worked on backend logic, APIs, integrations, release quality, and service maintainability under real production pressure.

Open a card for the full role breakdown

Product Offers and Sales Strategy Platform

MTS · Enablement Platform eCommerce core2025 — Present

Senior Go Backend Engineer · Platform Engineer

Stack: Go · GraphQL (Apollo) · gRPC · Kafka · ScyllaDB · PostgreSQL · Redis · Kubernetes · Prometheus · Grafana · Jaeger

Context: A core MTS eCommerce domain: Product Offering and Product Strategy are responsible for dynamic offer assembly, configuration, personalization, sales strategies, and delivery of prepared offers to customer-facing channels. My focus: backend logic, API contracts, compatibility, performance, and diagnostics.

High-load

Distributed system

Personalized Learning Platform

Beyim.ai2023 — 2024

Go Backend Engineer

Stack: Go · PostgreSQL · Redis · Kafka · Docker · Kubernetes · MinIO · Prometheus · Grafana · Jaeger

Context: Backend foundation of an education platform: courses, learning content, user journeys, material storage, tests, tracing, and monitoring. Focus: making the education product evolvable without breaking core learning flows.

beyim.ai

Beyim — personalized learning platform

An education platform for personalized learning and test preparation.

Distributed system

Illumimapi Geosocial Platform

Kvando Technologies2021 — 2022

Go Backend Engineer

Stack: Go · PostgreSQL/PostGIS · Redis · MongoDB · Docker

Context: Backend for a geosocial platform with an interactive map: geo-linked markers, media, time-based events, external APIs, geodata caching, and microservice support.

Illumimapi on the App Store

Illumimapi — geosocial platform

An interactive map with geo-linked markers, media content, and time-based events.

Distributed system

SCALE & OWNERSHIP

I have worked on systems where backend decisions affect not only code, but sales flows, customer journeys, integrations, and product reliability.

150M+

requests per day in a high-load product domain

years building commercial backend systems in Go

domains: telecom/eCommerce, EdTech, and geospatial products

Feature Lead

coordination of tasks, solution reviews, releases, and backend direction

Backend Responsibility Areas

Not a list of isolated projects, but recurring areas of my work: domain logic, user journeys, integrations, APIs, performance, and maintainability under real production load.

Commerce logic and product offers

Services where a customer-facing offer is not a static product card, but is assembled from prices, availability, promotions, product characteristics, sales rules, product relationships, and user context.

OffersCommercePersonalization

Education platforms and content models

Systems for courses, learning content, user journeys, material storage, monitoring, and reliable change delivery in an education product.

EducationContentFlows

Geospatial services, media, and external data

Backend for an interactive map, geo-linked markers, media content, external APIs, PostGIS, and caching of data that must be served quickly to users.

PostGISRedisMedia

API contracts and integration evolution

Designing APIs and internal contracts so the product can evolve: new scenarios, multiple consumers, backward compatibility, clear errors, and controlled change.

APIGraphQLCompatibility

Reliability, diagnostics, and maintainability

Tests, reviews, structured logs, tracing, metrics, task decomposition, and technical planning — everything that allows a system to evolve without hidden regressions and accumulated chaos.

ReliabilityDiagnosticsReleases

Performance and production load

Optimizing critical paths through caching, batching, pre-aggregation, and reduction of unnecessary network calls — so product scenarios remain fast under load.

LoadCachingOptimization

The product is growing faster than the architecture

When new roles, rules, scenarios, and integrations appear faster than the system can adapt, the backend quickly becomes fragile.

What I do

I structure the domain, define boundaries, simplify the model, and design APIs so new features do not break the existing logic.

Outcome

The product evolves faster, and new changes turn into regression risk far less often.

Integrations hide the real cause of failures

When a scenario flows through several services, external APIs, data, and configurations, the team spends time hunting for the failure point instead of fixing it.

What I do

I design contracts, errors, logs, and tracing so it becomes clear where a scenario breaks: data, integration, configuration, or domain logic.

Outcome

The team finds root causes faster, supports the system with more confidence, and relies less on manual investigation.

Changes have to actually reach production

Code is only part of the work. A change has to travel from requirements and decomposition through review, release, compatibility, and ongoing support.

What I do

I keep the product goal, architectural decision, and operations connected — thinking through boundaries, risks, tests, contracts, and the release itself.

Outcome

Delivery becomes more predictable, and changes stay safer for the product, the team, and the users.

Core Expertise

Primary

Go backend engineeringPlatform engineeringDistributed systemsAPIs and integrations

Technology stack

GraphQL / gRPCKafkaScyllaDBPostgreSQL / PostGISMongoDBRedisDockerKubernetesMinIOPrometheusGrafana / Jaeger

Engineering Principles

How I approach backend systems where the cost of a mistake is a broken customer journey, degraded integration, or incompatible API change.

The contract matters more than a beautiful implementation.

In a distributed system, an API usually outlives a specific piece of code. I design changes so new scenarios do not break existing consumers.

Complexity should be localized.

Complex business logic should not be spread across handlers, integrations, and infrastructure code. It needs clear boundaries and an understandable model.

Diagnostics are for decisions, not reports.

Logs, traces, and metrics should help the team quickly understand where a scenario broke: domain logic, integration, data, or configuration.

Reliability is designed before incidents.

Caching, batching, tests, diagnostics, and degradation boundaries should be designed before the fire starts.

Delivery is part of the engineering solution.

Good backend work does not end with implementation: decomposition, review, compatibility, release, and maintainability after launch all matter.

ENGINEERING APPROACH

Hey. For me, backend isn’t just code — it’s a way to turn a complex domain into a system the team can understand: with durable contracts, transparent diagnostics, and an architecture that keeps moving forward after release. I work where business rules, integrations, data, and load have to stay predictable not only during development, but well after the product ships.

Engineering Education

A direction where I invest in Go developer growth, code-review quality, and practical knowledge sharing inside the engineering community.

Open a card for the full role breakdown

Go Mentorship and Internal Engineering Education

MTS Teta2025 — Present

Go Backend Mentor · Technical Content Contributor

Topics: Go · context handling · error handling · concurrency · testing · interfaces · clean architecture

Context: I create learning materials, run practical reviews, and connect Go syntax with production backend engineering.

Code as a Way of Thinking

I started programming in school, around the age of ten. Pascal, Java, algorithmic problems, frontend, and an interest in building products gradually led me toward backend engineering.

In 2018, I discovered Go — a language where I found an engineering style that felt close to me: simplicity, speed, explicit logic, and pragmatic design for production systems.

Today, my focus is distributed systems, platform engineering, and technical leadership in complex product domains.

Outside of code

Guitar

Vinyl

Systems architecture

Product thinking

Sport

Engineering Library

Books and ideas that shape my engineering taste: distributed systems, reliability, architecture, and software craft.

Click to open.

Swipe sideways · tap a book to open.

Education

University: Voronezh State University
Faculty: Faculty of Computer Science
Major: Software Engineering
Years: 2022 — 2026

Let’s build systems that survive growth

Contact

Let’s be honest:you want to hire me.

avslyv.io@gmail.com

@avslyv

Timezone — UTC+3

Open to strong engineering challenges

Go backend platforms,architecture, and technical leadership.

Telecom · eCommerce · EdTech · geospatial services · enterprise · public-sector digital services

I respond best when the product domain, ownership area, engineering complexity, and expected outcome are clear upfront.

Go Backend
Backend Platforms
Distributed Systems
Technical Leadership

Artem Vasilyev

Senior Go Backend Engineer / Platform Engineer

Go · backend platforms · distributed systems · ownership

Building the backend foundation of digital products: domain models, APIs, integrations, diagnostics, and reliability that survive real product scale.

Connect on LinkedIn →Open to strong engineering challenges

Bonus

You reached the end. Want a short break?

SESSION COMPLETEThanks for reaching the end.

Artem Vasilyev

A strong backend platform is a business system: domain, APIs, data, integrations, and ownership of the outcome.

Experience in Product Systems

Product Offers and Sales Strategy Platform

Personalized Learning Platform

Illumimapi Geosocial Platform

I have worked on systems where backend decisions affect not only code, but sales flows, customer journeys, integrations, and product reliability.

Backend Responsibility Areas

Commerce logic and product offers

Education platforms and content models

Geospatial services, media, and external data

API contracts and integration evolution

Reliability, diagnostics, and maintainability

Performance and production load

Where My Engineering Delivers the Most Value

The product is growing faster than the architecture

Integrations hide the real cause of failures

Changes have to actually reach production

Core Expertise

Engineering Principles

The contract matters more than a beautiful implementation.

Complexity should be localized.

Diagnostics are for decisions, not reports.

Reliability is designed before incidents.

Delivery is part of the engineering solution.

Engineering Education

Go Mentorship and Internal Engineering Education

Code as a Way of Thinking

Outside of code

Engineering Library

Education

Let’s build systems that survive growth

Contact

Go backend platforms,architecture, and technical leadership.