I see the same mistake repeated across many of the UX job ads I review.

The job ad describes the JOB, yet highly-qualified candidates want to learn about the WORK.

These are very different things.

1/
What we hear from candidates:

Tell me what I'll be working on.
Tell me how my work will have an important impact on people.
Tell me what makes the work challenging, especially for someone at my experience level.
Tell me what makes this work unique.

This is the WORK.

2/
UX job ads rarely talk about those things. Or maybe they give 1-2 sentences about it.

Here's one example I just found. They give 1 sentence to what the company does. The rest of the paragraph could be describing any company on the planet.

3/
This is the only other paragraph about the team the new hire will be working on.

This could describe any design system effort at any of a thousand different companies.

There's nothing in here that makes this a special job.

4/
This ad is for a Sr. UX Design Manager position. Could you tell that from any of the description I've shared so far?

Nope.

Nothing about the team you'd manage.
Nothing about the work of the team.
Nothing about the impact you'll have as their manager.
Why should you apply?

5/
It gets worse.

Here's all the bullets that describe "the role."

Can you find 1 thing that doesn't describe what every manager everywhere should do?
Can you find 1 thing that is unique to this position?

They could replace this with just:
• Do what every manager does.

6/
Here's a quick way to get highly-qualified candidates banging down your door to join your team:

Actually describe the WORK.

Talk about what you love about it.
Talk about why you come to work every day.
Talk about the pride you take in a job well done.

7/
What does that work look like?
Why is it motivating?
What change are you making in the world by doing great work?

This is what every top candidate wants to know.

8/
Pretend you're hiring a Sr UX Designer.

Imagine the ideal person sat down next to you and you're trying to convince them to apply for your position.

They ask "What would I be working on?"

9/
Would you answer:

"Develop and manage user experience design documentation repositories including UI standards, personas, workflows, and research data."

No, of course not.

That's the JOB. Not the WORK.

10/
You'd describe the cool products your team delivers.
You'd describe how those products improve your users' lives.
You'd describe the really tough problems your team is up against, that someone like this person would have to solve.

You'd describe the WORK. Not the JOB.

11/
I'm hyper aware of this problem because my team and I help market all the positions on our UX Centered Careers job board (uxcareers.uie.com).

We try to write tweets and short ads to promote to our 230,000 followers, subscribers, and community members.

12/
If you follow me, you've probably see these tweets.

We're trying our hardest to share what makes each job uniquely cool. What makes it a unique challenge? What makes it ideal for exact right person?

Job ads that don't talk about the WORK make that really hard.

13/
With some ads, it's such a struggle.

And it shouldn't be.

If you're writing a job ad, don't fall into this trap.

Describe the WORK, not the JOB.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Jared Spool

Jared Spool Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jmspool

30 Nov
I pine for the day when UX research is no longer sold as a way to “validate” the designs of products or services.

This thinking limits what teams deliver.

Going down this path just to get a foot in the door creates so much extra work later on to break away from it.
Put another way:

If “validation” is the first time any team members are getting direct exposure to users and their problems, you’re doing it wrong.
I spend most of my time these days helping extremely frustrated UX leaders try desperately to push past the “research=validation” boundary with their leadership.

It’s really a dangerous mindset to let grow.

There are better ways to position research. We’re much smarter now.
Read 5 tweets
22 Nov
NPS, UMUX-lite, SUS, CSat, CES…

These are just tools for producing a number that will send your team off optimizing the wrong things.

Best thing you can do is just ignore them.

(If there’s a follow-on ‘verbatim’ question, spend your time there. That could be useful.)
The problem with ‘satisfaction’ is it’s a meaningless term.

Are you satisfied with this conversation?

If you gave me a 7, how is that different than if you gave me a 6? Or a 3?

Everyone brings a different meaning of satisfaction to the survey. We don’t know their context.
When every respondent brings their own meaning and context to a question, you can’t aggregate the answers. You’re aggregating apples, oranges, watermelons, and bees. What’s the average of all that mean?

Satisfaction measures are literally garbage measures.
Read 6 tweets
25 Sep
It makes me smile when a product manager tells me they need a full time researcher before they can do any research.

I look them in the eyes and say “you’re a full time user researcher.”

All PMs are user researchers.
Maybe not a good one.
However, they can become a better one.
User research is what PMs do.

They identify what users and customers need. Why the product doesn’t do that yet. What needs to change to make the user’s life better.

It’s the most important part of their job.
The great user research a PM has, the better their product will be. We’ve got 40 years of product management history to prove this.

It’s too bad the PM literature ignores this fact that user research is critical to great PM work.

It would make their jobs so much easier.
Read 7 tweets
19 Sep
Current status Image
Frog on a log Image
Status Update: Image
Read 4 tweets
18 Aug
"Don't let the perfect be the enemy of the good."

In UX design, this thinking delivers more damage than benefit.

There's usually a LOT of distance between good and perfect.

Good leaves room for better, which, when provided by someone else, leaves our designs behind.
We can do more that just good.

We can meet needs and exceed expectations.

We can excel beyond just satisfactory. (Satisfaction surveys should be banned in UX design. They measure the wrong things.)
There's a lot we can do to go beyond just being "good" before we come anywhere near being "perfect."

We should strive to provide experiences that people want, need, and enjoy.

Don't let the good be the enemy of the better.
Read 4 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(