<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sneha Gokhale on Medium]]></title>
        <description><![CDATA[Stories by Sneha Gokhale on Medium]]></description>
        <link>https://medium.com/@sneha_33328?source=rss-db797fe9c4d7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dDJ1XdaA2thP1XP3kxCMvQ.png</url>
            <title>Stories by Sneha Gokhale on Medium</title>
            <link>https://medium.com/@sneha_33328?source=rss-db797fe9c4d7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 22:03:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sneha_33328/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I built and reinforced a Claude skill that mimics my user research analysis process.]]></title>
            <link>https://medium.com/@sneha_33328/how-i-built-and-reinforced-a-claude-skill-that-mimics-my-user-research-analysis-process-fff59d56a431?source=rss-db797fe9c4d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/fff59d56a431</guid>
            <category><![CDATA[product-research]]></category>
            <category><![CDATA[cluade-ai]]></category>
            <category><![CDATA[ai-in-product-development]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[claude-skills]]></category>
            <dc:creator><![CDATA[Sneha Gokhale]]></dc:creator>
            <pubDate>Thu, 01 Oct 2026 18:02:43 GMT</pubDate>
            <atom:updated>2026-10-01T18:02:43.687Z</atom:updated>
            <content:encoded><![CDATA[<h3>How I built and reinforced a Claude skill that mimics my user research analysis process. (with prompts)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_0YkIDsoP1mHzG_muJRGg.jpeg" /><figcaption>Claude for UX Research</figcaption></figure><h3>Learning how to build a strong ‘Skill’</h3><p>For the last ten-plus years, analyzing qualitative research has been the part of my job that feels the most <em>mine</em>. Scanning transcripts, affinity mapping, watching patterns surface and slowly ladder up into insights. It’s a craft I’ve built quietly over a decade, and honestly, it’s the part I’m a little precious about.</p><p>I’ve built skills before, but to learn the best practices and the latest way to build a skill, I decided to take a course to sharpen mine. I took <strong>C</strong><a href="https://maven.com/caitlin/claude-code-insights?utm_campaign=aakash-gupta&amp;utm_medium=affiliate&amp;utm_source=maven&amp;promoCode=AAKASHxMAVEN"><strong>laude Code for Customer Insights</strong></a> by Caitlin, and I’d recommend it to any researcher who’s curious about this stuff.</p><p>Caitlin has a real gift for making the fundamentals click. The part that stuck with me most was her framing: don’t build a <em>generic</em> skill, build <em>your</em> skill. Mimic your own process. Produce outputs that still carry your voice and POV instead of collapsing into something bland.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eeGrG4KODc50z6D_NTUkpA.png" /></figure><p>So when I set out to build a Claude skill to do interview analysis, I wasn’t trying to replace that craft. I was trying to clone it.</p><p>I wanted a skill that thought the way I think, one that produced outputs in my voice, with my point of view, instead of the flat, generic synthesis you get when you just paste transcripts into a chatbot and ask for themes.</p><h3>Setting up the skill and grading its output.</h3><p>In my role, a big chunk of the job is running qualitative studies — testing new concepts, generative research to understand how people work today, what are their needs and expectations, etc.<strong> So building a research-analysis skill felt like the highest-leverage thing I could hand off.</strong></p><p>I poured everything into it: my current way of working, my process, example outputs, how I like to code my themes, and importantly the rules and guardrails I use to keep analysis from drifting into hallucination or misinterpretation.</p><p>The lucky part was the timing. I built the skill <em>in parallel</em> with a study I was already analyzing the old-fashioned way. So by the time the skill produced its report, I had my own manual analysis sitting right next to it. A perfect, slightly nerve-wracking A/B test.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m2NJNyPO6efCqhIKvYOuSQ.jpeg" /><figcaption>Manual analysis vs report produced by the Claude skill</figcaption></figure><p>At the surface, the two were strikingly similar. My themes and the skill’s themes were clearly cousins:</p><ul><li>I had <strong>“Wait time behavior/expectation.”</strong> The skill produced <strong>“Wait-time tolerance splits; perceived slowness is an adoption risk.”</strong></li><li>I had <strong>“Semantics confuse.”</strong> It had <strong>“Data hygiene / naming conventions block analysis today.”</strong></li><li>I had <strong>“Flow coherence and friction.”</strong> It gave me <strong>“Concept UX confusions.”</strong></li></ul><p>If you squinted, we were reading the same outcomes. But then I actually read the details. And that’s where the two outcomes parted ways.</p><h3>Where we diverged (my analysis and the skills analysis):</h3><h3>1. The wait-time theme</h3><p>This is the example that best captures the gap, so let me lay both versions side by side.</p><p><strong>My take:</strong> the problem wasn’t just time, it was <em>uncertainty</em>. People are used to AI wait times; what they can’t stand is waiting without knowing if the output will be any good. Manual work is slow but trusted — they’ve lived the effort-to-accuracy trade-off. A new platform hasn’t earned that yet, so even a shorter wait feels risky. The fix is trust, not just speed: use faster models for new users to prove the payoff early, then introduce slower, deeper analysis once they believe waiting is worth it.</p><p><strong>The skill’s take:</strong> genuinely sharp — sharper than mine in one respect. It spotted that tolerance tracked whether the wait felt like <em>delegated background work</em> or <em>blocking foreground work</em>, and it pulled the evidence from direct customer quotes. The fix it recommended was: run long jobs in the background with a notification and show live progress.</p><p>Both good. Both right, even. But notice what the skill <em>completely missed</em>: the new-user trust arc. The idea that first-time users need to verify results before they’ll invest their patience — and their token spend — in letting the AI run. That insight didn’t come from the transcript. It came from me knowing our users.</p><h3>2. <strong>UX confusion (</strong>The pattern repeats)</h3><p>Once I saw it, I couldn’t unsee it.</p><p>On <strong>UX confusion</strong>, the skill packed everything into one big theme. My analysis broke it into about five distinct insights, and I promoted the “dual entry point” problem to a top-level <em>core</em> issue. Why? Because it shows up right at the start of the flow, and if we don’t fix it there, we risk losing customers at the front door. That’s not in the transcript. That’s pattern-matching from years of watching where people fall off.</p><h3>What was missing in the skill</h3><p>When I stepped back, the divergences all traced to the same root: <strong>context and observation.</strong></p><p>My analysis was quietly shaped by years at this organization. I knew from past research that we have power users <em>and</em> new users, and that their behavior differ, and that designing for one can’t mean ignoring the other.</p><p>I knew that some of what we tested was placeholder, so I mentally discounted it instead of over-indexing on it. The skill had none of that history.</p><p>And there was a whole category of data I simply never gave it: <strong>observational.</strong> I fed the skill transcripts, not recordings. But I ran those interviews. <strong>I watched people’s eyes light up. I heard the tone shift. I saw the exact moment someone lost interest because a feature didn’t apply to them.</strong> Those signals never make it into a transcript, and they’re often the most honest data in the room.</p><p>The skill wasn’t wrong. It was working with a smaller world than I was.</p><h3>How I made the skill better</h3><p>Here’s the part I’m actually excited about. Every gap was a to-do item. So I revised the skill:</p><ul><li><strong>Feed it my interview notes.</strong> I now point the skill at the observations, quotes, and reactions I jot down while interviewing — so it works from my eyes and ears, not just the transcript.</li><li><strong>I added an explicit “positive signals and value prop” section</strong> to the output. It’s always good to bring the team wins alongside the opportunities, not just a list of what’s broken.</li><li><strong>I told it to slice UX friction more finely</strong> instead of dumping everything into one catch-all theme. Finer themes are easier for a PM or designer to pick up and act on.</li></ul><h3>Want to build your own? Start with this prompt</h3><p>If you’re a researcher curious to try this, here’s a prompt that bakes in everything. It interviews <em>you</em> first, so the skill comes out sounding like you, not like a generic bot.</p><blockquote>I’m a UX/qualitative researcher and I want you to help me build a <strong>reusable Claude skill</strong> that analyzes my interview transcripts the way <em>I</em> would carrying my point of view and voice. Interview me one section at a time before writing anything.</blockquote><blockquote><strong>1. Learn my process.</strong> Ask me how I actually work a transcript today, how I read, code, cluster, and name themes, and how I ladder from raw quotes to high-level insights. Don’t assume a method; extract mine.</blockquote><blockquote><strong>2. Learn my voice.</strong> Ask for 1–2 example reports I’m proud of. Study how I phrase themes, takeaways, and recommendations, and mirror that tone in the output. use this to shape the final output.</blockquote><blockquote><strong>3. Set the guardrails.</strong> Encode these rules and ask me what to add: never build a theme from a single unsupported quote; never stretch evidence to fit a tidy story. Flag low-confidence or thin-evidence findings instead of hiding them; call out contradictions rather than smoothing them over.</blockquote><blockquote><strong>4. Take in more than transcripts.</strong> Add a step that asks me for my <strong>interview notes, </strong>the observations, tone shifts, reactions, and standout quotes I capture in the room.</blockquote><blockquote><strong>5. Flag my blind spots back to me.</strong> Where the analysis depends on organizational context you don’t have (power users vs. new users, placeholder test content, prior research), say so and ask me to confirm.</blockquote><blockquote>Once you understand all five, propose a SKILL.md structure, then draft it. Treat the output as a rigorous first pass I’ll refine — not the final word.</blockquote><h3>What I’d tell another researcher</h3><p>If you take one thing from this: <strong>don’t build a skill that does analysis. Build a skill that does <em>your</em> analysis, </strong>and then be honest about where it can’t reach yet.</p><p>AI got me a genuinely strong 80%, and in a couple of places it out-noticed me. But the last stretch, the contextual judgment from years on a team, the observational data that lives in a glance rather than a sentence, that’s still mine to bring.</p><p><strong>The most useful mental model I’ve landed on isn’t “AI replaces the analysis.” It’s “AI gives me a fast, rigorous first pass, and I bring the context and the eyes it doesn’t have.”</strong></p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fff59d56a431" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Isn’t Replacing UX Researchers. It’s Rewriting the Job Description.]]></title>
            <link>https://medium.com/@sneha_33328/ai-isnt-replacing-ux-researchers-it-s-rewriting-the-job-description-f59723ed2843?source=rss-db797fe9c4d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/f59723ed2843</guid>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[career-growth-in-tech]]></category>
            <category><![CDATA[changing-jobs]]></category>
            <category><![CDATA[ux-research-process]]></category>
            <category><![CDATA[ai-and-ux-research]]></category>
            <dc:creator><![CDATA[Sneha Gokhale]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 17:23:36 GMT</pubDate>
            <atom:updated>2026-08-14T17:23:36.690Z</atom:updated>
            <content:encoded><![CDATA[<h4>Learning from Learners Research Week: How top researchers at LinkedIn, Google, and Meta are evolving the discipline.</h4><p>Scroll through any tech or design circle today, and you’ll find the same suffocating narrative: UX Research is on life support. The timeline is heavy with AI anxiety. Synthetic users and automated tools are coming for our jobs. But after attended the Learners Research Week in San Francisco back in May, I have a different take… It’s not doomsday yet.</p><p>I went in expecting at least a little collective panic about the future of our industry. Instead, I walked away with something entirely different: fierce inspiration.</p><p>Researchers across the tech ecosystem aren’t packing up their desks. They are actively reinventing the scope of what we do and how we participate in product development.</p><p><strong>AI isn’t replacing the UX researcher — it’s aggressively rewriting our job description.</strong></p><p>Here are four major shifts happening on the frontlines, and how you can evolve your own role to meet the moment.</p><h3>1. The Holistic Synthesizer</h3><p>Inspired by <strong>Anna Klutho, </strong>Senior Market Research Manager, LinkedIn. Presentation titled One data source is not enough.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*89NRLCt7B8O0U9-VCuoPxQ.png" /><figcaption>Anna presenting ‘one data source is not enough’ at the learners, research week</figcaption></figure><p>Anna’s session centered around a simple but powerful premise: <strong>one data source is not enough.</strong> Historically, UX researchers have relied heavily on a standard diet of pure qualitative interviews and isolated quantitative surveys. We stayed in our lane, mixing methods when we could, but largely keeping our data neatly categorized.</p><p><strong>The Evolution</strong></p><p>Thanks to AI, we now have the key to a massive, previously locked black box. We can rapidly process massive amounts of telemetry data and scrape social listening feeds to see exactly what customers are saying about our product in real-time and craft comprehensive narratives.</p><blockquote><em>My biggest takeaway from Anna was that we can now easily access these various channels and blend them together. We no longer have an excuse to look at data in silos.</em></blockquote><p><strong>In Practice</strong></p><p>Let’s say you’re mapping the customer journey for opening a new trading app account.</p><ul><li><strong>Look beyond the usability lab.</strong> Don’t just rely on qualitative data from testing the standard account creation flow.</li><li><strong>Scrape the wild.</strong> Layer in real customer friction by pulling complaints from LinkedIn, App Store reviews, and support tickets.</li><li><strong>Add macro context.</strong> Factor in broader market trends — like Gen Z’s baseline expectations when starting a relationship with a financial product.</li><li><strong>Let AI connect the dots.</strong> Use AI to process these disparate threads, synthesizing them into one unified, undeniable artifact that stakeholders simply can’t ignore.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-R78I2wbbB6C7rUU" /><figcaption>Photo by <a href="https://unsplash.com/@uxindo?utm_source=medium&amp;utm_medium=referral">UX Indonesia</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>By using AI to process these disparate threads, you synthesize them into one unified, undeniable artifact that stakeholders can’t ignore.</p><h3>2. The Insight Content Creator</h3><p>Inspired by <strong>Denise Sauerteig, </strong>Staff UX Researcher, Turo. Presentation titled Effervescent research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PtEH1vWDrSyNELnuMTBOXw.png" /><figcaption>Denise presenting ‘effervescent research’ at the learners, research week</figcaption></figure><p>Denise introduced a brilliant concept: “effervescent research.” In this ruthless attention economy, our stakeholders are drowning in dashboards, slack threads, and endless data streams. If we want our insights to land, we have to rethink how we deliver them.</p><p>In an era where everyone has access to information, having a strong point of view — and a compelling story to back it up — is the ultimate premium.</p><p><strong>The Evolution</strong></p><p>We are no longer just objective observers handing over raw data. We are internal content creators. The UX researcher of tomorrow engineers their deliverables to be highly consumable, ensuring insights are actually absorbed rather than filed away in a forgotten Google Drive folder.</p><blockquote><em>The value of research isn’t measured by the weight of the slide deck. It’s measured by how quickly and clearly stakeholders can grasp the story.</em></blockquote><p><strong>In Practice</strong></p><p>It’s time to officially retire the 50-page readout.</p><ul><li><strong>Adopt a “Key Questions” framework.</strong> During project kick-off, force alignment with your cross-functional partners to identify exactly four to six burning questions they need answered.</li><li><strong>Edit ruthlessly.</strong> When it’s time to share results, trim the fat so your report addresses <em>only</em> those specific questions.</li><li><strong>Show, don’t tell.</strong> Ditch the endless bullet points. Embed a crisp, two-minute video highlight reel of customers speaking directly to those core answers.</li><li><strong>Deliver speed.</strong> The result is a hyper-efficient, precise deliverable that gives your partners exactly what they need, faster than ever.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_DrHz6lePWDapI4CSWPFog.png" /><figcaption>Moving away from 50-page research report readouts to actionable, digestable and easy to follow formats</figcaption></figure><h3>3 . The Strategic Forecaster</h3><p>Inspired by <strong>Preeti Talwai, </strong>Staff UX Researcher, Google. Presentation titled Anticipatory research.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BuzOw7BYdDw-E6ILq-JnSg.png" /><figcaption>Preeti presenting ‘Anticipatory research’ at learners, research week</figcaption></figure><p>Preeti focused on the critical need for “anticipatory research.” As AI rapidly accelerates product development cycles, researchers are increasingly being asked to look around corners. We have to spot the shifts before they happen.</p><p>Because AI gives us easier, faster access to macro-level data and shifting behavioral trends, we no longer have to wait for a product manager to hand us a specific feature to test.</p><p><strong>The Evolution</strong></p><p>We need to learn how to predict the rainfall before it actually rains. This is the leap from tactical order-taker to strategic business partner. Instead of just reacting to the immediate roadmap, we use our deep understanding of human behavior to proactively shape what goes onto that roadmap in the first place.</p><blockquote><em>Anticipatory research means answering the questions your product team doesn’t even know they need to ask yet.</em></blockquote><p><strong>In Practice</strong></p><p>Imagine your company is planning to integrate a generative AI chatbot into your product next quarter.</p><ul><li><strong>Stop waiting for prototypes.</strong> A reactive researcher waits for the build to finish, then runs a standard test to see if the UI buttons make sense.</li><li><strong>Forecast the cultural shift.</strong> Proactively launch a study to uncover how your target users’ trust in AI is shifting based on recent news cycles.</li><li><strong>Build the framework early.</strong> Present a comprehensive “Trust and Safety” framework to your product and engineering leads before a single line of code is written.</li><li><strong>Guide the strategy.</strong> Shape the core direction of the feature itself, rather than just polishing the interface at the very end.</li></ul><h3>4. The Model Evaluator</h3><p>Inspired by Giuliano Morse (Principal UX Researcher, Meta) &amp; Chuck Kong (Principal UX Researcher, Microsoft AI). Panel discussion on User evals.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*py5ix_-D6Kq4PvpoDfkQ1A.png" /><figcaption>Giuliano and Chuck in a panel discussion about ‘UX Evals of AI models’ at learners, research week</figcaption></figure><p>Giuliano and Chuck addressed one of the most fascinating “wild west” scenarios in modern tech. As companies rush to deploy generative models and AI features, a massive research challenge has emerged: how do you evaluate a tool when every single user outcome is completely unique and unpredictable?</p><p>Traditional usability testing metrics — like time-on-task, error rates, or simple click-path completion — start to break down when the interface is generating open-ended content on the fly. Evaluating AI requires a completely new playbook. It forces us to focus on the quality, safety, and relevance of the output, rather than just the usability of the buttons around it.</p><p><strong>The Evolution</strong></p><p>UXR is expanding into a highly specialized, technical frontier. We are no longer just evaluating the static UI wrappers that house the technology; we are stepping in to evaluate the actual cognitive behavior and quality of the underlying AI models.</p><blockquote><em>We aren’t just testing whether a user can find the chat box. We are testing whether the AI inside that box is helpful, harmless, and aligned with human expectations.</em></blockquote><p><strong>In Practice</strong></p><p>You are testing a brand-new AI feature designed to summarize long, complex email threads.</p><ul><li><strong>Look past the interface.</strong> A traditional approach simply observes if a user can locate and click the “Summarize” button. You need to go deeper.</li><li><strong>Grade the output.</strong> Build a rigorous rubric. Bring in participants to evaluate the AI’s actual summaries for tone, factual accuracy, and missing context.</li><li><strong>Hunt for edge cases.</strong> Actively test how the model handles a highly sarcastic email or a sensitive HR dispute.</li><li><strong>Stress-test the logic.</strong> Evaluate the underlying cognitive behavior of the AI right alongside the user experience.</li></ul><figure><img alt="Image comparing an AI evaluating AI models vs UXR evaluating AI models" src="https://cdn-images-1.medium.com/max/1024/1*oAB0xMZwcdvEh4u2JU63zw.png" /><figcaption>Image comparing an AI evaluating AI models vs UXR evaluating AI models</figcaption></figure><h3>In conclusion</h3><p>It’s easy to look at the rapid advancement of AI, scroll through tech feeds, and feel a lingering sense of existential dread. But if my time at Learners Research Week proved anything, it’s that UX research isn’t dying — it’s leveling up.</p><p>The tasks that used to bog us down — transcribing endless interviews, manually coding hours of video, or fighting to get stakeholders to read dense PDFs — are being automated. This isn’t a loss of our core duties. It’s an unburdening.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pMTjIO3bMXbqUVs9IjOirQ.png" /></figure><p>By leaning into these evolving roles — <strong>the Holistic Synthesizer, the Insight Content Creator, the Strategic Forecaster, and the Model Evaluator </strong>— we are stepping into the most impactful era of our profession.</p><p>The doomsday clock isn’t ticking for UX researchers. The job description has just been rewritten. Now, it’s up to us to step up and own it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f59723ed2843" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[20 questions to help you prepare for your next UX Research Interview]]></title>
            <link>https://medium.com/@sneha_33328/20-questions-to-help-you-prepare-for-your-next-ux-research-interview-b4dc5785b65d?source=rss-db797fe9c4d7------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4dc5785b65d</guid>
            <category><![CDATA[tech-interview]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[ux-research]]></category>
            <category><![CDATA[user-experience-research]]></category>
            <dc:creator><![CDATA[Sneha Gokhale]]></dc:creator>
            <pubDate>Wed, 09 Mar 2022 21:16:09 GMT</pubDate>
            <atom:updated>2022-05-17T19:50:23.038Z</atom:updated>
            <content:encoded><![CDATA[<p>A curated list of questions from a fellow UX researcher and designer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*o_s3Ty2e91U2aO1T" /><figcaption>Photo by <a href="https://unsplash.com/@clemono2?utm_source=medium&amp;utm_medium=referral">Clem Onojeghuo</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In 2020 I decided to transition from an interaction design role to a UX research role. Even though I had gained design research experience in India, it still wasn’t easy to get my foot in the door of the UX research industry in the Bay Area. Not only is the industry fairly competitive, my interview skills were also a bit rusty.</p><p>When preparing for my interviews, I could only find <a href="https://medium.com/@eleonorazucconi/46-interview-questions-for-user-experience-researchers-at-google-amazon-microsoft-and-facebook-c582827267b9">a list</a> of questions that UX research candidates get asked by big tech companies. This list was helpful but very specific to large organizations. As a result, the recruiters from the companies I was interviewing for (small to mid-size) became my main source of information. And even though the information the recruiters provided was helpful it wasn’t enough. I did not feel confident to face the actual interviewers with whom I would interact during the 3–4 hour-long onsite interviews.</p><p>So I hacked together my own list of interview questions based on: “the list” from big tech companies, my own experience of interviewing, tons of medium articles, Glassdoor reviews, LinkedIn profiles, etc. Since I was greatly thankful to everyone who had taken the time to share their experience online I decided that I would do the same once I successfully got through mine. So here it goes.</p><h4><strong>Your Unique Process of Conducting UX Research</strong></h4><ol><li>What process/methods do you use to collect data during the inquiry phase?</li><li>How do you learn and grow as a researcher? What resources do you use to keep up with the latest processes and best practices?</li><li>How do you communicate the value of design research to decision-makers who do not have a UX design or UX research background?</li><li>How would you communicate your findings to different stakeholders?</li></ol><h4><strong>Your Experience as a UX Researcher</strong></h4><ol><li>What 3 principles of IXD and UXR have you learned while on the job and found to be useful.</li><li>Share an example of when you were surprised by your research findings.</li><li>What was the most challenging project you’ve worked on as a researcher?</li><li>What accordingly to you is the most challenging part of being a design researcher?</li><li>What industries have you conducted UX research for? Do you see any common trends or have any common learnings?</li></ol><h4><strong>Your Expertise as a UX Researcher</strong></h4><ol><li>What part of the design research process do you like the most and feel the most confident about?</li><li>What is your favorite methodology and why?</li><li>What are your top 2 strengths as a researcher and what are your weaknesses?</li><li>Do you feel comfortable in teaching research methodologies and techniques to other team members?</li></ol><h4><strong>The Company and Role-specific questions</strong></h4><ol><li>What got you interested in this role? Why do you want to transition from UX design to UX research?</li><li>The project manager has shared a new research requirement with you?(share’s a company-specific requirement.) Describe how you would begin creating a plan for conducting UX research.</li><li>How comfortable are you with remote collaboration? Did you have to work remotely in your current/previous jobs?</li></ol><h4><strong>Future Scenario-based questions</strong></h4><ol><li>If you share your research findings with the team and the product designer doesn’t take most of the suggested design principles into account and creates designs that are directly sent to the product manager/lead designer for approval. How would you resolve this situation?</li><li>When you start a research project with a hypothesis but the findings turn out to be diametrically opposite changing the course of the project to a substantial amount. How do you convince the team and project leads to make those changes?</li><li>While creating a new feature/product the team does not have resources allocated to conduct research what would you recommend as a plan of action to avoid failures post shipping?</li><li>When faced with multiple tasks how do you balance your time to deliver the best possible outcomes/how do you prioritize between tasks?</li></ol><blockquote>When it comes to preparing your answers to these questions, I have gotten the sense that interviewers love real-life experiences and stories. , If you have previous research or design experience, keep some of those stories handy. It lets the team know that you have relevant experience and are capable of handling difficult situations in your own unique way. You might find it helpful to scan through your previous work and research reports. Or think of various moments in your career where you felt challenged and how you managed to find a solution. Most importantly though, trust your instincts and stay confident, if the job is right for you, you’ll be able to crack it.</blockquote><p>Hopefully, these questions can serve as a helpful reference point for you. Please don’t hesitate to leave a comment with additional questions or suggestions. I would definitely appreciate it and I am confident that the rest of the UX Research community would too. In any case, I wish you all the best with your upcoming interview!</p><p>If you’d like to learn more UX research interviews, check out these articles:</p><ul><li><a href="https://medium.com/@eleonorazucconi/46-interview-questions-for-user-experience-researchers-at-google-amazon-microsoft-and-facebook-c582827267b9">46 Interview Questions for User Experience Researchers at Google, Amazon, Microsoft and Facebook</a></li><li><a href="https://careerfoundry.com/en/blog/ux-design/ux-researcher-interview-questions-toolkit/">Interview Toolkit: Top 5 UX Research Questions to Prepare For</a></li><li><a href="https://medium.com/@claudianatasia/cracking-the-ux-research-interview-3bb7a844f3ef">Cracking The UX Research Interview</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4dc5785b65d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>