READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 148 of 153
Interview experiences · Walmart
Walmart Product Manager Interview Experience: inconsistent screening and late manager call
My first contact was a roughly half-hour phone screen with a Staff PM. It was described as behavioral but had little advance structure, and the interviewer seemed to run it their own way. I left that call believing I would move forward. A later process had recruiter screening, a hiring-manager conversation, and additional interviews. During the recruiter call I introduced myself, then the recruit…
Interview experiences · Walmart Labs
Walmart Senior Software Engineer Interview Experience — System Design, Behavioral, and a Two Sum Variant Onsite
This was a Walmart hiring event. I had passed the phone interview before, and then this physical onsite had three rounds. First round: system design, Ticket Master, done on a whiteboard. The interviewer was friendly and reminded me that I might not be following the process in the right order. You need to write the functional requirements, the non-functional requirements, then the model, the API,…
Interview experiences · Walmart Labs
Walmart Software Engineer Interview Experience — A Disorganized Onsite Hiring Event
Actually, this is just me venting... First, the onsite is called a "hiring event," and there were about a dozen people there. After checking in, we even had to walk back to the car to put up the parking permit — pretty chaotic. The hiring manager for the BQ round was 15 minutes late! If they hadn't shown up soon, I was ready to pack up and leave. The conversation itself was pretty mediocre — not…
Interview experiences · Walmart Supply Chain
Walmart Supply Chain Software Engineer interview: coding rounds and backend stack discussion
The process felt structured and efficient. After the initial tech-focused intake, I had a roughly 30-minute technical assessment spread across three rounds. Each round was essentially a LeetCode-style coding challenge, and the interviewers were attentive and clear. I also talked through my background, resume, and the tech stack listed there. Kafka and Kubernetes came up along with Java and Spring…
Interview experiences · Walmart Supply Chain
Walmart Supply Chain Software Engineer interview: easy coding followed by silence
After I applied online, an email invited me to a virtual interview. The process was quick and felt fairly light. I was asked to solve an easy LeetCode-style problem, something like Two Sum or an array task, and worked through it as best I could. I never received a follow-up afterward. There was no rejection message, just silence. The interview itself hadn't felt difficult, but the lack of communi…
Interview experiences · Warner Bros Discovery
Warner Bros Discovery Senior Software Engineer Interview Experience — Full Loop, No Offer After System Design Ran Long
My Warner Bros. Discovery interview process, which dragged on for over a month, is finally over. CNN division - JS Senior Full Stack HR screening - they got to know my background, my reasons for job searching, and touched on a few technical-related questions. Technical Screening - live coding, with two Senior developers on the other side. Very simple: given an array and an integer k, shift left b…
Interview experiences · WatchGuard Technologies
WatchGuard Technologies Software Engineer Interview Experience: DSA and detailed project questions
The interview opened with an intense discussion of DSA fundamentals. First, the interviewer asked me to rate myself in my main programming language. The questions followed that rating and grew harder as we went. We spent a lot of time on my resume. Every project and technology I mentioned led to follow-up questions, and I felt I had to justify my work with technical understanding, not just give a…
Interview experiences · WatchGuard Technologies
WatchGuard Technologies Software Engineer Interview Experience: Strong technical, nervous manager round
The process was a quick three-step flow: first a technical screen, then a managerial-style round, with some candidates progressing further depending on early performance. My technical interview went so well that they skipped a second technical interview and moved me forward. The managerial conversation was emotionally different. The questions and discussion were good, but I became nervous and fum…
Interview experiences · Waters
Waters Software Engineer interview: selective full-stack and SQL assessment pipeline
I went through the more intense, high-volume track. It began with an online assessment containing 20 multiple-choice questions on full-stack topics and SQL. After that came a group discussion, and the numbers made the process feel very competitive. After the applications and screening, 30 people were shortlisted for the next step. From there, 12 reached a stage where the process continued far eno…
Interview experiences · Wayfair
Wayfair Applied Scientist Interview Experience — Product Judgment and a Changed Role
The author describes a Wayfair machine-learning scientist interview beginning with an advertising-bidding case. Virtual-onsite exercises covered homepage module ranking, recommendations sent after a purchase, an AI-assisted bandit simulation, and behavioral questions. The coding session permitted AI tools and web searches with screen sharing, but follow-ups required explanations of bandit strateg…
Interview experiences · Wayfair
Wayfair Software Engineer Interview Experience: A difficult HackerRank assessment
I started with a straightforward recruiter call about my background. Soon after, I took a HackerRank coding assessment. It ran about 75 to 90 minutes and had two medium-style questions, closer to LeetCode data structures and algorithms than anything company-specific. One problem involved string and array manipulation. The other relied on hash-map thinking and edge-case handling. The difficulty fe…
Interview experiences · Wayfair
Wayfair Software Engineer Interview Experience — Four-Round Virtual Onsite Rejection
Behavioral round: standard behavioral questions and conversation. Coding: simple coding with no algorithms involved. Calculate moving costs for different items based on their volume and category. The follow-up was how I would implement this in production. I talked about turning it into classes and then discussed object-oriented design. System design: design Shazam, a system that identifies a song…
Interview experiences · Waymo
Waymo Data Scientist Interview Experience — Rare Events, Sampling, and Probability Coding
A recruiter contacted me. After screening and a technical screen, I went into four interview rounds. I've made the original questions less specific for others preparing. Data Intuition, first round A new version performs significantly better in offline evaluation, in simulation, but shows no difference after going live. What could cause that? How would you model a rare event using a log form, and…
Interview experiences · Waymo
Waymo Machine Learning Engineer Intern Interview Experience — K-Means++ Miss and a Trajectory Prediction Question
First round: We just chatted casually at the start — they asked about the project I'd worked on, how big the network was, how many parameters, how big the data was, that kind of thing. I couldn't really remember most of it. Then we moved on to coding k-means. I had to explain what k-means is first, and after I finished writing it, they asked me to write a better initialization method. They gave m…
Interview experiences · Waymo
Waymo Senior Frontend Engineer Interview Experience — Rejected 30 Minutes After Pushing on the Process
I interviewed for a senior frontend engineer role, on the simulation team. Probably not much help to most people but in case someone needs it. Phone screen Part 1 — I don't remember the exact details, but it was related to n-ary tree recursion. Roughly, if a node's value contains a certain substring, you need to remove the entire subtree. Return the filtered tree. Part 2 was building a UI based o…
Interview experiences · Waymo
Waymo Site Reliability Engineer Interview Experience — Rejected After a Rough, Disrespectful Technical Screen
I got rejected. This interview was for an SRE (Site Reliability Engineer) role. The question was roughly this: there's a number line from 0 to 50. Points keep landing on the line, and each point contaminates the region 0.5 to its left and 0.5 to its right of where it lands — i.e., an interval of length 1. Once part of the line is contaminated, it stays contaminated forever. Points can land anywhe…
Interview experiences · Waymo
Waymo Software Engineer Interview Experience — A Four-Round Onsite With Two System Design Problems
A recruiter reached out to me on LinkedIn. Apparently the company's valuation went up 4x earlier this year, so they've been hiring a lot lately. The onsite was four rounds total. Round 1: System Design Design a Matchmaking Service: Join matchmaking queue Cancel matchmaking request Match two compatible players Notify both players when a match is found Handle disconnects and expired requests Round…
Interview experiences · Waymo
Waymo Software Engineer Interview Experience — A Simulation Design Round After a Recruiter Reassurance
Coding: 317. The second problem was traversing a graph with DFS, fairly simple. There was a follow-up: come up with an algorithm to prove your answer is correct. A strange follow-up. Behavioral: Very standard. A project I'm proud of, how to handle priorities, things like that. System design: This was the first round of the interview. What a disastrous start. I was interviewing with the simulation…
Interview experiences · Waymo
Waymo Software Engineer Interview Experience — Navigation Constraints and Mapping Systems
The author lists a Waymo phone screen followed by onsite system-design and coding interviews. The screen involved a robot moving in four directions, returning to its starting point, and avoiding obstacles. The design discussion asked about a vehicle fleet collecting map information. One onsite coding task matched dictionary words against input containing repeated letters. Another used a map with…
Interview experiences · Waymo
Waymo Software Engineer Interview Experience — Phone Screen Passed, Rejected After a Four-Round Virtual Onsite
I got rejected after the full Waymo loop. Posting this so the people after me can avoid the same landmine. Before the interview I looked through the forum and there seemed to be hardly any Waymo reports. After finishing, I do feel there is no fixed question bank, it all depends on what the interviewer feels like asking that day. The phone screen was a variant of the number-of-islands problem, and…
Interview experiences · Weiss Asset Management
Weiss Asset Management Data Scientist Interview Experience — A Power Trading Forecast Case Study
Case study: It was a one-hour interview with two documents to read. The first provided background and a short introduction to the electricity market in power trading. The market participants included ordinary consumers, utility companies, electricity producers, and electricity traders. The basic assumptions were: Electricity prices stayed constant within a day, and ordinary consumers did not chan…
Interview experiences · Wells Fargo
Wells Fargo Credit Risk Modeler Interview Experience — HR Screen, Technical Interview, 48-Hour Take-home Case Study, and Behavioral Fit
Position: Credit Risk Modeler (Associate Level) Location: Charlotte, NC (Hybrid) Rounds: HR Screening → Technical Interview → Case Study → Behavioral Fit Interview Process Recap ① HR Phone Screen (30min) Brief self-introduction, "Why Wells Fargo?" Confirmed my understanding of Credit Risk Modeling (PD/LGD/EAD basics). Asked one behavioral question: "Describe a time you worked with incomplete data…
Interview experiences · Wells Fargo
Wells Fargo Financial Analyst interview: HireVue to superday
After I applied, the process began with a virtual question screen that felt more like a proctored exam than a conversation. I was asked why I wanted the role and then answered many behavioral prompts. It was awkward more than difficult, and I wished it felt more human. That led into HireVue again before anything live. The early video rounds were not very technical; they were mostly open ended and…
Interview experiences · Wells Fargo
Wells Fargo Financial Analyst interview: three structured superday sessions
The process felt organized and standardized, especially at the superday. I completed HireVue and, about a week later, attended an in-person final round with three interviews of roughly 30 minutes each. Two were technical and one was behavioral. Everything ran smoothly, with a familiar rhythm across interviewers. The technical sessions covered accounting and ratios, including debt and equity conce…