{"id":257639,"date":"2025-06-25T20:13:37","date_gmt":"2025-06-25T19:13:37","guid":{"rendered":"https:\/\/inkbotdesign.com\/?p=257639"},"modified":"2025-10-15T22:37:41","modified_gmt":"2025-10-15T21:37:41","slug":"how-to-impress-interviewers","status":"publish","type":"post","link":"https:\/\/inkbotdesign.com\/how-to-impress-interviewers\/","title":{"rendered":"You’re a Designer? Here’s How to Genuinely Impress Interviewers"},"content":{"rendered":"\n

You're a Designer? Here's How to Genuinely Impress Interviewers<\/strong><\/p>\n\n\n\n

\n

\u201cBe confident.\u201d \u201cDress for the job you want.\u201d \u201cGive a firm handshake.\u201d<\/p>\n<\/blockquote>\n\n\n\n

It\u2019s generic nonsense. It\u2019s a checklist for actors, not designers.<\/p>\n\n\n\n

You are not there to perform if you\u2019re a designer sitting in an interview. You are there to demonstrate how you think. The person across the table\u2014especially if they\u2019re an entrepreneur or a small business owner\u2014doesn\u2019t have time for a theatrical production. <\/p>\n\n\n\n

They have a problem. They\u2019re hoping you are the solution.<\/p>\n\n\n\n

Impressing them has very little to do with your winning personality<\/a>. It has everything to do with showing them you are a commercial-minded problem-solver who uses design<\/a> as a tool to get results.<\/p>\n\n\n\n

The Ground Zero Mistake: Believing Your Portfolio Speaks For Itself<\/h2>\n\n\n\n
\"Student<\/figure>\n\n\n\n

This is the most common, and most fatal, assumption designers make. They think the job is halfway done because the interviewer has seen their work.<\/p>\n\n\n\n

Wrong. Your portfolio<\/a> doesn't get you the job. It gets you the interview.<\/p>\n\n\n\n

It is the ticket that lets you into the stadium. It doesn't mean you know how to play the game. The assumption that \u201cthey\u2019ve seen my work, they get it\u201d is pure laziness.<\/p>\n\n\n\n

No one “gets it” until you explain it. More specifically, until you explain the thinking behind it<\/em>. An image of a logo tells me nothing. The story of how you arrived at that logo tells me everything.<\/p>\n\n\n\n

The “Portfolio Walkthrough” is a Relic of the Past<\/h3>\n\n\n\n

The most oversized bore in the world is the designer who treats their portfolio presentation like a holiday slideshow.<\/p>\n\n\n\n

\n

\u201c…and here\u2019s a website I did for a bakery. They wanted it to feel friendly. I used a warm colour palette.\u201d<\/p>\n<\/blockquote>\n\n\n\n

I\u2019m already checking my watch.<\/p>\n\n\n\n

This approach tells the interviewer you see your work as a collection of artefacts. An impressive candidate sees their work as a collection of solved problems. You must shift the entire conversation away from what<\/em> you did and focus entirely on why<\/em> and how<\/em> you did it.<\/p>\n\n\n\n

I once interviewed two designers back-to-back for a branding project. The first had a portfolio of slick, beautiful work for trendy startups. He walked me through it, piece by piece. It was fine. Polished. Forgettable.<\/p>\n\n\n\n

The second designer had three projects in her book. One was for a local plumber. She spent 15 minutes on it. She didn't start with the final logo. She began with the plumber's problem: he was losing bids to bigger companies, and his cheap-looking flyers made customers think he wasn't professional<\/a>. <\/p>\n\n\n\n

She showed us the mind maps, the rejected concepts, and the reasoning for the typeface\u2014it was chosen because it was legible on the side of a van from 50 feet away. She framed the entire project not as a design exercise, but as a mission to win the plumber more business.<\/p>\n\n\n\n

Guess who got the job?<\/p>\n\n\n\n

Rule #1: Frame Everything as a Problem, a Process, and a Result<\/h2>\n\n\n\n

If you remember nothing else, remember this. Every single piece you show must be presented through this lens. This is how you show an interviewer\u2014especially a business owner\u2014that you understand that design serves a commercial purpose.<\/p>\n\n\n\n

\"Deconstructing<\/figure>\n\n\n\n

Deconstructing Your Work: The PRE-P Framework<\/h3>\n\n\n\n

Use a simple structure for every case study<\/a> you discuss to avoid rambling. I call it PRE-P.<\/p>\n\n\n\n