Skip to main content
Yevgen 'Scorp' Sukharenko

What I can build for you

I am one engineer, not an agency, and that is the point: the person who designs the architecture is the person who writes the code, sets up the servers and answers the phone when production breaks. Thirty years of that, across products I own and clients who include The New York Times.

Available for new projects

Taking on new work from September 2026 · remote, EET (UTC+2/+3)

Web applications and SaaS, end to end

For founders and businesses who need a product built and running, not a prototype.

I take a product from an empty repository to a running system: data model, architecture, backend, interface, deployment and the monitoring that tells you when something breaks. One person owning the whole stack means no hand-off gaps between a frontend contractor, a backend contractor and whoever was supposed to set up the server.

  • Architecture and data model designed for what the product becomes, not only for the first release
  • Backend, API and admin panel, with roles and permissions where the business needs them
  • Payments and subscriptions - Stripe or PayPal, including webhooks and reconciliation
  • Deployment, CI/CD, backups, error tracking and analytics, running on your own infrastructure or a cloud
  • Documentation and a handover, so the work can continue without me
Already done this

Sharvarok - a US classifieds platform with Stripe checkout, subscriptions and PCI DSS SAQ A eligibility, built and run as sole technical owner

How it is billed: Fixed price for a defined scope; monthly retainer for ongoing work and support.

Next.js · React · TypeScript · Node.js · PostgreSQL / MySQL · Prisma · Stripe · Docker

Mobile apps for iOS and Android

For products that need to be on a phone, in the stores, and reviewed without a fight.

Native iPhone apps in Swift and SwiftUI, native Android apps in Kotlin and Jetpack Compose, sharing one API with your web product so content and behaviour stay identical across all three. I have shipped both to the App Store and Google Play, passed review, and kept them in production - including the parts nobody budgets for: store listings, signing, push notifications, deep links and release pipelines.

  • Native iOS and Android clients against a single shared API
  • Offline-friendly behaviour - content cached and readable with no signal, which is the actual condition on a boat or in a lift
  • Push notifications, home-screen widgets and deep links that open the right screen
  • In-app purchases and subscriptions across Apple, Google and the web, resolved to one account
  • Store submission, review, and the release pipeline for shipping updates afterwards
Already done this

Red Sea Creatures - iPhone and Android apps live in both stores, cleared review, running against the same self-hosted API as the website

How it is billed: Fixed price per app for a defined scope; monthly retainer for releases and support afterwards.

Swift · SwiftUI · Kotlin · Jetpack Compose · React Native · Firebase · StoreKit · Play Billing

SEO and Core Web Vitals: audit and repair

For sites that already exist, already have traffic, and are losing both to a slow front end.

This is the work I did for The Athletic at The New York Times, and it is the most measurable thing on this page. I find what is actually costing you - payload, hydration, render blocking, broken canonicals, structured data Google silently ignores - fix it in the code, and show the before-and-after in your own Search Console and field data rather than in a lab score.

  • An audit naming the specific defects, ranked by what they cost, not a generic checklist
  • The fixes implemented - payload, LCP, CLS, INP, caching, image pipeline
  • Structured data and Schema.org markup that produces real rich results
  • Crawling and indexing repaired: sitemaps, canonicals, redirect maps, duplicate consolidation
  • Before-and-after numbers from field data, plus monitoring so regressions surface early
Already done this

Red Sea Creatures - 632 KB → 188 KB of page HTML, LCP 7.2s → 3.8s, mobile Lighthouse 65 → 93, CLS 0.247 → 0, TTFB ~1.3s → ~20ms, all measured on production traffic

How it is billed: Fixed price for the audit; fixed price or hourly for the repair work that follows.

Core Web Vitals · Schema.org / JSON-LD · Next.js SSR & RSC · Cloudflare · Search Console · Datadog RUM

AI integrations and technical leadership

For teams that need AI to actually ship, or need someone senior owning the architecture.

Two things that go together more often than not. On the AI side: image recognition, automatic translation, content moderation and generation, built as a real service with cost control and graceful failure - not a demo that calls an API and hopes. On the leadership side: architecture, technical specifications, code review, and running a team, which is what I did as CTO at Sharvarok and as Team Lead across distributed teams for a decade.

  • AI features designed around cost, latency and what happens when the model is wrong or the service is down
  • Image recognition, translation, moderation and generation pipelines wired into your product
  • Architecture reviews and technical specifications your team can build from
  • Code review, engineering standards and mentoring for an existing team
  • An honest assessment when AI is the wrong tool for the problem you described
Already done this

FishID - photo recognition across 1,337 species from 10,646 photographs, with its own recognition service, dataset pipeline and billing, built solo

How it is billed: Hourly or monthly, depending on whether you need a build or an ongoing pair of senior hands.

OpenAI · Anthropic Claude · Google Gemini · Image recognition · Python services · Architecture · Code review

How working together goes

The same four steps whether it is a two-week audit or a product built from nothing. You always know what happens next and what it costs before it happens.

  1. 01

    A call, and an honest answer

    Thirty minutes on what you are building and why. You leave knowing whether this is something I should be doing at all - sometimes the answer is that your existing team can, or that the problem is not the one you thought it was.

  2. 02

    Scope, estimate, and a written plan

    What gets built, in what order, and what it costs. Written down before anything is charged, so we are agreeing on the same thing rather than discovering the gap three weeks in.

  3. 03

    Build in short cycles, with something to look at

    Working software on a staging URL you can open, updated continuously. No month of silence followed by a reveal - you redirect the work while redirecting is still cheap.

  4. 04

    Launch, then hand over properly

    Deployment, monitoring, and documentation. The code and the infrastructure are yours, and I am reachable afterwards - but you are never locked to me by an undocumented system only I understand.

Available for new projects

Have a project in mind?

Tell me what you are building and what is in the way. If I am not the right person for it, I will say so and point you at who is.

Start a conversationMessage on Telegram