Most candidates finish an interview and send a simple “Thank you for your time.” And then they wait. But recently, one of my UX students did something different. After her final round, she didn’t send a thank-you note. She sent a 90-day onboarding plan . A few hours later, the hiring manager replied personally: “I appreciate you taking time to do that,” and invited her to discuss offer details. This is what most candidates miss. The interview does not end when the conversatio

Recently, I’ve been talking with several interviewer friends, and one topic keeps coming up again and again: AI. But not just in a general sense. More specifically, how to tell whether a candidate is truly “AI-native.” At the same time, many of my students have been sharing similar experiences. Whether they are applying for design or research roles, they are almost always asked some version of: “How do you leverage AI in your work?” And simply saying “I use ChatGPT for resear

“Do you have any questions for me?” Every interview includes this final segment. And most candidates ask something. But very few use it well. What you may not realize is that this moment is not a formality. It is part of the evaluation. And in competitive hiring environments, it can quietly decide between two equally strong candidates. I’ve seen this happen firsthand. In a previous role, I helped with hiring for a product position. After all the interviews, the team gathered

Many candidates make the same mistake during a UX case presentation. When they reach the solution section, they start walking through screens one by one, explaining features like: “This button takes you to the details page.” “You can filter by price and category.” “You can favorite an item here.” While this might feel like a clear explanation, interviewers often lose interest very quickly. The Core Problem: You’re Presenting Like an Internal Demo This approach is called a fea

Many people feel the same anxiety when preparing case studies. Their projects feel incomplete. The logic feels messy. Some steps were skipped. So they hesitate to use them, or they struggle to explain them in a convincing way. This is especially common if you have worked in startups or fast-moving teams. You might think: “We didn’t have time for full user research” “The PM gave direction and we just executed” “We didn’t even run proper usability testing after launch” And then

Most candidates struggle with the same problem during product or design interviews. They start an app critique and run out of things to say within ten minutes. Then they wonder, how is anyone supposed to talk about an app for forty five minutes? The truth is, the actual critique only takes about twenty minutes. What fills the rest of the time is your thinking, your perspective, your storytelling, and your ability to connect product decisions to user needs and business outcome

Many candidates make the same mistake in interviews: they take an internal project presentation and deliver it almost unchanged. While your original presentation may work well within the company, it often falls flat in an interview setting. The result tends to feel like a status update rather than a compelling narrative. The underlying issue is that these two scenarios serve entirely different purposes. In internal presentations, your audience already understands the busin

Most of you guys are familiar with Amazon’s STAR framework for behavioral interview questions - Situation, Task, Action, Result . STAR ...