React without the framework tax
I pick the stack for the product, never for the résumé. Vite and a plain server when that is enough, Next.js when it earns its place, no client framework at all when one HTML stream does the job.
React in production since 2017
A React developer who ships, reviews and measures
Fifteen years of shipping software, nine of them in React and TypeScript. I build the interface, the tests around it and the dashboard that tells you whether it worked.
Available from November 2026 · Wrocław, Poland (CET), remote
- “someone you can always count on”public LinkedIn recommendation
- “a true bias for action”client CTO, on LinkedIn
- 15+ yearsshipping software
- Free call, no pitch deck30 minutes, then you decide
2017React in production since
9years of TypeScript, React and Node.js
~30%of merged PRs in 2026 opened by an AI agent, ~85% reviewed by me
100,000+players of Korona Krulów, built in two weeks
Why me
Accessible by default
WCAG 2.2 AA behind an axe gate, keyboard paths tested in Playwright, text scaling to 200%. Older users of an email client I built never saw a regression.
Reviewed and measured
Hundreds of pull requests reviewed. PostHog from day one, so the component you paid for shows up as a number, never as a feeling.
Agents in the loop
An AI agent opens about a third of our pull requests under rules I wrote. You get the speed and I keep the quality bar where it was.
Proof
Work I can show
Problem, what I did, result. Client names only where I am allowed to use them.
A desktop 3D measurement product rebuilt for the browser, React in 2017
- The problem
- A US manufacturer of precision instruments had a desktop app for visualizing 3D scans and wanted feature parity in the browser.
- What I did
- WebGL and three.js for the scans, React for the interface, a .NET backend around the client’s computation library, Stripe billing, visual regression tests, shared team tooling. Work in English across a nine-hour time difference.
- Result
- Feature parity reached. When the client cut the team for budget reasons they chose which engineers to keep and I was one of two.
See also: C# & .NET (legacy)
Patriot Mail: from first commit to the App Store in four months
- The problem
- A greenfield AI-native email client for web, iOS and macOS had to reach real users fast, pass Google’s CASA Tier 2 security assessment and work for older people.
- What I did
- I was the principal engineer. I wrote the delivery plan, shaped the product vision and treated prompt injection through untrusted email as a design constraint before any model touched a mailbox. CASA and OWASP ASVS controls became a Playwright suite that runs on every pull request. WCAG 2.2 AA sits behind an automated axe gate.
- Result
- Public App Store release in four months. CASA Tier 2 passed and the yearly questionnaire turned into a check on every PR. Text scaling to 200% and a calm-email mode shipped for older users.
See also: SaaS & MVP · Mobile & desktop apps
Korona Krulów: a satirical React game for 100,000+ players, built in two weeks
- The problem
- Spring 2020, lockdown, a joke that deserved a game before the joke got old.
- What I did
- React, 400+ actions, a leaderboard, open source on GitHub, shipped in two weeks of evenings.
- Result
- 100,000+ players and ~700 upvotes on Wykop at launch.
See also: JavaScript · Games
One foot in the door
Not ready for a project? Start smaller.
Two ways to see how I work before you commit to a sprint. Fixed scope, a number in writing after a short call.
React codebase audit, one week
I read the repo, CI, tests, security and the parts the team avoids. You get a written report with findings ranked by risk, a plan with milestones and a go or no-go you can defend. I have run this for a large software house before its clients saw the code.
Code review of one pull request or one module
Send me the diff that worries you. Within a few days you get line-level comments, the three things I would change first and whether I would merge it.
Ask about an audit Free 30-minute call first. If an audit is the wrong tool, I say so on the call.
Live demo
A component you can edit
Edit the component below. It renders live with React 18 loaded from this page, no bundler, no build step. The Profiler readout shows every commit and how long it took. Flip StrictMode on and watch effects run twice, exactly as they do in your dev build.
Demo loading…
Break it on purpose. The error boundary catches it and tells you why.
How it works
Three steps from this page to a running project.
- 1
A 30-minute call
You describe the product and the problem. I ask the questions I would ask on day one. If I am not the right person, I say so and point you to someone who is.
- 2
Scope in writing
A short written plan follows: what we build first, what we measure, how we work together and what it costs. No slide deck.
- 3
Something to touch in week one
The first slice ships in the first week: deployed, measured, reviewable. From there the work is paced by what the numbers say.
Fit check
Is this a fit?
A good fit when
- You need a senior who owns delivery, not a pair of hands
- The product has to ship and be measured, with or without a product manager
- A solo engagement or a team of up to four
- TypeScript, React, Node.js, Cloudflare, Postgres, PostHog
Probably not when
- A program that needs a ten-person vendor team
- A stack built around Java, Python or a cloud I do not sell
- Body leasing by the hour with no say in how the work is done
- A start before November 2026
Working style
How I work
Review as a craft
Hundreds of pull requests reviewed. I review for the product and its reasons. The code comes second.
Agents under rules
Claude Code and Codex work on main with hooks, lint and test gates. The model suggests, the criteria decide. Every PR gets a human review and AI-assisted content is disclosed.
Measured, not assumed
PostHog in every project from day one. A tracking plan per feature and dashboards leadership actually reads.
FAQ
Questions people ask before they book
Do you work with Next.js?
Yes, with reservations. App Router, Server Components, the lot. If your product is a long-lived app with a stable API, I will tell you when Next.js is a tax rather than a tool. There is a whole page about it: hire me for Next.js.
How do you test React code?
Playwright for end-to-end and visual regression across browsers and devices, axe for accessibility, unit tests where the logic lives. On one project Google’s CASA security controls became a Playwright suite that runs on every pull request.
React Native too?
Shipped to iOS and Android as wrappers for a SaaS and as ad features in a travel app. Native where it pays, web where it does not. More on the mobile and desktop apps page.
Can you take over an existing codebase?
That is most of my work. First an audit with findings you can act on, then a plan, then the first pull request within days.
Do you use AI coding agents?
Yes, under enforced rules: lint and test gates, review of every PR by me, disclosure of AI-assisted work. About 30% of merged PRs in 2026 came from an agent and about 85% of those crossed my desk. How that works day to day is on the AI and agents page.
How soon can you start?
November 2026. Book the call now and we scope the work so I start on day one.
Let’s find out in 30 minutes
Free 30-minute consultation. No prices on this page because scope comes first.
If I am the wrong person I will say so on the call and point you to someone better.
After you book: a calendar invite, then the call. Nothing else to fill in.
Available from November 2026 · B2B contract or employment · Wrocław, Poland (CET), remote