Director of Content Engineering at Tenexlabs in New York City, NY

THE ROLE Content Engineering is to modern marketing what DevOps was to software. A new discipline that makes scale, governance, and speed possible without sacrificing craft. As Director of Content Engineering, you’ll build and own the system that produces editorial content at Tenex. Not a content function that uses AI to make the old playbook 20% faster, but one that breaks the old playbook entirely. You’ll be the operator who treats content the way a product team treats software. Workflows are versioned, brand voice is encoded, quality bars are tested, and every piece that ships compounds the system that made it. The default at Tenex is to build with the frontier, not around it. Your job is to make sure that posture shows up in every word we publish. You’ll build and own a portfolio of editorial franchises across our three content pillars (research, applied, and education) that together make Tenex the smartest, most useful publisher in our space. Research surfaces original data and POVs nobody else is putting out. The franchises are the deliverable. The system that produces them is the moat. You’ll start as the team. Over time, you’ll hire the writers, freelancers, and contractors who execute against the system you build. The mandate is not to be the only person doing the work forever. It’s to build the function that scales beyond you. WHAT YOU’LL DO - Build the content production system. Design the workflows, prompt libraries, agent stacks, and quality checks that turn raw insight into published work. Treat every part of the pipeline (research, drafting, editing, repurposing, distribution) as something to engineer for repeatability and bar. - Encode the house voice. Tenex has a point of view. Your job is to capture that voice in style guides, evaluators, and reference sets so it shows up in every output the system produces, not just the ones you personally touch. - Own the editorial product. Calendar, briefs, deadlines, distribution checklists, performance dashboards. Run the editorial function the way a PM runs a product: with a roadmap, a backlog, and weekly ship cadence. - Launch and operate franchises across our three content pillars: research, applied, and education. Each franchise needs a clear point of view, a repeatable format, and a path to compounding distribution. You define the format and own the bar. - Write and edit at the bar. You can sit at the keyboard and produce a 2,500-word piece that holds. You can take a draft and make it 3x better in an hour. The system is only as good as your taste, and your taste shows up in what you ship and what you reject. - Run AI as the default, not the add-on. Identify, test, and integrate new models and tools across the stack. Build workflows that let one operator output what used to take a team. Be customer zero on every tool you adopt. - Measure as a product owner. Define and track KPIs that map to revenue: organic traffic, MQLs and SQLs sourced from content, pipeline influenced, content-assisted revenue, engagement metrics, and AEO rankings. Report weekly. Iterate fast on what’s working and kill what isn’t. WHAT YOU’LL BRING - 7+ years operating in content, editorial, or technical writing, with at least the last few owning a function at a B2B SaaS, media company, or similar high-bar publisher. Bias to candidates who’ve built or scaled a content system, not just produced inside someone else’s. - Builder’s mindset. You treat content like a product: workflows, briefs, evaluators, dashboards, version control. You can describe a system you’ve built end-to-end and the metrics it moved. You don’t wait for tooling to exist before you start solving the problem. - Whipsmart writer and editor. You can produce a 2,500-word piece that holds, and you can take someone else’s draft and make it 3x better in an hour. House style is something you build, not something you follow. - Technically fluent. Comfortable in the modern AI stack: prompt design, agent workflows, evals, content APIs, basic scripting. You don’t need to be a software engineer, but you need to be the person on the team who pairs with engineers without translation overhead. - Deeply AI-pilled. Actively using frontier tools day-to-day. You can name what shipped this month and why it matters. Bonus credit for having already built AI-native content workflows that produced real output, not demos. - Strategic chops. You can articulate how a content program ladders up to revenue, which formats work for which stages of the buyer journey, and what to kill when something isn’t working. You obsess over the buyer, not vanity metrics. - Soul. You can engineer the pipeline, but the pipeline still needs a point of view. You hold the line on quality even when a tighter deadline or bigger reach would tempt you to ship slop. The best content has a voice and a reason to exist beyond the funnel. THE BAR The best Directors of Content Engineering can do four things at once: write or edit at a high caliber themselves, think strategically about how content ladders up to revenue, build the systems that produce that content at scale, and operate the function with engineering discipline. They obsess over the buyer, not vanity metrics. They treat content as a product rather than a series of one-off posts. And they find the balance between driving performance and creating content that has soul. If that sounds like you, we want to meet.