Skip to content
mykhaylo kolesnik

I fix the infrastructure nobody owns.

Startups build fast, with developers and now with AI. The result works until it doesn't: deploys people fear, one engineer holding everything in their head, an AI feature whose bill and behavior nobody can explain. Every engagement starts with what you have already shipped.

services

Diagnose and fix2-4 weeks

Starts with a 1-2 week diagnostic: written assessment, prioritized risk register, a 90-day plan. Then I implement the highest-value fixes from it - cloud and AI spend, reliability, deploys - as a scoped second phase. You can stop after the diagnostic; most of the value is in the fixes.

Good fit if the system was built fast, the person who knew it best is gone or overloaded, and you want it examined and repaired by the same senior hands.

Stabilization retainermonthly

Ongoing senior ownership of the production side: infrastructure, deploys, cost, agent and prompt tuning, evals, on-call for AI-system issues. Bounded monthly hours.

Good fit if you shipped an AI system and need a senior engineer on call who actually understands the production path.

Every engagement is fixed price, scoped on a call: a defined end, named deliverables, and you own everything I build - code, runbooks, and the knowledge to run it without me.

Something else in mind - part-time, embedded, a scoped build? That works too: the shape gets set on the call. The one thing I don't sell is a report that confirms everything is fine.

Get in touch

recent work

Data platform for a US marketplace startupMar to Jul 2026, solo

Took over a stalled data initiative and shipped it to production in six weeks, one engineer across the whole stack.

  • Domain-keyed warehouse unifying nine data sources across email, calls, LinkedIn outreach, and direct mail: 425k cross-source merges, zero orphans.
  • Go API and a self-serve ingestion UI the growth team uses without engineering in the loop. Terraform and AWS underneath.
  • Built to run without its builder: scheduled, watermark-resuming pipelines operated unattended and kept running after a clean handover.

roles

Also deployed on Solana mainnet: payment splitting, deadline validation, agent identity (ERC-8004).