READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 139 of 153
Interview experiences · Tripadvisor
Tripadvisor Software Engineer interview: coding, design, and culture rounds
The Tripadvisor loop began with HR covering my background and fit, with a few quick basic technical checks. The next technical screen included an easy LeetCode-style question, OOP and data-structure discussion, and an open-ended technical problem. Later coding rounds had two LeetCode questions and discussion of time and space complexity. The last technical round combined another LeetCode problem…
Interview experiences · Tripadvisor
Tripadvisor Software Engineer Interview Experience — A Four-Level Frontend OA Building a Blog App
A couple of days after the referral I got an AI HR call — 15 minutes answering some behavioral questions — and then I received two separate OA links. OA1 was a 15-minute, 50-question IQ-style test plus a company culture questionnaire. I didn't do that well on it — I only got through 45 of the 50 questions, and I'd estimate my accuracy was somewhere around 35-40%. OA2 was a frontend CodeSignal OA:…
Interview experiences · Tripadvisor
Tripadvisor Software Engineer interview: fizz buzz technical prompt
I had an easy, straightforward process. The meeting invitation arrived well before the interview, which gave me time to prepare, and communication about the process was clear. The technical questions were light rather than deep system questions. I was asked fizz buzz, passed it, and moved through the process. I still did not get an offer. Location: London, England. Overall feedback: positive. Off…
Interview experiences · TripStack
TripStack Software Engineer Interview Experience — Go-Heavy Screen and a Notepad Coding Round
I applied online to a platform that searches and sells connecting/interline flight tickets. After I applied, a recruiter reached out and said I'd need to do an OA first. Since the company uses Go, there was no other language option. The OA had two questions, one greedy and one DP, and the difficulty was unusually high for an OA. After I passed the OA, it took the recruiter two weeks to tell me I'…
Interview experiences · TrueFoundry
TrueFoundry Senior+ Software Engineer Interview Experience — VersionedArray, Interview-Scheduling APIs, and a Behavioral Round with the Chief
Round 1 Given a sequence of words written using a scrambled alphabet, determine whether the strings are sorted in ascending lexicographic order. The input is a string array (e.g. cat, bat, tab) plus a sorted char array giving the alphabet order (e.g. C, B, A, T). Return true or false. Design a VersionedArray class that implements the following interface: Init: pass in a length to initialize the a…
Interview experiences · TSMC
TSMC Customer Success Engineer interview: behavioral, teamwork, and leadership discussion
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…
Interview experiences · TSMC
TSMC Software Engineer interview: a short ML and semiconductor screen
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…
Interview experiences · TSMC
TSMC Software Engineer Interview Experience: A clear view of the role
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…
Interview experiences · TSMC
TSMC Software Engineer Interview Experience: A same-week invitation for a different role
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…
Interview experiences · TSMC
TSMC Software Engineer Interview Experience: Conflict and operational-workflow scenarios
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…
Interview experiences · TSMC
TSMC Software Engineer Interview Experience: Follow-ups on behavioral stories
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…
Interview experiences · TSMC
TSMC Software Engineer Interview Experience: panel interview and online assessment
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…
Interview experiences · TSMC
TSMC Software Engineer Interview Experience: Panel interview that never moved ahead
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…
Interview experiences · TSMC
TSMC Software Engineer Interview Experience: semiconductor fundamentals in a three-person panel
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…
Interview experiences · TSMC
TSMC Software Engineer Interview Experience: troubleshooting and behavioral problem solving
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…
Interview experiences · TSMC
TSMC Software Engineer interview experience: two relaxed resume-focused rounds
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…
Interview experiences · TSMC
TSMC Software Engineer Interview Experience: two resume-driven manager and team interviews
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…
Interview experiences · TSMC
TSMC Software Engineer interview: projects, research, and practical challenges
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…
Interview experiences · TSMC
TSMC Software Engineer interview: waiting after the interview invitation
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…
Interview experiences · TSMC
TSMC Software Engineer one-hour manager interview about role and experience
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…
Interview experiences · Tubitv
Tubitv Software Engineer Interview Experience — Passed the Coding Rounds, Then Rejected After a Mandarin-Only Screen for a US Role
I mass-applied online in March, and this is how the interview came about. The process was: Round one: coding — a log parser question, identical to one that's already been posted on the forum. I didn't actually get it running successfully during the interview, but the interviewer said at the end that I was on the right track. I ended up passing this round anyway. Round two: "cache design." This wa…
Interview experiences · Turing
Turing AI Engineer interview: monitored three-tier assessment
After applying, I went straight to an online assessment with easy, medium, and hard tiers. I had to keep my camera and audio on and share my screen while answering. The setup was straightforward and seemed intended to assess my ability progressively. After submitting, I was told I should receive feedback about moving to the next phase. I did not get an offer through this path, but the process was…
Interview experiences · Turing
Turing Software Engineer interview: HR conversation and escalating coding test
I started with an HR conversation centered on motivation, personality, and general questions about how I think and work. I then moved to the technical stage and completed coding exercises. The technical part was an online coding interview lasting about an hour. I received three questions and could choose among programming languages. The difficulty rose as the session continued, and the final ques…
Interview experiences · Turo
Turo Data Scientist Interview Experience — Solid Through ML and Coding, Tripped Up by Business and Stats
Sharing a rejection experience from Turo. The interview process itself was actually pretty good — I could tell that if I'd gotten in, I would have learned a lot. Unfortunately I still got rejected. Round 1 was an HR screen. It was mostly going through my resume, and based on what was on there they'd ask some ML-related questions, like what's the difference between XGBoost and LightGBM. Round 2 wa…