I’m looking for a seasoned Next.js developer to step into an already-running project and focus purely on the server-side code. The application itself is stable on the front end, but several backend routines need attention so we can roll out the next release with confidence. THIS CAN BE A LONG TERM ASSOCIATION IF YOU'RE A GENUINE AND CAPABLE DEVELOPER. THIS CAN BE A LONG TERM ASSOCIATION IF YOU'RE A GENUINE AND CAPABLE DEVELOPER. THIS CAN BE A LONG TERM ASSOCIATION IF YOU'RE A GENUINE AND CAPABLE DEVELOPER. THIS CAN BE A LONG TERM ASSOCIATION IF YOU'RE A GENUINE AND CAPABLE DEVELOPER. THIS CAN BE A LONG TERM ASSOCIATION IF YOU'RE A GENUINE AND CAPABLE DEVELOPER. What you’ll be touching The job is entirely about modifying an existing application, zeroing in on its backend functionality. You’ll be working inside Next.js API routes and the related Node.js logic that powers them. Expect to review current patterns, tighten up code paths, and introduce any missing best practices for reliability, performance, and maintainability. Access & workflow As soon as we agree, I’ll share the private Git repository, an outline of the current architecture, and a concise list of the problem areas we’ve identified. We use GitHub Issues for task tracking and pull-request reviews; CI runs on GitHub Actions. Deliverables (discrete and verifiable) • Clean, well-commented commits that close each assigned issue • Updated unit/integration tests demonstrating that the new or revised backend logic works as intended • A short change log and deployment notes so our DevOps pipeline can pick up the changes without surprises Acceptance criteria The build must pass all automated tests, existing functionality must remain intact, and the new logic should meet the documented requirements without introducing regressions. If you know your way around Next.js, Node.js, and modern testing workflows, let’s get this wrapped up quickly and cleanly.