READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 34 of 153
Interview experiences · Arup
Arup Software Engineer Interview Experience: project and internship discussion with another round pending
I introduced myself, then answered questions about my projects and internships. My supervisor explained the kinds of tasks the team handled, which gave the conversation useful context. The meeting felt positive and welcoming, as though the interviewer wanted to understand my background and fit. It was not the final round, though. I was told another interview was still to come, so the process rema…
Interview experiences · Arup
Arup Software Engineer Interview Experience: structural diagrams in written exam
My process had a written exam followed by a follow-up interview. The exam covered foundation and superstructure knowledge and often required diagrams of structural systems, including BMD-style sketches. I knew I needed time to prepare, so I treated the written portion as the main hurdle before the interview. After the exam, I moved to the follow-up conversation. That stage was more about walking…
Interview experiences · Arup
Arup Software Engineer Interview Experience: two-hour technical test and face-to-face interview
About a month after I applied online, I received an email invitation saying the process would take around two hours. It combined a technical test with a face-to-face interview. The invitation did not give me much more detail, but the structure was clear: a short technical portion followed by a direct in-person conversation. My impression was that they wanted to assess both capability and how I ca…
Interview experiences · Asana
Asana Account Executive interview with six stages and a final presentation
I went through an intense, multi-step process that felt excessive for the role. After speaking with a recruiter, I had several interview rounds with detailed technical questions. The process stretched across six stages, ending with a 45-minute presentation that required a lot of preparation on top of everything else. I passed every stage with positive feedback and felt that the conversations were…
Interview experiences · Asana
Asana Software Engineer coding interview with no feedback before rejection
I started with an initial screening that left me genuinely excited about the opportunity. The technical part didn’t match what I expected from the preparation materials. Instead of feeling like a collaborative back-and-forth, the interaction was noticeably less engaging, and the interviewer’s involvement felt minimal. I didn’t receive feedback after the coding interview, so the uncertainty dragge…
Interview experiences · Asana
Asana Software Engineer interview: CodeSignal, coding round, and onsite
The process started with a CodeSignal assessment, followed by a dedicated coding round. After that, I attended an onsite that included system design and a behavioral interview, all in a fairly standard sequence. The questions leaned toward LeetCode, but they didn't feel too extreme. Many covered the kinds of problems I could find online with the right search terms. I didn't move forward, although…
Interview experiences · Asana
Asana Software Engineer Interview Experience — Two Onsites, Rejected Over "Communication Clarity"
Round 1: Given two code snippets and asked what they do, plus their time/space complexity Jigsaw Puzzle design — the forum said pseudocode was fine, but the interviewer still made me pick a language and write actual code Round 2 (split across two days): Ascii Printer: 1 hour of coding (the last 45 minutes the interviewer asks questions about your code). A handful of functions to implement. A 10x6…
Interview experiences · Asana
Asana Software Engineer interview: six-step Salesforce-focused process
My interviews followed a longer, structured process with six steps and plenty of feedback between rounds. Everyone I spoke with was professional and attentive, and the process never felt chaotic or improvised. The technical portion was for a role related to Salesforce development. The topics were what I expected: async processes, bulkification, trigger contexts, and the relevant syntax. The round…
Interview experiences · Asana
Asana Software Engineer interview: two-hour OOP coding session
My process started with a coding round, followed by a system design round, and then security became part of the evaluation too. After that, I had a longer, two-hour coding session focused on OOP. That coding block was less about solving one algorithm and more about writing classes and methods, then explaining my logic and time complexity. I had to talk through my thinking as I worked, not just pr…
Interview experiences · Asana
Asana Software Engineer interview with a referral
My process was short and ended quickly. It started with an HR introduction call focused on standard resume and experience questions, along with how my background fit the role. It didn't feel like much of an exploration of my strengths or working style. The call felt more like someone moving through a checklist. Because I had a referral, the conversation also felt somewhat ceremonial. After the HR…
Interview experiences · Asana
Asana Software Engineer interview with a specific systems modeling problem
The overall experience felt professional, and most of the rounds ran cleanly. One interviewer came across as standoffish, which threw me off more than anything technical, but the logistics and tone were mostly well handled. The part I struggled with was the systems interview. It involved a very specific modeling problem that didn't resemble the general patterns I expected. Unless I'd previously b…
Interview experiences · Asana
Asana Software Engineer interview with repeated rescheduling
From the beginning, the scheduling and communication felt unreliable. I had multiple rounds where steps seemed to be skipped without much explanation, and I kept waiting for the next stage to move forward. Several interviews also had to be rescheduled because the interviewers didn't show up at the scheduled times. One HR conversation felt mostly like a checklist. The questions seemed to come from…
Interview experiences · Asana
Asana Software Engineer interview with roughly six rounds
My interview process felt well organized overall and took place over about two weeks, with roughly six rounds. The interviewers were friendly and collaborative, and the questions generally matched what I had seen mentioned elsewhere, including coding and design topics related to the role. I received a rejection with a list of areas to improve. That was discouraging because when there are several…
Interview experiences · Asana Spa
Asana Spa Software Engineer Interview Experience: Chasing a delayed rejection
The first stage seemed promising, but the process dragged on longer than it needed to. After the interview, I realized I had effectively fallen through the cracks in their system and had to chase for a status update. There was no clear communication cadence. I had been told I would hear back within a certain timeframe, but the delay continued. When a response finally arrived, it was essentially t…
Interview experiences · Ascendion
Ascendion Software Engineer interview: fair project questions followed by silence
After a recruiter call that pressed for immediate availability, I interviewed that same afternoon. Later, I was told to be ready for a final round in June, so I waited for the next update. What followed was a long silence. After the final-round readiness message, I did not get meaningful updates, and by late July the process still felt unresolved. The uncertainty weighed on me because it gave me…
Interview experiences · ASM
ASM Software Engineer Interview Experience: low-pressure presentation and management discussion
The first round gave me an early sense that this would be a low-pressure process. It wasn't technical grilling. I mainly described my previous job and discussed what the role would involve. Shortly afterward, I had a final conversation with top management. It leaned toward explanation and discussion rather than trying to catch me with specific technical questions. The tone stayed straightforward…
Interview experiences · ASM
ASM Software Engineer interview: resume presentation and CS fundamentals
After a quick recruiter touchpoint, I had a 60-minute Teams interview with two senior software engineers. We began with my resume and projects, including questions about what I had built and how I approached it. Then we covered several straightforward CS fundamentals and finished with a manageable coding challenge. Later rounds followed a similar pattern: a short presentation about my work, follo…
Interview experiences · ASML
ASML Customer Success Engineer interview with an early end and a separate video assessment
The interview got off to a rough start and threw me off right away. The meeting felt awkward and rushed, and I didn't think the interviewer had strong practical familiarity with the job details we were discussing. The conversation barely moved beyond basic prompts, and it ended earlier than planned. I didn't feel I had a fair chance to engage. I had expected a deeper evaluation, but the interview…
Interview experiences · ASML
ASML Software Engineer interview: a single-attempt HireVue video screen
I started with a HireVue video round where I recorded answers to a few prompts on my own time. It was straightforward and low stakes, mostly common questions about me rather than deep technical material. The unusual part was talking to a camera instead of a person, but the questions did not ask for anything unexpected. The format was consistent: short preparation, a brief response window, and one…
Interview experiences · ASML
ASML Software Engineer interview: automated and face-to-face rounds with candid expectations
I went through several rounds, with some parts automated and others happening face to face. The process moved at a deliberate pace, as if they were taking time to assess whether I matched the company and the role. What stood out was how openly they described their expectations. The conversations addressed what the position would require and how their view of fit compared with mine. I didn't menti…
Interview experiences · ASML
ASML Software Engineer interview: disengaged manager call
After waiting a while after applying, with the first interview in May and then a long silence, I eventually had another virtual interview with the hiring manager. It was scheduled for 45 minutes but did not feel balanced. The manager asked one question early, then spent most of the call talking about himself and the role. When I spoke, he appeared to be looking at another screen and typing. That…
Interview experiences · ASML
ASML Software Engineer interview: HireVue assessment and one-hour backend and Java discussion
My first step was a video assessment, followed by a more direct interview with team members. The video round felt like a standard HireVue-style screening. I had to record responses and keep my answers focused. After that, I had a one-hour conversation with two people, focused on backend work and Java. What I remember most about the hour was that it centered on what I could talk through, especiall…
Interview experiences · ASML
ASML Software Engineer interview: HireVue, coding test, and senior-engineer discussion
My process was fairly compact. I started with a HireVue round where the system recorded my responses, although there was no strict time limit for each answer. It was a set of questions about me, and then the process moved quickly to a more traditional technical conversation. The second round included a group-style meeting with two senior engineers, along with a coding test. I was nervous about th…
Interview experiences · ASML
ASML Software Engineer interview: HireVue screening on experience, company knowledge, and logistics
After applying, I was contacted and moved into an AI interview on the HireVue platform. The prompts were fairly broad. They covered my experience in the role, what I knew about ASML, and logistical considerations. The questions were clear enough, but I didn't progress beyond that stage. I came away feeling that the screening was designed to cast a wide net rather than explore any particular techn…