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
- Prime Video Software Engineer interview: LRU cache and evictionPrime Video · Software Engineer · Technical Screen · Jun 2026Offer
My first real screen ran longer than expected and went deep into implementation. I was asked to design an LRU cache using a hashmap and doubly linked list while keeping eviction correct. The interviewer was direct and kept probing my approach, especially the eviction behavior and the reasoning behind it. The rest of the process added more technical depth along with behavioral interviews connected…
- Providence India Software Engineer interview: three rounds and delayed rejectionProvidence India · Software Engineer · Onsite · Jun 2026Rejected
The process felt a little unstructured from the start. I completed three rounds: two virtual interviews on Teams, then an in-person interview at the office. I got feedback fairly quickly after the first two rounds, so while things were moving I had some sense of where I stood. After the third, in-person interview, communication went quiet. I waited a long time without updates and eventually recei…
- Providence Software Engineer interview: three rounds and silence after onsiteProvidence · Software Engineer · Onsite · Jun 2026Rejected
My Providence process felt somewhat unstructured. There were three rounds: two virtual interviews on Teams, followed by an in-person interview at the office. The first two moved quickly, and I received feedback promptly after each one, so I had a sense of where I stood while the process was active. After the final in-person round, communication stopped. I waited a long time without hearing back,…
- Python File Handling Before an Open-Ended Regression TaskVoleon · Data Scientist · Technical Screen · Jun 2026
Question format The interviewer gives one or more datasets: X: contains multiple features, possibly an m x n matrix y: a continuous, real-valued target You're expected to explore: which columns are related to y which features provide useful signal whether there's redundant information or collinearity among the features how you should build and evaluate a predictive model Before that part, there w…
- Quantiphi Machine Learning Engineer Interview Experience: two theoretical modeling roundsQuantiphi · Machine Learning Engineer · Technical Screen · Jun 2026
I had two rounds, and both were theoretical rather than hands-on coding. The first covered time-series and classification concepts, including deeper ML topics. I spent most of the time explaining my understanding and reasoning through how ideas applied instead of simply defining terms. The second round stayed in that same territory but felt more architectural. The questions explored how I think a…
- Rate Limiter and N-ary Tree Rounds, No DP AllowedSnowflake · Software Engineer · Technical Screen · Jun 2026Rejected
3 YOE, mid-level. After talking with the HM, there were two phone screens, and they were still pretty hard. Coding 1 Design a rate limiter. Just one rule Multiple rules Is it thread-safe, and how would you make it thread-safe (lock) If the request handler throws an exception for a given request, that request shouldn't be counted Don't drop the other rate-limited requests — when there's spare capa…
- RBC Software Engineer Interview Experience: an easy behavioral interview without closureRBC · Software Engineer · Other · Jun 2026No response
The process was simpler than I expected. It started with a roughly 30-minute behavioral interview and situational questions that were not especially difficult. I was told I would hear about my application status within a week. Almost two weeks passed without an update, so I sent a follow-up email thanking them and asking about timing. That email was not answered either. I ended up without closure…
- Red Hat Software Engineer Interview Experience: four rounds disrupted by schedulingRed Hat · Software Engineer · Technical Screen · Jun 2026
A recruiter contacted me quickly after I applied, but reaching them afterward was frustrating. Once I was scheduled, the process became chaotic because scheduling was the biggest source of stress. I had four interviews: a hiring-manager call, two technical discussions, and a coding round. I had given availability for a week, and the schedule was set around it. Then my final-round interview was mo…
- Red Hat Software Engineer interview: system design, coding, and projectsRed Hat · Software Engineer · Jun 2026Rejected
My Red Hat loop followed the usual order: a screening round, a conversation with the hiring manager, and technical rounds. I reached a later technical stage but was not moved forward after it. The technical discussions covered system design and coding concepts. I also talked through my current projects and the design decisions behind them, which kept the interviews tied to how I actually work. Th…
- Regression and Matrix QuestionsVoleon · Quantitative Researcher · Technical Screen · Jun 2026
The author’s Voleon phone-screen report combines mathematical reasoning, statistical modeling, and a short programming task. Matrix questions concerned the implications of unit row and column totals, including whether nilpotence was possible. The regression discussion examined bounds on the coefficient of determination and what could happen when two predictors were used together. Further question…
- Restaurant Brands International Business Analyst interview: data and project decisionsRestaurant Brands International · Business Analyst · Other · Jun 2026
I went through a conventional process with several rounds. Some questions were specific to Restaurant Brands International, while others asked me to go deeper on my background. Early on, they wanted to know how I had used data and organized work in past projects. I was asked to describe one of the hardest projects I had handled, how I used data to get to the result I wanted, and the tools I used…
- Revolut Operations Manager Interview Experience: a structured process with late red flagsRevolut · Operations Manager · Take-home Project · Jun 2026Offer
My process was long and structured: a recruiter screen, a cognitive-style test, a home task, a case interview, a bar raiser, and a team-fit stage. The recruiter did a fair amount of preparation between rounds and kept things moving, although there were hiccups. Interviews could start more than 10 minutes late without much notice. The bar raiser was much shorter than I expected. Parts of the proce…
- Revolut Product Manager interview: hypothetical business caseRevolut · Product Manager · HR Screen · Jun 2026Rejected
My process felt lighter than the intense multi-round processes I had seen elsewhere. It started with an HR screen and moved into a case-style evaluation. Recruiter interactions were straightforward, prep materials were provided, and I was expected to do structured analysis. For the case, I worked through a business scenario and gave reasoning and a recommendation. The examples were hypothetical r…
- Rippling Software Engineer interview experience: coding, system design, and AI useRippling · Software Engineer · Technical Screen · Jun 2026
My loop followed the familiar structure of several coding rounds followed by broader rounds. I completed three coding rounds, then a high-level system design round, and finished with a hiring-manager round. AI was allowed in the process, which made it feel different from stricter interview settings. The work meant solving coding problems in sequence, switching to system design, then meeting the h…
- Robert Half Financial Analyst interview: reading red flags in spending dataRobert Half · Financial Analyst · Technical Screen · Jun 2026
The recruiter-to-interview path was straightforward, and I got the impression they were moving quickly because they had several hiring needs. For the technical part, I received a spending spreadsheet for an account and had to identify patterns that might be red flags. The follow-up went past basic background questions. We covered my work history, salary expectations, and the software I had used.…
- Rokt Account Executive interview with two CCAT assessments and HireViewRokt · Account Executive · Online Assessment · Jun 2026
After applying, I went through a fast-moving assessment sequence centered on CCAT-style cognitive testing. I took two different CCAT versions, which felt a little odd and even useless to me, although the tests themselves weren’t especially hard. After reviewing my results, the recruiter scheduled a HireView step. It was short and not difficult, but I found the format oddly off-putting. I then mov…
- Rushed Team Match, Ghosted Before the OnsiteSalesforce · Software Engineer · Technical Screen · Jun 2026Rejected
This was a really baffling hiring process. Is Salesforce's general hire now all team-specific interviews instead of a unified track? Round 1: OA — sent later on, an online test on the HackerRank platform. If I remember right it was LeetCode-style stuff, not too hard, but the test cases were kind of annoying. After I passed, about a month later an HR person reached out — but it wasn't the general-…
- Safran Full Stack Engineer Interview Experience: a month-long structured processSafran · Full Stack Engineer · HR Screen · Jun 2026
I applied early in the month and first heard back about two weeks later for an HR interview. About two weeks after that, I had an in-person conversation, then waited another week for the decision. The whole process took about a month, which made the scheduling feel fairly smooth. The process itself felt structured. It began with a phone conversation about my academic and professional background,…
- Scale Software Engineer interview: card-game coding exerciseScale · Software Engineer · Technical Screen · Jun 2026
The recruiting flow felt friendly at first, then the technical work proved unlike a standard LeetCode trick question. The coding prompt used a card-game theme and was more about implementing many conditions than finding an elegant idea. It moved through multiple cases, so I had to track the logic and states carefully. In the live coding round, I needed to work through those conditions quickly. Th…
- Schweitzer Engineering Laboratories Software Engineer Interview Experience: a structured three stage loopSchweitzer Engineering Laboratories · Software Engineer · HR Screen · Jun 2026
My interviews had three stages: an initial HR screen, a technical interview on Microsoft Teams, and an on site day. The HR conversation covered my background, experience, and interest in the role. The Teams interview focused on programming knowledge and problem solving, and I connected my answers to relevant projects. The on site went deeper into engineering conversations with the team. We discus…
- SDE I New Grad Loop in Canada, Offer the Monday After the Final InterviewAmazon · Software Engineer · Onsite · Jun 2026Offer
Hey everyone! I recently graduated with a CS degree from a school in Canada (I'm an international student) and ended up with an SDE I offer from Amazon. Here is how the process went, hopefully it's useful to somebody. Timeline My application went in during the last days of January 2026. Nobody referred me. In early April the online coding assessment arrived in my inbox, and I sent it back after t…
- SDE II Loop with a Job Scheduler DesignRobinhood · Software Engineer · Onsite · Jun 2026Rejected
I want to share my Robinhood SDE II interview experience. Although I did not get an offer in the end, I learned a lot while preparing, and I hope this gives people interviewing later a useful reference. Technical Screening A frequently seen Referral Count problem, solved with DFS and memoization. Coding Fractional Stock Inventory, 45 minutes. My main implementation and all test cases passed. Ther…
- ServiceTitan Account Executive, cold outreach role-playServiceTitan · Account Executive · Other · Jun 2026No response
My interview process started with a recruiter conversation, followed by a second round that focused on how I handled the sales discussion and the details behind it. After that round, I heard nothing. I followed up with the recruiter and still got no response, so it felt like I was ghosted after investing time in the process. The role-play case study focused heavily on outbound behavior, even thou…
- Siemens Digital Industries Software Software Engineer Interview Experience: C++ and teamwork discussionSiemens Digital Industries Software · Software Engineer · Technical Screen · Jun 2026Offer
After the recruiter call, I had a smooth, organized interview that stayed professional throughout. I started by introducing my background, the projects I had worked on, and the technical experience I could bring to the role. The questions then moved into programming basics, especially C++ fundamentals and object-oriented concepts. They also wanted to hear how I approach problem-solving and teamwo…
- Siemens Software Engineer interview: technical depth and resume discussionSiemens · Software Engineer · Technical Screen · Jun 2026
The Siemens process felt structured and focused on technical depth without becoming a huge drawn-out process. I went through rounds that mixed coding and probing with a manager discussion and an HR step. Throughout, the questions kept coming back to my resume. In the technical rounds, I discussed core data structures and algorithms as well as real-world problem-solving scenarios. I had to explain…
- Sii Group Italy Software Engineer interview: a fast client-project processSii Group Italy · Software Engineer · Technical Screen · Jun 2026Offer
The process was fast and strongly oriented around the assignment. I started with a conversation with a business manager or sales representative. The next day I had a technical interview, followed immediately by another step that moved very quickly. The format surprised me because it was so conventional: direct questions centered on the role. The role was tied to a client project, but I did not ha…
- Sii Netherlands Software Engineer interview: technical interview and quick offerSii Netherlands · Software Engineer · Technical Screen · Jun 2026Offer
I had a very fast hiring process. First came an interview with a sales representative or business manager. The next day I had a technical interview, and by the day after that I already had an offer. The content itself was fairly conventional. What surprised me was that the role was for an external-client project, so I did not have to complete the client interview that often appears in these proce…
- Silicon Labs Software Engineer interview: three online technical roundsSilicon Labs · Software Engineer · Technical Screen · Jun 2026
My biggest frustration was the way HR handled scheduling and communication. The follow-up felt ego-driven, and they kept pushing me to drop my application instead of giving a clear, consistent process. I learned that the second interview would take a long continuous block, around three hours with multiple hiring managers. The plan kept changing, and I was only called for the interview after a mon…
- Six Onsite Rounds That Felt Like Six Different CompaniesApple · Software Engineer · Onsite · Jun 2026
Six rounds, written for people as confused as I was. One thing I only understood after the whole process: this company hires by team, so each team sets its own bar and writes its own questions — which means whatever interview experience you find here for this company might be less useful than you'd hope. Over my six rounds, the six interviewers were different enough in style that it felt like six…
- Smartsheet Account Executive: dry, transactional recruiter meetingSmartsheet · Account Executive · HR Screen · Jun 2026Offer
I went into the recruiter-stage meeting expecting something more thoughtful, but it was oddly dry and transactional. It felt like someone was just ticking boxes. There wasn't much back-and-forth or emotional engagement, and I didn't feel like the interviewer was listening so much as running through a script. That gave me a pretty negative impression from the start. As I thought more about what I'…
