Product Engineer / Full Stack Builder

We're an early-stage company building infrastructure that connects loyalty programs to premium sports inventory. We move fast and we ship weekly. We're looking for a builder who can take an outcome, not a spec, and turn it into shipped, working product by the end of the week, on their own. This is not a ticket-taking role. You will be handed an outcome ("a partner can upload inventory and have it flow into our system," "a client can log in and see a live dashboard") and own it end to end: the product thinking, the build, and the ship. You decide how. We decide what. You'll move across the whole stack week to week. One week it's a partner-facing portal or dashboard (React, front-end, clean UX). The next it's data plumbing, an API integration, an AI-powered intake pipeline that parses messy inputs into structured data. We want range and judgment, not a narrow specialist. What you'll actually build (examples from our current roadmap) Partner-facing portals: onboarding flows, live dashboards, inventory filtering A fast white-label re-skin capability (drop a logo, change colors, ship) An inventory intake system: structured forms plus AI (Claude API) parsing PDFs and unstructured submissions into a clean schema Third-party API integrations feeding a central inventory store You're a fit if: You ship. You can point to things you built and put in front of real users, fast, by yourself. You're fluent with modern AI build tooling (Cursor, v0, Claude, etc.) and you use it to move fast without losing quality. You're full-stack enough to own a feature front to back: front-end (React/Next), back-end, APIs, data. You're comfortable being given an outcome and figuring out the how. Ambiguity energizes you rather than blocking you. You communicate by showing working things, not status updates. You're not a fit if: You need detailed specs and tickets to start. You go quiet when a task is ambiguous instead of pushing forward or asking sharp questions. You think in "I worked on it" rather than "here's the thing, it's live, try it." How we work: Monday: you commit to one thing you'll ship by Friday, stated as something a user can now do. Friday: you demo it live. If it's not demonstrable, it didn't ship. That's the rhythm. Weekly, end to end, working product. To apply Don't send a generic proposal. We'll ignore those. Instead, answer the screening question below. We read every answer to it and we hire almost entirely off it plus a short paid test. Screening question (put this in the post) Tell us about one thing you built and shipped end to end, by yourself, in a week or less. What was the outcome you were given (or gave yourself), how did you decide what to build, and what could a user actually do when you were done? Include a link if it's live. Then: if we asked you to build "a way for a partner to upload messy inventory data (a PDF, a pasted email, a spreadsheet) and have it turn into clean structured records in our system," how would you approach it, and what would you ship in the first week?