Availability

Hire a Next.js and TypeScript developer

Next.js is what I build on daily — App Router, server components, server actions, streaming, and the deployment and caching behaviour that comes with them. Every production product in my portfolio runs on it, so the tradeoffs I recommend come from having lived with the consequences.

Start a conversation

Next.js applications in production: 20+Next.js applications in production
load time reduction on a Next.js revamp: 40%load time reduction on a Next.js revamp
App Router used across all current work: Next 14App Router used across all current work

Where teams get stuck

App Router is a genuine relearning curve

Server components, caching layers, and server actions change how data flows through an application. Teams migrating from the Pages Router routinely hit caching behaviour they did not expect.

Your Next.js app is slower than it should be

Next.js is fast by default and easy to make slow — client components where server components belong, unoptimised images, oversized bundles, and blocked rendering paths.

Hiring for React is not hiring for Next.js

React experience does not cover rendering strategies, caching semantics, or route-level data patterns. Those are exactly where production Next.js applications go wrong.

What you get

Next.js App Router applications built on current, supported patterns
Pages Router to App Router migrations done incrementally
Server components and server actions used where they genuinely help
TypeScript throughout, typed end to end from database to UI
Core Web Vitals optimisation with before-and-after measurements
SEO fundamentals built in — metadata, structured data, sitemaps, canonicals
Deployment on Vercel, Google Cloud, Docker, or your own infrastructure

How it works

01
Codebase review
For existing projects I start by reading the code and identifying the highest-impact issues before proposing any changes.
02
Plan with tradeoffs stated
You get the approach in writing, including what it costs and what it rules out. No architecture decisions made silently.
03
Ship incrementally
Work lands in reviewable pieces your team can follow, rather than one enormous pull request at the end.
04
Document and hand over
Patterns documented so your team can extend the work without needing me.

Frequently asked questions

Do you work with the App Router or Pages Router?

Both, though I build new projects on the App Router. I also handle incremental Pages-to-App migrations, which can run route by route without a rewrite.

Can you improve our existing Next.js app's performance?

Yes, and it is common work. I start with a measured audit — bundle analysis, Core Web Vitals, render blocking — and report improvement against that baseline rather than by assertion.

What backend do you pair with Next.js?

Next.js API routes and server actions for most products, Node.js or FastAPI services where the work justifies a separate backend, with PostgreSQL and Prisma for data.

Can you join our existing team?

Yes. I work in your repository, follow your review process, and match your existing conventions rather than importing my own.

Need a Next.js developer who has shipped it?

Send me your repository or a description of the project. I will tell you what I would change and what it would take.

Email me Contact form

Replies within one business day · NDAs signed as standard