Full-Stack Developer

We're a science and education media company (YouTube channels including What If and How To Survive, 30M+ subscribers combined) with an in-house video platform called Storysuite. It already handles asset management, publishing, and distribution. We're now building production workflow and freelancer payments into it, replacing a third-party PM tool whose contract ends in December. What you'll build, in order: 1. A kanban-style production board. One card per episode, milestone templates configurable per channel by non-technical showrunners, plus a personal task view with notifications for every freelancer. 2. Approval flows. Frame.io review status syncs onto the card, scripts render in an embedded Google Docs viewer, and the approve/request-changes verdict lives in Storysuite and drives the workflow. 3. A payments engine. Manager approvals write payment lines (never "Done" alone). Three compensation types: per-deliverable with task-keyed rate cards, hourly via approved weekly timesheets, monthly retainer. Idempotent lines, multi-currency, multi-entity, strict row-level visibility (contributors see only their own rates), monthly CSV batch to Tipalti. 4. A cross-channel publishing calendar rendered over the same episode objects as the board (one dataset, two views), plus upload-on-approval to YouTube via the Data API. We are NOT rebuilding video review (Frame.io stays) or payment disbursement (Tipalti stays). A detailed scope document exists and you'll get it before we talk. You're a fit if: - You've shipped production web apps end to end and have built at least one of: a configurable workflow system, a billing/payments pipeline, or a row-level permissions model. Ideally two. - Data modelling is your strength. Most of this project is getting the schema right. - You've integrated third-party APIs and handled their realities: OAuth, quotas, webhooks. YouTube Data API or Frame.io experience is a plus. - Money-touching code makes you careful. Idempotency, audit trails, and parallel-run reconciliation are reflexes. - You can work directly with operations and finance people, not just from tickets. Working setup: Remote or hybrid. Some overlap with Central European and Toronto hours. You'd work with our existing Storysuite codebase and team, not greenfield.