READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 82 of 153
Interview experiences · Macquarie Group
Macquarie Group Software Engineer interview with a rushed whiteboard discussion
The process opened with a screening step and then a technical interview. The recruiter and interviewers were professional and friendly, but the logistics got muddled. My discussion started late, then felt rushed once it began, which threw off the timing. The technical part relied heavily on whiteboarding. It was not only about writing code. I was asked to reason about engineering and architecture…
Interview experiences · Management Solutions
Management Solutions Data Analyst case and partner interview experience
The process began with a group practical-case exercise. We were given a scenario and had to solve it as a team by agreeing on and refining a proposal. After that I had an HR interview about my background, how I thought during school, subjects I liked, and how I organized myself. Then came a technical interview and, finally, a meeting with a partner. The partner stage was the most intense. It dug…
Interview experiences · Manpower Belgium
Manpower Belgium Business Analyst interview: requirements, SQL, and OS
The interviews centered on business analysis and stayed more functional than purely technical. After the recruiter step, I had a short technical screen of around twenty minutes that moved quickly through business-analysis topics. I discussed requirement gathering and BRD-style documentation, then shifted to capital-markets fundamentals and SQL queries. The interviewer seemed to want evidence that…
Interview experiences · Manpower Belgium
Manpower Belgium Consultant interview: a verbal offer later rescinded
Things moved quickly at first. Once I received a verbal offer, I expected the next steps to follow, but instead I was left waiting and felt ignored. I later learned that the offer had been withdrawn. The explanation was that my salary expectations didn't match what another candidate would accept. That was discouraging after the early progress. I came away feeling I couldn't rely on the process, e…
Interview experiences · Manpower Belgium
Manpower Belgium Consultant interview: changing final rounds and poor follow-up
I thought the first interview was the final one. The interviewers discussed my experience, told me I was doing well, and said not to worry. I was then unexpectedly invited to a second interview, a one-person conversation still focused on my background. What was described as the final stage with a partner and hiring manager felt uncomfortable. The questions seemed designed to make things harder ra…
Interview experiences · Manpower Belgium
Manpower Belgium Consultant interview: guided start and disturbing director interview
The process began in a structured, guided way. HR clearly explained what each step was meant to assess. I had an on-site HR conversation, a team-setting evaluation, and a cybersecurity test. Having one consistent HR contact helped reduce uncertainty about expectations. The tone changed sharply in a follow-up interview with a team director. He raised his voice, behaved in a visibly outburst-like w…
Interview experiences · Manpower Belgium
Manpower Belgium Consultant interview: recruiter, director cases and partner discussion
There were three clear stages. I first spoke with a recruiter, then met a director and worked through case prompts. The final conversation was with a partner. The format was manageable because each meeting had a defined purpose. The early discussion was mainly about fit, the middle stage concentrated on cases, and the partner conversation seemed to bring those parts together. I knew what each ste…
Interview experiences · Manpower Belgium
Manpower Belgium Consultant interview: rescheduled manager round and three-month wait
My interviews were spread across several rounds, but the waiting became the difficult part. I completed the first two rounds in the same week, and a third round with the hiring manager was set for a few days later. It was rescheduled just hours before the interview, but I attended and it went fine. Afterward, I spent a long time without much clarity. I followed up regularly, yet it took roughly t…
Interview experiences · Manpower Belgium
Manpower Belgium Consultant interview: robot lawnmower market case
After my first recruiter conversation, I went straight to a group business-case day. Our case concerned a robot lawnmower and what it would take to enter and win a new market. I had to work through it with others in the room and arrive at a clear approach. There was also a structured team evaluation and a cybersecurity-related test. An HR contact guided me through the whole process and clearly ex…
Interview experiences · Manpower Belgium
Manpower Belgium Consultant interview: three online interviews and case presentation
After applying online, I entered an assessment session that ran as one tightly scheduled block. The first meeting contained three 30-minute online interviews back to back. One was a case interview, one behavioral, and one a more technical case. Everything happened in the same Zoom session, so there was little time to reset. What stood out to me was the effort to simulate the actual work environme…
Interview experiences · Manpower Belgium
Manpower Belgium Consultant Oracle HCM and consulting motivation interview
The interview felt professional and relevant to the role. I began by discussing my background, then answered questions about Oracle HCM, my project experience, and my functional knowledge. Scenario questions tested whether I could reason through real-time situations rather than simply recite theory. The tone was relaxed and easy to follow. I was treated openly, and the conversation switched quick…
Interview experiences · Manpower Belgium
Manpower Belgium Frontend Engineer interview experience: technical and IQ assessments
My process was fast and smooth. It started with an HR interview that included a few technical questions. After that I completed two online assessments, one technical and one IQ-focused. Then I had a technical interview followed by a manager interview. I passed the earlier steps, and the manager round was the final stage. There was no offer at the end, but the process was organized and easy to fol…
Interview experiences · Manpower Belgium
Manpower Belgium Frontend Engineer interview: segmented process and missing follow-up
The process took about 20 days and felt unusually segmented. It began with HR calls: an initial phone screen, then a Teams call with algorithmic exercises. I then switched platforms for additional JavaScript exercises that lasted quite a while. More HR coordination followed, and the role details shifted during the process. I eventually reached a technical interview that went very well. The manage…
Interview experiences · Manpower Belgium
Manpower Belgium Full Stack Engineer interview: early silence
An initial call went well, and I was told I would receive information about the next phase. I waited through the week, but nothing arrived. My messages went unanswered and there was no follow-up. Around the same time, I received an email about an AI-bot screening test of non-technical questions. I had completed it about ten days earlier and still had no response. The uncertainty began to wear on…
Interview experiences · Manpower Belgium
Manpower Belgium Full Stack Engineer interview with React and Node.js rounds
I began with one online assessment and then completed three technical interview rounds. React and Node.js were central throughout, and each technical conversation involved problem-solving rather than a purely introductory discussion. The final step was an HR phone conversation. We covered compensation, availability, and general questions. The technical work called for practical thinking, but the…
Interview experiences · Manpower Belgium
Manpower Belgium Software Engineer Interview Experience: broad fundamentals amid poor scheduling
The interviews focused on fundamentals, although the process quality did not feel great. The technical rounds began with detailed questions from my resume about projects, internships, and technical contributions. From there, the discussion expanded into OOP, data structures and algorithms, and language-specific concepts. On the backend, I was asked about APIs, databases, server-side architecture,…
Interview experiences · Manpower Belgium
Manpower Belgium Software Engineer interview experience: hashmap and Spring Boot
The first round felt strong and deeply technical. I was asked how a hashmap works internally, how I would handle a race condition, what rehashing means, and why Spring Boot differs from the broader Spring framework. Another stage went further into Java and backend work: Java, Spring Boot, microservices, REST APIs, SQL, and system design. We also discussed my projects, problem-solving approach, an…
Interview experiences · Manpower Belgium
Manpower Belgium Software Engineer interview: four virtual scenario rounds
My process started with a recruiter call and continued through four virtual rounds. The first was an online test. Then I spoke with someone on the team in a technical interview, followed by two rounds that were driven by scenarios rather than theory alone. In the final step, I had to handle several skills at once while two interviewers were involved at the same time. The setup felt structured and…
Interview experiences · Manpower Belgium
Manpower Belgium Software Engineer interview: fundamentals over project history
I applied for a full-stack C# and Angular role, but the interview ended sooner than I expected. The first-round questions felt fairly simple, and I would call the difficulty easy. What caught me unprepared was the emphasis on core concepts rather than the projects I had built. I did not clear the interview, and my sense was that fundamentals mattered more here than demonstrating prior work. Locat…
Interview experiences · Manpower Belgium
Manpower Belgium Software Engineer interview: HR screen, video and face-to-face rounds
I began with an HR screening call about my experience, notice period, and availability. HR then sent the job description, the details of where the rest of the process would take place, and what to expect next. After a few further stages, I had a technical interview by video and then three face-to-face interviews that mixed technical and business topics. One memorable question was whether I wanted…
Interview experiences · Manpower Belgium
Manpower Belgium Software Engineer interview: junior-role mismatch and harsh tone
The technical round was what stayed with me. The questions felt far beyond what I expected for a junior role and included code concepts I did not know. When I struggled to answer, the interviewer's tone became harsh. At one point, they essentially indicated that I was wasting their time. I had expected the interview to be challenging, but their frustration made it feel both difficult and uncomfor…
Interview experiences · MANTECH
MANTECH Network Engineer referral and offer interview experience
Recruiter outreach was low-friction after a quick introduction. I discussed what I would do day to day and what the team expected. A strong referral in the background made the start feel easy and familiar. The technical conversation was not brutal, but it was substantive. Questions tracked the job description and tested my prior programming work, including lower-level and assembly-related experie…
Interview experiences · Marks & Spencer
Marks & Spencer Account Executive Interview: Shop-floor exercise and role play
I arrived early and was first sent to the shop floor to identify a few things that could be improved. Afterwards I went upstairs for a more formal interview. The setting felt welcoming, and the conversation moved quickly from who I was to what I could bring to the role. They asked about my background, what I knew about the brand, customer service, teamwork, and how my previous experience related…
Interview experiences · Marvell Technology
Marvell Technology Software Engineer Interview Experience: tense resume-depth questioning
My first impression was negative. The interviewers seemed to be looking for flaws instead of evaluating my skills. I felt the questions were testing for the answers they expected rather than exploring whether I could solve problems well. Technically, the conversations drew on my resume and the smaller details behind the processes I had mentioned. They were checking how deep my understanding went,…