Job profile examples for common roles

A job profile is a short internal document that defines one role: why it exists, the outcomes it owns, the skills and behaviors needed to deliver them, and how success gets measured. The job advert is the public, edited version of it. The profile is the source it gets edited from.

Below are 10 job profile examples you can copy, a blank template, and the part most teams skip: turning each listed skill into evidence you can actually collect before you hire.

TL;DR

• A job profile defines the role itself. A job description advertises it. Write the profile first, then cut the advert out of it.
• Five parts do the work: role purpose, outcomes, competencies, evidence, and success measures at 30, 60 and 90 days.
• Years of experience is the weakest line in most profiles. Write the capability you need instead, then test for it.
• Only 47% of employees strongly agree they know what is expected of them at work, so the profile has a job to do long after the offer.
• Use the 10 role examples as starting structures, not finished text. Swap in your own metrics before anyone sees them.

What is a job profile? Meaning and purpose

A job profile is a structured summary of a single role covering its purpose, key responsibilities, required competencies, reporting lines, and the measures that show it is being done well. It sits inside the organization as a reference document, and it stays useful across hiring, onboarding, performance reviews, and promotion decisions.

The purpose is alignment. When a recruiter, a hiring manager, and a candidate all read the same profile, they argue about the role before the interviews rather than after the offer. That is the whole point of writing one.

Role definitions are not arbitrary, either. The federal statistical system classifies all US workers into one of 867 detailed occupations, which is a useful reality check when a draft profile invents a role that is really two jobs stapled together.

What does a job profile example look like?

A job profile example has five blocks: role purpose in one sentence, the three to five outcomes the role owns, the competencies needed to hit them, the evidence that proves each competency, and the success measures for the first 90 days. Everything else is optional detail.

Here is the anatomy, with what belongs in each block and the mistake that shows up most often.

The evidence row is the one that changes hiring outcomes, and it is the one almost every template leaves out.

Job profile vs job description: what is different?

A job profile is the internal definition of a role. A job description is the external, edited version written to attract applicants. The profile carries competencies, evidence, and success measures. The description carries the pitch, the summary of duties, the location, and the pay range.

One is written for your hiring team. The other is written for the market. Teams that maintain only the advert end up re-deciding what the role actually is every time it opens. For a closer look at where the two documents split, see our breakdown of how a description differs from a profile.

Why do clear job profiles matter?

Because role clarity decays fast, and the profile is the only artifact that holds it. Gallup found that 47% of employees strongly agree they know what is expected of them at work, measured in the second quarter of 2025. Just under half. That gap is where duplicated work, missed handoffs, and unhappy performance reviews come from, and no job advert has ever closed it.

There is a second reason, and it is moving faster. Employers expect 39% of workers' core skills to change by 2030, down from 44% in the 2023 edition of the same report. A profile written as a fixed list of tools will be wrong within two review cycles. A profile written around competencies and evidence survives, because the competency ("can diagnose a data quality problem") outlives the tool that happens to be in use this year.

Skills are also what postings increasingly describe. Indeed's Hiring Lab, analyzing more than 3,000 individual skills across 47 categories in US postings, found business operations skills appeared in nearly three-quarters of all US job postings in the fourth quarter of 2025.

How do you write a job profile in 7 steps?

Write the outcomes before the responsibilities. Most drafts go the other way and end up as a task list with no way to tell a strong candidate from an adequate one.

1. Name the outcomes. Ask the hiring manager what has to be true 12 months in for this hire to be obviously worth it. Write 3 to 5 answers. Those are the outcomes.
2. Work backwards to competencies. For each outcome, list what a person must be able to do to produce it. Keep the list under eight items.
3. Split must-have from nice-to-have. If everything is a must-have, nothing is, and your shortlist will be empty.
4. Attach evidence to every must-have. Name the assessment, work sample, structured interview question, or reference check that verifies it. A must-have with no evidence source is a preference, so demote it.
5. Write the context. Reporting line, team size, budget authority, the three teams this role works with weekly.
6. Set 30, 60 and 90 day measures. These become the onboarding plan, so you write them once and use them twice.
7. Pressure-test with someone doing the job. Fifteen minutes with a current holder of the role catches the invented responsibilities.

