Job Summary

We need one engineer who can own everything that runs on the web at FluxCo—the marketing site, the marketplace, the customer and supplier portals, and the internal tools that keep the business running. The catch: you don't ship like a 2019 engineer. You use Claude Code, Cursor, Codex, and whatever comes next as core tools, not novelties. We expect a small AI-native team to out-ship a large traditional one, and we're building that way from day one.

Core Responsibilities

• Own fluxco.com end-to-end: marketing pages, the marketplace (submission, bidding, Q&A), customer and supplier portals, and internal admin tools.
• Work full-stack on our Next.js (App Router) + TypeScript + Tailwind + Supabase + Vercel stack—React on the front, API routes and Postgres on the back, Resend for transactional email.
• Use AI coding tools (Claude Code, Cursor, Codex, etc.) as a force multiplier—plan with them, draft with them, review with them, ship faster because of them. We care about throughput and quality, not hand-keystroke purity.
• Design and migrate Postgres schemas safely; keep RLS, indexes, auth, rate limits, and abuse controls tight as the marketplace grows.
• Instrument the system—logs, metrics, error tracking—so we catch issues before customers do.
• Translate product ideas and design references (Figma, sketches, plain English) into shipped features without needing a spec doc for every detail. Push back when something feels off.

Requirements

• Education: We don't care how you got here. Show us code you've shipped and products you've owned.
• Experience: 3+ years shipping production web apps end-to-end—front-end UI through to API routes, Postgres, and deploys. Bonus for marketplace, bidding-system, or multi-sided-product experience.
• Stack: Strong TypeScript and SQL (Postgres). Hands-on with Next.js (App Router preferred), Tailwind, Supabase or similar managed Postgres, and a transactional email provider. Vercel familiarity is a plus.
• AI Fluency (required): Daily user of Claude Code, Cursor, Codex, or equivalent. You have opinions about agentic workflows, prompt patterns, when to let the model run vs. when to drive manually, and how to keep AI-generated code reviewable. Tell us how you actually use these tools today—specifics, not buzzwords.
• Product & Operational Sense: You make UI calls without a spec, but you also think about migrations, idempotency, and what happens at 3am when a webhook fails. You write tests where they matter and skip them where they don't.
• Growth Mindset: This is the founding engineering hire for the web platform. If you want to own the whole platform—and grow into a lead role as the team scales—this is the on-ramp.