Katkat

real interview stories, told over a cup of tea ♡

TSMC Interview Experiences

3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.

3935
Experiences
857
Companies
532
Offers

16 results

  • The process felt organized and professional from start to finish. I began with a conversation about my background, experience, and qualifications, then the questions shifted to the role, my technical knowledge, and how I approach problem-solving. They also left time for my questions and gave me an overview of what the position would involve. What stood out was how complete the interview felt. It…

  • I had two video-call rounds. The first was a one-on-one with the hiring manager for about an hour. The second was also about an hour and included the hiring manager and two process engineers. Both rounds asked specific questions about handling conflict and operational issues at work. They covered high workloads and efficient task management, including how I communicate, prioritize, and keep work…

  • My process had two rounds. The first began with an introduction, then moved to behavioral questions about a time I disagreed with my boss, my most difficult project, and a failure I had handled. They asked a lot of follow-ups to what I said. It felt less like working through a checklist and more like they were trying to understand how I think. The second round stayed in that same territory. It wa…

  • TSMC Software Engineer Interview Experience: panel interview and online assessmentTSMC · Software Engineer · Online Assessment · Aug 2026

    I had a panel interview with three people: a software engineer, a DevOps specialist, and an HR representative. The questions were mostly behavioral and situational, and the tone was standard and straightforward. There was also an online assessment. I did not perform as well on that part as I hoped, which made the overall experience more stressful than the interviews themselves. Despite the mix of…

  • My first round began with a small panel of three to four people. There was a quick assessment segment of about fifteen minutes, then the session was supposed to shift to a longer interview with a similar panel and the hiring manager. The timing became strange. When I left, I was still waiting for the interview to happen and had not heard anything back. The setup sounded normal on paper, with pane…

  • I went through a tight panel interview with three employees. After a quick discussion of my background and projects, the conversation turned to semiconductors: what different functions were and how the pieces fit together. They then reviewed my resume in a more direct, detail-oriented way and said they would follow up soon. It felt focused. They were not only asking generic career questions. Ther…

  • The interview focused on my background, technical experience, and how I approach problem solving. Much of the conversation covered engineering concepts and troubleshooting scenarios. The interviewers seemed interested in my reasoning, including the steps I would take to work through an issue. They also asked behavioral questions, so the evaluation was not only about knowing the material. It felt…

  • I had two interviews with managers and members of the team. The overall theme was behavioral, but there were also detailed dives into my resume. I had to explain what I had done and why, with enough detail that I could not rely on high-level descriptions. It felt as though they were connecting my previous roles to the work they expected me to do there. The pace stayed resume-driven, and I remembe…

  • I began with a self-introduction presentation of about ten minutes. My supervisor asked questions from what I presented and sometimes interrupted, so I had to respond in real time rather than treat the presentation as a formality. The team then explained its work and responsibilities, and I was able to ask questions. The process felt structured and respectful. Its main challenge was handling acti…

  • I spoke with team members in an interview that leaned on behavior and my resume rather than deep technical knowledge. They asked about my background, why I wanted TSMC and this role, teamwork and leadership, disagreement, and solving problems under pressure. A lot depended on explaining my past clearly, especially how I communicated and stayed effective when things were not smooth. The difficulty…

  • After applying to multiple positions, I received an interview invitation for a role different from the one I had originally targeted. Scheduling was fast: once I accepted, the interview was set for that same week. When I wrote my update, the interview had not happened yet. My experience was mostly about the quick turnaround. I did not yet know the difficulty or the specific questions, but the pro…

  • This was a low-pressure experience. I had two rounds within a week, and the whole process felt pretty relaxed. It was not especially technical. Most of the conversation was about my resume, projects, and previous work. There were not many deep technical probes, but I still needed to explain what I had done and how I described my contributions. The difficulty felt mild, and the conversational atmo…

  • TSMC Software Engineer interview: a short ML and semiconductor screenTSMC · Software Engineer · Technical Screen · Jul 2026

    My interview was mostly behavioral, with technical questions mixed in. They were particularly interested in ML and any semiconductor experience I had, so I had to connect my background to those areas. What surprised me was how short it was for the time booked: about 30 minutes. Even in that brief window, both a team manager and a director attended and asked questions. That raised the stakes becau…

  • On Microsoft Teams, the interview began with a short self-introduction and then turned to my projects and research. The interviewers asked for details, the specific problems I had encountered, and how I solved them. They were nice and respectful, and the process felt smooth. The conversation was friendly but still required enough clarity about my work to show how I approached challenges. The diff…

  • At the time of my update, I was only at the early stage. I had just received the interview invitation and was waiting to see how the experience would go. I was looking for guidance from people who had already been through the process because I did not yet have firsthand details. I could not judge the difficulty because I had not interviewed yet. I felt anticipatory and cautious, trying to get som…

  • The manager was very nice, and the interview matched what I expected for an engineering role. It lasted about an hour and covered role-related topics alongside my previous experience. The straightforward structure made it easier to focus on my background. The questions did not seem designed to be tricky. They were about matching my experience to what the team needed. It felt average in difficulty…