Pro tip: run step 4 as a separate meeting with the interview panel. The argument about what counts as proof is exactly the argument you want to have before candidates arrive, not in the debrief when everyone is defending a favorite.

Our step-by-step guide to building a role profile from scratch covers the intake conversation in more detail.

What goes in a job profile sample template?

Copy this job profile sample, replace each line with your own detail, and delete any line you cannot justify. A blank template is only useful if you are willing to leave parts of it empty.

Role: Job title, level, department, reports to, direct reports, location and work pattern.
Role purpose: One sentence. Why this role exists and who it serves.
Key outcomes: Three to five results owned, each with a measure.
Must-have competencies: Four to six, each with the evidence that verifies it.
Nice-to-have competencies: Two or three, explicitly not screened on.
Success at 30 / 60 / 90 days: One line each.
Career path: The next role this one usually leads to.

Notice what is missing: a years-of-experience line. It is the most copied line in job profiles and the least defensible one. A 2019 meta-analysis in Personnel Psychology by Van Iddekinge and colleagues found that pre-hire work experience, when measured the usual broad way as years served, showed little relationship with later job performance. That is not an argument that experience is worthless. It is an argument that counting years is a poor way to measure it, and that job-relevant capability assessed directly is the better signal.

The market is drifting the same way. About 30% of US job postings in April 2024 carried a years-of-experience requirement, down from 40% two years earlier, according to Indeed data reported by SHRM. More role-specific starting structures are collected in our library of role profile templates.

10 job profile examples for common roles

Each example below is deliberately short. A job profile that runs to three pages stops being read, and an unread profile aligns nobody. Take the structure, keep the outcome-plus-evidence shape, and rewrite the specifics for your team.

1. Customer service representative

Purpose: Resolve customer issues at first contact so support volume does not compound.
Outcomes: First-contact resolution rate, CSAT, accurate case notes that the next agent can act on.
Must-have competencies: Written clarity, de-escalation, product recall under time pressure, judgment on when to escalate.
Evidence: A written-response work sample using three real (anonymized) tickets, plus a situational judgment assessment.
90 days: Handling the full queue unaided, at or above team median CSAT.

2. Sales executive (inside sales)

Purpose: Convert qualified pipeline into closed revenue within a defined segment.
Outcomes: Quota attainment, pipeline coverage ratio, forecast accuracy.
Must-have competencies: Discovery questioning, objection handling, CRM discipline, commercial numeracy.
Evidence: A live discovery role-play scored against a rubric, plus a short sales executive assessment covering commercial numeracy.
90 days: Self-sourced pipeline at 2x quota, first closed deal.

3. Human resources generalist

Purpose: Run the employee lifecycle so managers get consistent, compliant support.
Outcomes: Case resolution time, policy compliance, manager satisfaction with HR support.
Must-have competencies: Employment law fundamentals, confidential handling, difficult conversations, HRIS accuracy.
Evidence: A scenario assessment on a grievance, plus an HR generalist skills test and an attention-to-detail check on data handling.
90 days: Owning two lifecycle processes end to end without escalation.

4. Digital marketing specialist

Purpose: Grow qualified demand through owned and paid channels at a defensible cost per lead.
Outcomes: Cost per qualified lead, channel contribution to pipeline, experiment velocity.
Must-have competencies: Campaign analytics, copy judgment, budget allocation, testing method.
Evidence: A campaign teardown exercise with real numbers and a written recommendation.
90 days: Two channels running with a tested improvement in cost per lead.

5. Content writer

Purpose: Produce content that ranks, converts, and survives an expert read.
Outcomes: Organic sessions to assisted pipeline, publishing cadence, revision rate before approval.
Must-have competencies: Research and sourcing, structural editing, subject-matter interviewing, search intent judgment.
Evidence: A paid, timed writing task on an unfamiliar topic with sources required.
90 days: Publishing on cadence with fewer than two revision rounds per piece.

6. Software developer (full-stack)

Purpose: Ship and maintain product features across the stack without degrading reliability.
Outcomes: Cycle time, change failure rate, review quality on other people's code.
Must-have competencies: Practical coding in the team's stack, debugging, code review, system reasoning, responsible use of AI tooling.
Evidence: A coding assessment in the real stack plus a code review exercise on deliberately flawed code.
90 days: Independently shipping medium-sized features with clean reviews.

7. Data analyst

