The Digerati

Contract Next.js developer · Singapore

Next.js developer in Singapore, available now

Most of my recent production work ships on Next.js: a subscription product on Next.js 16 and React 19 with the compiler enabled, a GenAI agent platform delivered full stack inside Colgate-Palmolive, and an organisation tier added to a live B2B SaaS with zero breaking changes. Between them they cover the problems that decide whether a Next.js build holds up: paid content gated server-side so it cannot leak through the RSC payload, technical SEO that survives crawlers, and deployment that does not assume one managed platform. Twenty years of full-stack delivery sit behind all of it. On a contract you get the lot, in your codebase and your conventions.

  • Next.js in production across a subscription product, a Colgate-Palmolive platform and a live B2B SaaS
  • Server-side content gating that does not leak through the RSC payload
  • Self-hosted deployment on Node, not tied to a single managed platform
See selected work

Availability and engagement

Straight answers to the things recruiters screen on first.

Available now Singapore, on-site or hybrid Full-time contract engagements Fixed-scope projects Day rate on request

Next.js

What I actually do with Next.js.

App Router

Server and client component boundaries drawn deliberately, dynamic segments, and revalidation tuned per route rather than globally.

Technical SEO

Titles, descriptions and canonical URLs set per route, JSON-LD for the content types that earn rich results, and IndexNow submission on publish.

Auth & subscriptions

NextAuth v5 with credentials, account management, admin surfaces, and entitlement checks resolved on the server.

Data access

Reading directly from the same relational store a separate pipeline writes to, with the query cost of a page treated as a budget.

Styling

Tailwind 3 and 4, framer-motion where motion earns its place, and component libraries built rather than imported when the design is specific.

Self-hosting

next start on Node 20 behind a reverse proxy with a PID-file launcher, for clients who cannot or will not deploy to a managed platform.

Worked examples

Three problems and how they were solved.

All three from the subscription product, because it is the build I can walk you through end to end. The rest comes up in conversation.

The freemium gate most sites get wrong

A client component receives every field you pass it, whether it renders them or not: the whole object ships in the RSC payload and is readable in the page source. Hiding paid values behind a conditional in JSX is not a paywall, it is an inconvenience. On this site the gating happens server-side, nulling the fields before they cross the boundary, so a logged-out visitor and a crawler receive markup that genuinely does not contain the paid data. This is the single most common paid-content bug I see in App Router codebases.

Historic pages that do not silently rewrite themselves

The site publishes dated prediction pages that are indexed and linked. If the selection thresholds behind them are retuned, every historic page would quietly change to match the new rules, which is both dishonest and terrible for search. Instead, the configuration is snapshotted into an append-only history keyed by date, and past pages render against the config that was live when they were published. Predictions are also frozen at kickoff in the database layer, so the record cannot be revised after the fact.

Off the managed-platform default

This runs as an in-place next start on a cPanel-style Node 20 host with a PID-file launcher on a fixed port, because that is what the hosting allowed. Plenty of Next.js work assumes a specific managed platform and quietly falls apart without it; knowing which features depend on that platform, and which are just Node, is the difference between a deployment that works and a migration that stalls.

FAQ

Next.js contracting in Singapore: common questions

Are you available for Next.js contract work in Singapore?

Yes. Available now for full-time contract engagements in Singapore, on-site or hybrid. On Next.js I am usually brought in for the front end and the service behind it together, which is where most of the awkward problems live. Fixed-scope work runs through The Digerati.

What is your day rate?

Day rate on request. Engagement length and on-site requirement matter most. Tell me the shape of the role and you will get a number rather than a range.

Do you work with the App Router or the Pages Router?

Both, though my current production work is App Router. If you are on the Pages Router and it is working, I will not push a migration you do not need; if you do need one, I would rather scope it honestly than start it optimistically.

Can you help with Core Web Vitals and SEO?

Yes. That is a large part of why I get hired for Next.js specifically: metadata and canonicals per route, structured data that matches what is actually on the page, sensible revalidation, and keeping the client bundle small enough that interaction metrics hold up on a mid-range phone.

Do you do the back end too?

Yes. Most of my work is full stack. On the Next.js side that usually means route handlers and server actions; where there is a separate service, I am typically the one writing that as well, in Python and FastAPI.

Can you work with our designers rather than around them?

Yes. I spent over a decade in agencies alongside UX and creative teams, and I have also shipped a product that converts Figma files into production markup, so I am fairly fluent in the handover in both directions.