READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 83 of 153
Interview experiences · Mastercard
Mastercard Software Engineer interview: a bad technical round and a warm behavioral one
The technical interview was bad enough to overshadow the rest. The interviewer had not read my CV, gave little guidance, and either did not listen to my answers or could not understand them. It felt as though my responses were not landing. The behavioral interview was the opposite. At least one interviewer was friendly with the hiring manager, and that part had a good tone. I did not get an offer…
Interview experiences · Mastercard
Mastercard Software Engineer interview: a rushed EV design and BFS coding round
My Karat round was fast, high pressure, and oddly disorganized. The interviewer had a list of questions to get through, so there was little room for a natural conversation. I got a system-design question about an EV charging scenario, and they covered multiple items in a way that made it hard to go deep on the design choices. Then I had a LeetCode-style coding problem with under 20 minutes. It wa…
Interview experiences · Mastercard
Mastercard Software Engineer interview: eliminatory coding and same day later rounds
I entered through a college placement style process. The first call was for a coding round, and that round was explicitly eliminatory. After I completed it, I finished the remaining rounds a couple of days later, all on the same day. The sequence began with the coding interview and continued with manager level and bar raiser style evaluation. Those later rounds seemed to be about more than coding…
Interview experiences · Mastercard
Mastercard Software Engineer interview: inflexible schedule and Hangman OOD task
The process began with scheduling friction and a rigid structure. I received about 10 days' notice and could not change the interview date. There was also a preparation session that suggested the process would be more organized than it eventually felt. In the interview, I had to implement object-oriented design for a Hangman game. The interviewer was rigid and seemed to expect particular answers,…
Interview experiences · Mastercard
Mastercard Software Engineer interview: scenario based screening rejection
My screening was built around hypothetical situations. It was not a friendly chat. The interviewer walked through scenarios and tested how I would think about them, with a clear focus on decision making rather than coding. The interviewer was professional and kept a positive attitude, but I was rejected in that screening round. The quick outcome surprised me because the tone had been good, and I…
Interview experiences · MathWorks
MathWorks Intern Software Engineer Interview Experience — Two Friendly Video Onsites, Offer Three Weeks Later
9/7 – Received the OA. I don't really remember the details anymore. 9/2 – Got notified it was the last day to do the OA, so I did it quickly. Three fairly simple questions, plus a recorded video interview (details shared earlier in this thread). 10/21 – HR reached out to schedule an interview. 11/7 – VO1. One question was the second question from the OA, plus a greedy problem. Aside from asking a…
Interview experiences · MathWorks
MathWorks Software Engineer Interview Experience — A Seven-Round Superday With a Presentation Deck and No Lunch Break
This year a lot of companies are on a hiring freeze. MathWorks is one of the few still hiring — I landed an offer for the SWE2 role. I got in through a referral. Recruiter call: matched with a team in Simulink product cloud infra. Just a simple introduction and some logistics questions. OA: debugging plus a coding problem. Breezed through it. Phone screen 1: self-intro plus the classic CS trivia…
Interview experiences · Matrix Missions
Matrix Missions Marketing Analytics Specialist interview: background fit
My interview was scheduled about a month after I applied. The interviewer was nice and the process felt smooth. Most of the discussion centered on my previous work experience, and nothing about the conversation was especially surprising. I did not get an offer, but it felt mainly like a background-based fit evaluation: more comfortable and conversational than stressful. Location: Hong Kong. Overa…
Interview experiences · Matrix Missions
Matrix Missions Marketing Analytics Specialist interview with panel round
I began with an HR phone screen covering my resume, salary expectations, and basic background. The process then had two interviews. The first was with the line manager and focused on relevant experience plus scenario questions about how I would handle work in practice. The second was a panel interview with senior team members. The process was smooth and structured. It took about three weeks from…
Interview experiences · Maven Securities
Maven Securities Data Scientist Interview Experience — Three Rounds of Online Assessments
The first round OA was 30 minutes with 18 probability questions. The time wasn't tight — most of them were easy-to-medium difficulty questions from the green book, or similar ones. I still remember the last question: from the 30 numbers 1 to 30, you draw three numbers without replacement — what's the probability that the three numbers form an arithmetic sequence? I think I'd seen a similar questi…
Interview experiences · Maybank Singapore
Maybank Singapore Software Engineer interview experience: restructuring delay
The process began with a lack of clarity that never got resolved. I never received a proper job description. Although I was scheduled for a senior software engineer track, the interviews felt pitched more at a lead level. I completed two technical rounds, and an HR round was confirmed. Then the process was abruptly put on hold because of internal management restructuring. Long gaps stretched to a…
Interview experiences · Maybank Singapore
Maybank Singapore Software Engineer interview with a Git technical assessment
I started with a technical assessment that required me to build something small and upload the result to Git. After it was reviewed, I was invited to a career discussion, where I connected my previous work to the role they were hiring for. The timeline became strange after I passed the first round. I waited about three months before the next round and had to follow up with the recruiter repeatedl…
Interview experiences · MBDA
MBDA Software Engineer Interview Experience: Welcoming panel and conversational pace
I felt surprisingly at ease from the moment I arrived. The panel was welcoming, warm, and down to earth. The conversation moved at a relaxed pace, giving me time to explain my answers without feeling rushed or pressured. The questions mixed technical and non-technical topics, but the tone stayed conversational. I discussed what I could bring to the role and my background without feeling interroga…
Interview experiences · MBDA
MBDA Software Engineer interview: month between HR and recruiter meeting
I started with an HR phone call. About a month later, I met the recruiter on site at the Plessis-Robinson location. Every exchange I had with the people involved was positive. The meeting was structured but did not feel hostile or overly pressuring. They seemed to be trying to get a clear read on my fit. The month-long gap made the process feel slower than the interactions themselves. Location: L…
Interview experiences · MBDA
MBDA Software Engineer interview: several-hour assessment centre process
I went through a full assessment-centre process that took several hours. It began with an icebreaker in a small group of applicants, which set a calmer tone. From there I had a personal interview with one person and later a group task. The assessment included looking at a partnership proposal for a new collaboration. They wanted to see how we thought through the situation together. There was also…
Interview experiences · MBDA
MBDA Software Engineer interview: values and CV Teams conversation
I had a friendly MBDA Teams call centered on whether my values aligned with the company. They asked what I could bring to the team and to MBDA, and they also asked about my CV. The tone was more probing than I expected because values and motivation drove the conversation. I left feeling that they took fit seriously, so the call felt more focused than a generic screening. Location: United Kingdom.…
Interview experiences · Mcdonald'S Global Office In India
Mcdonald'S Global Office In India Software Engineer interview experience: timed coding
I applied online and received an email invitation for a virtual interview. In that session, I solved an easy LeetCode-style problem involving pairs or arrays. It was manageable and did not feel especially long or brutal. There was also a nontechnical behavioral round about my experience and resume. That interviewer looked for critical thinking, communication, and some familiarity with data analys…
Interview experiences · McGraw Hill
McGraw Hill Software Engineer interview: verbal engineering discussion
After a brief recruiter chat, I had what was scheduled as an engineering-manager discussion, although a senior developer led it. It was a one-hour, verbal technical round with no live coding. We discussed Terraform, CI/CD strategy, GitHub Actions, observability, and day-to-day production support. I also described a simple education-domain schema for teachers, students, classes, and assignments, i…
Interview experiences · McKinsey &
McKinsey & Business Analyst interview: case pace and opaque decisions
I applied online and waited for the Solve-style assessment and next steps. I advanced after the pre-screen, but the connection between the test and interview decisions wasn't clear to me. Even when I asked later, I couldn't fully understand the scoring and matching. At one stage, it seemed that both my assessment and resume affected whether I moved forward. The live interviews paired personal exp…
Interview experiences · McKinsey &
McKinsey & Business Analyst interview: partner-level case jump
The process grew harder as it went. I had two relatively easier first-round interviews, often with Business Analysts, on cases such as market entry and profitability. The final partner rounds used much harder strategy cases and less familiar story lines, so I had to adapt quickly. They also asked about my resume and experience before moving into the cases. The schedule felt tight, with cases taki…
Interview experiences · McKinsey &
McKinsey & Business Analyst interview: preparation support, personal experience and cases
The recruiting team gave me a lot of preparation support. I could access resources, join online sessions and use help groups to understand the stages and expectations. The process was long, but I knew how the interviews would work. The rounds paired a personal experience interview with case work. I could ask about the interview format beforehand, which reduced some of my uncertainty about the cas…
Interview experiences · McKinsey &
McKinsey & Business Analyst interview: Solve score and unexplained rejection
I applied for a Business Analyst role and went straight to the McKinsey Solve online assessment, a gamified problem-solving test of roughly 80 minutes. About two weeks after finishing it, I received a rejection email without reaching a live interview. I asked for my score. A couple of days later, they said I was in the 10th decile with a 537 score. That made the rejection hard for me to understan…
Interview experiences · McKinsey &
McKinsey & Business Analyst interview: supportive case conversations
I expected a stressful process, but the case interviews felt tightly run and well supported. The interviewers were professional and seemed genuinely interested in helping me do well. It was intellectually demanding without feeling hostile. The cases and discussions had structure, and the interviewers gave detailed answers when I asked questions. They were unusually open about the realities of the…
Interview experiences · McKinsey &
McKinsey & Consultant interview: case rounds, fit, and respectful offer process
I had a very good process, beginning with friendly and professional interviewers. It started with a phone screen, then two case-interview rounds with a partner and a senior associate. Near the end, there was a final round covering fit and problem-solving skills. It was a direct way to understand how I thought, how I explained my reasoning, and how my experience related to day-to-day challenges. I…