Next.js · React · TypeScript · Full-stack
You can hire a Next.js developer in two ways: the kind who knows the framework, and the kind who has shipped products with it. I'm the second kind. Eight years of frontend work, several of them leading teams, building production Next.js apps for web3, developer tools, and government workflows.
Most teams don't actually need another Next.js developer. They need someone who can decide what to build, set the standards the rest of the team codes against, and own the parts of the app that determine whether the product feels professional. These are the three situations where that work lands on my desk.
You've validated the idea and you need someone who can ship the whole thing: auth, billing, dashboards, marketing site, the lot. You don't have time to coordinate three freelancers who each own one slice. I bring a full-stack Next.js skillset and a bias toward shipping the smallest version that proves the product works.
Your senior pipeline is months out and you have growth ahead of your hiring. I plug in as a contract senior, ship the next milestone, and document the standards so the eventual full-time hire ramps in days, not months. The work I leave behind is the kind a senior engineer is glad to inherit.
You're shipping into EU, MENA, or LATAM and you need someone who actually understands locale-aware routing, hreflang, RTL layouts, and currency formatting. Not someone who'll Google "next-intl" on day one. I've shipped multilingual Next.js apps with real users in more than one language.
Every tool below is one I've used on a production app this year. If your stack uses something different, I can adapt. These are the tools where I move fastest and where you get the most senior judgment for your money.
Next.js 13, 14, and 15. App Router and Pages Router. React 18 and 19. Server Components, server actions, route handlers, and the streaming model.
TypeScript in strict mode. Codegen at the API boundary (GraphQL Code Generator, OpenAPI). Discriminated unions and mapped types when they pull their weight.
Tailwind CSS with design tokens, shadcn/ui, Radix UI primitives, CSS variables for theming. Packaged design systems as internal npm libraries when scale demands it.
React Query, SWR, Apollo, urql, Zustand. Server components where they fit. Postgres with Supabase, Prisma, or Drizzle for typed database access.
Directus and Sanity. Type-safe GraphQL codegen so the content model and the frontend types stay in lockstep. Marketing teams ship without engineering involvement.
Auth.js, Clerk, Supabase Auth, web3 wallet auth (Privy, viem, wagmi). Stripe, Lemon Squeezy, and Polar for billing, subscriptions, and merchant-of-record setups.
next-intl in production. Locale-aware routing, hreflang, currency and date formatting, RTL languages (Arabic, Hebrew), and content modeling for translation workflows.
Playwright, Jest, React Testing Library, Vitest. Vercel, Cloudflare Pages, Netlify, and AWS deployments. Sentry, PostHog, and Vercel Analytics for what happens in production.
Three projects that say more than a CV bullet point. Each one a different shape (web3 staking interface, developer-tools marketing, government workflows) but the work underneath is the same: senior Next.js judgment, shipped in production.
Problem. A web3 liquid-staking product needed a lead frontend engineer to architect the staking DApp and the marketing surface from scratch. Wallet auth, CMS-driven blog, SEO, design system, all of it from a clean slate.
What I built. Next.js plus TypeScript app with wagmi and Privy for wallet auth, Directus for CMS-backed marketing content, a design system grown from primitives, and SEO surfaces engineered for organic discovery rather than retrofitted.
Outcome. Ownership expanded twice. The frontend now spans multiple Kintsu products and the design system I authored is the foundation new pages are built on.
Read the Kintsu case study →Problem. A Kubernetes autoscaling SaaS needed a marketing site that engineers respected and a marketing team could ship into without filing tickets.
What I built. Astro plus TypeScript front-end sharing the same React design system used in product, MDX-driven content, custom Web Components for interactive demos, and a static-plus-dynamic content pipeline tuned for performance.
Outcome. The marketing team now ships pages and blog posts on their own. Time-to-publish dropped from days to hours, and engineering reclaimed the time it was spending on content tickets.
Read the Kedify case study →Problem. Complex government-tech forms with multi-step flows, field interdependencies, and validation rules that change per region. Built once, used by many.
What I built. React plus TypeScript with Formik and Apollo GraphQL, custom validation primitives, accessible form components, and a Redux-backed data layer for the long-running workflow state.
Outcome. A form engine the internal team continues to extend. Patterns I introduced (typed validation schemas, accessible primitives) became the house style.
Read the ZForm case study →Fixed-fee deep dive on a specific problem: architecture, performance, type safety, or design system. You get a written report, prioritized findings, and patches for the top three issues.
Embedded senior Next.js engineer. I ship features, run code review, and leave the codebase better than I found it. Weekly demos, async-first communication, written summaries every Friday.
1 to 3 days a week as your frontend lead. Architecture decisions, hiring rubrics, design-system governance, mentoring. For teams not ready for a full-time head of frontend.
Public proof beats a sales deck. The posts below are how I think about Next.js, and the level of detail you can expect in an engagement.