Latest / The Career Change Podcast with Fexingo: Switching Fields, Bootcamps, and Reskilling / How Bootcamp Grads Can Transition Into UX Research
Transcript
- Lucas: There's a career path in tech right now that almost nobody tells bootcamp grads about, and it's growing because companies are obsessed with one thing: knowing exactly what users want before they build it. Luna: You're talking about UX research, right? Not design, not testing — the person who actually talks to users and synthesizes what they learn. Lucas: Exactly. And the reason it matters today is that the era of 'ship fast and break things' is over. In mid-2026, the dominant philosophy is 'ship what you know works.' Companies like DoorDash, Shopify, Atlassian — they've all scaled back on big usability labs and moved to lightweight, remote research cadences. That shift opens the door for people who can think like a researcher without a psychology PhD. Luna: I want to get to the how in a second, but first — give me a concrete example of a research win that saved a company real money. Lucas: Sure. DoorDash in 2024 redesigned their menu browsing flow based on a three-week research sprint. They found that users were confused by the way sides and modifiers were grouped. After the change, order errors dropped 18 percent. That's not a design decision — that's a research win. And the team that did it wasn't a bunch of academics. It was two former bootcamp grads who moved into research from support. Luna: Okay, so the skill set matters more than the degree. What specific skills from a typical coding bootcamp actually transfer to UX research? Lucas: Three big ones. First, structured thinking. Bootcamp grads learn to break a problem into user stories, acceptance criteria, edge cases. That's exactly how you structure a research plan. Second, sprint-based workflows — you're used to two-week cycles with a demo at the end. Research operates the same way: recruit, interview, synthesize, present. Third, and this one surprises people, pull request culture. Luna: Pull request culture? How does that relate to talking to users? Lucas: Because research is collaborative. You write a discussion guide, your team comments on it, you revise — that's a pull request. You share raw notes, the product manager adds a question, you iterate. Bootcamp grads already know how to give and receive structured feedback in writing. That's half the researcher job. Luna: I buy that. But what about the portfolio? If you don't have a degree in psychology or HCI, how do you prove you can do the work? Lucas: You do a self-initiated research project. Pick a product you use every day — say, the Starbucks app. Recruit five friends, spend two weeks doing interviews and a usability test, write a three-page findings report with recommendations. That's your portfolio piece. No permission needed, no degree required. And it's more convincing to a hiring manager than a thesis from ten years ago. Luna: I know someone who did exactly that with the Notion mobile app. She interviewed eight people who had switched from Evernote, found three pain points, presented them to a Notion product team member on a coffee chat. She got a contract offer two weeks later. Lucas: That's the playbook. And the reason it works is that research is still a supply-constrained role. According to the Bureau of Labor Statistics, the category 'survey researchers and market research analysts' is projected to grow 19 percent through 2034. But the tech version — UX researcher — pays significantly more. Median total comp for a mid-level UX researcher in the US right now is around $130,000. That's competitive with many engineering roles. Luna: And a lot of those roles don't require a technical interview. You're not whiteboarding algorithms. You're talking about user behavior. Lucas: Right. The interview is usually a portfolio presentation and a case study where you walk through how you'd research a hypothetical feature. That's it. No leetcode, no system design. For bootcamp grads who love the problem-solving but are tired of coding, this is a natural pivot. Luna: Let's talk about the money question. You mentioned $130k median. What does the entry point look like for someone transitioning from a bootcamp? Lucas: Entry-level UX researcher roles — places label them 'associate researcher' or 'research associate' — start around $75,000 to $90,000. That's for someone with zero years of formal research experience but a strong portfolio. After two years, you're usually in the $100k to $120k range. And there's a fast-growing subfield called research ops that pays even earlier. Luna: Research ops — that's the operations side, managing tools, recruitment, scheduling, that kind of thing? Lucas: Exactly. Research ops is the infrastructure that makes research scalable. You're the person who sets up the participant database, manages consent workflows, runs the calendar of studies. It's less interpretive and more organizational. And it's a great entry point because you learn the research process from the inside. Many research ops people transition into full researcher roles after a year or two. Luna: Okay, so if I'm a bootcamp grad listening right now, what's my first step this week? Lucas: First: read one study from the Nielsen Norman Group on a topic like 'how users read on the web.' It's free. Second: pick a small app you use, run a five-minute usability test with one friend, and write down what you observe. Do that three times. Third: look up the job title 'UX researcher' on LinkedIn and read the job descriptions. You'll see that most don't require a degree — they ask for 'experience with qualitative research methods' and 'ability to synthesize findings.' You can demonstrate both of those with your self-initiated project. Luna: I want to push back a little. Some companies still require a master's in HCI or psychology. How do you handle that? Lucas: You don't apply to those. There are plenty that don't. Atlassian, for example, has explicitly stated they value 'research craft over credentials.' Shopify's research team includes people from bootcamps, from journalism, from teaching. You're looking for companies that hire for skill, not pedigree. And the list is growing because the best researchers often come from non-traditional backgrounds — they ask better questions about real user behavior. Luna: That's a good note to end on. But before we wrap, I want to address something practical: how do you know if you'd even like research? It's very different from coding. Lucas: Great question. The simplest test: do you enjoy having a twenty-minute conversation with a stranger about how they use a product? Do you find yourself wondering why people do what they do? If you've ever been the person on your bootcamp team who said 'but what does the user actually want?' — that's a signal. Research is for the curious, not the conclusive. You're never done learning. Luna: Honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. It's the smallest possible way to say this content matters, and it keeps the show ad-free. Lucas: Yeah, we don't run ads, so listener support is what keeps this going. If we helped you think through a career move, that link is there. Luna: Right. Back to the topic: one more thing I think listeners should know — there's a Slack community called Research Ops Assembly that's free to join. It's full of people who transitioned from other roles. Great place to ask questions and find mentors. Lucas: Perfect. And if you want to go deeper, look up the 'UX Research' playlist on the Fexingo podcast network. We have episodes on interview prep, portfolio building, and how to negotiate your first research offer. That's it for episode 101. See you next time.