READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 36 of 153
Interview experiences · Attentive
Attentive Software Engineer Interview Experience: role closed after the phone screen
I started with an initial phone screen. After that, I expected a fairly standard sequence: a second round with coding and system design, a third round with more of the same assessment, and then a meeting with the team. The role closed before the process could get that far, so I never reached those later rounds. It left me feeling as though the interview process was just about to expand, and then…
Interview experiences · Attentive
Attentive Software Engineer Interview Experience — Two Onsite Rounds and an Unexpected Catalog Design
I was contacted and invited to an onsite. Round 1 combined coding and system design. Round 2 included coding, system design, and behavioral questions. I felt that my system design and behavioral performance in Round 2 was poor, and I was ultimately rejected. There were not many interview reports about this company, so I summarized everything I could find. All the questions I received turned out t…
Interview experiences · Aubay Spain
Aubay Spain Software Engineer interview experience: Java, Spring, SQL, and Docker
The process began with a formal HR discussion of my background, motivations, and the professional projects I wanted next. I also received an overview of the company and its opportunities. Afterwards, I took an in-office technical test in Boulogne-Billancourt. That was the difficult part. It covered Java, Spring, SQL, and Docker backend fundamentals through knowledge checks, practical exercises, a…
Interview experiences · Aurecon
Aurecon Software Engineer interview
I completed a one-way recorded interview, then was invited to meet several people from the team in person. HR scheduling moved quickly. Some people were relaxed and conversational, while other parts of the day felt more formal. The in-person questions were mostly behavioral. I discussed my background, working with others, and handling disagreement or conflicting ideas with colleagues. In one scen…
Interview experiences · Aurecon
Aurecon Software Engineer Interview Experience: AI-marked video and engineering email tasks
I completed a HireVue-style process with an AI-marked video component and an extended-response question. I had to read an email from a manager, then give feedback on the possible risks and benefits of an engineering decision. It was an applied judgment test, not only a chance to talk about myself. The process also had short video introductions, extra prompts paired with multiple-choice items, and…
Interview experiences · Aurecon
Aurecon Software Engineer Interview Experience: one-way video answers with re-recording
After I applied, I received a one-way video interview prompt. I had to record answers to several questions and submit them quickly, with responses capped at about a minute. At first it felt like a single pass, but I learned that some questions allowed re-recording, so I could review an answer and do it again. Before the video portion, there was an online step with a few yes-or-no questions. The H…
Interview experiences · Aurora Innovation
Aurora Innovation Cloud Engineer interview, C++ and system design
After connecting through the recruiter, I moved through a structured process: a recruiter call followed by technical discussions, system design, and coding. The recruiter and interviewers kept the tone comfortable, and I felt they were genuinely interested in how I’d approach realistic work scenarios instead of searching for one exact answer. The onsite lasted a few hours and included several tec…
Interview experiences · Aurora Innovation
Aurora Innovation Software Engineer 60 to 90 minute Python CoderPad
My interview process had five steps in a clear order, so the timeline was easy to follow. It began with an online Python CoderPad homework assignment that took about 60 to 90 minutes. After that, I had a 30-minute hiring manager interview. Next came a short prep call with the recruiter, followed by a two-hour virtual interview. The final step was the offer decision, and it didn't go my way. What…
Interview experiences · Aurora Innovation
Aurora Innovation Software Engineer: Coding Interview Passed, No Offer
My interview started with a behavioral phone screen, followed by a behavioral conversation with a tech lead and then a coding interview. Everyone I spoke with was genuinely nice and seemed passionate about the project. The overall vibe felt supportive instead of combative. I passed the coding interview, which made me feel optimistic about the later stages. Even so, they chose another candidate. T…
Interview experiences · Aurora Innovation
Aurora Innovation Software Engineer interview: DSA round and two coding onsite rounds
I went through an intensive process that began with a DSA round and continued with several onsite interviews. I remember the onsite as multiple rounds with different evaluators, including two coding rounds and an HR discussion. The interviews weren’t easy. I prepared from the job description because the expectations were clearly tied to the actual responsibilities. The coding rounds and HR conver…
Interview experiences · Aurora Innovation
Aurora Innovation Software Engineer interview, visa sponsorship
The process started when the hiring manager reached out directly for basic details, including my background and visa status. When I said I’d need visa sponsorship, I was told they’d have to double-check. A few days later, I heard that they couldn’t sponsor, and the process ended there. It was short and abrupt, with the outcome determined more by eligibility than interview performance. I didn’t ge…
Interview experiences · Aurora Innovation
Aurora Innovation Software Engineer interview with a 45-minute graph traversal screen
I went through a direct, coding-focused process that came down to timing. After speaking with the recruiter, I completed a coding screen on a CodePad-style platform. I couldn't finish the DSA question within the 45-minute window, so the process stopped there without an offer. The most frustrating part was how close it felt. I knew which direction to take, but I couldn't turn that approach into a…
Interview experiences · Aurora Innovation
Aurora Innovation Software Engineer interview with four virtual onsite rounds
I started with a recruiter call, followed by a technical discussion with the hiring manager. There was no coding in that round. We talked through my experience and how it fit the role. After that, I had a DSA-style technical round with one coding problem that didn't feel especially hard. The virtual onsite had four rounds: a behavioral interview with the hiring manager, a technical interview abou…
Interview experiences · Aurora Innovation
Aurora Innovation Software Engineer interview with unpredictable hiring-manager criteria
My hiring manager interview stood out because it felt unpredictable and, frankly, capricious. I had more directly relevant experience and stronger credentials, but the conversation didn't reflect that consistently. The recruiter experience also differed from what I expected. I felt pushed to frame the process in a way that didn't match how I believed they were judging fit. By the end, it was clea…
Interview experiences · Aurora
Aurora Senior Machine Learning Engineer Interview Experience — Grilled on Using LLMs to Drive Self-Driving Cars
I interviewed with Aurora for an MLE role. Overall the questions were pretty middle-of-the-road and not really that hard. Maybe I just wasn't prepared enough and didn't manage to wow them. The senior package can only go up to about 500k at most, which maybe isn't all that attractive either. The question that came up the most in the interviews was how to use LLMs in autonomous driving, how to use…
Interview experiences · Autodesk
Autodesk Software Engineer interview: assessment and silent follow-up
I started with an online test scored out of 600. After clearing it, I had two technical interviews covering programming and SQL, which felt aimed at practical breadth rather than theory. After the second technical round, my college placement channel gave no clear update. I had also seen another process path with a resume-screening call, an OA, and onsite interviews that was described as average d…
Interview experiences · Autodesk
Autodesk Software Engineer Interview Experience — A Project Deep Dive and Real-Time Data System Design
Only two rounds in total First round: project deep dive Second round: system design - "Design a real-time data processing system that consumes changes from operational databases, combines data from multiple sources, and maintains a queryable output dataset with low latency. Walk through the architecture you would choose and how you would handle correctness, updates and deletes, ordering, state, f…
Interview experiences · Autodesk
Autodesk Software Engineer interview: full-stack development and agentic AI deep dives
The hardest round for me involved designing a full-stack web application in React and Node.js. I had to write frontend and backend code and cover API design in about two hours. Everything felt tightly timed. Coordinating the architecture from end to end added to the pressure of writing the code. Another technical session lasted three hours. The first half was technical and the second was behavior…
Interview experiences · Autodesk
Autodesk Software Engineer interview: longest-substring DSA screen
After a recruiter call, I entered a structured sequence. I started with a short introduction about a university or personal project, then had a technical screen with one medium-level DSA problem: finding the longest substring without repeating characters. The interviewer followed up on complexity, edge cases, and possible optimizations. Later, I went through a deeper track with senior and princip…
Interview experiences · Autodesk
Autodesk Software Engineer interview with shifting expectations
The process began reasonably but became confusing when it mattered. In a coding round, I solved a straightforward problem, yet the expectations kept changing. After I had a working solution, the interviewer shifted the problem and pushed toward more abstract architecture improvements without explaining the criteria. It felt as if a particular end state was expected instead of an open engineering…
Interview experiences · Automatic Data Processing
Automatic Data Processing Account Executive Interview Experience: Behavioral structure, sales scenarios, and STAR reflection
My recruiter conversation set the tone for a straightforward process. We discussed expectations and my past experience, and after the call went well I moved to a one-on-one interview with higher-ups. That part felt strong, and I left feeling that it had clicked, though I was then waiting for next steps. The format varied, but each stage relied on prepared questions. In a roughly half-hour Zoom in…
Interview experiences · Automatic Data Processing
Automatic Data Processing Account Executive Interview Experience: manager discussions and a team shadow
After I applied, a recruiter called to set up an initial phone conversation. That led to an interview with a director, followed by office discussions with Sales Executive managers. Those conversations focused heavily on my sales history and behavioral questions, so I had to explain what I had done and how I approached selling. I then shadowed a team member, which was a welcome surprise. It felt l…
Interview experiences · Automatic Data Processing
Automatic Data Processing Account Executive Interview Experience: recruiter no-show and delayed feedback
The process looked as though it would go smoothly at first, but the timing and communication soured it. I had gone through a couple of interviews out of college and did not get the role. That was disappointing but fair. About two years later, a recruiter contacted me on LinkedIn to reconnect and set up an interview. The recruiter then failed to show up without an explanation, which felt unprofess…
Interview experiences · Automatic Data Processing
Automatic Data Processing Account Executive Interview Experience: second video interview with a decision pending
I was still in the interview process when I shared this. A recruiter had contacted me, and I had completed an initial interview with a kind interviewer. My second conversation was a video meeting and felt like a normal next step. There was not much more detail beyond the process moving forward and being enjoyable so far. At that point, I felt positive enough to continue and comfortable rather tha…