You have opted out of job matches in .
To undo this, go to the 'Skills and Interests' section of your preferences.
Shared by 
1 day ago
Requirements and responsibilities
About FarosFaros gives engineering leaders the visibility and control to maximize AI engineering outcomes, while managing costs and keeping every team within policy. Some of the most sophisticated engineering teams in the world, ranging from fast-growing technology companies to F500 enterprises, use Faros to see what their AI investment actually ships, diagnose what's holding it back, and tune it continuously. We are defining how enterprises operate AI engineering, and the story is being written in real time.About the RoleFaros helps engineering leaders see and improve how software actually gets built. Our buyers are VPs of Engineering and CTOs, and they read the way engineers read: they trust data, primary work, and people who clearly know the field. You'll be the technical voice of Faros in the market. That means owning the content that creates demand for us: original research built on our engineering data, and editorial work that shapes how the market thinks about AI-native engineering. Our AI Engineering report is the proof point and your starting asset. You'll build it into a collection of data-driven reports the industry cites, and back it with field guides, frameworks, and points of view the market doesn't have words for yet. This is a content-first DevRel role. The job is educating the industry on how to use AI engineering effectively, and generating awareness for Faros by doing it well. There's no community to manage, no support queue, no docs backlog. Just research, writing, and being credible in front of a technical audience. Search-driven content is owned separately.What you'll doOwn the research content program: concept, methodology, analysis, and publication of reports built on Faros engineering dataPartner with our data and engineering teams to interrogate the dataset, find the cuts worth publishing, and kill the ones that misleadBuild the editorial content that shapes the category: field guides, frameworks, and opinions engineering leaders repeat in their own wordsRepresent the research in market: webinars, podcasts, conference talks, and analyst conversationsAtomize each report cycle into derivative assets the demand gen and sales teams can run withMeasure what your content does: what gets cited, what converts to intent, and feed that back into what you make nextWhat we're looking forYou've shipped developer-facing research with your name on it: a State of X report, an ecosystem survey, a benchmark studyYou'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 misleadingYou write for engineers the way the best developer-facing companies do. We hold a high bar on register and will test for itYou're comfortable being the face of the work: on stage, on a podcast, in a room with a skeptical CTOYou're rather publish one thing people cite than ten things people skimNice to HaveBackground in software engineering or data analysisFamiliarity with the engineering leadership space: DORA, developer productivity, AI-assisted developmentExperience producing or scripting short video for technical audiencesHow we'll evaluatePortfolio first. Then a paid exercise using real Faros data.