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

Most designers don’t struggle because of their design skills. They struggle because they don’t know how to communicate with people who don’t speak design. Executives don’t think in Figma files or visual hierarchy. They think in revenue, efficiency, risk, and outcomes. If you want your work to land, you need to translate design into something they care about. Here are 9 principles that will change how you present your work. 1. Speak Business, Not Design ❌ Saying “we improved u

“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

Recently, several candidates told me the same story during their interview debriefs. The interviewer casually asked, “What’s your favorite app?” And before they realized it, the conversation turned into a 10-minute deep dive. No one told them there would be an app critique. Not HR. Not the interview prep materials. But here is the truth. Most companies will not explicitly label a round as “App Critique.” And many interviewers will not frame it that way either. Instead, they a

Most candidates misunderstand the role of recruiters. They assume that once they receive an interview invitation, they should minimize contact, avoid asking too many questions, and “not bother” HR. But the reality is the opposite. The moment you enter the interview process, you are no longer an interruption. You become part of their responsibility. Recruiters are measured by one core goal: helping hiring managers find the right candidate. That also includes helping strong can

Ten years ago, I graduated with an HCI degree and landed a full-time offer in Los Angeles after casually applying for a month. Today, many candidates from top schools, with strong internships and polished portfolios, struggle to even get interviews. This is not because you are not good enough. The market has changed. The bar is higher, competition is stronger, and hiring has become much more selective. In this environment, being good is no longer enough. What you need is stra

Job searching can feel exhausting. You revise your resume over and over again. You go through rounds of interviews. Sometimes you even get close, only to be rejected, or worse, have an offer taken away. Every day, you push yourself to keep going. But the more you try, the more lost you may start to feel. If this sounds familiar, I want to tell you something simple. You are not alone. And in today’s environment, getting a job is no longer just a test of your skills. It is also

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

As our society undergoes rapid technological transformation, working at a startup has become part of many people’s journey. Yet, startup experience comes with both strengths and weaknesses. On the positive side, you move fast, take end to end ownership, and can turn ideas into execution quickly. You are also used to working under pressure and navigating ambiguity. On the downside, processes are often unstructured, systems are not mature, and decisions are rarely driven by str

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 of my clients ask me the same question: When do you get into the weeds, and when do you stay vague? Zoom in, or out? It sounds simple. But it's one of the hardest things to get right in interview storytelling , because the mistake goes both ways - Some people drown the interviewer in details when a high-level answer was all that was needed. Others stay so generic when specifics were called for that they sound like every other candidate. The fix is one principle: Detail i

When a company does layoffs, the "kill list" isn't built by auditing who worked the hardest. It's built from impressions — what your skip-level remembers about you, what your cross-functional partners would say if asked, how you show up in people's mental models of the team. The same dynamic applies to intern conversions and promotions. The decision-maker isn't reviewing your Figma file count or code base. They're going off their perception of your skills, your impact, and yo

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

Starting outreach on LinkedIn or email is already hard.  What’s even harder is sending a message, getting no reply, and then wondering what to do next.  “Should I follow up? Did they ignore me on purpose? Am I being annoying??” If this feels familiar, you’re not alone. I’ve been there too, many times...   In reality, no response is not rejection. It is simply how networking works. Why No One Replies (And Why It’s Normal) Many people assume that silence means something is wron

Starting a new job is exciting, but it can also feel overwhelming. Especially if you’ve just joined a larger organization, the volume of information, stakeholders, and expectations can hit all at once. Many new hires feel pressure to prove themselves quickly and rush into output. But in reality, the fastest way to grow is rarely by moving fast in the beginning.  Start by Building Your Foundation System Before focusing on output, make sure your setup is stable. This includes

I didn’t wake up one day and decide to become a coach. For years, I was just doing my job: UX research, product strategy, mentoring junior UXers & college students, sitting in hiring committees, interviewing candidates. But a pattern kept showing up. Some of the most capable, thoughtful product builders I met were the ones struggling the most to get offers, recognition, or promotions. That’s when something clicked. Doing the Work ≠ Getting the Outcome We like to believe that

One of the most common frustrations I hear from candidates is this: “My best project is under NDA, so I can’t include it in my portfolio.” But in most cases, this conclusion is reached too quickly. 🤔 Why? An NDA doesn’t mean you can’t tell your story. It just means you need to be more intentional about how  you tell it. In reality, most NDAs are more nuanced. So understanding the boundary is the first step. They typically restrict specific confidential data, internal metrics

If there’s one thing that takes down even strong designers in a whiteboard challenge, it’s time. Everyone walks in with good intentions — “I’ll show two design directions and discuss trade-offs.” But reality hits fast: 45 minutes later, they’ve barely finished one version, and the conversation feels rushed. I’ve coached over 200 designers through whiteboard mock sessions, and more than half of them stumbled not because of weak ideas, but because they ran out of time. The good