Purpose: Turn business questions into analysis that a decision-maker acts on.
Outcomes: Decisions supported, dashboard adoption, data quality issues caught before they spread.
Must-have competencies: SQL, data cleaning, statistical judgment, explaining findings to non-analysts.
Evidence: A SQL assessment plus a short presentation of findings from a messy sample dataset.
90 days: Owning one recurring business report and one ad hoc investigation.

8. Operations executive

Purpose: Keep daily operations running to standard and surface the bottleneck before it bites.
Outcomes: On-time delivery, exception rate, process documentation kept current.
Must-have competencies: Process mapping, vendor coordination, spreadsheet fluency, prioritization under conflicting demands.
Evidence: A spreadsheet-based operational task and a prioritization scenario.
90 days: Running the weekly operating cycle unaided.

9. Administrative assistant

Purpose: Protect the time of the people and processes the role supports.
Outcomes: Scheduling accuracy, turnaround on requests, zero missed compliance deadlines.
Must-have competencies: Calendar and inbox judgment, document accuracy, discretion, software fluency.
Evidence: A timed task on scheduling conflicts and document formatting.
90 days: Managing the full calendar and travel cycle without supervision.

10. Talent acquisition specialist

Purpose: Fill roles with candidates who pass probation and stay.
Outcomes: Time to fill, offer acceptance rate, quality of hire at six months.
Must-have competencies: Intake conversations, structured interviewing, sourcing, candidate experience.
Evidence: A mock intake meeting with a hiring manager, scored on whether they extract outcomes rather than a task list. Our talent acquisition role template shows the finished shape.
90 days: Two roles closed and an intake process the managers actually follow.

You will notice the same pattern in all 10: the evidence line is what stops the competency list from being decoration. For the underlying components in more depth, see our guide to the parts that make up a role profile.

What is a candidate profile example?

A candidate profile is the mirror image of the job profile. The job profile describes the role. The candidate profile describes the person likely to succeed in it: the capability level, the context they have worked in, the motivations that fit, and the deal-breakers.

A short candidate profile example for the data analyst role above: works comfortably with messy, undocumented data; has explained an unpopular finding to a senior stakeholder and held their position; wants depth in analysis rather than a route into management within a year; will not thrive if every request arrives as a fully specified ticket.

Write it as observable behavior, never as personality shorthand. "Detail-oriented" screens nobody out. "Caught a data error that three prior reviews missed" is something you can ask about and verify.

Turn your job profile into a hiring scorecard

The Testlify Competency-to-Evidence Matrix maps every role to the competencies that matter, then connects each competency to measurable evidence through assessments, simulations, interviews, references, and structured feedback. Applied to a job profile, it means no must-have survives without a named source of proof, and the interview panel scores the same things in the same order for every candidate.

That is the difference between a profile that sits in a folder and one that runs your hiring. Across the teams we work with, the profiles that hold up are the ones where somebody had to write the evidence column and could not fake it.

You can build role-based assessments straight from a finished profile. Book a demo to see how the competencies in your profile map to assessments your panel can score consistently.

Key Takeaways

• The profile is the source, the advert is the output. Writing the internal profile first means the job advert, the interview plan, and the onboarding checklist all trace back to one agreed definition, so you stop re-deciding the role every time it opens.
• Outcomes before responsibilities. A task list cannot separate a strong candidate from an adequate one. Three to five outcomes with measures gives the panel something to actually assess against, and gives the hire something to aim at in week one.
• Every must-have needs an evidence source. If you cannot name the assessment, work sample, or structured question that verifies a competency, it is a preference rather than a requirement. Demote it, or the interview will improvise a test nobody agreed on.
• Years of experience is the weakest proxy in the document. Broad experience measures track poorly against later performance, and postings have been dropping the requirement. Describe the capability and test for it instead of counting years.
• Role clarity is a retention problem, not just a hiring one. With 47% of employees strongly agreeing they know what is expected of them, the profile earns its keep long after the offer, through onboarding, reviews, and promotion decisions.
• Write for the review cycle you will actually run. With 39% of core skills expected to shift by 2030, a profile pinned to today's tools ages badly. Competency-level language survives a tooling change; a tool list does not.
• Short beats thorough. A one-page profile gets read, argued with, and used. A three-page profile gets skimmed once and then ignored, which is the same as not having one.

FAQs