If You Can’t Explain the Role, You’re Not Ready to Hire: 5 JD Mistakes That Repel Top Talent

Einstein said it. Applies perfectly to hiring.

If you can’t sum up what you’re looking for in clear, human language, it’s time to revisit your needs internally before publishing that post.

Your future team — and your sanity — will thank you.

Published on July 15, 2025

Why this matters more than ever

Most architecture studios think writing a job description is about listing requirements. A few lines on software, some years of experience, a generic blurb about “dynamic environments” — and done.

But here’s the problem: the best candidates aren’t desperate. They’re selective. They want to know exactly what they’re stepping into, what kind of work they’ll be doing, and whether your team is a place they can grow.

If you can’t clearly explain the role, why it exists, and how it fits your studio’s vision, you’re simply not ready to hire.

Key Takeaways

Clarity trumps everything: a vague JD scares top talent away.
Start with the problem this role solves, not just a list of tasks.
Align your JD honestly with your actual studio culture.
Keep must-haves realistic; drop the endless wish lists.
Show growth and future opportunity — it matters more than salary.

Why this matters more than ever

If you can’t clearly explain the role, why it exists, and how it fits your studio’s vision, you’re simply not ready to hire.

The silent talent killer: vague job descriptions

Studies show 72% of candidates say poorly written JDs turn them off immediately. They read like you don’t know what you need. Or worse, like you didn’t care enough to figure it out.

The irony? Most hiring mistakes can be traced back to this exact point. Not slow processes. Not low salaries. But unclear expectations.

5 job description mistakes that repel top talent

1. Listing duties instead of solving a problem

Most JDs start with a laundry list:

Prepare detailed drawings
Coordinate consultants
Attend site meetings

That’s not inspiring. It also doesn’t differentiate you from the 500 other architecture firms hiring the same role.

Instead, start with the problem this person will help you solve. Example:

“We’re taking on a series of complex heritage projects across Europe, and we need a designer who thrives on adaptive reuse challenges. If you love balancing historical sensitivity with new interventions, we want to talk.”

2. Overcomplicating with jargon or unrealistic wish lists

“Proficiency in Revit, AutoCAD, Rhino, Grasshopper, Enscape, Adobe Suite, Twinmotion, V-Ray, plus 8 years experience, LEED AP, and must speak 3 languages.”

That’s exhausting. It’s also a great way to scare off brilliant people who might check 90% of your boxes. Candidates self-select out if they see a wall of must-haves.

Keep it clear: what’s genuinely non-negotiable, and what’s nice to have?

3. Not aligning the JD with your actual studio culture

If your office is big on collaboration and mentorship, your JD should say so. If it’s more autonomous, highlight that instead.

Mismatch is a huge reason hires don’t work out. Candidates might be sold on “dynamic teamwork,” only to join a firm where everyone wears headphones and hardly talks.

4. Skipping growth opportunities

Ambitious designers want to know what’s next. If your JD only describes what they’ll do today, you’ll miss people who are planning their future.

Example:

“This role is designed to grow into a project lead position within 12-18 months. We’ll support your leadership development through direct mentorship and exposure to client-facing work.”

5. Making it all about you

“Our award-winning firm… our prestigious projects… our talented leadership team…”

That’s nice, but top talent is asking: what’s in it for me?

Flip the script. Show how joining you advances their goals, not just yours.

“You’ll get hands-on experience designing community-forward spaces that directly impact how people live and connect.”

How to fix it: a quick framework

Use this simple order, but think deeply about each part:

Start with the why: What problem does this role solve? Why is it critical now? Connect it to your studio’s bigger mission so candidates see purpose, not just tasks.
Describe the impact: Show them how their work will shape real projects and communities. Use tangible examples or stories from past projects.
Define must-haves vs. nice-to-haves: Be ruthless in cutting fluff. This keeps great talent from self-eliminating because they only tick 90% of boxes.
Share your culture honestly: Is it fast-paced, mentoring-heavy, or highly independent? Let them mentally walk through a typical day.
Highlight growth: Paint a picture of where this role could go in 1–2 years. Ambitious designers want to see a future, not just a job.

Examples: weak vs strong JDs

Weak Example:

“Seeking architect with 7+ years experience, must know Revit, Rhino, SketchUp. Will work on residential and commercial projects. Competitive pay.”

Feels generic. No personality. No sense of why the role matters.

Stronger Example:

“We’re growing our studio’s focus on sustainable hospitality projects. Looking for a designer who’s excited by biophilic concepts and can lead small teams. This role is critical as we expand into new markets and will evolve into a design lead position within 18 months. You’ll work directly with clients who value innovation, not cookie-cutter solutions.”

Shows mission, type of work, ownership, growth and client philosophy.

Why it saves you money and time

The clearer your JD, the fewer mismatches you’ll have. That means:

Fewer wasted interviews
Shorter hiring cycles
Lower turnover in the first year

That alone can save tens of thousands. Not to mention, it protects your studio’s reputation as a place people want to work.