Can You Hire Without a Job Description in 2026?

[McNorah]

Yes, you can absolutely hire someone without a formal job description, but it’s a high-risk move that requires a very deliberate strategy. I’ve seen it work best in fast-moving startups or when filling a role that’s never existed before, where a rigid description would actually get in the way.

The key is to replace the job description with a clear set of expectations and outcomes. Instead of listing duties, I focus on the problems the new hire needs to solve and the metrics we’ll use to measure success. For example, “We need someone who can reduce our candidate screening time by 30% in the first quarter” is far more actionable than a paragraph about “managing the recruitment pipeline.”

In practice, this means leaning heavily on structured interviews and skills-based assessments. You can’t rely on a resume matching a checklist, so you need to be very specific about what you’re testing. A recent study by the Society for Human Resource Management (SHRM) found that structured interviews have a predictive validity of 0.57, compared to 0.19 for unstructured ones. This is where you put your energy.

Hiring Method	Predictive Validity
Structured Interview	0.57
Work Sample Test	0.54
Cognitive Ability Test	0.51
Unstructured Interview	0.19
Reference Checks	0.18

I also make sure the entire team is aligned on the “why” behind the hire. Without a written document, it’s easy for stakeholders to have wildly different ideas of what the person will do. A quick alignment session before the job goes live can save months of frustration. The real danger isn’t the lack of a description, it’s the lack of clarity. If you can provide that clarity through conversation and measurable goals, you can skip the document.

[VonRemington]

I’ve done it, and honestly, it was a bit of a mess. You end up with a person who is technically brilliant but spends half their time doing things nobody asked for. Without a job description, you have no baseline for performance reviews. It’s fine for a three-month trial, but for a permanent role, it’s a recipe for confusion. I’d only recommend it if you’re building a completely new function and are willing to iterate on the role as you go.

[SanAdelyn]

It depends on the company culture. In my last role, we hired a community manager without a description because we wanted someone who could define the role themselves. It worked because we had super strong one-on-one feedback loops. If your managers are skilled at giving clear, weekly feedback, you can make it work. If they are not, you’ll just create a lot of anxiety and scope creep.

[KathrynLee]

From a legal perspective, skipping a job description can be risky. It makes it harder to prove that a hiring decision was based on job-related criteria. If a candidate claims discrimination, you need a clear record of the required qualifications. A written description is your best defense. I’d never recommend it for any role where you have more than five applicants, it’s just asking for trouble.

[VonAyla]

I think it’s the best way to hire for creativity. A job description can be a cage for a person’s potential. When I hire for a role like “innovation lead,” I want someone who can build the job as they go. I use a one-page brief with three key objectives instead. The candidate’s application is then a proposal for how they would achieve those objectives. It filters out people who need hand-holding and attracts real self-starters.