Advanced Technical Content Operator & Calendar Owner — Multi-Brand, CLI/API-Driven

I run an entirely code-and-API-driven content operation across multiple brands. Nothing here happens in a drag-and-drop tool: - Video: raw OBS footage → FFmpeg cuts → Remotion compositions (React- based templates I've built) → rendered output - Social publishing: pushed live via the Blotato API (not a GUI scheduler) - Blog posts: authored/edited as markdown or HTML, pushed directly to the website repo via CLI, deployed from there - Source of truth: a backend calendar/registry (office.temerarii.xyz) defines what goes out, where, and when — you work from that registry, not from ad hoc instructions I need someone who lives in a terminal daily and treats a git repo as home base, not an unfamiliar place. You own the entire content calendar's execution, across every live brand in the registry — not one brand, all of them. That means: - The registry (office.temerarii.xyz and equivalent per-brand registries) stays accurate and current: no stale entries, no silent gaps, nothing skipped without a flag - Every scheduled entry gets executed on time and in order: footage cut, rendered, published, blog pushed, exactly as the registry defines - You enforce drift-gate integrity — if two entries in the same lane collide, you catch it and flag it before anything ships, you don't resolve it yourself - When the queue backs up, you decide execution order across brands (whose post ships first today) — you do NOT decide content, voice, or strategy for any brand. That stays with me. - You maintain a live status view I can check at a glance: published, pending, blocked, per brand - Trigger Blotato API publishing calls (via existing scripts/workflows) for scheduled content across all channels - Pull raw OBS footage, cut with FFmpeg, populate existing Remotion templates per each project's brand guidelines (found in that project's repo — read them before touching anything; do not improvise brand voice) - Push finished blog posts to the website repo via CLI, following the existing content structure - Use an AI coding agent (Claude Code or similar) daily to navigate codebases, debug failed publishes or renders, and commit changes - Verify every post actually went live correctly post-publish (broken API calls, malformed posts, and failed renders get caught and reported, not ignored) - Log daily status against the registry so nothing silently falls through What you escalate to me instead of deciding yourself: new campaign topics, any brand-voice judgment call, anything not already defined in a brand's guideline doc, and adding a new brand to the registry. Your job is that the calendar runs correctly — not what the calendar says. Required: - Daily-driver comfort with git, npm/node, bash - Working knowledge of REST APIs (calling one from a script, reading a response, handling an error) - Working knowledge of React/TypeScript (enough to edit a Remotion composition) - FFmpeg command-line experience - Experience using an AI coding agent (Claude Code, Cursor, etc.) as a daily tool - Comfortable reading a project's README/brand guidelines and following them exactly, without inventing your own interpretation This is a technical operations role. The systems (Remotion templates, Blotato integration, publishing registry) are built by me — you run them, maintain the discipline of the calendar, and flag what breaks. ## Full channel & production scope The registry publishes across every format on a single calendar row — this role owns execution of all of them, not just video/social: **Channels, per the registry's column structure:** - **Blog** — authored/edited as markdown or HTML, pushed via CLI to the website repo, tagged with the correct canonical URL and UTM parameters (per the existing `engine/lib/utm.py` convention) - **Video** — the FFmpeg/Remotion pipeline described above - **Email** — staged and sent via API/CLI to the existing list platform, following the campaign's copy and the weekly send cadence in the registry - **SMS** — staged and sent via API, following the same discipline (one rule that governs this channel per the brand's own rails: if it doesn't earn the interruption, it doesn't send — you enforce that check, you don't decide message content) - **Social — all 9 channels** — triggering the Blotato API calls for the per-channel native rewrites the registry defines (each channel has its own length, tone, hook, and format rules baked into the system; you verify the output matches those rules before it ships, you don't rewrite them yourself) **SEO & analytics:** - Ensure every blog and video asset carries correct UTM tagging and canonical links per the existing convention - Track published-content performance against the metrics I've defined (qualified inbound, saves/replies over raw likes, revenue-traced signals — not vanity counts) and report status weekly; you are not setting which metrics matter, you are reporting against ones already defined **Content review / QA:** - Run every draft through the existing voice gate (banned words, brand rails, no unapproved claims) before anything publishes — this is a checklist you execute, not a judgment call you make from scratch - Flag anything ambiguous rather than resolving it by guessing brand intent **Automated production, at scale — this is the core technical craft of the role:** - Motion graphics: populating and rendering the existing Remotion compositions per each brand's visual spec (color caps, typography, recurring motifs — defined per campaign in the brand book, not invented per asset) - Voice-over: integrating narration tracks per the tone spec defined for each campaign (calm/even, instructional, documentary, etc. — these are already specified per week; you match the spec, you don't set it) - Captions: burning in dynamic captions per platform convention (native per-channel formatting, not one caption style copy-pasted everywhere) - Background music: applying the specified music bed per campaign (a low steady pulse, sparse low-tempo, etc. — again, spec'd per week, not chosen freely) - Multiple aspect ratios: rendering the same source asset natively per channel (9:16 for TikTok/Reels, 16:9 or 1:1 for LinkedIn/YouTube, etc.) from one Remotion source, not re-editing manually per platform **Ideation — scoped narrowly:** you run the system's generation step (the engine drafts a full week's fan-out from one brief), then package those drafts for my review. You are not originating campaign topics or brand voice — that stays with me. If the distinction is ever unclear on a given asset, flag it rather than deciding. **What you escalate to me instead of deciding yourself:** new campaign topics, any brand-voice judgment call, anything not already defined in a brand's guideline doc, which metrics matter, and adding a new brand to the registry. Your job is that the calendar runs correctly, completely, across every channel — not what the calendar says. Question: "Start your proposal with 'REGISTRY READ.' Then tell me: have you called a third-party API from a script before (any API, doesn't need to be Blotato)? And what AI coding agent do you use day-to-day, if any?"