The Essential Job Description

The biggest problem with job descriptions isn’t that leaders treat them like compliance checklists. The deeper issue is that many leaders never start with a clear concept of the problem the role exists to solve.

They know there are problems; that much is evident, but they do not deeply understand the problems.

What does this mean to “deeply” understand the problems?

“There are a thousand hacking at the branches of evil to one who is striking at the root.”

– Henry David Thoreau

To “deeply” understand the problems a role exists to solve is more than naming the obvious frustrations (too many RFIs, delayed schedules, cost overruns). Those are symptoms.

Deep understanding looks beneath the surface:

1. Root cause clarity
   • Not just: “We need a project manager because projects are behind.”
   • But: “Our projects are behind because communication between estimating and field execution breaks down. We need a PM who can translate preconstruction assumptions into field accountability.”
2. Contextual awareness
   • Seeing how the problem ties into company mission, culture, and market realities.
   • For example: “We don’t just need a superintendent who runs schedules—we need one who can represent our company well with neighbors and city officials because this project sits in a sensitive community.”
3. Precision, not generalization
   • Most leaders stop at “we need someone experienced.” Deep understanding asks: “Experienced in what specifically? Which types of projects? Which delivery methods? Which relational dynamics matter most here?”
4. Impact lens
   • Understanding the downstream consequences if the problem isn’t solved.
   • For example: “If we don’t get a controller who can enforce process discipline now, we’ll never scale to $150M in revenue.”
5. Alignment with how the company solves problems
   • Every company has a way of working. Deep understanding connects the problem to the company’s philosophy of execution.
   • “We need an estimator who thrives in collaborative preconstruction, not one who locks themselves in an office and hands off a number.”

In short: to “deeply” understand the problems means being able to articulate not just what hurts but why it hurts, where it comes from, how it connects to the business, and what solving it will make possible.

The Problem

To appreciate the medicine, one must understand the ailment.

Every hire is problem-solving. A superintendent is brought in to bring order and accountability to the field. A project manager exists to balance client expectations with cost and schedule realities. An estimator is hired to turn risk into predictable numbers. Yet most job descriptions skip that first principle. Instead, they jump straight into a vague list of tasks and years of experience, leaving the real “why” unspoken.

When that happens, the job description becomes an exercise in paperwork instead of a leadership tool. Interviews default to gut feel. Onboarding lacks direction. And retention risk rises, because expectations were never aligned in the first place.

As Jim Collins wrote in Good to Great, “If you have more than three priorities, you don’t have any.” The same applies to roles. If you can’t name the core problem this role exists to solve, everything else in the hiring process is built on sand.

What Every Strong Job Description Includes

Once the problem is clear, the rest of the description takes shape. A durable job description has six essential parts. Skip one, and you introduce blind spots that ripple through hiring, onboarding, and retention.

1. Role Purpose
Why does this role exist? State it in terms of the business problem it solves. A good purpose statement anchors every other part of the description.

2. Core Accountabilities
List the 5–7 measurable responsibilities that define success. Focus on ownership, not tasks. Instead of “attend project meetings,” write “own project documentation and communication cadence across internal and external stakeholders.”

3. Required Competencies
What skills, experiences, and certifications are truly necessary? Be ruthless. Many leaders list “nice-to-haves” as “must-haves” and unintentionally filter out excellent talent.

4. Relational Dynamics
Who does this role report to? Who reports to it? How should they interact with peers? Often the difference between someone thriving or burning out isn’t skills, it’s relationships.

5. Key Performance Indicators (KPIs)
What metrics will define success? In construction, that may include budget adherence, schedule control, safety incidents, or client satisfaction. Putting these in writing makes performance expectations clear from day one.

6. Culture and Values Alignment
How does this role connect to your company’s mission and values? Candidates don’t just want to know what they’ll do; they want to know why it matters.

Job Description vs. Job Ad

Leaders often confuse these two, but they serve different purposes:

• The job description is an internal leadership document. It defines the role with precision, sets accountability, and becomes the basis for interviewing, performance evaluation, and compensation. It is as much about screening out the wrong candidates as it is attracting the right ones.
• The job ad is the external marketing version. It pulls from the job description but is written to spark interest, show opportunity, and invite candidates into a conversation.

The two should be consistent, but not identical.

And here’s a key leadership point: it’s not a terrible thing for the hard parts of the job to be apparent in the job description. If the role requires navigating tough city permitting processes, managing demanding clients, or leading subcontractors who push limits, write that down. The right people will be energized by those challenges. The wrong people will self-select out. That’s not a failure, it’s effective screening.

Four Diagnostic Questions for Leaders

A strong job description isn’t just for recruiting, it’s a leadership mirror. Ask yourself:

1. Ownership
   If we evaluate each part of a candidate’s ability per the job description, can we take responsibility as hiring authorities for the hire?
2. Performance
   Can this document double as a performance review tool, providing a fair and objective baseline for ongoing evaluation?
3. Compensation
   Can this description guide appropriate compensation, tying pay directly to defined responsibilities and measurable outcomes instead of guesswork or market averages?
4. Operational Precision
   Are people in this role expected to execute with high precision aligned to the company’s mission, or are we tolerating a wide range of “do it how you see fit” approaches that dilute performance and culture?

If you can’t answer these with confidence, the job description isn’t finished.

Free Advice: Keep Job Descriptions Realistic

A job description is only as strong as it is usable. Two simple rules will keep you grounded:

1. Hire to the job description.
   If your job description is lofty and unrealistic, you won’t find candidates who meet it. The document must reflect real, attainable qualifications, otherwise you’re setting yourself up for endless frustration.
2. Interview to the job description.
   Every requirement you put in the job description becomes something the hiring team is accountable to assess. Load it with too many demands, and you’ve just created a massive and impractical interview project.

The best job descriptions are lean, clear, and realistic. They define the problem to be solved, the outcomes to be delivered, and the capabilities required. Nothing more, nothing less.

Why This Matters Beyond Recruiting

When your job description starts with the problem and builds out with clarity, something powerful happens:

• Interviews become structured instead of scattered.
• Leaders evaluate candidates against the same standard instead of gut feel.
• Onboarding has a built-in roadmap.
• Retention risk drops, because expectations were clear before day one.

By contrast, a vague job description leaves leaders asking after an interview: “Do we think they can handle it?” A strong one reframes the question: “Did they demonstrate the ability to solve the problem this role exists to solve?”