Let's talk about what early career UX folks should emphasize in interviews, especially when searching for the first job.

A mistake I see folks make is when they focus on the designs they've created. Often these are school or side projects. They look great. They work great.

1/
However, that's not what smart hiring managers care about.

Of course, if you produce crappy-looking stuff, they won't give you the time of day.

But you don't have crappy-looking stuff. That's not what's preventing you from getting that first dream gig.

2/
What's preventing you from getting that gig is that the hiring managers can't see your vector of growth.

You see, it's likely you're not telling your story right. The hiring manager doesn't care about your designs, because, let's face it, they aren't that impressive.

3/
You're early in your career.

None of us produced impressive work when we were early in our careers.

It takes years to learn how to produce impressive work.

You haven't put in those years of hard work yet.

You will. I have every confidence that you will.

Someday.

4/
But, for now, you need to focus on getting you that first job.

And to do that, you'll need to impress the hiring managers.

And if you won't do that with your designs, what will you do that with?

Answer: How you *learned* to do those designs.

5/
This is what most early-career UX folks miss: It's about how you learn, not how you work today.

Whatever work you've done? It's not good enough for your first job.

It never is.

To produce good work when you get your first job, you'll need to learn a lot of stuff.

6/
That's what a smart hiring manager cares about most: How good are you at learning?

The hiring manager knows you just learned all this stuff.

How did you do it?
How quick were you?
How thorough were you?
How did adapt to new information?

7/
Think about that.

It's not what you can do. It's what you *will* do.

That's what the hiring manager wants to know.

Given that, how are you telling that story about yourself?

How are you showing how good you are at learning?

8/
You probably have a résumé.
How well does your résumé tell the story of what you've learned and how you learned it?

You likely have a portfolio.
How well does your portfolio tell the story of all the things you've learned?

9/
When you describe a project in your portfolio, do you explain what you didn't know at the start that you learned during the project?

Do you explain how you went about learning it?

Do you explain how what you learned changed how you'll design in the future?

10/
Do you show the mistakes you made?

What did you learn from those mistakes?

What did you learn from trying to correct those mistakes?

11/
Do you show what you've learned by studying the designs of others?

Do you show what you learned by emulating other designer's work?

Do you show what you learned by transforming their work into your own style and solutions?

12/
Do you show what you've learned from user research?

How did your chosen research methods help you learn what you learned?

Where did the research methods fail to teach you something you later learned was critical?

What did you learn to do differently the next time?

13/
Can a hiring manager look at your portfolio and résumé and see how you've grown?

Can they see how the most recent projects are so much better than the earlier projects?

(Can they even tell which are the most recent and which are the earlier works?)

14/
Can a hiring manager see your vector of growth?

A vector represents direction and distance. Can they see the distance you've come and the direction your design education has taken you?

Not just what you've learned in school. All of your education.

15/
The hiring manager needs to see your vector of growth.

They need to plot it from today into the future.

They need to see that it will cover all the thins you don't know. That you can't possibly know. That you will need to learn.

That's what makes you impressive.

16/
If you're not talking about how you've learned and grown in your UX journey, you're likely leaving out the most important part of your story.

If you're wondering why you're not getting the job offers you hoped you would get, this may be why.

17/
Why don't you see others doing this?

Because it's much harder to do this than just showcasing your best project work.

But it's not what your user (the hiring manager) needs from you.

Design is hard. That's what makes it fun.

Do the hard work. I promise, it's worth it.

18/fin

• • •

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

11 Aug
Dashboards are often what customers ask for.

They are rarely what customers need.

If you’re building a dashboard, it’s likely your user research wasn’t finished.
Dashboards report on current status.

Users don’t act on status.

They act on change in status.

Dashboards are passive when the user needs something active.

They are a failure before it happens.

“Users wouldn’t ask if they didn’t need them.”

Oh, there’s a need alright.

Dashboards aren’t a need. They are a solution. And, often, the wrong one.

Learn more about the problem and a better solution will likely present itself.

Read 13 tweets
20 Dec 19
Disappointed there are still hiring teams who won’t even talk to a candidate who doesn’t have an up-to-date portfolio.

Several excellent designers I know were unexpectedly laid off recently. They don’t have portfolios ready.

These teams will miss the chance to hire them.
Requiring a portfolio for an interview is a great way to push highly-qualified candidates away.

These folks can show their work, they just don’t have it packaged in a way to supply it when applying.

It’s a *huge* hiring mistake to refuse to talk with them.
I wrote about how to avoid key hiring mistakes like this one.

articles.uie.com/reviewing-ux-p…
Read 24 tweets
3 Dec 19
Hello, UX Managers.

Are you building your team and hiring UX professionals?
UX Designers?
UX Researchers?
UX Writers and Content Specialists?

Reply to this tweet with a link to the job description and the job's location.

I'll retweet it to my 100k followers.
My followers include very talented UX professionals who:

• Are early in their career and are looking for their first job.

• Can work remotely.

• Are looking for an org that will sponsor a visa.

You get extra karma points if your job is open to any of these wonderful folks.
Feel free to reply with any open posting, even if I retweeted it recently.

I do this every month. Here's November's collection of posts:
Read 5 tweets
6 Nov 19
“Quant tells us what. Qual tells us why.”

This oversimplification regularly gets teams into trouble.

It suggests that quant and qual are simple, single dimensional measurements.

And it suggests they’re somehow to be considered separately.

Neither suggestion is correct.
Qualitative data comes in all shapes and sizes, as does quantitative data.

For qual data, we have user's problems, their needs, their journeys, their outcomes.

For quant, we have success rates, problem rates, attitudes, costs.
We mix and match. More importantly, we combine them to tell a story the informs the decisions we have before us.

The richer the data, the better the story.

And the better our decisions will be.
Read 11 tweets
1 Nov 19
A/B testing is an effective approach to use science to design and deliver deeply-frustrating user experiences.
A/B testing without upfront research is just random monkeys testing random designs to see which of those designs do “best” against random criteria.

If drug testing was actually implemented like most A/B tests, you’d give 2 drugs to 2 groups of people and pick the “winner” by whichever group had fewer deaths.

Read 4 tweets
4 Sep 19
Goodness, no.

This is a proven recipe for producing frustrating products that users will hate.

Qual has to drive quant if you want to deliver great products and services.
By observing users and talking with customers, you learn what they need that neither you nor your competitors provide.

Then you translate the scenarios into behaviors you can track in the data, to learn the extent of the need.

articles.uie.com/ux-metrics-ide…

That drives great design.
Qual-first ensures you’re focused outwardly on your customers and users.

Quant-first drives orgs to be inwardly business-metric focused and ignore true user needs.
Read 6 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 Become our Patreon

Thank you for your support!

Follow Us on Twitter!