Did the LinkedIn product designer loop last month for a role on the job seeker experience team. Eight years in, ex-agency, have been through about a dozen design interviews at this point. Writing this because design interview advice is usually generic and LinkedIn's portfolio review has some quirks worth knowing.
Process: a recruiter screen, a portfolio review, then a four-round onsite.
Portfolio review (45 min): One interviewer, usually a senior designer on the team. They told me upfront: pick 1-2 cases you want to go deep on, we're not doing a gallery tour. I picked two: a 0-to-1 feature for a B2B product and a redesign of a complex information architecture. They asked sharp questions. Not "why did you choose blue" but "what data did you have before you committed to this direction" and "what would you do differently now." They care about your thinking process and your relationship with ambiguity. If your case studies are all clean success stories with no honest reflection on failures, that's a yellow flag for them.
Onsite:
Round 1, design challenge: 30-minute prompt given in advance, present your thinking in the interview. My prompt was: design a feature to help LinkedIn users who've been laid off. I had 48 hours. They're not looking for pixel-perfect mocks. They're looking for how you frame the problem, what research questions you'd ask, what constraints you acknowledge, and whether you can defend tradeoffs in the design.
Round 2, cross-functional collaboration: a round with a PM and an engineer. They simulate a real situation: PM wants X, eng says X is expensive, what do you do? They're checking whether you can facilitate and move things forward without being a pushover or being a roadblock.
Round 3, behavioral: the same STAR method questions you'd get anywhere. Tell me about a time you advocated for the user when business goals pushed the other way. Tell me about a time a design shipped that you weren't proud of. Have real answers, not platitudes.
Round 4, hiring manager: cultural fit, team context, growth conversation. They told me a lot about the team's current roadmap. Pay attention, you'll be asked what you'd prioritize.
Leveling: I came in hoping for senior (IC5 equivalent), got a strong offer at IC4. The feedback was around scope of ownership in my cases, which I think was fair. If you're gunning for senior, make sure your cases show you owning a problem end-to-end including research and outcomes, not just execution.