The Business CaseWriters spend 2–3 hours on every brief. Editors spend 15–30 minutes reviewing and approving each one.AirOps automates brief creation. A writer submits a keyword, the system generates a structured brief, an editor reviews in 15 minutes or less. That 100–150 hours goes back to drafting.The Content Engineer owns the system that makes this work at scale.Why This Role ExistsAirOps is currently being built and expanded across three pilot clients. As it scales to more clients and content types, it needs a dedicated owner — someone who designs, maintains, and grows the workflows.The workflow logic, prompt architecture, and brand kit structure require focused ownership. Adding this to a writer or editor’s existing workload cancels out the time savings the system creates.What the Role DoesDesign and maintain AirOps content workflows across all content typesCreate and configure brand kits during client onboarding; maintain the workflow that keeps them synced when editors update writer’s guides — Content Engineer owns the mechanism, editors own the contentAssess workflow output quality at the structural level: research approach, methodology alignment, brief readiness for editorial reviewUpdate workflows as Foundation’s strategy evolves — new formats, methodology changes, template updatesOnboard new clients as the pilot expandsTroubleshoot workflow issues; escalate to AirOps support when neededExpand Foundation’s use of AirOps by experimenting with new capabilities and piloting them into productionWhat This Role Does Not DoWrite client content or create briefs manuallyManage client relationships or communicate directly with clientsDetermine brand kit content — that’s the editor’s domain via the writer’s guideMake client-specific content strategy decisionsWho This Person IsRequired:Systems thinking — breaks content processes into logical steps, spots where they break downAI fluency — comfortable with AI tools, prompt logic, and automation platformsContent knowledge — understands how different content types work; familiarity with AI visibility and GEO is a strong assetAttention to detail — small prompt changes have meaningful downstream effectsSelf-directed — finds what’s not working and fixes itCollaborative — aligns before moving forward on experiments or changesNice to have:Experience with AirOps or similar tools (n8n, Zapier, Make)Background in content operations, strategy, editorial, or content creation — the more content knowledge, the betterFamiliarity with SEO, B2B content marketing, or AI visibilityWhat Success Looks Like at 90 DaysRuns briefs end-to-end for any active client without supportHas shipped at least one workflow improvementEditors spend 15 minutes or less on brief reviewReady to onboard the next client independently

Heads-up

Content Engineer (Part-Time)

Emma

Requirements and responsibilities

Skills wanted:

Language(s) required:

La Tabron

La Tabron

About Foundation:

www.wkkf.org/

Admin access needed

Payment confirmed

A member of the Torre team will contact you shortly