real interview stories, told over a cup of tea ♡
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
3935 results
- TSMC Customer Success Engineer interview: behavioral, teamwork, and leadership discussionTSMC · Customer Success Engineer · Other · Jul 2026
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…
- TSMC Software Engineer Interview Experience: A same-week invitation for a different roleTSMC · Software Engineer · Jul 2026In progress
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…
- TSMC Software Engineer interview experience: two relaxed resume-focused roundsTSMC · Software Engineer · Jul 2026
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…
- TSMC Software Engineer interview: projects, research, and practical challengesTSMC · Software Engineer · Other · Jul 2026
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…
- TSMC Software Engineer interview: waiting after the interview invitationTSMC · Software Engineer · Jul 2026
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…
- Turing AI Engineer interview: monitored three-tier assessmentTuring · AI Engineer · Online Assessment · Jul 2026
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…
- Turing Software Engineer interview: HR conversation and escalating coding testTuring · Software Engineer · HR Screen · Jul 2026
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…
- Twilio Product Manager interview: three rounds in under a weekTwilio · Product Manager · Technical Screen · Jul 2026Offer
My process was unusually quick: three interview rounds in under a week, with five interviewers across them. Each person covered a different area, including engineering partnership and culture-fit discussions, so I was not having the same conversation over and over. I received an offer within about 72 hours of the last interview and accepted it. Even with the speed, the setup felt intentional beca…
- Twilio Software Engineer interview: full day of design problemsTwilio · Software Engineer · HR Screen · Jul 2026
After the recruiter interaction, I spent a long 9-to-5 interview day with different interviewers each hour. Every hour brought a new design problem, so I had to keep switching gears and reframing my approach. The final conversation was with HR. When I gave my salary expectations, HR asked again and indicated they still needed to think about it. I did not receive an offer. The process itself was c…
- Two Coding Rounds Plus a Hotel Reservation System DesignLead Bank · Software Engineer · Onsite · Jul 2026
The first coding round was similar to what people describe online — it's the one where you treat it as a stock ticker + date + price log. The interviewer guides you step by step, so you can pretty naturally arrive at the solution. Here's roughly what my code looked like: System design: the classic hotel reservation system design that shows up online a lot. Though there was a twist — the interview…
- Two Coding Rounds, System Design, Then a RejectBridge · Software Engineer · Onsite · Jul 2026Rejected
I recently interviewed at Bridge, which has since been acquired by Stripe. Sharing my interview experience here. Coding 1: You're given a list of objects, each looking something like: {"key1": 10, "key2": 20} All values are integers. You're given a specific key, plus a requirement of MAX or MIN. You need to find, among the objects in the list that contain this key, the one whose value for that ke…
- Two Onsite Coding Rounds, Rejected Over a Tricky Input AssumptionSnowflake · Software Engineer · Onsite · Jul 2026Rejected
Two onsite rounds, mid-level, both coding. Both rounds were repeat questions I'd seen before, but they happened to be from the few I hadn't practiced. A bit unlucky. Overall the interview experience was fine — the interviewers were all nice, and they asked me a lot about how I use AI in my day-to-day developing cycle. Wiki Hopper — basically a webpage has multiple links that let you jump to other…
- Two Onsite Rounds, Same Day, Coding and System DesignOpenAI · Software Engineer · Onsite · Jul 2026Rejected
I had two rounds back to back on the same day, each about 60 minutes. The interviewer was about 5 minutes late both times. The coding round interviewer was really nice, but the second round felt a lot more serious. Overall the experience was fine. I got the rejection letter the next day. The coding round was a multipart social graph + snapshot problem. The first question was the same as H2H. The…
- Two Onsite Rounds, Team Matching in ProgressGoogle · Software Engineer · Senior+ · Onsite · Jul 2026In progress
Round 1 Coding (45 min): Job Processing Schedule with priority. Higher-priority jobs get processed first. Asked to implement a class with two APIs, addJob and getJob. Follow-up: add a delay to each job — for example, after job A is processed, it can't be processed again until at least 3 getJob API invocations have happened. BQ (45 min): Standard behavioral questions — the biggest challenge I ran…
- Two Phone Screens, Easy Coding Then a Distributed Cache DesignApple · Software Engineer · Technical Screen · Jul 2026
This was for ASE, on the storage infra team. Phone screen round 1: the HM, 45 mins. BQ Coding 1: string run-length decoding. For example, a5b3c -> aaaaabbbc Coding 2: count the nodes in a chain. Each node can only access the node to its left and the node to its right, and you have to count how many nodes there are in total. Both problems needed test cases. Summary: the coding questions were very…
- Two Technical Rounds, Set Card Game Follow-up Ran Out of TimeSnowflake · Software Engineer · Technical Screen · Jul 2026Rejected
I interviewed about a month ago. Mid level. The HR screen already told me they would ask medium to hard questions. There were 2 interviews of 1 hour each. In some of them you get 2 questions in the hour, in some just 1. We started with a quick self-introduction and then went straight into the problem. The first round was a variant of a known problem. It asked for the sum of all node values along…
- Two-Day Onsite With System Design, Project Deep Dive, and CultureAnthropic · Software Engineer · Onsite · Jul 2026
Process Recruiter call. Phone screen (coding) — a question that had already shown up on this forum. Phone screen with the hiring manager — again, a question already posted here. Onsite: four rounds. Onsite Day one: two system design rounds, both domain specific, not much reference value since they're not the kind of thing that gets asked repeatedly on this forum. Day two: project dive deep + cult…
- U.S. Bancorp Financial Analyst interview experienceU.S. Bancorp · Financial Analyst · HR Screen · Jul 2026
I started with an HR conversation about the role and compensation. The recruiter emphasized behavioral questions, and I used a STAR structure because the answers clearly mattered. After the interview, communication fell off. The timeline felt rushed and disorganized, and despite feeling that the interview went well, I was left waiting for next steps rather than guided through the process. Locatio…
- U.S. Bancorp Financial Analyst interview: welcoming questions on finance and fitU.S. Bancorp · Financial Analyst · Jul 2026
I went through a straightforward, mostly people-focused sequence. The recruiter call covered what I wanted, my interests and their fit with the role, my real-estate and Excel experience, and the office I was targeting. Interviews with managers or team members remained welcoming. They asked about my background, teamwork, leadership, why I wanted the bank, and how I thought about the future. I also…
- U.S. Bank Financial Analyst interview experienceU.S. Bank · Financial Analyst · HR Screen · Jul 2026
The HR conversation covered the role and compensation and felt structured from the beginning. Most questions were behavioral, and the interviewer kept coming back to clear STAR-style examples. I got the sense that connecting prior experience directly to day-to-day work mattered to them. After the recruiter stage, I spoke with people on the team. The rounds were friendly, conversational, and behav…
- U.S. Bank Financial Analyst interview: simple rounds with unclear timingU.S. Bank · Financial Analyst · Jul 2026
The process started normally, but its pacing soon felt off. The interviews themselves were straightforward, yet I received little communication afterward. Things on their side felt rushed and not well organized, and I was left waiting even when I thought an interview had gone well. Another part of the journey became a longer sequence: phone screen, hiring-manager round, then a final conversation…
- U.S. Bank National Association Business Analyst interview: organized behavioral roundsU.S. Bank National Association · Business Analyst · HR Screen · Jul 2026
I began with an HR screen about my background, experience, and behavioral questions. Everything felt organized, and the communication about scheduling and next steps was clear enough that I never felt lost. Later rounds remained formal but friendly. The interviewers asked many behavioral questions and created a comfortable rhythm, which made it easier to discuss my experiences without overthinkin…
- U.S. Bank National Association Financial Analyst interview: behavioral rounds and a superdayU.S. Bank National Association · Financial Analyst · Other · Jul 2026
After the recruiter stage, the process felt relaxed and well paced. I was kept informed and had enough time to prepare between conversations. Most questions were behavioral scenarios about how I'd handle different situations. When I needed a moment to think, the interviewers were calm and patient. I never felt rushed. The process moved quickly through several conversations. Apart from the superda…
- Uber Account Executive interview: vendor experience screenUber · Account Executive · HR Screen · Jul 2026
After applying through the website, I was shortlisted and had an initial HR screen. The questions focused on my client-facing experience and how I worked with vendors, including different alcohol vendors and what that looked like in practice. The round was average in difficulty. It was not overly technical, but it did require me to explain real-world vendor and stakeholder work. I did not receive…
- Uber Data Scientist interview: 17-question SQL and aptitude testUber · Data Scientist · Online Assessment · Jul 2026
My first step was a 60-minute test with 17 questions: two medium SQL questions and fifteen aptitude questions. The aptitude portion felt fairly straightforward, and I think I could have finished it in about half the allotted time. I used more of the clock on SQL because I did not fully solve one problem, then submitted what I had. The process did not continue after that test. The non-SQL portion…
- Uber Data Scientist interview: SQL and consumer fraud riskUber · Data Scientist · Technical Screen · Jul 2026Rejected
The interview was centered on risk. I worked through an SQL question and then a confusion-matrix-style question, and I felt technically comfortable with both. The problem came when the discussion moved to consumer fraud risk. I answered, but the reaction suggested that the way I framed the risk analysis and reasoning had not landed. That difference in how we saw the quality of the answer stayed w…
- Uber Drivers Account Executive interview: aptitude and phone screenUber Drivers · Account Executive · Online Assessment · Jul 2026Rejected
I had a direct process that began with a recruiter-style check. The early screening asked about my client-facing work and how I had handled vendor relationships, including relationships with different alcohol vendors. An aptitude-style step followed, then a phone interview focused on my experience and gave me more information about what the role would involve. These early rounds felt average in d…
- Uber Drivers Data Scientist interview: framing consumer fraud riskUber Drivers · Data Scientist · Technical Screen · Jul 2026Rejected
The first round was about risk. I completed one SQL task and then answered a question about a confusion matrix. The follow-up on consumer fraud risk was what threw me. When I explained the risks as I saw them, they did not seem impressed, and that feedback came across quite directly. I did not move to later stages. It felt as though the bar was not only technical correctness. How I framed fraud r…
- Uber Drivers Data Scientist interview: SQL bottleneck in a timed testUber Drivers · Data Scientist · Online Assessment · Jul 2026
My first step was a 60-minute test with 17 questions: two medium SQL questions and 15 aptitude questions. The aptitude questions felt easier, as though I could get through most of them in under half the time. I spent longer on the SQL section and could not fully solve everything. By the end, I was hoping that the partial progress would be enough to move forward, but I did not get an interview aft…
