Hand me a company's job descriptions and I can tell you how clearly its leaders understand their own business. Most of what I read is bloated, vague, and quietly revealing. The document lists twenty requirements, names no outcome, and describes a role no one on the team could explain out loud. That is not a writing problem. It is a thinking problem. The quality of the hire you eventually make is set long before the first resume arrives, and it is set by how well you can see the role yourself. A job description is the first mirror. If you cannot articulate why the seat exists and what winning in it looks like, no candidate pool will rescue you.

Written well, the same document does three jobs at once: it attracts the right person, it maps performance, and it keeps the role aligned with the business. Written badly, it does none of them and you spend the next year wondering why the hire is not landing.

Start with the pain or the opportunity

Every role exists for a reason. Before you list a single duty, name the problem the role resolves or the opportunity it captures. Three questions force the clarity:

  • What problem will this role solve for the company?
  • What opportunity does this position help capture?
  • How does it move the business forward?

Compare the two versions I see most often:

Weak: "We need a Project Manager to oversee jobs and manage budgets."



Strong: "Our business is growing fast, and we need a Project Manager who can sharpen our project execution, delivering on time and on budget while keeping client relationships strong."

If you cannot articulate the pain or the opportunity, you have not defined the job clearly enough to hire for it. Stop and define it first.

Describe outcomes, not just duties

Most job descriptions list tasks and never say what success looks like. Flip it. Tell the candidate the impact you expect them to have.

  • Define what success looks like at 3, 6, and 12 months.
  • Name the key challenges this person will solve.
  • Make expectations measurable wherever you can.
Weak: "Manage construction schedules."



Strong: "Deliver 95% of projects on time by managing schedules, coordinating subcontractors, and anticipating delays before they cost you."

Make it double as a performance review

A strong job description works as a performance review template. If the employee reads it a year in, they should know immediately whether they are succeeding. Tie each responsibility to a measurable indicator. Keep the language action-oriented. A description that states what someone should do but never says how success is measured is incomplete, and the gap will surface in every review conversation you have with them.

Clarify reporting in every direction

Most descriptions name who the role reports to and stop there. That is a fraction of the picture. Show how the role fits the team and the structure around it:

  • Who the role reports to.
  • Who it supports and collaborates with.
  • Who depends on the work this person produces.
"This role reports to the Project Manager and works closely with Estimators, Superintendents, and clients to keep budgets accurate and projects on schedule."

A candidate should understand where they fit in the organization before they ever walk in.

Outline the real responsibilities

The description should tell candidates what they will actually do without drowning them in a list of every task. Identify the 5 to 7 responsibilities that matter most. Focus on major areas of ownership, not minor daily chores. Describe the processes they will run or take part in.

Weak: "Answer emails and coordinate with team members."



Strong: "Manage communication between project teams and subcontractors to keep schedules aligned and problems solved quickly."

Good responsibilities guide the new hire's priorities without dictating how they execute. Direction, not micromanagement.

Tie the role to the mission

People want work that matters. A strong description explains why the role exists and how it contributes to the company's success. Answer the question directly: how does this job move the company forward? Then connect the responsibilities to the company's values and goals.

"Our mission is to build high-performing construction teams that deliver exceptional projects. As a Project Engineer, you keep budgets accurate and coordination seamless, directly shaping our ability to deliver on time and on budget."

When a candidate understands how their work feeds something larger, they show up more engaged and they stay longer.

Test it on an outsider

Here is the cheapest clarity test I know. Hand the description to someone outside the company, ideally outside the industry, and ask them to summarize the role back to you in their own words.

  • Ask a friend, family member, or professional from another field to read it.
  • Have them describe the job back to you.
  • If they struggle, your wording is doing the struggling, not them.

If someone with no background in your business can explain the job, you have written it well.

Keep it a map, not a maze

A job description should be a map, not a maze. Cut the corporate jargon, keep the sentences short, and stay on what actually matters.

Do:

  • Be clear, concise, and specific.
  • Focus on outcomes and impact.
  • Make it usable for hiring, onboarding, and performance management.

Don't:

  • Overload it with requirements.
  • List generic duties with no measurable outcome.
  • Hide behind buzzwords.

The job description is the first place your clarity gets tested, and the candidate reads your clarity long before they read your benefits. Write the role you can actually see, and the right person will recognize themselves in it.