If you’ve never hired before, writing a job description feels like guessing.

You know you need help.

But you don’t know:

What should actually be in the role
What tasks belong together
What’s realistic for one person
Or what “good” even looks like

So most founders do one of two things:

❌ Copy a generic job description from Google
❌ Write a long list of everything they hope to stop doing

And then they wonder why the hire doesn’t work out.

Here’s the problem:

You’re trying to create a role from scratch without a reference point.

But there’s a free tool almost no founders know about that solves this.

It’s called O*NET OnLine.

And once you use it, writing a job description becomes dramatically easier…and far more accurate.

Why This Matters Before You Hire

Most bad hires don’t fail because the person was “bad.”

They fail because the role was unclear.

A job description isn’t just a list, it’s a decision tool.

When you define the role clearly, you:

Attract the right candidates
Filter out weak fits early
Reduce emotional decision-making
Set your hire up to succeed

And most importantly: you create the foundation for hiring based on fit, not guesswork.

In fact, the Harvard Business Review study “Job Matching for Better Sales Performance” found that when people are matched to the actual demands of a job, rather than hired based on surface traits, performance improves dramatically.

That applies just as much to your first hire.

Step-by-Step: How to Use O*NET to Build Your Job Description

Step 1: Find the Closest Matching Role

Go to O*NET OnLine and search for a job title similar to what you need.

Examples:

Executive Assistant
Office Manager
Operations Assistant
Marketing Coordinator

Don’t worry about getting it perfect. You’re not trying to match exactly; you’re trying to find a strong starting point.

Expert Tip: If your role combines functions (like ops + marketing), review two roles and pull only what’s relevant.

Step 2: Use “Tasks” to Build Your Core Responsibilities

This is the most valuable section.

O*NET lists real tasks people perform in that role.

What to do:

1. Copy 8–12 tasks that match your needs
2. Remove anything irrelevant
3. Group them into 3–7 responsibility categories

Example

O*NET task:
“Prepare correspondence, reports, or presentations.”

Your job description:

Manage internal documentation and reporting
Maintain project updates
Prepare reports
Update shared documents

Do This, Not That

❌ Copy tasks word-for-word
✅ Translate them into your workflow

❌ List 20+ bullet points
✅ Group into clear responsibility areas

If you’re feeling stuck, don’t start writing yet.

Do this first:

1. Search your role on O*NET
2. Pull 8–12 real tasks
3. Group them into 3–7 responsibilities
4. Then write your job description

This alone will put you ahead of most first-time hirers.

Step 3: Use “Work Activities” to Define What the Job Actually Involves

Tasks tell you what gets done.

Work Activities tell you how the work happens.

Examples:

Organizing information
Coordinating with others
Planning and prioritizing
Handling customer concerns

Translate This Into Expectations

Instead of:

❌ “Must be organized”

Write:

✅ “Plans and prioritizes weekly tasks and keeps systems updated consistently.”

This is where your job description starts to feel real.

Step 4: Use “Work Context” to Describe the Reality of the Job

This is one of the most overlooked parts of a job description.

O*NET’s Work Context shows:

Pace of work
Interruptions
Communication level
Attention to detail required

Example

Work Environment

High volume of messages and requests
Frequent context switching
Daily communication with clients or team
Requires sustained attention to detail

This prevents: “I didn’t realize the job would be like this.”

Step 5: Use Skills, Abilities, and Work Styles to Identify Competencies

This is where O*NET becomes powerful.

It shows you what drives performance in the role.

Think of O*NET as a behind-the-scenes database of how jobs actually work, not how founders guess they work.

Example: Attention to Detail

Strong pattern

Catches errors early
Maintains accurate systems
Keeps work consistent

Weak pattern

Misses inconsistencies
Leaves tasks incomplete

Example: Dependability

Strong pattern

Follows through without reminders
Communicates proactively
Meets deadlines

Weak pattern

Needs chasing
Avoids updates
Misses deadlines silently

This is the shift most founders never make:

❌ You’re not just hiring for tasks.
✅ You’re hiring for performance patterns.

Step 6: Build a Clear, Focused Job Description

Once you’ve used O*NET, your job description should include:

Role purpose (why it exists)
3–7 core responsibilities
Work environment
Tools and workflow
Success outcomes (30/60/90 days)
Competencies (strong vs weak patterns)

Important Reminder

O*NET gives you structure.

But you still need to adapt it to your business.

❌ Don’t copy it directly
✅ Use it to validate and refine your thinking, and make sure all your bases are covered.

Where Most Founders Still Go Wrong

Even with a strong job description, many founders still:

Hire based on personality
Choose candidates they “like”
Skip structured evaluation
Assume skills = performance

That’s where things break. Because knowing the role is only half the equation.

Structure Helps, But Fit Drives Performance

O*NET gives you structure to write your job description.

But structure alone doesn’t guarantee a good hire.

Because performance doesn’t come from job descriptions; it comes from matching the job to the person.

That’s where competencies matter.

And why founders who rely only on tasks often end up rehiring within 90 days.

Your first hire should create leverage, not more stress.

Clarity is what makes that possible.

O*NET Gets You the Role. This Guide Gets You the Hire.

O*NET helps you design a clear job description. But a strong description is only half the work — most first hires still go wrong in the interview and decision stage. The free guide How to Hire the Right Person — The First Time covers everything that happens after you press “post.”

Inside:

Behavioral interview questions that reveal real performance patterns
The 6 hiring mistakes every first-time founder makes (and exactly how to avoid them)
A simple evidence-based decision filter
A pre-offer checklist so you hire with confidence, not crossed fingers

Get the Free Guide