READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 150 of 153
Interview experiences · Wissen Technology
Wissen Technology Software Engineer Interview Experience: Java questions and two programs
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…
Interview experiences · Wix
Wix Software Engineer interview: timed LeetCode exam and system design follow-up
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…
Interview experiences · Wolverine Trading
Wolverine Trading Software Engineer interview: CoderByte trading assessment
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…
Interview experiences · Wolverine Trading
Wolverine Trading Software Engineer interview experience
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…
Interview experiences · Wolverine Trading
Wolverine Trading Software Engineer interview: OOP clarification with a helpful interviewer
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…
Interview experiences · Wood Consulting
Wood Consulting Software Engineer interview: a short Teams conversation
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…
Interview experiences · Wood
Wood Software Engineer interview: Teams competency discussion
After a recruiter conversation, I moved quickly to a Teams video interview with one interviewer. It lasted about 30 to 45 minutes and began as a competency and HR-heavy discussion, with some job-related technical questions. We talked mainly about my background, motivation, and how my experience fit their work. The tone was conversational. Technical discussion was manageable and centered on what I…
Interview experiences · Workday
Workday Account Executive interview: deal review and leadership interview
After a casual recruiter-to-hiring-manager conversation, I did a deal review with a panel. I walked through my sales experience and execution, turning my background into a clear account of what I had done and how I would drive outcomes. The next step was an interview with hiring leadership, which focused more on judgment and fit than on repeating those sales stories. The process followed a standa…
Interview experiences · Workday
Workday Software Engineer interview experience: REST APIs and internship leadership
The first step was meant to be a recruiter screen, but a technical staff member conducted it. I began with the usual behavioral introduction, and the conversation soon shifted into technical territory. They asked about my resume, REST APIs, and leadership examples from my most recent internship. Although the opening sounded as if it would be light, the later questions checked both how I communica…
Interview experiences · WorldQuant
WorldQuant Intern Quantitative Researcher Interview Experience — Round One, All Behavioral and Math, No Coding
Hiring process There are three rounds of interviews in total. This is round one. Behavioral questions Self-introduction Why WorldQuant? Why do you want to do Quant? Introduce your most relevant project Future plans Vague goals vs. specific goals Math questions First question: the child-birth problem A country has a rule: every family keeps having children until the last child is a boy, then they…
Interview experiences · WorldQuant
WorldQuant Quantitative Analyst interview: probability, math, and light coding
After recruiter outreach, I entered a straightforward early loop. I discussed previous work and what I would do in scenarios. The technical prompt was a live-coding-style question that felt fairly easy compared with what came later. Soon afterward, I completed an online round with math-focused, probability-style questions and some light coding. It was clearly about math and probability, but it di…
Interview experiences · WorldQuant
WorldQuant Quantitative Researcher Intern Interview Experience — Round Two Expected-Value Brainteasers
The whole process has three rounds of interviews. This is round two. Interview content Behavioral Self-introduction How much I know about WorldQuant Walk through my past internship experience What I know about finance and investing Can you talk about your own investing experience? Why did you start investing? What did you learn from investing? Math questions Problem 1: Four boxes There are four b…
Interview experiences · Worley
Worley Software Engineer interview: standard questions, poor delivery
The interview itself was fairly standard. It leaned on behavioral questions about what motivated me to join and how well I understood the company. I would rate the difficulty around average, but the logistics changed the tone. The interviewer arrived late. Once we started, the questions were delivered so mechanically that it never became a natural back-and-forth. That made it harder to connect th…
Interview experiences · Woven By Toyota
Woven by Toyota 2 YOE Onsite
Two coding rounds. First question was a merge intervals variant dressed up as “Detect attacks along a horizontal line from 0 to 10.” The idea being you have a list of ‘attacks’ represented as intervals of integers/floats (e.g. [1, 2], [3.4, 5.2], and you need to merge the attack intervals to determine T/F representing if the horizontal line was attacked/blanketed in its entirety. Second question…
Interview experiences · WSP
WSP Software Engineer interview: timed video assessments
My process began with a video interview and quickly moved to assessments. In a HireVue-style format, I recorded webcam responses to prerecorded questions. Each prompt allowed a short preparation window before a timed answer. The questions covered behavioral experience, motivation for the role, and interest in the energy sector. There was also a test-like cognitive component with timed numerical,…
Interview experiences · WSP
WSP Software Engineer interview with CV-based technical discussion and an in-person second stage
After a recruiter touchpoint, I had a direct technical interview that began with a quick look at my background. There were a few behavioral questions, but most of the session became a technical discussion based on the projects on my CV. I also talked about the work they were doing and what I might handle at the beginning. The process had an initial online discussion and then a second stage in per…
Interview experiences · WTW
WTW Financial Analyst interview with actuarial knowledge assessment
I sent in my CV, then had a short telephone personality interview. That was followed by an in-person round on actuarial knowledge and an aptitude test in the same area. The process had three clear stages and seemed designed to filter quickly on technical fit. The first step was more about personality, but the later stages put pressure on my actuarial fundamentals. By the in-person assessment, the…
Interview experiences · xAI
xAI Machine Learning Engineer Interview Experience — Passed a 15-Minute Vibe-Check Call
xAI's 15-minute call. The interviewer started by introducing himself and giving a quick overview of the team. Then I introduced myself, talked about what I'm working on right now, and went deep into my project — walked him through the whole thing end to end. He asked about challenges and I answered that too. After all of that, he suddenly threw in a more basic question: what's the difference betw…
Interview experiences · xAI
xAI Machine Learning Engineer Interview Experience — Three Tech Rounds in Two Days, Rejected at the Offer Stage
I got a reach-out this September. I'd heard Elon's company pays really well, so I did a phone screen with the company. It was 15 minutes: we introduced ourselves, then they had me walk through how I collected and processed the data for a project on my resume, followed by some questions about how I think about data vs. downstream task impact. We went a bit deeper into some technical questions from…
Interview experiences · xAI
xAI Software Engineer Interview Experience: a rushed rocket simulation
After the recruiter step, I had a technical interview that felt medium to hard. The main task was a simulation that involved moving a rocket in a game like setting. I understood the idea and made progress, but the time box was brutal for implementing it cleanly. I ran out of time before I could make the solution fully correct and complete. It felt as though the target was polished execution, not…
Interview experiences · xAI
xAI Software Engineer Interview Experience — HC Canceled the Night Before, Rerouted to a Rushed 15-Minute Coding Screen
I applied on a whim to a network-related infra role. A coordinator reached out afterward. They do have a recruiter, but I only got one on the line when I asked about salary and the RTO policy. No exaggeration: this company runs 60-hour weeks as the baseline, and 80-100 hours isn't a dream scenario, it's normal. Basically Palo Alto RTO5. Interview process Originally the network team's hiring manag…
Interview experiences · xAI
xAI Software Engineer interview: final-stage silence
The process ended strangely. I felt that I had done well and reached a final interview stage. Nobody promised me anything, but the momentum seemed positive. About a week and a half later, I followed up and never heard back. That lack of closure stayed with me more than anything that happened during the interviews. Even after a smooth process and a final-stage appearance, the silence left me frust…
Interview experiences · xAI
xAI Software Engineer interview: language-model take-home
My process centered on a take-home assignment and a live follow-up. The topic was a Python language-model application. Before writing code, I had to explain at a high level how the language model worked and how that understanding applied to the specific context. In the live portion, I filled in a function based on what the application needed. They seemed to care about correctness and clarity in c…
Interview experiences · xAI
xAI Software Engineer interview: power-systems questions and an onsite presentation
My interview journey was compact but all over the place in what I was expected to handle. I began with a general manager conversation about the company and team, starting with my resume. That lasted about half an hour. Then I had a technical discussion on electrical-engineering power-systems topics that also lasted about half an hour. It was a crossover rather than a purely software-oriented conv…