Responsibilities

• Own the strategy and roadmap for our content: what we publish, when, and how the portfolio compounds over time
• Build a collection of data-driven reports, starting from our AI Engineering report, and own each one from concept and methodology through writing and launch
• Partner with our engineering and data teams to find the stories in the data and land claims that survive a technical audience
• Run the content calendar around each report: the findings, charts, and short-form pieces built to be cited by people and AI engines
• Write the editorial pieces that give Faros a point of view: field guides, frameworks, and arguments the market doesn’t have yet, gated where they fuel demand gen
• Define how content attaches to pipeline, and own that scorecard with demand gen and marketing ops
• Hold the line on how Faros writes about data: precise, quantified, engineer-to-engineer

Requirements

• 6+ years in content, editorial, or research roles for a technical audience, with real ownership of what got published
• You've shipped a research report or benchmark study with your name on it
• Experience at early-stage startups where you were the marketing infrastructure. Self-sufficient, resourceful, and able to ship without a team behind you
• You have fluency with data. You can interrogate a dataset with the people who built it, spot the finding worth leading with, and know when a cut of the numbers is misleading
• Strong, fast writing in an engineer's register; writing samples required
• You've owned a content program, not a queue: strategy, calendar, and the judgment about what not to publish
• You can connect content to revenue: you've defined what success looks like and answered for it

Preferred

• A background in software engineering, data analysis, or data journalism
• Video skills, from scripting to producing short-form for technical audiences
• Familiarity with the engineering leadership space: DORA, developer productivity, AI-assisted development
• You use AI in your own research and writing workflow and have opinions about where it breaks
• Quality over volume. You'd rather publish one report people cite for a year than twelve posts people skim. You notice the weak claim and cut it before anyone else sees it.
• Ownership over process. If it has a number in it and the Faros name on it, you've checked the number. You don't wait for a brief to kill a finding that doesn't hold up.
• Transformational over predictable. The data can support safe observations or claims nobody has made yet. You look for the second kind and do the work to earn them.
• Intensity over comfort. Your findings go in front of buyers, press, and skeptical engineers who will check your math. You like that.
• Living by our values over avoiding conflict. When the data says something inconvenient, you say it. You'd rather lose an argument than publish something soft.