Kostiantyn Amurov

Available for one focused project

Ship the fix.
Clear the bottleneck.

I diagnose software failures and build practical web, API, automation, and data solutions for teams that need a concrete outcome—not an open-ended engagement.

Send a project brief Review GitHub
  • Fixed scope before work starts
  • Milestone-based delivery
  • Source code and handoff included

Focused services

Small enough to move fast.
Complete enough to matter.

01

Technical diagnosis

Turn a reproducible failure or unclear bottleneck into an evidence-based root-cause report and a practical fix plan.

  • Reproduction and investigation notes
  • Likely root cause with supporting evidence
  • Prioritized implementation plan
Typical delivery: 24–48 hours From $75
02

Bug-fix sprint

Reproduce, isolate, fix, test, and document a specific defect in an existing codebase.

  • Root-cause note
  • Regression coverage
  • Review-ready pull request
Typical delivery: 1–2 days From $150
03 Most useful

API or automation mini-build

One workflow, integration, internal tool, or API endpoint built around a measurable outcome.

  • Implementation and tests
  • Configuration example
  • Runbook and handoff
Typical delivery: 2–5 days From $300
04

Data workflow

Turn repetitive CSV, spreadsheet, or reporting work into a repeatable validated process.

  • Cleanup and transformation
  • Validation checks
  • Reusable output template
Typical delivery: 1–3 days From $200
05

Conversion landing page

A fast, responsive page for a product, service, campaign, or technical proof of concept.

  • Responsive implementation
  • Accessible components
  • Deployment-ready source
Typical delivery: 2–4 days From $250

Prices are starting points, not quotes. Final scope, price, delivery date, and included revisions are agreed in writing before implementation.

Public build samples

Systems over screenshots.

These repositories and the diagnostic case study are public samples, not claims of client work. They show the investigation, testing, architecture, and implementation patterns I can bring to a scoped project.

01 Negative-adjustment diagnosis Reproduction · Root cause · Tests · Merged repair Diagnostic case study 02 VendorShield Vendor risk monitoring · Go · ClickHouse Security data platform 03 Cashflow Pilot Forecasting and budget workflows · Rails · React Full-stack product 04 DocVault Managed identity and cloud deployment · TypeScript · Azure Cloud service 05 Stockroom Inventory ledger API · FastAPI · SQLAlchemy Backend API

Working process

One clear path from brief to handoff.

  1. 01

    Define the finish line

    We agree on deliverables, acceptance checks, timeline, price, and included revisions.

  2. 02

    Build in a reviewable slice

    You get concise progress notes and an implementation that stays inside the agreed scope.

  3. 03

    Verify and hand off

    I run the agreed checks, provide source and documentation, and address the included revision pass.

Have a concrete bottleneck?

Send the outcome, constraints,
budget, and deadline.

The initial brief is public on GitHub. Do not include credentials, customer data, private source code, or payment details.

Open a project brief