READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 149 of 153
Interview experiences · Wells Fargo
Wells Fargo Software Engineer Interview Experience: Broad assessment and a condescending later call
After the recruiter stage, I took a HackerRank-style online assessment that combined multiple choice and coding. It focused on DSA and practical problem-solving. Some versions also included aptitude and general computer-science questions. The platform questions did not always match what I expected, but I pushed through and moved to live rounds after passing. The technical interviews felt more lik…
Interview experiences · WeRide
WeRide Intern Data Scientist Interview Experience — OA, Three Rounds, and a Sour TL Round
I applied for the PhD intern position. First I did the OA, which was pure coding. After that HR called, and then they referred me to a team interview — the team I ended up interviewing for was the DS metric team. There were three rounds total. Round 1 was coding, three questions. The first was a SQL question — I forgot what it was. The second was pandas: computing a sliding window average, specif…
Interview experiences · WeRide
WeRide New Grad Software Engineer Interview Experience — Expression-to-Sum-of-Products Problem
WeRide New Grad SDE first-round technical screening, entirely on HackerRank, including video. The interviewer was 4 minutes late. We first talked about my resume for about 15 minutes — they asked how what I did during my PhD connects to an SDE role. Then we moved on to the problem, conducted entirely in Chinese. The question was as follows: Given an expression made up only of lowercase English le…
Interview experiences · Western Digital
Western Digital Software Engineer interview: staff-level leadership assessment
After a recruiter call, I spoke with a hiring manager or tech-lead-style interviewer about past projects and a high-level architecture scenario. The questions pressed on what I had built, the tradeoffs behind my decisions, and how I reasoned about technical direction. Later rounds focused on staff-level scope: quantifiable outcomes, ambiguity, communication, and cross-functional influence without…
Interview experiences · Whatnot
Whatnot Account Executive: HR conversation followed by a director interview
My experience was fairly simple and conventional. I first had a conversation with an HR professional, which was pleasant and followed standard questions. Soon after, I met with a director for a second round, and that conversation also felt straightforward. Overall, it didn't feel like a complicated, multi-day process. It was a typical process with two meaningful touchpoints. I followed up to ask…
Interview experiences · Whatnot
Whatnot Full Stack Engineer: recruiter call ended before technical depth
My first step was a quick recruiter call focused almost entirely on my projects. I tried to give a one-sentence summary of each team and company so I could cover my experience efficiently, but the interviewer stopped me earlier than I expected and focused on one project in more detail. The conversation ended shortly afterward, and I was declined. What bothered me was that it never went into much…
Interview experiences · Whatnot
Whatnot Machine Learning Engineer Interview Experience — A Weird Product Sense Round, Then Silence
The recruiter reached out before the new year, but it got pushed to after the new year before interviews actually started. Whatnot is a livestream sales platform. The recruiter screen was simple, just chatting about my background and interests. They quickly scheduled the HM interview. The HM interview was half an hour, also mostly chatting about background and interests, but they did ask what imp…
Interview experiences · Whatnot
Whatnot Software Engineer interview: DSA pre-screen and two technical rounds
I started with a structured DSA pre-screen that felt similar to a HireVue or Karat flow. I answered a set of coding prompts and then had a recruiter call. That conversation led into two more technical DSA rounds with engineers from Whatnot. Each session had only a couple of problems, and the interviewers focused on how I was thinking, not just whether I reached the correct output. The process fel…
Interview experiences · Whatnot
Whatnot Software Engineer Interview Experience — One-Hour Karat, Two of Three Questions Finished
Karat interview, one hour. I finished two questions. For the third one I explained my approach but ran out of time to finish writing it. Question 1 Given a store map with different products and a shopping_list, find the minimum number of times needed to buy all the items. Question 2 Given a graph representing a map, with some attractions on it and travel times between the attractions. Several car…
Interview experiences · Whatnot
Whatnot Software Engineer interview: four rounds and a collaborative process
My interview loop had four rounds. It started with a technical screen focused on core software engineering skills, followed by coding, system design, and product sense rounds. The product sense round felt different from the others because it was more of a discussion than a typical question-and-answer session. The interviewers were kind and supportive throughout, and the overall tone felt collabor…
Interview experiences · Whatnot
Whatnot Software Engineer interview: Karat timing and communication challenges
My first meaningful technical round was a Karat interview that began with a discussion of my project. After that, I had two coding questions to solve. I struggled with the second one and couldn’t get all the test cases to pass, so the session ended with me chasing correctness. In another attempt, the Karat interview went poorly for a different reason. The interviewer explained the problem badly a…
Interview experiences · Whatnot
Whatnot Software Engineer interview: one-way video with one-minute answers
I was pulled into a short, one-way video interview. The setup was straightforward: there were several questions, and I had to answer each one on camera within a tight preparation window, with only about a minute to respond to each prompt. The questions focused on behavior and my resume, with some emphasis on why Whatnot specifically. What surprised me was how quickly everything moved. I heard bac…
Interview experiences · Whatnot
Whatnot Software Engineer interview with a one-hour LeetCode-style round
I had a one-hour LeetCode-style round with an engineer. The interviewer was present but very quiet while I worked, so there wasn't much back-and-forth or verbal guidance. The session felt more isolated than I expected, and I ended up not moving forward. The unusual silence is what I remember most. It put more pressure on me to drive the problem-solving process on my own. Location: United States.…
Interview experiences · Whatnot
Whatnot Software Engineer interview with an unstructured behavioral process
My process started with mostly behavioral conversation, and it felt a little unstructured. A hiring manager asked quick, experience-based questions, but I never got a clear sense of what they were prioritizing or how much detail they expected. Whenever I started to expand on an answer, I’d get interrupted or the conversation would move to the next question. The logistics were messy too. I coordin…
Interview experiences · Whatnot
Whatnot Software Engineer interview with HireVue and Karat
My process started with a HireVue-style interview, followed by a Karat technical interview. The technical portion moved from easy to harder LeetCode questions, and the increase in difficulty was noticeable. After the Karat round, I had a short recruiter screening. If I passed that, I would move on to another technical interview with engineers. That phase was described as including more problem-so…
Interview experiences · Whoop
Whoop Senior iOS Engineer Interview Experience — Four Onsite Rounds, Rejected on System Design
I recently interviewed for a Senior iOS position at WHOOP (had a referral). Got rejected on the last round of the onsite, System Design. Didn't make it. My overall impression of this company's interview process was really, really good. The company also supports H1B and green card, so I hope anyone who needs that applies quickly. First, my impressions of WHOOP: Very efficient — from the initial co…
Interview experiences · Wipro
Wipro Software Engineer interview: communication-focused easy screening
The process felt unusually easy. Most of the attention was on how I communicated: my accent, vocabulary, and whether I could express myself clearly. It was not a heavy technical grilling. The questions were simple and personal. I was asked to talk about myself, my hobbies, and what I had done the previous weekend. Because the conversation stayed light, I never felt as though I was being tested on…
Interview experiences · Wipro
Wipro Software Engineer interview: resume-based technical rounds
After a recruiter call, I had two technical rounds and one HR round. Technical questions stayed close to my resume, so they felt grounded in my experience. One section began with multiple-choice questions and then a coding test. The MCQs were basic concept checks. The coding portion had multiple moderately difficult problems, moving from theory to implementation in one sitting. The HR discussion…
Interview experiences · Wise. Energy
Wise. Energy Software Engineer Interview Experience: Rigid technical screens and contradictory role expectations
The vibe and fairness felt off from the start. In a technical round where I filled in parts of a skeleton script, the session felt rushed and rigid, as if I were being judged against a memorized approach instead of how I reasoned. The scope changed at the last minute because they could not define what they wanted. There was also a mismatch in fundamentals: state-machine concepts were not handled…
Interview experiences · Wise. Energy
Wise. Energy Software Engineer interview with pair programming
I went through a standard multi-stage loop. It started with a recruiter conversation, then a 30-minute coding interview, followed by a longer technical session with system design and another coding segment with two engineers. After that came a product interview and a final conversation with managers and a lead. The exercises felt practical rather than contrived. In the pair-programming portion, c…
Interview experiences · Wise
Wise Software Engineer Interview Experience: A rushed skeleton task with shifting requirements
My experience went in a direction I did not expect. Early on, the interviewers seemed to rely on a rigid, memorized script instead of exploring architecture and trade-offs in a real way. The session rushed toward finishing a skeleton task and left little room for production concerns such as comprehensive error handling. When foundational concepts came up, especially state-machine thinking, the in…
Interview experiences · Wise
Wise Software Engineer interview: supportive pairing and contradictory design guidance
After a recruiter chat, I entered technical rounds of about an hour each. The pair-programming panel was mostly friendly and helped when I got stuck. I tried to collaborate and explain my thinking, and one interviewer said at the end that I had done better than most senior IC candidates, but I still did not advance. System design felt less stable. Two interviewers pulled in different directions:…
Interview experiences · Wissen Infotech
Wissen Infotech Software Engineer Interview Experience: DSA, SQL, and graph questions
The process was short and very technical. I had two rounds. In the first, I solved two DSA problems by writing actual code and explaining my approach. I also had to dry run the solution, so intuition alone was not enough. The final round had an ED-style format. I was asked about SQL and then worked through two more DSA questions, with graphs appearing in at least part of the problem framing. It f…
Interview experiences · Wissen Infotech
Wissen Infotech Software Engineer interview: OA, DSA, SQL, and director round
I completed an OA with general coding questions, then a technical interview with two DSA questions and a SQL problem. The process then moved toward a director-level discussion. The technical work was practical and problem-solving focused. Each stage had a clear purpose, while the director round focused more on how I presented and thought through things. The early parts went well, but the director…