I was speaking with a designer recently who had been interviewing for a while.
Not struggling to get interviews o. He was getting them.
Sometimes second stage. Sometimes final stage.
But somehow, the offer was not coming through. So naturally, he thought the problem was his accent.
He had even started trying to sound more American with one fake borrowed accent.
I asked him to walk me through one of his projects like we were actually in an interview.
His work was really good, I’m not even going to deny that part. Very good actually.
But about 10 minutes into the call, I could already see the problem.
Every response he gave me was about what he made.
“We designed this.” “We added this.” “We created this flow.”
But almost nothing about why. Nothing really about the role he played.
Nothing about tough decisions he had to make.
Some of the stories were not even connecting properly. I don’t even know if it was the accent causing that particular one 😂
So I started asking him some annoying questions.
Why did you choose this direction?
Was there ever a time everyone disagreed with your design decision? If yes, how did you handle it?
When a stakeholder disagrees with your work, how do you convince them?
Did users actually ask for this?
What did engineering push back on?
What did the business want?
What did you have to compromise on?
That was where things started getting uncomfortable.
I could tell he knew what he wanted to say. But he could not articulate it properly.
And unfortunately, these guys don’t really care that you “know it in your head.” There are too many options out there for them to choose from.
And I think this is where a lot of designers misunderstand interviews.
By the time somebody has invited you to speak with them, they can already see that you can design. Your portfolio did that part.
Now they are trying to figure out what it would actually feel like to work with you.
Can you explain a decision without going round in circles?
Can you politely disagree with an opinion that does not sit well with you?
Can you understand when the business needs something different from what you originally designed?
Can you work with engineers when the perfect solution is not possible for them to build?
Can you look at a messy problem and bring some clarity to it?
That is the part most hiring managers find interesting. Sometimes the screen is the easy part.
The real work might be everything that happens before that screen gets approved.
Anyway, by the end of our conversation, I told him not to touch his accent again 😂
Leave the accent alone.
Learn how to communicate your thought process properly. Practice talking about the work. Not presenting it. Talking about it.
You know that way you discuss your ex with someone who actually cares to listen?
The way you suddenly remember every detail? 😂😂
Eheee.
Just like that.
That is how you should be able to tell the story behind your experience. All those messy situations. The back and forth.
And yes, it might even require you to practice in the mirror. As stupid as that sounds, it works.
If this helped you, just tap the follow button gently ooo and repost this for someone preparing for their next interview.
And if you have an interview strategy that has worked for you, abeg share it. Somebody might need it.
Design is one of the few professions where almost everybody has an opinion.
I have met someone, a designer who had a bit of a concern.
She had mentioned that "Every time she present her work, everybody wants something different. By the end of every meeting, it always feel like she does not know what she is doing."
Truth be told a lot of designers have been there.
Most feedback comes out genuine.
Some is even based on experience.
While some is simply their personal preference that wears feedback as bongo trousers.
It gets even harder when you are new to the company. You will want to prove yourself, thats how you will fall into the trap of trying to satisfy everyone.
Come.. Just come closer, let me tell you something.
Don't start what you cannot finish.
If one person wants the button full corner radius, and another person wants the corner radius set at 10px, and someone else wants it without any at all, you will just find yourself making changes without making the product any better.
Stop asking, "Which idea do people like?"
Start asking, "What problem are we trying to solve?"
Every piece of feedback has to answer that question.
If it solves the problem, it is worth exploring.
If it is only a preference, or belongs to the category of folks that says "my wife thinks the button should fly" acknowledge it and move on.
Just accept that you CANNOT please everyone.
You become better by learning which opinions deserve your attention. Enjoy your day.
I have been thinking about whether to comment on this. Not clear if Gal is serious, rage baiting, etc. Whatever the case, it has spread enough in the design community that I want to share some thoughts.
The psychological journey people go through with AI is quite fascinating to me. A new model launches, people think the world has changed, they sometimes have an existential crisis, then they play with the model, they understand its strengths and limitations and then they settle down. A few weeks later, the cycle repeats.
On top of this, even before AI, designers have often shown insecurity and imposter syndrome. There are probably many reasons for this. First, before ~2010 design wasn't valued by the tech industry in the way it is today. Second, the people attracted to working in the field of design are often very open to new ideas and have high empathy. Third, there is no "one path" to working as a designer and designer backgrounds are often pretty random.
Ironically, despite the insecurity + imposter syndrome so many designers feel, design is more important than ever. I truly believe this. And yes, I have an incentive to believe this. But just think about it... the logic couldn't be more clear. More design is entering the world, the attention economy is real and therefore creativity / design / point of view is how you will stand out. Your brand, marketing, product design, moments of delight and overall customer journey must be excellent. Some companies already get this and are fighting wild battles over design talent. Other companies are still figuring it out. Everyone will get there and it will be obvious in retrospect.
This isn't a new trend with AI. It is a trend that we've seen over the last decade. Designers used to complain about not having a seat at the table. Now designers have a seat at the table. And many of the businesses I speak with are pulling from their design bench when looking for new leaders for their business... they know that design thinking and the design process is what they need to adopt everywhere to win.
I'm not saying that every stakeholder gets it. But so many are trying to learn right now. Designers need to do more than create great work, they have to spend a lot more effort educating.
Showing work can also trigger anxiety. Sometimes the best solution to a design challenge is the first thing you think of. And other times you have to explore for quite a long time to come up with something great. Inputs to a design process might include things that feel like traditional office work and are easy to point to... reading docs, talking with teammates, formal research, etc. Inputs might also include a walk in the park, an interesting dream you had the night before, a good song you listened to on the radio during your commute, a painting from the 1800's or all sorts of other cultural / emotional input.
In summary, I've never been more confident in the role of design and impact design can have. I wish designers felt the same confidence. This is the moment to be more bold, to take more creative risk, to double down on the power of design. Everyone is on their own journey, and there are lots of fascinating ways to move through life, so if Gal is serious about "quitting design" then I wish him the best in his adventures ahead. But I hope if others follow they do it because there are other things they are so excited about spending time on vs fear of AI.
I have seen developers vibecode a product. I have seen designers vibecode a product.
I recommend that more designers vibecode products, as you have a better advantage because of your taste.
🚨 The creator of Claude Code just shared a full walkthrough on how to actually use it the right way.
30 minutes. Free. Straight from the person who built it.
Watch the workshop and save it for later.
You’ll likely get more practical value from this than from most expensive coding courses online.
Most people are only scratching the surface of what Claude Code can do.
Then check out the guide below.
Instead of learning how to write code
- Learn why an app needs a websocket
- Understand polling
- Know what caching is
- Know why & when to optimize DB calls
- Know when it should be a monolith or when MVC is best
- Know how to correct and balance your CSS
- know how to structure your dashboard page architecture. are you loading pages or you're routing views
There are lots of things you should shift your learning focus to know that is not writing code
Should you learn how to read code at the basic level? Yes.
A reality many designers only discover after joining a startup 👇
You’re not hired to design landing pages.
You’re hired to design tools.
You’re hired to design tools.
📌 Internal tools.
📌 Operational tools.
📌 Data tools.
📌 Admin dashboards.
You’re designing for:
📌 Speed over beauty
📌 Accuracy over delight
📌 Scale over visual flair
This kind of work forces you to think beyond screens to:
📌 How does data flow?
📌 Where do errors happen?
📌 What decisions are users making under pressure?