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
- Walmart Global Tech Data Scientist interview experienceWalmart Global Tech · Data Scientist · Jul 2026Offer
The process was smooth and professional from the beginning. After the recruiter conversation, the questions stayed focused on what they said they wanted, without drifting into unrelated areas. I appreciated how clear and intentional that made the conversation feel. I had a good back-and-forth and left the call feeling heard. Overall it was a pleasant experience rather than a stressful or chaotic…
- Walmart Global Tech Software Engineer interview: Java design and a virtual onsiteWalmart Global Tech · Software Engineer · Online Assessment · Jul 2026
After a recruiter call, I went through a coding assessment, two technical and behavioral rounds, and a larger virtual onsite. The sequence felt structured. The assessment started with a medium array problem that needed LeetCode-style DSA thinking. Later discussions focused on Java, including SOLID and common design patterns. I also had a high-level design conversation about a Zomato-like system.…
- Walmart Labs Account Executive interview: next-day callWalmart Labs · Account Executive · Other · Jul 2026Offer
After applying, I met in person with two people at the store, a sales manager and a lead cashier. It was a quick, low-stress conversation about ordinary role fit. They asked the usual questions about me, why I wanted to work there, when I could start, my availability, and whether I could handle the schedule. I also had time to ask questions. It felt more like checking whether I would be comfortab…
- Walmart Labs Software Engineer interview: a short virtual coding roundWalmart Labs · Software Engineer · Technical Screen · Jul 2026No response
I applied online and received an email invitation to a virtual interview. During the call, I worked through an easy LeetCode problem that felt similar to 2-sum or a basic array question. I explained the solution during the interview and never heard back afterward. The process was short and uncomplicated, but without a follow-up it felt anticlimactic. There was no clear conclusion to the experienc…
- Walmart Labs Software Engineer interview: compact technical rounds and backend stack discussionWalmart Labs · Software Engineer · Jul 2026
After recruiter-style contact, I entered a compact technical process that felt straightforward and clearly structured. The setup was about 30 minutes for a sequence of technical rounds, with a LeetCode-style problem as the main expectation. Between questions, I was also asked about my work history, resume, and how it mapped to my tech stack, including Kafka, Kubernetes, and Java Spring Boot. The…
- Walmart Product Manager Interview Experience: inconsistent screening and late manager callWalmart Labs · Product Manager · HR Screen · Jul 2026Rejected
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…
- Walmart Supply Chain Software Engineer interview: coding rounds and backend stack discussionWalmart Supply Chain · Software Engineer · Jul 2026
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…
- Walmart Supply Chain Software Engineer interview: easy coding followed by silenceWalmart Supply Chain · Software Engineer · Technical Screen · Jul 2026No response
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…
- WatchGuard Technologies Software Engineer Interview Experience: DSA and detailed project questionsWatchGuard Technologies · Software Engineer · Technical Screen · Jul 2026
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…
- WatchGuard Technologies Software Engineer Interview Experience: Strong technical, nervous manager roundWatchGuard Technologies · Software Engineer · Jul 2026
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…
- Waters Software Engineer interview: selective full-stack and SQL assessment pipelineWaters · Software Engineer · Online Assessment · Jul 2026
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…
- Wayfair Software Engineer Interview Experience: A difficult HackerRank assessmentWayfair · Software Engineer · Online Assessment · Jul 2026
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…
- Wells Fargo Financial Analyst interview: HireVue to superdayWells Fargo · Financial Analyst · Online Assessment · Jul 2026
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…
- Wells Fargo Financial Analyst interview: three structured superday sessionsWells Fargo · Financial Analyst · Onsite · Jul 2026Rejected
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…
- Wells Fargo Software Engineer Interview Experience: Broad assessment and a condescending later callWells Fargo · Software Engineer · Online Assessment · Jul 2026
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…
- Western Digital Software Engineer interview: staff-level leadership assessmentWestern Digital · Software Engineer · Technical Screen · Jul 2026Offer
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…
- Wipro Software Engineer interview: communication-focused easy screeningWipro · Software Engineer · Jul 2026
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…
- Wipro Software Engineer interview: resume-based technical roundsWipro · Software Engineer · HR Screen · Jul 2026Offer
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…
- Wise Software Engineer Interview Experience: A rushed skeleton task with shifting requirementsWise · Software Engineer · Technical Screen · Jul 2026
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…
- Wise Software Engineer interview: supportive pairing and contradictory design guidanceWise · Software Engineer · Technical Screen · Jul 2026
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:…
- Wise. Energy Software Engineer Interview Experience: Rigid technical screens and contradictory role expectationsWise. Energy · Software Engineer · Technical Screen · Jul 2026
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…
- Wise. Energy Software Engineer interview with pair programmingWise. Energy · Software Engineer · Technical Screen · Jul 2026
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…
- Wissen Infotech Software Engineer Interview Experience: DSA, SQL, and graph questionsWissen Infotech · Software Engineer · Technical Screen · Jul 2026
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…
- Wissen Infotech Software Engineer interview: OA, DSA, SQL, and director roundWissen Infotech · Software Engineer · Online Assessment · Jul 2026
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…
- Wissen Technology Software Engineer Interview Experience: Java questions and two programsWissen Technology · Software Engineer · Technical Screen · Jul 2026
My first interview with Wissen Technology was direct and focused. After a brief introduction, it moved quickly into Java questions and two Java programs for me to implement. The conversation lasted about an hour. It was a good experience overall. The pacing was not awkward, and nothing made me feel completely unprepared. I did not get an offer, but the round was clear and structured, and I unders…
- Wix Software Engineer interview: timed LeetCode exam and system design follow-upWix · Software Engineer · Onsite · Jul 2026
I went through a tight technical process that began with an onsite LeetCode-style exam. It lasted about two hours and included a warmup plus easy, medium, and hard questions. The structure matched what I had been told to prepare for. I did not feel rushed when I finished, but the main challenge was getting the medium and hard questions right under the clock. After the exam, I interviewed with dev…
- Wolverine Trading Software Engineer interview experienceWolverine Trading · Software Engineer · Online Assessment · Jul 2026
After applying, I was sent to an online OA on CoderByte. It involved object-oriented coding and trading-flavored logic, including registering and monitoring stock pairs and reporting when their price relationship moved beyond a tolerance. The specification was long, so careful reading mattered more than finding a trick algorithm. I spent most of my time translating requirements into code. The nex…
- Wolverine Trading Software Engineer interview: CoderByte trading assessmentWolverine Trading · Software Engineer · Online Assessment · Jul 2026Rejected
An early conversation led quickly to a CoderByte assessment built around trading concepts. The coding was lighter than the systems-style prompts I had seen elsewhere, but it depended on using the right trading vocabulary and mapping it to simple logic. Timing and execution made the difference, and the platform's format pushed me to be precise. The live coding interview gave me more room to explai…
- Wolverine Trading Software Engineer interview: OOP clarification with a helpful interviewerWolverine Trading · Software Engineer · HR Screen · Jul 2026
My process felt straightforward end to end. After an initial recruiter-style conversation, I had a quick early exchange where I introduced myself and answered an OOP-oriented question. The process felt professional. The interviewer was clear about the specification and helped me work through what they expected, so it felt more like collaborative clarification than a gotcha. It was what I expected…
- Wood Consulting Software Engineer interview: a short Teams conversationWood Consulting · Software Engineer · HR Screen · Jul 2026
I had a 30-minute Teams interview with one other person. It felt more like working through a checklist than having a conversation. The questions were mostly generic competency and HR questions, with a few technical ones mixed in. What stayed with me was the interviewer’s manner. I did not feel as though they were really listening to my answers, which made the conversation feel one-sided and uncom…
