~/dmitrii-krylov
$whoami

Dmitrii KrylovAI / Platform Engineer

Open to new opportunities

I turn LLMs from demos into company infrastructure.

Nineteen years in IT: from database administration to engineering leadership and back to building. Today that means the platform layer that makes AI usable inside a company — and it means shipping it, not demoing it.

Remote-friendly · on-site ready · full-time priority

19 yrsin IT since 2007
30+engineers in the largest team I led
20+services shipped in the last six months
~430pages of engineering documentation

About

$whoami

AI / Platform Engineer. I started in 2007 as a database administrator, spent a decade building high-load and ad-tech systems, led engineering teams of up to thirty people, and came back to hands-on work in the place I find most interesting: the platform layer that decides whether AI actually gets used inside a company.

Over the past six months I shipped about twenty internal services to production — support analytics on RAG, a gateway in front of the model provider, a secrets platform, a marketplace of shared AI tooling and documentation that maintains itself. They are used daily by engineering, QA, product and HR.

The through-line across nineteen years is the same: I like the boundary where engineering meets operation. Anyone can demo a model, ship an MVP or promise a migration. The work that matters is SSO, audit trails, migrations, CI gates, monitoring and documentation that does not rot — the things that decide whether it is all still running six months later.

Selected systems

$ls -l ./systems
rag-support-analytics/Semantic search and LLM insight over the support ticket stream
  • Vector search over tickets on PostgreSQL + pgvector, with eight retrieval strategies, cross-encoder reranking and A/B comparison of answer quality.
  • Parsing, embedding and report generation run asynchronously on Celery behind a caching layer.
  • Delivered where the team already works — inside chat — instead of as one more dashboard nobody opens.
  • Corporate SSO on every endpoint and strictly typed prompt boundaries against injection.
PythonFastAPICelerypgvectorRedisRAGKeycloak
secrets-platform/Self-service secrets for every project, with values nobody can read back
  • Web UI and API over HashiCorp Vault: project-scoped access, membership roles and a full audit trail of every change.
  • Storage paths derive from immutable project IDs, so a recreated or renamed project can never inherit an older namesake's secrets.
  • Service tokens let CI jobs and automated agents write secrets without a human in the loop.
  • Bulk import of environment variables, schema migrations, generated API docs. First commit to production use in one month.
PythonFastAPIHashiCorp VaultKeycloak / OIDCPostgreSQLReact
ai-skill-marketplace/One source of truth for reusable AI tooling, delivered to three runtimes
  • A registry of shared AI skills with named owners, versioning and an actual lifecycle instead of prompts pasted between chats.
  • Fully automated CI: validation and merge gates on review, artifact publishing, per-skill releases and team notifications.
  • A status page showing, per runtime, what is live and which pipeline put it there.
CI/CDGitLabNexusPagesClaude API
docs-autopilot/Documentation that updates itself from the code that changed
  • Consumes change events from repositories, diffs against the last processed commit and asks a model what actually changed.
  • Cosmetic edits — formatting, tests, pure refactors — are classified out and never touch the docs.
  • Guardrails: a generation that rewrites more than 60% of an existing document is rejected and retried, secrets never reach the model, and a redelivered event never produces a second commit.
PythonKafkaPostgreSQLClaude API
llm-gateway/A key pool in front of the model provider, so services never hold a real key
  • Key rotation, quota tracking, automatic disabling of banned or exhausted keys and transparent retries across the pool.
  • Revocable per-client tokens with per-token usage statistics; streaming responses pass through untouched.
  • Drop-in by design: clients talk to it exactly as they would to the provider itself.
Goreverse proxySSEDocker
careers-backend/The public careers section and the HR admin behind it
  • Replaced a fully mocked frontend with live data without asking anyone to rewrite the frontend — response shapes matched the mocks field for field.
  • OpenAPI as the contract, with frontend types generated from it and published as a package, so drift becomes a failing pipeline instead of a production bug.
  • Graceful degradation: rate limiting falls back to in-memory counters and file storage falls back to the database when infrastructure is not provisioned.
GoPostgreSQLOpenAPIS3GitLab CI

