Ivan DolgovTech Lead / Full-Stack Engineer

Sheet 06 / Services

Services

Four engagements I can take alongside a full-time role: reviews that end in a written decision, not a delivery team.

Each is scoped in days rather than months, because that is what I can give it, and each rests on work published on this site — the case study or the note under it is the evidence, not a testimonial. English, Japanese or Russian; remote from Tokyo, or with teams outside Japan.

  1. S01

    Performance audit — DynamoDB and AppSync

    Problem
    Loading times and timeouts grew with the data, for every customer rather than on one screen, and nobody changed the architecture.
    What I do
    Every read path in the code, queries profiled against real volumes, request behaviour in CloudWatch. Where the code is hard to follow, the data flow is drawn before anything is proposed.
    What you get
    A written diagnosis — which access patterns are wrong and why, in the order they should be fixed — with the migration and rollback each change needs. The first milestone implemented if you want it.
    From
    ¥480,000
    Duration
    1–2 weeks

    EvidencePackaging-Industry SaaSWhy your DynamoDB app got slow as data grew

  2. S02

    Multilingual audit — hreflang, routing, indexing

    Problem
    A site exists in several languages and the translated pages are not being found, or a language is about to be added and the URLs cannot move afterwards.
    What I do
    Canonical and hreflang reciprocity on every page, locale routing and URL stability, sitemap and robots agreement, and what each locale does to type and layout — a measure set in characters breaks the moment a page is not Latin.
    What you get
    The defects ranked by what they actually cost in traffic, and the build-time checks that stop them coming back — a broken hreflang cluster is not visible in a screenshot.
    From
    ¥280,000
    Duration
    About a week

    EvidenceClient Project Delivery

  3. S03

    Architecture review before a rebuild

    Problem
    A rewrite is being argued for, or a stack is being chosen, and the decision is about to be made on preference because nobody has the time to test it.
    What I do
    What the system has to do first, then whether what exists is a foundation. Candidates are compared by proof of concept — one question that can fail, one timebox, criteria agreed before the first commit, including how the codebase will hold up when much of it is written with an assistant.
    What you get
    A decision record in the form a team can revisit — what was compared, against what criteria, what was chosen and what would change the answer — and the PoC plan. The PoCs run if you want them run.
    From
    ¥480,000
    Duration
    1–2 weeks

    EvidenceAI Chat Game PlatformChoosing a stack by proof of concept

  4. S04

    Japan bridge — requirements in Japanese, specification in English

    Problem
    The client, the users and the regulations are Japanese; the team that will build it is not, and what reaches them is a translation of a translation.
    What I do
    I sit in the 要件定義 meetings in Japanese, and write the specification the offshore team builds from in English — with the terms that have no English equivalent kept as terms, defined once, rather than paraphrased differently in every document.
    What you get
    A specification an engineer who does not read Japanese can build from, a glossary both sides agree on, and review of what comes back against what was actually agreed in the room.
    From
    ¥320,000
    Duration
    A requirements round or one specification, about a week; longer alongside delivery

    EvidenceClient Project Delivery

Prices are floors, before consumption tax, and the scope sets the figure — so describe the problem and I will say what I would do and what it would cost, or that someone else is a better fit. Write to ivan.d@wanya.group. Or book 30 minutes. Or read the work first.