Full-Stack Developer (Go + Next.js + Python) to improve & maintain a Live Production Platform

We run a live web platform that collects pricing and availability data from third-party sources, tracks how it changes over time, and notifies users the moment something they're watching changes. It's in production with real users and real revenue. We're bringing on a developer to take primary ownership of the system as we transition away from our original builder.

This is an established, well-structured codebase — not a greenfield build and not a rescue job. It's version-controlled, documented, and the critical business logic even has tests. We have a full architecture map, a system overview, and an onboarding guide ready to hand to the right person.

We're hiring for the full-stack role below. If your strength is heavily on one side, it's still worth applying — just tell us honestly where you're strongest, since we may also bring on a part-time specialist.

The Stack Backend: Go (Fiber, GORM, pgx), running in Docker behind a Caddy reverse proxy

Frontend: Next.js 16 / React 19, deployed to Cloudflare Workers via the OpenNext adapter

Data pipeline: Python (async) scraper using Playwright and rotating proxies → PostgreSQL → a Go sync job that normalizes into Supabase

AI: Google Gemini (live chat assistant with function calling) and Anthropic Claude (batch content generation) Supporting services: Resend (transactional email automations), AWS S3, and several third-party API integrations

What You'd Own - Ongoing maintenance and new feature work across the backend and frontend Keeping the data pipeline healthy as the source sites change their markup and defenses

Deployments - (Docker for the backend, Cloudflare Workers for the frontend) Keeping the AI features and the email alerting system running reliably Clear, independent communication — we're a small team and we need someone who explains their work plainly

Required - Strong Go — production web services, ideally with Fiber or a similar framework Next.js / React — current versions PostgreSQL — comfortable working directly with schemas and queries, not only through an ORM Docker and basic Linux server administration (our deployment is straightforward: containers and cron, not a heavy CI/CD setup)

Comfort taking over someone else's codebase and working independently

Cloudflare Workers deployment via OpenNext — note this is meaningfully different from deploying to Vercel LLM API integration using function calling / tool use

***A Big PLUS if you are able to maintain a data scraper for the project (not required but advise when you apply if this is in your skill set) --

• Python (async) with real web-scraping experience — Playwright or similar browser automation, proxy rotation, rate limiting, and handling sites that actively resist automated access

Supabase specifically — auth, Row-Level Security, and its connection-pooling model (session vs. transaction pooler)***

About the Transition- We've done thorough groundwork and hired to do a proof of concept. We're ready for full production.

You'll receive a full architecture map, a system ownership document, and an onboarding guide that includes an honest list of the system's known quirks and fragile areas. A few details are still being confirmed with the original developer and are clearly flagged in our documentation — nothing hidden, no black box to reverse-engineer.

To Apply-

Tell us your relative strength across backend (Go), frontend (Next.js), and data collection (Python scraping). Be honest — we're mapping a team, not looking for someone who claims everything equally. Have you deployed a Next.js app to Cloudflare Workers, as opposed to Vercel? Tell us about it. Have you worked with Supabase's connection pooling — session vs. transaction pooler? What's the practical difference?

We'll share our architecture documentation with serious candidates, and we start with a small paid trial task so we can both confirm fit before committing to ongoing work.

If you want to send over your application, please write "no ai" in the title.