About

We're Looking for an experienced Next.js engineer to help us tame our Prismic usage. Our website (https://thedecisionlab.com) runs a large content hub - hundreds of resource pages, category archives, and dynamic listings, on Vercel (Next.js 13) with Prismic as the headless CMS. Over time we’ve accumulated a sizable mix of static generation, ISR, serverless API routes, and Edge middleware that pull from Prismic’s REST and GraphQL endpoints. The downside: we’re now seeing extremely high API traffic (millions of requests hitting /api/v2, graphql, and /documents/search), leading to higher costs and slower revalidations. We need someone who can audit our current data-fetching patterns and implement pragmatic optimizations to drastically reduce our prismic API calls. Typical tasks would include: - Reviewing our Prismic client utilities (lib/prismic, caching helpers, middleware) to identify redundant fetches and opportunities to reuse refs, leverage caching, or batch requests. - Refactoring pagination loops, ISR flows, and webhook handlers to minimize repeated master-ref and document searches. - Introducing appropriate caching layers (Redis, in-memory on Vercel Edge, etc.) and guarding against cache-miss storms. - Validating changes end-to-end: profiling API traffic before/after, ensuring pages build correctly, and confirming that our editorial workflow (preview, revalidation, redirects) still behaves as expected. Ideal experience: - Deep familiarity with Next.js (ISR, middleware, API routes) deployed on Vercel. - Hands-on knowledge of Prismic’s REST and GraphQL APIs, including best practices for master ref handling and caching. - Comfort working in larger codebases with shared components, TypeScript/JavaScript, and modern tooling (pnpm/yarn, linting, testing). - Bonus: prior work optimizing headless CMS integrations or tuning rate-limited APIs.