Payload CMS Bug Fixes and Launch Prep

We're getting a content-heavy marketing site ready to launch and need a dependable full-stack dev to help clear our QA punch list. The workflow is simple and repeatable: pick up a ticket from our QA board → reproduce and fix it locally → open a PR to GitHub for our team to review and merge. Clear acceptance criteria on most tickets. No production access needed — we merge. This is a mature, existing codebase. What you'll do - Pick up QA tickets and clarify scope where needed - Reproduce and fix issues locally — UI/responsive, CMS content blocks, occasional back-end - Open clean, focused PRs (one fix each) with a note on how you verified it - Address review feedback until approved Stack Next.js (App Router) · React · TypeScript · Tailwind · Payload CMS (MongoDB) · Storybook · Vercel · GitHub Must have - Strong React + Next.js (App Router) + TypeScript - Pixel-accurate, responsive Tailwind work - Confident Git branch → PR → review workflow - Methodical debugging and clear written communication Nice to have Payload or another headless CMS · Storybook / design systems · Vercel · pre-launch QA punch lists Scope - Type: Ongoing, short-to-medium term (through launch) - Hours: ~10–20 hrs/week, weekly cap - Full project brief, repo access, and setup docs shared after we connect