The Interview Questions I Couldn’t Answer Changed Me
There was a time when I walked out of interviews thinking more about the questions I couldn’t answer than the ones I did.
Recently, I started giving interviews for UX design internship opportunities to grow as a designer. I was excited because I finally had the chance to showcase everything I had been learning over the past few months. I had spent countless hours working on projects, refining my portfolio, completing design assignments, and trying to improve every single day. I thought I was prepared. But every interview I attended made me realize that preparation and readiness are two very different things.
With every interview, I discovered a new area where I needed to improve, not only as a designer but also as a person. Every conversation made me realize that there was another mountain waiting behind the one I had just climbed. Whenever I felt like I had finally reached a point where I understood design a little better, another interview would introduce me to concepts I hadn’t even thought about before. At first, that realization made me anxious. It made me question whether I was actually progressing or simply convincing myself that I was.
There were moments when I genuinely felt left behind. Looking at other designers online, seeing experienced professionals talk confidently about research, product thinking, business strategy, and user behavior made me wonder if I was learning fast enough. Sometimes, I questioned whether I was good enough to become a UX designer at all. Those thoughts would stay with me long after the interview had ended. But instead of letting them stop me, I tried to focus on learning from every experience, even though it wasn’t always easy.
The first interview challenged me in a way I wasn’t expecting. I walked into it thinking I would mostly be discussing my portfolio, my UI decisions, and the projects I had worked on. I had prepared myself to explain the interfaces I had designed and the reasoning behind some of my visual decisions. Instead, the interview quickly shifted toward something much deeper.
The questions were no longer about how my screens looked. They were about how I thought.
I was asked to explain my design process from the very beginning. How would I approach the discovery phase? How would I validate whether a problem actually existed before trying to solve it? If I had limited resources, how would I conduct user research? What hypothesis would I create? How would I validate that hypothesis? What role would AI play throughout my design process? How would I measure whether my solution was successful? And perhaps the most difficult question of all wasn’t any single question; it was having to explain the reasoning behind every design decision I had made.
I answered every question as honestly as I could. I explained my previous projects and the work that I had done. I talked about research methods that I knew and how I usually approached solving problems. But while I was speaking, I slowly realized something that I had never noticed before.
My answers were based more on intuition than on a structured process.
I knew what I had done during my assignment, but I struggled to explain why I had done it in a way that felt systematic. I discussed research, but I couldn’t clearly explain how I would plan the discovery phase from start to finish. When asked about creating and validating hypotheses, I found myself searching for the right words. I mentioned AI because I had started using it in my workflow, but I hadn’t yet thought about how it could be used as a research partner to challenge assumptions, generate hypotheses, or validate ideas.
When that interview ended, I didn’t immediately think about whether I would get selected or rejected. Instead, I kept replaying every unanswered question in my mind. Those questions followed me home. They stayed with me for days. The rejection certainly hurt, but what stayed with me wasn’t the rejection itself. It was the realization that companies weren’t only evaluating my ability to design beautiful interfaces. They wanted to understand how I discovered problems, how I validated assumptions, and how I connected research to every design decision.
That interview completely changed the way I looked at product design.
I realized that product design begins long before wireframes. Discovery is just as important as the final interface. Every design decision should be backed by evidence instead of assumptions. Confidence doesn’t come from speaking louder; it comes from understanding the reasoning behind what you’re saying. Most importantly, I realized that preparation isn’t about memorizing answers. It’s about understanding the fundamentals deeply enough that you can explain your thinking clearly.
After that experience, I didn’t stop applying. Instead, I went back to learning. I started paying much more attention to the discovery phase. I began asking “why” much more often than “how.” Looking back now, I don’t think that rejection was the end of anything. It was simply the point where my understanding of design started changing.
A little later, I had another interview for a different internship opportunity.
Naturally, I carried all the anxiety from my previous interview into this one. I was worried that I would freeze again or fail to explain my thinking. But this time, something felt different. I had spent time reflecting on my previous mistakes instead of trying to forget them.
The interview started with the usual introduction and a walkthrough of my portfolio. Then I was asked to explain one of my design assignments in detail. Instead of rushing to show the final screens, I focused on explaining the problem, the research, the users, the challenges I faced, and why I made certain design decisions. We discussed the reasoning behind the assignment, how I approached solving user problems, how I collaborated with developers, and what I had learned throughout the project.
For the first time, I felt like I wasn’t simply presenting screens.
I was telling the story behind them.
Get Deepak Nath’s stories in your inbox
Join Medium for free to get updates from this writer.
That didn’t mean I answered everything perfectly. I was still nervous. There were moments where I questioned myself while speaking. But compared to my previous interview, I noticed something had changed. I wasn’t trying to sound like I knew everything anymore. I was simply trying to explain my thinking as honestly and clearly as I could.
A few days later, I received an offer.
I remember staring at the email for a while because I genuinely wasn’t expecting it. After spending so much time doubting myself, it felt strange to see someone else believe in my abilities before I fully believed in them myself.
In the end, I decided not to accept the offer. It wasn’t because I didn’t appreciate the opportunity. In fact, declining it was one of the most difficult career decisions I have made so far. At that time, I was still completing my graduation, relocation wasn’t practical, and I wanted to choose an opportunity that aligned better with my long-term goals and current circumstances. It wasn’t an easy decision, but it felt like the right one after carefully thinking through my priorities.
Looking back now, I find it interesting that these two interviews taught me completely different lessons.
One interview showed me everything I didn’t know.
The other showed me how much I had already learned.
One made me realize that I had been thinking too much like a UI designer and not enough like a product designer. The other reminded me that preparation, reflection, and understanding the product deeply can completely change the way you communicate your work. Together, they taught me that presenting beautiful screens is only a small part of being a designer. Explaining the thinking behind those screens is just as important.
There is one lesson, however, that both interviews had in common.
Communication.
Before these experiences, I believed that becoming a better designer meant improving my visual skills, learning more tools, creating better prototypes, or producing cleaner interfaces. I rarely thought about communication as a design skill. But during those interviews, I realized that even the strongest idea can lose its impact if you cannot explain it clearly. Interviewers weren’t just evaluating my designs; they were trying to understand how I think. They wanted to see my reasoning, my decision-making process, and the logic that connected one step to the next.
I used to think communication was something you learned with time.
Perhaps the biggest realization wasn’t about product design or interviews at all.
It was about me.
I realized that I judge myself on an incredibly high scale. After every interview, I focused only on the questions I struggled with. I ignored the answers I gave well, the progress I had made, and the fact that I was improving with every conversation. In many ways, that self-criticism pushed me to learn more. It stopped me from becoming comfortable too early. But I also learned that if I only focus on my shortcomings, I never allow myself to acknowledge how far I’ve come.
Today, I still don’t remember every answer I gave during those interviews.
But I remember almost every question I couldn’t answer.
Not because those questions embarrassed me.
But because they became the starting point for everything, I decided to learn next.
Maybe interviews aren’t just about proving what you know.
Maybe they’re also about discovering what you still have left to learn.
