Quick answer
A developer persona describes who your product is for in developers' terms: the stack they work in, their seniority, where they read, and what makes them trust or dismiss a tool. It replaces job titles with what people build.
Developer persona
DefinitionClassic personas describe a job title and a set of goals. Developer personas work better when they describe a situation: a backend engineer migrating a service to Kubernetes, a frontend lead choosing an authentication provider, a data engineer who owns the pipeline that keeps failing. The stack, the task and the seniority predict more than the title does.
Also called: Developer ICP, Ideal customer profile for developers.
How do you build a developer persona that targeting can use?
Start from the problem, not the person. Write the situation in one sentence: "a backend engineer migrating a monolith to services who needs tracing that works across both." Then fill in what predicts behaviour: the stack and tools, the seniority and whether they can approve a purchase, the company stage, where they read and ask, what they tried before, what they distrust, and which proof would convince them.
Each line maps to a decision. Stack and tools become the tags you target; where they read becomes the channel; what they distrust becomes what the creative must avoid; the proof becomes the landing page. If a line does not change a decision, cut it. The stock photo and the invented first name never do.
Where does the data come from?
- Your own users: sign-up data, support tickets, the questions in onboarding calls, and five interviews a quarter.
- Communities on your stack: what the persona asks, what they recommend, which tools they compare you to.
- Audience data a developer platform publishes: which stacks, seniorities and regions read which tags.
- Search and prompt data: the queries and AI prompts the persona uses when they have the problem.
On daily.dev the audience pages describe each persona by what they read, and targeting runs on 800+ targetable keywords plus seniority and region, so a persona written in these terms translates directly into a segment.
Common mistakes
- Personas built from job titles instead of stacks and tasks.
- A stock photo and a name instead of where they read and what they distrust.
- Ten personas, none of which drives a targeting decision.
- Never updating them after the first year of sign-up data.
How developers experience it
- They are reached as "someone on Kubernetes with a tracing problem", not as "DevOps Manager".
- The creative speaks to the task they have this week.
- They dismiss anything that reads as written for their boss.
How many personas should a developer marketing team have?
Two or three, named by situation, ranked by who adopts first. A tool for CI pipelines might have the platform engineer who sets it up, the application developer who lives with it, and the engineering manager who approves the team plan. Each needs different proof, reads in different places and arrives at a different stage of the funnel. Ten personas means none is used.
Revisit them when the data changes: a new stack appearing in sign-ups, a segment converting that was not planned for, an AI-tool persona that did not exist two years ago.
What is the difference between a developer persona and a developer ICP?
The persona is a person; the ideal customer profile is a company. The persona says who adopts and what convinces them; the ICP says which organisations, by size, industry, stack and stage, the product expands in once a developer has adopted. Use the persona for targeting and creative, the ICP for sales and account selection, and keep them consistent: the persona should work at an ICP company.
On daily.dev
How it works on daily.dev
Targeting on daily.dev is built around personas in this sense: 800+ stacks and topics, seniority from on-platform activity, and region. Each audience page describes one persona and what they read.
Explore my optionsDeveloper persona vs buyer persona vs ideal customer profile
| Capability | Developer persona | Buyer persona | Ideal customer profile |
|---|---|---|---|
| Describes | Who adopts and evaluates | Who signs and budgets | Which companies expand |
| Built from | Stack, task, seniority, where they read | Title, goals, objections | Size, industry, stack, stage |
| Used for | Targeting and creative | Sales messaging | Account selection |
| Becomes | Tags, keywords and audience filters | A pitch deck | A target account list |
| How many | Two or three | One or two | One, revised yearly |