Stack

$cat stack.txt
languages
Python · Go · TypeScript · SQL
services
FastAPI · Celery · Fastify · OpenAPI · REST · microservices
data
PostgreSQL · pgvector · Redis · Kafka · MySQL · query optimisation
ai
RAG · embeddings · reranking · LLM APIs · agent tooling
platform
Docker · Kubernetes · GitLab CI · HashiCorp Vault · Keycloak / OIDC
frontend
React · TypeScript · Vite
earlier
Perl · Lua · Django · high-load and RTB systems

How I work

$cat principles.md

01Production is the deliverable

A prototype that cannot be operated is not finished. SSO, audit, migrations and a rollback path are part of the feature, not a follow-up ticket.

02Fix the process, not the incident

Making automated tests mandatory and rebuilding deployment did more for stability than any individual hotfix ever did. I would rather change how a team ships than firefight what it shipped.

03Degrade, never fail

Every service assumes its dependencies may be missing: counters fall back to memory, file storage falls back to the database, an exhausted key drops out of the pool by itself.

04Write it down once, then automate it

Knowledge that lives only in someone's head is an outage waiting for a vacation. A document maintained by hand is wrong within a month.

Experience

$git log --author=dk --oneline

Feb 2026 — Sep 2026 · Batumi, Georgia

Engineering Manager · Prequel Inc.

Internal AI and platform layer: RAG-based support analytics, a secrets platform, a marketplace of shared AI tooling, an LLM gateway and self-maintaining documentation. Standardised service delivery onto shared CI pipelines and a single convention for configuration and secrets.

Dec 2024 — Feb 2026 · Batumi, Georgia

Engineering Manager · inDrive

Jan 2024 — Oct 2024 · Madrid, Spain

SSP Project Lead · Vidoomy

Led the supply-side platform project and assembled the team around it, with a mandate to reach results in a short window.

Mar 2022 — Nov 2023 · Moscow

Development Team Lead · SberMarket / Instamart

Joined as the advertising platform was being formed and took it from scratch to a revenue-generating product within a year. Owned all fourteen engineers on the project — backend, frontend, QA, later mobile — and split the domain into three teams once the MVP shipped. Designed the services and subsystems behind a classic RTB stack.

Feb 2019 — Mar 2022 · Moscow

Development Team Lead · IPChain Association

Joined as a senior developer and grew into technical ownership of a project with more than thirty people. Made automated tests a mandatory part of development, planned the retirement of legacy subsystems, hired and split the group into three teams on the way to microservices, and rebuilt deployment with real monitoring and alerting.

Mar 2014 — Oct 2018 · Moscow

Senior Developer / Big Data Engineer · IPONWEB

Started in Lua and moved to the ETL team to scale an existing data-processing system. Designed and built a microservice-based subsystem for pre-release automated testing.

Jul 2012 — Mar 2014 · Moscow

Senior Full Stack Developer · KnoRus

Technical lead for a publishing house's digital library: backend and frontend, server procurement and setup, monitoring and alerting, new subsystem design, and quality control over external contractors.

May 2011 — Jul 2012 · Moscow

Senior Python Developer · Kokoc Group

Automated content updates for satellite sites — faster, more stable and with verification of results — and optimised the database and its queries.

Sep 2008 — May 2011 · Moscow

Senior MySQL DBA · SoftPower Solutions

Database infrastructure and stored routines: schemas from scratch, performance analysis, storage optimisation and bottleneck elimination.

Nov 2007 — Sep 2008 · Moscow

Junior DBA · InfoTechnoProject

Where it started: relational database architecture, performance tuning, stored procedures, clustering and replication.

Education

$cat education.txt

Bachelor's Degree, Computational Science

Modern University for the Humanities · 2005 — 2009

Certification

Inspiring and Motivating Individuals

Contact

$cat contact.txt
Hidden from scrapers — one click to reveal
email••••••••••••••
telegram@pentabion
phone••••••••••••
availabilityRemote-friendly · on-site ready · full-time priority
$exit  ·  Thanks for reading. The fastest way to reach me is email.