Developer Advocate, Research and Content
About Faros
Faros 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 Role
Faros 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 do
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
What we're looking for
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
Nice to Have
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
How we'll evaluate
Portfolio first. Then a paid exercise using real Faros data.
Research Content Lead
About Faros
Faros 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 Role
You'll own the content that creates demand for Faros: reports, guides, blogs, video, and the assets that fuel our campaigns. Research is the centerpiece: reports built on our engineering data that only Faros can publish. Our buyers are VPs of Engineering and CTOs, so everything you publish has to hold up to a technical audience. Our AI Engineering report set the standard for how we do this, and it's working. Your job is to scale it into a full program of reports and content assets. You'll report to the CMO and work as a peer to our product marketing and content leads. Search-driven content is owned separately. Your lane is the content only Faros can make.
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
What We Value
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.
Required Qualifications
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
Nice to Have
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
Product Marketing Lead
About Faros
Faros 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 Role
We're looking for a technical product marketer to drive how Faros is positioned in the fast-moving AI engineering market. You get to craft the story we tell and keep pace with the market without losing precision. You own it, and every surface where it meets the market.
The audience is engineering leaders and the engineers who influence them. They're allergic to marketing that smells like marketing, so everything you ship has to be technically true and lead with authenticity and precision instead of jargon and filler. You know what good looks like for a technical audience at every altitude, from the positioning narrative down to the word choice on a banner ad, and you sharpen it as the market moves. You'll lead core product marketing: messaging, the website, launches, campaigns, sales enablement, and content.
You'll work directly with the CMO, CEO, and product, and your work goes in front of buyers, analysts, and investors within days of writing it.
Responsibilities
Build and maintain the core messaging and positioning for Faros, keeping every claim tied to shipped product and evolving the narrative as the market moves
Write and own the website's message architecture and copy, treating it as our highest-traffic salesperson
Equip sales with decks, battle cards, competitive intel, objection handling, and demo narratives built from real call data and kept current
Run product launches end to end, deciding what we say, where we say it, what sales gets, and what the market hears
Bring your own quarterly campaign ideas backed by research, then partner with demand generation to build and run them
Build gated assets that fuel demand programs: industry reports, assessments, calculators, and education etc. that a buyer will trade their contact for
Set and hold the quality bar on everything a buyer sees, from ad copy and banners to headlines, emails, and social posts
Develop customer proof that gives skeptical buyers evidence: case studies, win stories, and testimonials
Create content engineering leaders actually share, including reports, blogs, technical narratives, and webinars
Track your pipeline impact, knowing which campaigns and content source and influence deals, and adjusting to what the data says
What We Value
Craftsmanship over throughput. You'd rather ship one page an engineer trusts than ten pages that read like everyone else's. You notice the extra adjective and the vague verb, and you cut them.
Ownership over process. If it carries the Faros name, you've read every word. You don't wait for a brief to fix a weak headline.
Transformational over predictable. The category is forming now. You'd rather write the claim that defines it than optimize the one that's safe.
Intensity over comfort. Your work goes in front of buyers, analysts, and investors within days of writing it. You like that pace.
Living by our values over avoiding conflict. You have a point of view and defend it with evidence. You'd rather lose an argument than ship something weak.
Required Qualifications
6+ years in product marketing at a dev tools, infrastructure, or AI company, with real ownership of messaging and launches
Technical degree, computer science or a related engineering field; MBA preferred
Experience at early-stage startups where you were the marketing infrastructure: self-sufficient, resourceful, and able to ship without a team behind you
Proven experience marketing to engineering buyers, with instincts for what they respect that are demonstrated, not theoretical
Technical depth to read API docs, follow an architecture discussion, and question engineers without a translator
Strong, fast writing with first drafts that are usable and final drafts that are tight; writing samples required
Have an operational mindset. You think in pipeline, conversion, and shipped work, and you've been accountable to a number
Demonstrated taste, in words and in how things look and feel, and the ability to articulate why something is good rather than just accurate
Nice to Have
Video skills, from scripting to directing short product and social video
Experience marketing against or alongside AI coding tools
You use AI agents in your own workflow and have opinions about where they break
The full posting opens here — pay, setting and the full description, without leaving the list.