V·NESTERENKO

What you can hire me for

I build and run web systems for businesses that need one person to own the whole thing – from the first requirements call through architecture, code, deployment, and the alerts that fire at 3am. Six years, mostly solo or leading a small team.

Start a conversation →Book a 30-min call

You know what the business needs. You don't have the engineering to build it.

Build the product end to end

I take it from requirements to production: scoping workshops, data model, architecture, the build itself, deployment, and monitoring. You get a running system and a codebase your next developer can actually read – tests, migrations, and documentation included, not promised.

A creator–brand marketplace: primary author on a five-person team – 74 API routes, 19 data models, 5 scheduled jobs, built over 12 months.

Your numbers live in four tools and someone reconciles them by hand every week.

Unify systems that don't talk to each other

I connect the providers over OAuth, handle the token storage and refresh nobody wants to think about, normalise the data, and put it behind one interface your team actually opens. The manual reconciliation stops.

A multi-brand e-commerce operator: QuickBooks, Shopify, Meta Ads, and Google Ads/GA4 unified into a single dashboard – 32 API routes, built in three months.

Your users work in screens where a mistake costs real money.

Interfaces for dense, high-stakes data

Deal books, trading flows, financial dashboards – tables that stay fast at volume, multi-step flows that can't lose state, and typed API clients generated from your schema so the frontend can't drift from the backend.

A securities-lending trading desk: built the deal-book table, the returns and recall flows, and led the migration from JWT to session-cookie auth – 52,000 of 260,000 lines added to the codebase.

It works, sort of. The person who built it left. Deploys are frightening.

Take over a system nobody wants to run

I learn the system, put its infrastructure into code so it can be rebuilt on purpose rather than from memory, add the monitoring that tells you before your customers do, and then keep it running. This is the work most contractors won't take.

A staffing provider's time-tracking and accounting platform: two years of maintenance and development, 41 Terraform resources covering VPC, ECS, RDS, load balancing, autoscaling, and CloudWatch alarms.

How it runs

No surprises, and nothing about the process that only benefits me.

  1. Call

    Thirty minutes. You describe the problem. I tell you honestly whether I'm the right person – sometimes I'm not, and I'll say so.

  2. Discovery

    Fixed fee. I produce a written architecture, a scope, and a real estimate. This is where the unknowns get found, before they cost you.

  3. Build

    Fixed scope per milestone, with a working demo at the end of each one. Not a status report – something you can click.

  4. Handover

    You own the repository, the infrastructure, and every account from day one. Nothing is hosted on something only I can access.

Where the risk sits

The discovery phase is fixed-fee and the output is yours to keep – the architecture document and the estimate – whether or not you hire me to build it. If the estimate is more than you want to spend, you've lost a small fixed amount and gained a specification you can hand to anyone. That's deliberate: it means I have to be worth choosing at the point where you're best informed, rather than at the point where you're most locked in.

Ways to engage

Questions I get asked

Can you work with our existing team?

Yes, and most of my work has been exactly that. I've been primary author on a five-person team and a frontend contributor on a four-person one. I'm comfortable owning a slice rather than the whole thing.

What if we already have a codebase?

That's the normal case, not a problem. I've taken over a two-year-old system, moved its infrastructure into Terraform, and run it in production. Inherited code is a category of work I actively want.

Where are you, and how do you work?

Innsbruck, Austria – Central European Time, authorised to work in Austria. I work remotely by default and can be on site in the Innsbruck and Tyrol area. Most of my clients have never been in the same room as me.

What languages do you work in?

English at C2 and Ukrainian natively. My German is B1 and improving – fine for everyday conversation, and I'd rather tell you that up front than discover it in a meeting.

What do you actually use?

TypeScript, React, Next.js, Node, and Ruby on Rails, on PostgreSQL. Infrastructure on AWS with Terraform, or Cloudflare Workers. I pick the boring option unless there's a reason not to.

How soon can you start?

Depends on the month – ask. I'd rather give you a real date than a reflexive 'immediately'.

Tell me what you're building

Describe the problem in a couple of sentences. If I'm not the right fit I'll tell you, and where I can I'll point you at someone who is.

Start a conversation →Book a 30-min call