Field Guide · hiring
Role teardown — Linear's Developer Marketing role
We pulled a real job post — Linear's Developer Marketing role — and broke its responsibilities into three load-bearing Fidelic agents (KALA, DARO, VEXA). All three are live; the human factor is what your hire is actually for.
Linear posted a Developer Marketing role this month — remote, US plus Europe, competitive salary and equity. The job is real and the JD is rich enough to read straight: use-case discovery, content production, video walkthroughs, creator partnerships, conversation-monitoring on X. The full posting is linked at the bottom of this page (and at the top of every section that quotes it).
We're using it as the first piece in a new genre — the role teardown. We pull a real job post, break it into responsibility groups, and tag each group with the Fidelic agent that owns that slice (or the human factor when the work is irreducibly human). The point isn't to argue Linear should fire their developer marketer. The point is to show, on a real role, exactly what "hire by the role, not the project" looks like when the role is unbundled.
Why it matters
A senior developer-marketing hire at a Series C company runs roughly $200K fully loaded. Roughly 60 to 70 percent of the responsibilities in the JD are production work — content drafting, documentation, repurposing, monitoring, distribution. The other 30 to 40 percent is irreducibly human: on-camera presence, conference panels, the relationships with engineering creators that have to be authentic to land. The bundle exists because the labor market couldn't easily split them. Now it can.
Two scenarios get value from the unbundling. The team that already hired the human can give their developer marketer a team of four agents in their #marketing channel — KALA-01 drafting, DARO-01 writing docs, VEXA-01 picking the use cases worth telling, HOLT-01 watching the conversation — and free the human to do the parts that don't scale. The team that hasn't hired yet can cover the production half of the role with a roster team and put their founder or product lead on the camera-and-conferences half. Both scenarios are operator moves; both are cheaper than the bundled hire (see the math on /pricing).
For teams already running this trio and wanting a fourth, HOLT-01 (AI Brand Monitoring Analyst, shipping next) would pick up the X/Reddit/Hacker News conversation watch — drafts proposed replies, the human approves and posts. That's a useful expansion once the core three are humming.
The unbundling, at a glance
Six responsibility groups, twelve patches. Each patch is verbatim Linear copy — the words come straight from the JD on Linear's Ashby board; we just wrap them in the color of the agent (or the human) that owns each phrase. Like marking up a printed job post with colored highlighters.
Three of the four agents in the diagram are live on the public Roster: KALA-01 for content production, DARO-01 for technical documentation, VEXA-01 for narrative strategy. HOLT-01, the brand-monitoring agent, is in formation — shipping next.
Who's covering what
KALA-01 — AI Content Marketing Manager
KALA owns the production line. Content calendar, draft batches, headline variants, social and blog posts, distribution plan, repurposing one piece across formats. For Linear's role, KALA is the agent that takes the use case VEXA flagged and turns it into a Twitter thread, a blog post, a walkthrough script, and a LinkedIn carousel. The human picks which one to actually ship; KALA does the volume. Read the agent's full Roster page →
DARO-01 — AI Technical Writer
DARO owns developer-facing documentation and educational content. Getting-started guides, API walkthroughs, tutorial sequences, the sample-code currency that decays silently between releases. For Linear, DARO is the agent that lives in the docs-review queue alongside the support and product teams — translating new features into clean dev-facing prose without the marketing department having to wait for engineering bandwidth. DARO on the Roster →
VEXA-01 — AI Marketing Strategist
VEXA decides which stories are worth telling. Use-case discovery, narrative selection, positioning against alternatives, the strategic moves a marketing lead would draft on Sunday night. For Linear, VEXA is the agent that reads the product surface — every release, every agent-platform capability — and proposes a shortlist of use cases that would resonate with engineering teams. The human picks the winners; VEXA does the sweep. VEXA on the Roster →
The human factor
Three categories of work the agents don't touch. The first is on-camera presence — Linear's JD is explicit: "comfortable on camera and on stage … able to create video content end to end." The second is creator relationships, the part the JD names as "authentic rather than sponsored." Authenticity is partly a function of consistency over time with a specific human, which an agent can't supply. The third is taste — the call on what's interesting on X today, which creator is worth a conversation, which conference panel matters. These are the parts of the developer-marketing role that don't unbundle, and the team that hires for this role should hire specifically against these qualities.
The human factor is the load-bearing input, not the residual. The agents handle volume so the human handles presence.
Two scenarios that move money
Scenario one — augment a hired developer marketer
A Series C company that's already paying for the role can give their marketer four agents in their #marketing channel. Production volume goes up by roughly 5–10x (KALA drafts ten threads in the time a human drafts one; DARO covers documentation freshness without waiting on engineering; VEXA proposes use cases continuously rather than monthly; HOLT surfaces conversations daily rather than weekly). The human's hours redistribute to the parts that don't scale: relationships, camera, taste. See the architectural argument for many agents in one team channel →
Math: roughly four Professional-tier agents at $500/month each = $2,000/month, or 1 percent of the fully-loaded human cost. The marketer is the same hire; the team output is materially higher; the marketer's job satisfaction is materially higher because they're doing the developer-marketing parts that drew them to the role rather than the production grind. Pricing math is on /pricing.
Scenario two — plug the gap without the full-time hire
An earlier-stage company that can't yet pay $200K for a developer marketer can deploy the same four agents and assign the human factor to the founder or product lead. The production line runs (content, docs, monitoring, narrative); the founder appears on camera for the walkthrough videos and on stage for the conference panels. The relationships are founder-to-creator, which is often more authentic at this stage anyway. The bundled $200K expense becomes ~$2K/month plus the founder's existing time. Linear's own playbook on how to operate a small team reads like a manual for this pattern, incidentally.
What this is not
We're not arguing the role disappears. Linear's posting names work the agents cannot do, and a serious developer-marketing program needs that human work. The unbundling isn't a substitution argument. It's a sizing argument: the role is smaller than the JD suggests if you have agents covering the production half, and most SMB-stage companies aren't sizing their marketing hires against this reality yet.
We're also not claiming the agents are autonomous in the Sierra or Decagon sense. KALA, DARO, VEXA, and HOLT all work in your #marketing channel, post their work in front of the team, take feedback in thread, and ask for review before publishing. The team is the orchestration; the agents are the production. That's the model the Roster ships against — the long version of the argument is in the two-kinds-of-AI-teammate essay.
Honest take
The four agents cover production work cleanly. They do not cover the parts of a developer-marketing role that depend on a specific human's presence over time. The founder-as-camera variant works at early stage but becomes a bottleneck if the founder is split across too many functions. At Series B or later, the human hire is back on the table. What changes is what the human is hired for — taste, relationships, presence — not production.
We are not claiming this maps to every dev-marketing role. Linear's posting is unusually production-heavy. A dev-marketing role at a smaller company might be 80 percent founder time already. A role at a bigger company might have an existing PR firm absorbing the conversation-monitoring slice. The teardown is a method, not a template.
Three load-bearing agents — KALA-01 for content, DARO-01 for technical docs, VEXA-01 for narrative strategy — cover the role's recurring work (KALA-01, DARO-01, VEXA-01. The role is real, the JD is linked, and the math is in dollars per month against the bundled hire.
If you're hiring for a role like this, the first move is to read your own JD against this decomposition before the requisition closes. The second move is to talk to TESS about which agents on the Roster cover which slices of the role you're describing. The third move is to decide whether you're augmenting an existing hire or covering the gap with the founder. We have an opinion on which is right for your stage; the math is on /pricing.
Source: Linear's Developer Marketing posting on Ashby — verbatim responsibility list extracted May 15, 2026. The role is currently open as of publication.