Responsibilities

• Own the research content program: concept, methodology, analysis, and publication of reports built on Faros engineering data
• Partner with our data and engineering teams to interrogate the dataset, find the cuts worth publishing, and kill the ones that mislead
• Build the editorial content that shapes the category: field guides, frameworks, and opinions engineering leaders repeat in their own words
• Represent the research in market: webinars, podcasts, conference talks, and analyst conversations
• Atomize each report cycle into derivative assets the demand gen and sales teams can run with
• Measure what your content does: what gets cited, what converts to intent, and feed that back into what you make next

Requirements

• You've shipped developer-facing research with your name on it: a State of X report, an ecosystem survey, a benchmark study
• You're fluent enough in data to be a real partner to engineers: you can interrogate a dataset, spot the finding worth leading with, and know when a cut of the numbers is misleading
• You write for engineers the way the best developer-facing companies do. We hold a high bar on register and will test for it
• You're comfortable being the face of the work: on stage, on a podcast, in a room with a skeptical CTO
• You'd rather publish one thing people cite than ten things people skim

Preferred

• Background in software engineering or data analysis
• Familiarity with the engineering leadership space: DORA, developer productivity, AI-assisted development
• Experience producing or scripting short video for technical audiences