Content Engineer (part-time)

The Business Case Writers 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 Exists AirOps 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 Does Design and maintain AirOps content workflows across all content types Create 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 content Assess workflow output quality at the structural level: research approach, methodology alignment, brief readiness for editorial review Update workflows as Foundation’s strategy evolves — new formats, methodology changes, template updates Onboard new clients as the pilot expands Troubleshoot workflow issues; escalate to AirOps support when needed Expand Foundation’s use of AirOps by experimenting with new capabilities and piloting them into production What This Role Does Not Do Write client content or create briefs manually Manage client relationships or communicate directly with clients Determine brand kit content — that’s the editor’s domain via the writer’s guide Make client-specific content strategy decisions Who This Person Is Required : Systems thinking — breaks content processes into logical steps, spots where they break down AI fluency — comfortable with AI tools, prompt logic, and automation platforms Content knowledge — understands how different content types work; familiarity with AI visibility and GEO is a strong asset Attention to detail — small prompt changes have meaningful downstream effects Self-directed — finds what’s not working and fixes it Collaborative — aligns before moving forward on experiments or changes Nice 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 better Familiarity with SEO, B2B content marketing, or AI visibility What Success Looks Like at 90 Days Runs briefs end-to-end for any active client without support Has shipped at least one workflow improvement Editors spend 15 minutes or less on brief review Ready to onboard the next client independently