Professional Summary
Backend engineer with 6+ years of production experience across e-commerce, adtech, and SaaS, now focused on Elixir and the BEAM ecosystem. My path was deliberate: Ruby on Rails as a foundation, a production Ruby-to-Go migration, and Elixir as the current direction. OTP supervision trees, fault-tolerant concurrency, and Phoenix's architecture are principled answers to the distributed systems problems I have been solving the hard way for years.
I bring production depth in system design, API architecture, and database performance that shortens ramp-up on an Elixir team, plus a strong habit of reading and verifying unfamiliar code carefully before shipping and a track record of catching system-level tradeoffs before they become incidents.
Technical Skills
- Elixir/BEAM: Mix, GenServer, OTP supervision trees, Task, pattern matching, immutability, ExUnit, let-it-crash/process-isolation design.
- Phoenix: Router, controllers, LiveView, Ecto (schemas, changesets, associations, query building, migrations).
- Ruby/Rails: 6+ years production — REST API design, background job architecture, TDD, large-scale refactoring.
- Go: Production microservices, goroutines, channels, service rewrites, inter-service communication.
- Databases: PostgreSQL (EXPLAIN ANALYZE, query optimization, index design, N+1 elimination), MySQL, MongoDB, DynamoDB.
- Infrastructure: Docker, Kubernetes, Terraform, Kafka, AWS (EC2, S3, DynamoDB), GitHub Actions, GitLab CI/CD.
Work Experience
- Rewrote 4 core production modules from Ruby to Go.
- Led system design for inter-service communication—evaluated messaging patterns, failure isolation, and retry logic before implementation, preventing two identified architectural issues from reaching production.
- Critically reviewed the existing codebase for correctness issues in concurrency primitives and API boundary contracts; produced written specs for refactored modules before any code was written.
- Refactored the internal shared library, improving reuse across services and reducing onboarding time.
- Relevance to Elixir: The distributed-coordination and failure-handling problems solved here with goroutines are exactly the ones OTP supervision trees were designed to make elegant.
- Delivered full-stack features for a travel booking platform (Ruby on Rails, React, PostgreSQL).
- Integrated third-party booking and payment APIs with robust failure/retry handling; wrote integration contracts upfront to catch edge cases before implementation.
- Self-managed delivery with async written updates; no micromanagement required.
- Improved overall platform performance by 46%—systematic work with EXPLAIN ANALYZE, N+1 elimination, and index redesign across the product catalogue and order management.
- Owned the backend purchase funnel (Ruby on Rails + PostgreSQL), including third-party tire-supplier API integration with retry and failure handling designed from the specification stage.
- Mentored 2 junior developers to independent feature delivery within 3 months via structured code review and pair debugging.
- Setup the GitHub Actions CI/CD pipeline, moving the team from ad-hoc deploys to structured, verified releases.
Elixir Projects & Self-Study
- InsightNest (Alpha): Structured knowledge-community platform built in Elixir/Phoenix/LiveView with Ecto, OTP supervision tree, and GenServer-based background worker. Designed schema and supervision tree before writing production code.
- Sign-In with Ethereum (SIWE/EIP-4361): Implemented full authentication flow in pure Elixir—no NIFs, no JavaScript SDK—working directly from the specification.
- Study: Programming Elixir, Elixir in Action, Designing Elixir Systems with OTP, Phoenix in Action.
Education
Technical University, Minsk, Belarus
Engineering Design and Production of Materials
What I'm Looking For
An Elixir/Phoenix team with real production problems—distributed systems, data integrity, performance—where deep backend experience is a genuine asset. Async-friendly remote culture with clear ownership, honest code review, and room to grow into a strong Elixir engineer.