I recently had a 30-minute interview where I presented my design work. The session began with me walking through my portfolio, focusing on key projects that showcased my research process, design thinking, and the outcomes I delivered. I aimed to highlight both my problem-solving approach and the real-world impact of my work. After the presentation, the interviewers asked me several questions about the projects I shared. Their questions were mostly centered around the design decisions I made, my role within the team, and the results of my work. For example, they asked how I balanced user needs with business goals in one of my projects and how I collaborated with engineers to implement specific features. I appreciated these questions because they gave me a chance to explain my thought process and how I approach design challenges. However, I left the interview feeling a bit disappointed. I had expected more in-depth questions or a deeper conversation about design strategy, user research methodologies, or even challenges I faced during my projects. Since the position I applied for focuses on design strategy and research, I was hoping for questions that would allow me to dive into those areas more thoroughly. I wanted to talk about how I identified user needs, how I translated research insights into actionable design solutions, and how I measured the success of those solutions. While I understand that a 30-minute interview can be limited in scope, I was still hoping for more engagement on those aspects. That said, I appreciated the opportunity to share my work and I remain interested in the role. I’m hoping that if I move to the next round, there will be more space for deeper discussions about design strategy and research impact.

The recruiter was kind. It was a phone interview. The interview felt more like a conversation. Research the company's subsidiaries. Research the 20 isms and which ones relate to you.