READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 15 of 153
Interview experiences · AkunaCapital
AkunaCapital Quantitative Analyst interview experience: probability screen after timed assessments
My process had several online stages before I spoke with anyone live. The assessment setup combined coding with a video interview, where I worked through math and probability questions while explaining my reasoning. The timing was tight enough that I had to be deliberate, though it felt relevant to the work expected of a quantitative researcher. After those assessments, I had a technical screen c…
Interview experiences · Alarm
Alarm Software Engineer interview: scripted questions that missed the project context
I had a multi-stage process that felt more about vibe than deep technical evaluation. It began with a recruiter conversation about my resume and work history, plus a brief sense of what the role required. The technical interview did not match my background well. It felt rigid and disconnected, and the interviewer repeatedly asked about things already clear on my resume. The behavioral questions i…
Interview experiences · ALDO Group
ALDO Group Account Executive Interview Experience: helping a customer choose shoes
After a simple start, I had a friendly video or in store conversation with a store manager. It was relaxed, and I had time to ask questions, but it was still structured enough that I understood what they wanted. We discussed the role, the day to day work, why I wanted the position, and why I was leaving my current job. The manager also asked how I would handle an upset customer or help someone ch…
Interview experiences · Alibaba Group
Alibaba Group Account Executive interview: CV, motivation, and office-lead discussions
I started with a brief introductory conversation focused on my CV. The hiring-manager conversation was straightforward: we spent about 20 minutes reviewing my background and discussing my perspective based on what I had written. I later had a separate conversation about motivation and intent. The questions were meant to understand who I was, why I wanted the position, and how serious I was about…
Interview experiences · Align Technology
Align Technology Software Engineer Interview Experience: A checkbox-style recruiter screen
My first touchpoint was a screening call with the HR recruiter, and it did not feel like a real conversation. It seemed low-effort and unprofessional, more like filling out a multiple-choice form than someone actively assessing me. Instead of interactive questions or a back-and-forth about my background, the recruiter appeared to be checking boxes. That immediately made the process feel less resp…
Interview experiences · Align Technology
Align Technology Software Engineer interview: project discussion and a riddle
The technical screen began with a discussion of a project I had worked on. I had to explain the algorithms I used and how the system worked. Then I was given a real-world riddle connected to the job description, which felt like a curveball after the project deep dive. The first part was a direct conversation about engineering choices; the puzzle asked me to reason aloud with more ambiguity. Overa…
Interview experiences · Ally Financial
Ally Financial Financial Analyst Interview Experience: A short HireVue with no closure
My first step with Ally Financial was a self-recorded HireVue-style video interview. I recorded an introduction and answered a handful of behavioral prompts. The format was lightweight and straightforward, with no technical questions. It still created pressure because I had limited attempts for each answer and had to redo recordings when something came out awkward. The prompts were mostly "tell m…
Interview experiences · ALSTOM
ALSTOM Software Engineer interview
After I cleared the first technical screening, things moved quickly. The test produced a very large shortlist, and I was invited to an in-person group discussion on online versus traditional education. In that setting, they seemed to be watching how I reasoned and communicated. The technical interview lasted about half an hour. I began with my projects, then answered basic questions tied to what…
Interview experiences · ALSTOM
ALSTOM Software Engineer Interview Experience: aptitude test, group discussion and technical selection
I started with a computer-based aptitude test. It felt straightforward enough to settle into a rhythm, and I saw it as the first real filter. Only candidates who passed moved on. I was then called for a group discussion. There was another shortlist after the discussion, followed by a technical interview. After the recruiter-style stages and technical evaluation, I had a final one-to-one interview…
Interview experiences · ALSTOM
ALSTOM Software Engineer interview experience: direct manager outreach
A manager contacted me directly, and we met for an interview. The conversation felt fine, but there was no follow-up afterward. I sent a thank-you email, applied for another opening, and resent my application to the same manager, yet still heard nothing. I tend to go deep into details, and I can see how that may not have fit their preferred pace. Still, the bigger issue was the lack of closure or…
Interview experiences · ALSTOM
ALSTOM Software Engineer interview: technical qualification and onsite
After a few weeks, I was contacted to confirm a face-to-face meeting with project managers and HR. The process began with a recruiter phone call of about twenty minutes, then a qualification technical discussion with the manager by video. I later had an hour-long talent-acquisition video call about my motivation, understanding of the role, English, and previous experience. The final onsite includ…
Interview experiences · Altec Industries
Altec Industries Software Engineer interview: plant tour and cross-department conversations
After applying, I received a call scheduling an onsite a few weeks later. The day began with a plant tour, followed by short meetings with managers from different engineering areas, each taking about half an hour. The conversations covered fit, daily work, and behavioral examples about challenges, teamwork, stress, and my work history. The process gave me a view of the whole operation. I met peop…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer army-mission mismatch and no follow-up
I did not get far at first because my context did not match what was available. After I applied, the only missions offered were related to the army, and I chose not to continue beyond that initial stage. Later, I did have a phone interview about my professional project and goals, so there was an effort to understand where I was coming from. Afterward, I was told they would get back to me when a s…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer early HR process experience
I only reached an early, administrative part of the process. The first HR phone call was meant to make contact and begin the application. A second HR call was set up to schedule a skills demonstration. Logistics problems prevented me from continuing after that point. The early contact was straightforward, but the process never reached a deeper evaluation. It felt as though the application stopped…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer Interview Experience: A friendly start that drifted from cyber to DevOps
My experience was quick and simple at first. I had a straightforward conversation about my skills, and I got the impression that they were trying to place me on a project that matched them. The tone was friendly and positive, without feeling overly formal. Later, though, the process felt misleading. I was invited to talk about cyber, but I ended up in a conversation that felt more related to DevO…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer Interview Experience: A technical meeting where no one joined
My process started badly. The first HR interaction was not really an interview to assess my skills. It felt like a briefing for what would come next. Then I showed up on time for the second technical meeting, waited about an hour, and nobody joined. I reported it immediately, but I received no apology, explanation, or clear reason for the time I lost. Even after following up, I heard nothing. The…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer Interview Experience: business manager interview never happened
The process began with HR reviewing my profile, contacting me, and arranging an introductory call. That conversation covered the basics and gave me the main information about the role and process. I was then scheduled to meet the business manager. The frustrating part was the scheduling. The business manager interview was postponed several times because of the manager's commitments, and it ultima…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer Interview Experience: Four steps from recruiter to contract
After the recruiter stage, the process followed a clear four-step rhythm. It began with a short introductory call about my background and fit. About a week later, I had a semi-technical remote interview that assessed how I could operate in the role without trying to trap me. Next came a more complex remote technical interview with the client. It was more serious and detailed but remained professi…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer interview experience: technology-list coding game
The assessment began with a coding exercise. I received a technology list by email and used it to complete a coding game, which made the technical portion self-directed while still requiring me to implement something. Afterward, I spoke with the recruiter about available projects. That discussion gave the technical work context and suggested there could be a way to match me with an appropriate pr…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer interview: ten-minute introduction
After an initial recruiter call, I had an online meeting with a business manager. We discussed my experience and skills, as well as how I would learn and fit with the company. The tone was direct and practical. I began with about ten minutes to talk about myself, then the conversation moved into follow-up questions. It was not a deep technical dive. It was a structured way to understand my backgr…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer interview with a five-day backend assignment and client loop
I didn't apply directly. Alten contacted me through LinkedIn, and what was described as a one-time track became much longer than I expected. The recruiter said my profile would remain in their database for future opportunities even if I didn't join, but then the interviews kept stretching out. I started with a brief HR screen, then met with a backend technical lead. That round went well, and I go…
Interview experiences · ALTEN Belgium
ALTEN Belgium Software Engineer interview with one-week profile check
The interviews felt intentionally light. I got the sense they wanted to confirm that my profile matched what they needed rather than test technical depth. The early conversations were about fit and discussion more than whether I could do the job at a technical level. The process moved quickly. I first had a phone contact to validate my profile and discuss salary, then spoke with the responsible m…
Interview experiences · Alten Delivery Centre Spain
Alten Delivery Centre Spain Software Engineer interview: client-mission fit
I first spoke with a recruiter about my background, then we discussed how my profile fit the work they were seeking. Even though it was an initial conversation, they followed up on what I had said with more detailed questions. I then spoke with the relevant business manager and, finally, had a technical interview with the client. The discussion centered on how I related to the planned work and th…
Interview experiences · Alten Delivery Centre Spain
Alten Delivery Centre Spain Software Engineer Interview Experience: a backend task and disorganized client preparation
They contacted me on LinkedIn even though I hadn't applied. HR described a more one-time process and said my profile would stay in their database for future opportunities even if I decided not to continue. It sounded simple at first. In practice, it took much longer and was less organized than they'd led me to expect. I started with an HR screen and an interview with a backend technical lead. Tha…