READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 140 of 153
Interview experiences · Turo
Turo Software Engineer Interview Experience — Four Onsite Rounds, Verbal Offer in Under a Month
Background I got a referral, and as soon as the role opened they scheduled a call directly. (My personal takeaway: right now applying early matters more than being strong.) Timeline: 01/13 Applied 01/15 Recruiter call 01/15 OA 01/28-01/29 Four rounds of virtual onsite 02/06 Verbal offer Interview Experience Recruiter call Simple questions about my background, how long I've been working, what this…
Interview experiences · Twilio
Twilio Product Manager interview: three rounds in under a week
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…
Interview experiences · Twilio
Twilio Software Engineer interview: full day of design problems
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…
Interview experiences · Twitch
Twitch Backend Engineer interview with AWS system design prompts
I interviewed at Twitch for a Software Engineer role. The process felt challenging and deliberate over roughly a few weeks, with a testing approach that was more distinctive and less focused on standard LeetCode problems. It started with a timed coding assignment. After that, I had a recruiter phone call, followed by a hiring manager discussion as the second phase. The technical testing used ques…
Interview experiences · Twitch
Twitch Data Science Intern Interview Experience — SQL Screen on the Classic Streaming and Viewing Tables
I did a mass application to Twitch's Graduate DS intern program. About two weeks later I got an HR phone screen — they asked why this company and three or four traditional behavioral questions, about 30 minutes total. A week after that came the technical round: 4-5 SQL questions, all built around two tables related to streaming and viewing. The questions were slightly different from ones already…
Interview experiences · Twitch
Twitch Data Scientist Interview Experience — A SQL Screen Where Every Question Got Follow-Up After Follow-Up
Just finished my SQL interview, written on CodePad. It was pretty similar to a question set from the forum, but the interviewer kept hammering me with variant follow-ups on every single question... my brain was practically on fire. Every row in this table represents one minute, recording what a streamer was doing during that minute: Q1: total monthly hours streamed for each month, in order by mon…
Interview experiences · Twitch
Twitch Software Engineer Interview Experience — First-Ever Interview, Four-Round Onsite, No Offer
Full interview timeline: 9/28 — Mass-applied. 11/3 — Received an OA invite and an HR reach-out. 11/14 — HR phone screen, asked about my basic background and some BQ. 11/24 — Tech round. They gave a rock-paper-scissors game design question with two follow-ups — you got extra credit for handling win streaks and for breaking ties. Someone on this forum had shared this one before. Then some BQ, diggi…
Interview experiences · Twitch
Twitch Software Engineer interview: OOP assessment and no offer
I interviewed for a Software Engineer role at Twitch. The process felt fairly standard: a recruiter screen followed by an assessment focused on object-oriented programming. The recruiter screen covered my resume and previous work. The technical assessment involved an OOP coding question. I wasn't offered the role. My main takeaway was to be ready to code directly around object-oriented fundamenta…
Interview experiences · Twitch
Twitch Software Engineer interview with a 45-minute hiring manager technical round
I interviewed for a Software Engineer role at Twitch. The process followed a typical assessment, then hiring manager flow: recruiter outreach, a CodeSignal assessment, and a short technical interview. The recruiter explained the role and contacted me to start the process. I completed the CodeSignal assessment, waited a few days, and then had a 45-minute technical interview with the hiring manager…
Interview experiences · Twitch
Twitch Software Engineer interview with a CodeSignal design and debugging assessment
I applied to Twitch for a Software Engineer role, completed an assessment focused on design and debugging tasks, and then didn't move forward. The OA was a CodeSignal-style assessment with a system-design-and-coding prompt split into two parts. First, I had to implement classes and functions. Then I had to debug a helper class. I didn't hear back after the assessment. My takeaway was that the "de…
Interview experiences · Twitch
Twitch Software Engineer interview with a two-hour assessment
I interviewed for a Software Engineer role at Twitch and went through an unusually long assessment. I never received clear follow-up afterward. The process began with a recruiter conversation. The online assessment was a single extended technical assessment that lasted about two hours. I wished I could see my scores, but I never received them. I didn't hear back, and the experience left me thinki…
Interview experiences · Twitch
Twitch Software Engineer interview with an unexpected behavioral call
I went through Twitch's early pipeline for a Software Engineer role, starting with a Codesignal pre-screen to earn an invitation. The behavioral intro call caught me off guard, and I didn't progress. The Codesignal pre-screen was a coding assessment. The intro and recruiter call focused on behavioral questions I hadn't expected, and I felt that my answers weren't strong. I didn't advance. My take…
Interview experiences · Two Sigma
Two Sigma Data Scientist Interview Experience — Piecewise Interpolation, Temperature Prediction, and Streaming Linear Regression on the OA
This Two Sigma research OA is also an old question that's been floating around on the forum. Question 1: You're given a bunch of discrete points that connect into a polyline. Now you're given an x, and you need to compute the corresponding y. If x falls between two points, do linear interpolation; if it falls outside the range, extend the line segments on either end to compute it. The question ma…
Interview experiences · Two Sigma
Two Sigma New Grad Software Engineer Interview Experience — Two OA Questions, Advanced the Next Day
I applied for Two Sigma's New Grad SWE role. I didn't have much hope going in — not long after a mass application round, I got an OA invite: two problems to solve together in one time-limited session. Before applying I'd heard this company has a lot of rejection stories, so I specifically went and dug through the forum to do my homework. Several posts said the OA questions on the forum were the a…
Interview experiences · Two Sigma
Two Sigma Quantitative Software Engineer Interview Experience — Order-Matching HackerRank Then a Quant Systems Deep Dive
Round 1: HackerRank Coding — Stock Exchange / Order Matching The task was to implement buy/sell order matching: Buy side uses max priority. Sell side uses min priority. Match orders when the price can cross. Handle partial fills. Output trade records. Handle the remaining resting orders. Follow-ups: How to add more tests to increase confidence. Why my output didn't match the sample. How multiple…
Interview experiences · Two Sigma
Two Sigma Software Engineer Interview Experience — Rejected After One Technical Screen on a Huffman-Style Encoding Problem
11.9 – applied 11.12 – OA 11.24 – got the invite for the next round 12.1 – interview 12.3 – rejection letter The interviewer's English was really good, and he was patient and kept trying to guide me, but at the time I just couldn't understand why we needed to build a tree to encode things. It wasn't until later that it clicked — it's to get a unique binary representation, so that the most frequen…
Interview experiences · U.S. Bancorp
U.S. Bancorp Financial Analyst interview experience
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…
Interview experiences · U.S. Bancorp
U.S. Bancorp Financial Analyst interview: welcoming questions on finance and fit
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…
Interview experiences · U.S. Bank
U.S. Bank Financial Analyst interview experience
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…
Interview experiences · U.S. Bank
U.S. Bank Financial Analyst interview: fit, Excel, and superday conversations
My interview path focused on fit and motivation, with enough structure that it felt clear. Early conversations with HR and a manager combined my interests with practical fit questions. We talked about real estate, my Excel skills, and which office I wanted to apply to. The later stages put the industry and my background at the center. I discussed my experience with accounting systems, where I saw…
Interview experiences · U.S. Bank
U.S. Bank Financial Analyst interview: simple rounds with unclear timing
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…
Interview experiences · U.S. Bank National Association
U.S. Bank National Association Business Analyst interview: organized behavioral rounds
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…
Interview experiences · U.S. Bank National Association
U.S. Bank National Association Financial Analyst interview: behavioral rounds and a superday
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…
Interview experiences · Uber
Uber Account Executive interview: vendor experience screen
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…