Do you work hourly, weekly or fixed-scope?

Weekly retainer for ongoing work, fixed price for a defined deliverable. Hourly billing rewards slowness, so I don't use it.

Can you join an existing codebase?

Yes, that's most of this work. I start with a read-through and a short written note on what I found: the risky parts, the quick wins and where I'd start.

What timezone do you work in?

Central European Time, with overlap into US mornings. Async by default over Telegram, with calls when a decision needs faces.

Can you do backend too?

Yes. Postgres schemas, serverless functions, auth, Stripe billing and third-party integrations are part of normal delivery, not a separate hire.

How fast can you start?

Usually within the week, depending on how many builds are already running. Ask and I'll tell you the real date, not a hopeful one.

React development

Hire a senior React developer without hiring a whole agency.

You have a product, a roadmap and not enough hands. What you usually don't need is an onboarding deck and three people on every call. I plug into your repo, ship features that survive contact with users, and leave the codebase cleaner than I found it.

Get a scoped estimate See shipped work

Engagement: Weekly retainer or fixed scope
Stack: React 19, TypeScript, TanStack
Backend: Postgres, serverless, Stripe
Timezone: CET, overlaps US mornings

What you get

Feature work shipped to your branch with typed, reviewable commits
SaaS dashboards, customer portals and internal admin tools
Design-to-code from Figma, a screenshot, or a rough sketch
Performance work: bundle size, LCP, hydration cost, list virtualisation
Auth, roles and multi-tenant data rules that hold up in review
Stripe or Paddle billing, webhooks and subscription state handling
Refactors of code written under deadline pressure — no lectures
Written handover notes so knowledge doesn't leave when I do

What senior actually buys you

The difference between a mid and senior React developer is rarely syntax. It's knowing which abstraction will hurt in six months, when a state library is overkill, when a component should be split and when splitting it makes things worse. That judgement is what you're renting — the typing is the cheap part.

Data fetching modelled with the router and query cache, not stacked useEffects
Forms, tables and permissions built once and reused, not copy-pasted per screen
Errors and loading treated as first-class UI states, not afterthoughts

Rescuing a codebase someone else started

Half of this work is inherited code: a contractor left, an AI-generated build stalled, or the founder wrote it themselves and hit the ceiling. I don't rewrite as a reflex. I map what exists, isolate the parts that actually block you, and fix those first so you get momentum back before any big refactor.

Read-through plus a short written risk note in the first days
Stabilise the build, the types and the deploy pipeline before adding features
Refactor incrementally behind working software, never a big-bang rewrite

How working together looks

Async by default in a shared Telegram thread, with a deployed preview for anything visual. You see progress continuously instead of a weekly status meeting. Decisions that need a call get a call — usually short, usually the same day.

Frontend, but not only frontend

Most React work stalls on the seams: the API shape is wrong, the auth model leaks, the webhook is unreliable. I handle those seams as part of delivery — Postgres schemas, row-level security, serverless endpoints and payment webhooks — so you aren't coordinating two contractors across one bug.

Who this is (and isn't) for

Good fit

— Funded startups missing a frontend lead
— Teams with a stalled or inherited React codebase
— Agencies needing senior overflow on a real deadline
— Founders who write some code and want a partner, not a vendor

Not a fit

— Angular, Vue or native mobile work
— Roles that need on-site presence
— Long-term full-time employment
— Projects where nobody can answer product questions

Questions I get asked

Do you work hourly, weekly or fixed-scope?: Weekly retainer for ongoing work, fixed price for a defined deliverable. Hourly billing rewards slowness, so I don't use it.
Can you join an existing codebase?: Yes, that's most of this work. I start with a read-through and a short written note on what I found: the risky parts, the quick wins and where I'd start.
What timezone do you work in?: Central European Time, with overlap into US mornings. Async by default over Telegram, with calls when a decision needs faces.
Can you do backend too?: Yes. Postgres schemas, serverless functions, auth, Stripe billing and third-party integrations are part of normal delivery, not a separate hire.
How fast can you start?: Usually within the week, depending on how many builds are already running. Ask and I'll tell you the real date, not a hopeful one.

Keep reading

MVP development servicesFor products that don't exist yet — scoped and shipped in 4–8 weeks.Open Shipped workApps, bots and dashboards already in production.Open How I workWeek-by-week from kickoff to handover.Open Why work with meThe honest version, including the trade-offs.Open Client feedbackWhat people said after the invoice cleared.Open Engineering notesReact performance, scoping and shipping essays.Open

Prefer chat? Message on Telegram instead — same inbox, faster.