A Test batsman doesn't open the batting in a T20.

Not because he isn't good enough. Because the format demands a different specialist. Same sport, same skill on paper, completely different job on the day.

Hiring works the same way — and most job descriptions don't say the quiet part out loud.

The title tells you almost nothing

Post a role for "Senior Product Designer" and you'll get applicants who've done everything from redesigning a checkout flow to building a design system from scratch to leading a five-person team through a Series B pivot. On paper, they all match the title.

But sit down with the hiring manager, and the brief is never really "find me a Senior Product Designer." It's something much more specific — they just haven't said it yet, sometimes even to themselves.

In practice, "senior" might actually mean someone who:

• Has shipped 0→1, not just optimised an existing product

• Is stronger in UX thinking than UI polish — or the reverse

• Can build and own a design system, not just follow one

• Has enough product sense to push back on a PRD

• Can hold their own in a room with engineering leads

• Is genuinely okay not knowing the answer on day one

• Can lead a small team while still shipping their own work

• Will raise the craft bar for a team that's already strong on systems

Same title. Same-looking JD. Completely different job.

Why two identical-looking roles are rarely the same role

The real spec was never the title — it's the business behind it.

A Series A SaaS startup needs a different designer than a consumer app operating at scale. A fifteen-person design studio needs different instincts than an enterprise platform team. "Senior" at a company solving a brand-new problem looks nothing like "senior" at a company optimising a well-understood one.

Domain matters. Product maturity matters. Team composition matters. The stage of the company's journey matters. None of that shows up in a title, and most of it doesn't show up in a job description either — because it's rarely written down. It lives in the hiring manager's head as a set of instincts about what "good" looks like for this team, right now.

Where hiring goes wrong

Here's the part that trips up most hiring processes: everyone aligns on the title in the kickoff call. Almost no one aligns on the actual shape of the role.

So the JD goes out generic. Applicants get filtered against the wrong bar — too senior on paper, not senior in the way that matters; strong UI portfolio, but no real product judgment; great at scaling, but the company actually needs someone who's comfortable building from nothing. Interviews happen. Weeks pass. And three rounds in, the hiring manager says "these aren't quite right" — without being able to say exactly why.

That's not a sourcing problem. It's a specification problem. You can't filter for a requirement nobody wrote down.

The fix isn't a better job description

It's a sharper conversation before the job description gets written.

That conversation isn't about years of experience or a list of tools. It's about the stage the company is at, the ambiguity the role will sit in, the specific gap this hire needs to close, and how that person needs to work with the team that's already there. It's not about finding someone who's done the exact same job before — it's about finding the right combination of strengths, experience, and ways of working for this team, this product, and this stage of the company's journey.

Get that right, and one designer changes what the whole team is capable of. Get it wrong, and even a genuinely great designer ends up looking like a bad hire — not because they weren't good, but because they were never the right specialist for the format being played.

If your last design hire didn't work out despite ticking every box on the JD, this is usually why. The title matched. The gap didn't.

At BeingUser, the first thing we do — before we source a single profile — is have the conversation most hiring processes skip: what does "senior" actually need to mean for your team, at your stage, solving your problem. That's the spec we hire against.

Book a call and let's figure out what you're actually hiring for.