Full-Stack Developer (Next.js/TypeScript) — AI Video SaaS, long-term

Full-Stack Developer (Next.js/TypeScript) — AI Video SaaS, long-term I run a live AI video-generation SaaS. It turns a script into a finished, editable documentary — AI narration, sourced footage, motion graphics, and a full editing timeline. The core product works. I'm looking for one developer to work alongside me long-term: getting it properly SaaS-ready, then building the features I design. I handle product direction, design, and requirements. You handle the code. What you'll be doing: Strengthening deployment, testing, and monitoring Improving how heavy background jobs are processed Building new features I spec out — I'll describe what I want in plain English, you translate it into working code Fixing bugs and keeping production stable Stack: Next.js 15 (App Router) · TypeScript · PostgreSQL + Drizzle · Node · job queues · Remotion (video rendering) · Stripe · LLM APIs Required — you must actually know how to code: Strong TypeScript, React, Next.js App Router Backend: REST APIs, PostgreSQL, background job queues Confident on Linux servers — deploying, reading logs, debugging live issues Able to work independently in a large existing codebase and make careful changes without breaking things Clear written English I provide a paid AI coding subscription (Claude) as a tool. It speeds you up — it does not replace knowing how to code. You need to be able to review what it produces, catch when it's wrong, and take responsibility for what ships. Please don't apply if AI is doing the thinking for you. Nice to have: ffmpeg/video processing, LLM APIs, Docker, GPU workloads How I work: I'm non-technical on the code side. I need someone who explains things in plain English, tells me when an idea is bad, and tests before deploying. I want a long-term working relationship, not one-off gigs. To apply — answer these three. I ignore generic proposals: Describe a production incident you caused or fixed, and what you changed so it couldn't happen again. In Next.js, what breaks if a long-running streaming (SSE) response goes silent for 5+ minutes, and how would you prevent it? How would you move a feature out of a running production app into a separate worker with zero downtime? Start your reply with the word "kettle" so I know you read this. NDA and IP assignment required before code access. First task is small and paid, so we can both check the fit.