← Aleksandr Ryzhakov Interactive resume
A resume that behaves like a decision system

Don’t read my resume. Interrogate it.

Most resumes are a list you scroll. This one branches. Tell it what you care about — or walk the actual tree of how I take a piece of work from request to production. Everything here is a real decision, made the way I make it.

A request lands. Now what?

every branch is a real rule
path taken

This is the genuine routing logic behind League60 and the exhibits on this site — not a simplified cartoon of it. The same tree decides who builds what, and nothing ships until its gate shows real output.

The analytics depth

eleven years, indexed
Analytics & strategy, across industries
11 years · pricing, retention, market sizing, executive reporting

Pricing and demand modelling, retention and churn economics, market sizing, and reporting straight to the people who make the calls. The recommendations that — on this site — stopped ending at the slide and became the working tools you can open.

branch ready — facts to come

Role-by-role, this path will branch into the specific engagements: the industry, the decision at stake, the model built, and the number it moved. We’re assembling those together.

Full role-by-role history lives in the CV — request it →

The systems I build

shipped & live
League60 — live tennis-league PWA
React · PWA · offline-first · Supabase · Cloudflare · 2025

An offline-first app that runs a real tennis league — fixtures, live standings, results that sync when there’s signal and keep working when there isn’t. Built solo in six weeks by writing specs and routing them to AI agents. Read the build →

The live exhibits on this site
vanilla JS · public data · self-writing analysis

A break-even model, a European price dashboard, and a global health-value chart — each built by the same pipeline, each writing its own analyst’s notes. Not screenshots: open them.

branch ready — facts to come

This path will branch into the systems that came before the public ones — the internal tools and pipelines from your roles, described to the line your confidentiality allows.

One person, a team’s output

the operating model
Spec → Route → Verify → Ship
the loop behind everything here

I write a spec precise enough that an AI can build from it, route each piece to the agent best suited to it, gate the result on real output — not trust — and ship when the gates pass. A skill library carries the standards between builds. It’s how one analyst delivers like a delivery organisation.

Prefer to see it in motion? The is this model, walkable.

Open an exhibit → Two doors — hire me, or the process → built with the system it describes