Linguistics → UXR | Applying for UXR (1): Qualifications & Mindset

Do you need a master's or PhD? What if you don't have industry experience? Can career-switchers get in? Answers to the questions I get most often on ADPList.

Intro

First — congratulations on taking the first step toward UXR. 🙂

For context on my own transition, see:
Linguistics → UXR | Career Pivot Prep & ShopBack UXR Intern Interview
Linguistics → UXR | Academia vs. Industry: What’s Different After 8 Years of Research?

This post starts with qualifications and mindset. Most of these questions came from ADPList mentees — I’ve synthesized my own experience plus conversations with colleagues in the field. These aren’t absolute rules; they’re my honest perspective. Future posts will cover resumes, portfolios, and interviews.

Questions in the comments welcome throughout. 🙂


Qualifications & Mindset

Q: Do I need a master’s or PhD to apply for UXR?

No.

An advanced degree may indirectly signal research ability, but it’s not required. Having a degree doesn’t guarantee research competence, and not having one doesn’t prevent it. Some of my most capable colleagues don’t have postgraduate degrees, and I sometimes catch myself still thinking in academic modes that hold me back in industry.

In practice, degree requirements have been stricter in overseas markets (especially recently, with many excellent senior UXRs being laid off, making degree a quick first-round filter). In Taiwan, I haven’t seen it applied as rigidly.

Q: If I don’t have a degree, how do I prove my research ability?

UXR is fundamentally about logical reasoning and analytical thinking. A degree historically signals that through thesis writing and dissertation defense. Without one, there are many other ways to demonstrate the same.

For job applications, your resume and portfolio matter most — and your resume comes first, always.

In your resume, you can describe past projects — even non-traditional ones — and show:

For example, if you worked in social media marketing:

Simple example, but it demonstrates research thinking. Because research, at its core, is: identify a problem, find a way to solve it. If a hiring manager sees that logic and gets curious, they’ll look at your portfolio next.

Q: If I don’t have industry experience, how do I show I can do the work?

This comes up a lot from academic backgrounds. Hiring managers know PhD/master’s candidates won’t have much industry experience — their expectations shift toward adaptability, interpersonal skills, and real-world responsiveness.

Industry research involves far more human interaction than academic research. I’d suggest leaning into how you navigated collaboration in your academic work — how you worked with your lab, your advisor, your committee. Relatedly: industry work needs to create impact, so try framing your research in terms of what it changed, influenced, or enabled downstream.

For a more detailed comparison of academic vs. industry research:
Linguistics → UXR | Academia vs. Industry

Q: My qualifications don’t seem to match the JD. Should I still apply?

Apply.

In some countries, candidates will apply with full confidence even if they only meet half the requirements — presenting themselves as “the chosen one.” In Taiwan, we tend to see one slightly-off requirement and lose confidence entirely. I was the same way for a long time.

JD requirements are a framework, not a hard filter. They describe what the company is roughly looking for — not an exact specification.

For instance: a job asks for 2 years of experience, but you have 1. That doesn’t automatically disqualify you. “2 years” signals they want someone who can ramp quickly. Someone with 1 strong year may be better than someone with 2 mediocre ones.

Another case: a company wanted a Product Designer with Figma experience. The candidate only knew Sketch. They got hired anyway — and learned Figma before their first day.

JD conditions are mostly external signals. If you can convince the company you’re the right person, they’ll hire you regardless of a gap in the checklist. As long as you’re not wildly off-target, apply, and let your resume make the case.

(Exception: hard requirements like work authorization. Those you can’t talk your way around.)

Q: I want to switch careers. Do UXR teams welcome career changers?

Yes.

UXR is a role that draws on an enormous range of skills and knowledge. In a tech company, we touch products, business, design, marketing, and data — plus we spend a lot of time working with different types of people, which I think naturally attracts people with high empathy. Most researchers I’ve met are open to career changers. More than open, actually — often enthusiastic.

That said, career changers often feel most lost when facing a JD full of requirements they don’t meet. My suggestion: lean hard into your previous expertise. Present it with confidence and explain clearly how it translates to UXR work. That specificity is what makes an impression.

Q: What skills do I actually need?

In my view, the most important is research ability — it’s the foundation. Beyond that, everything else is a soft skill. And the most important soft skill, in my experience: communication.

I joined ShopBack with research ability and not much else. E-commerce knowledge, statistics, survey design, Python, Figma — all of that came after I joined and needed it.

One thing worth noting: in overseas markets, job listings are often more explicit about method orientation — qualitative, quantitative, or mixed methods. If you see these:

Worth doing some digging before you apply. 🙂


Wrap-Up

Hope this helped as a starting point for thinking through your UXR application. 🙂
Next up: resume, portfolio, and interviews. Leave a comment if there’s something you want me to address first.

Want to chat 1:1? Find me on ADPList. 🙂


Thanks for reading :D

If you enjoyed this post, feel free to click the coffee button in the lower right to support us and give Lottery a can 🐾

Comments

  • Loading…