READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 88 of 153
Interview experiences · Meta
Meta Software Engineer Interview Experience — Phone Screen Plus a Four-Round Virtual Onsite
Meta phone screen + virtual onsite writeup, with the questions and my thought process included. Since I signed an NDA, I'm coding the problem names as homophones — sorry about that. Phone Screen 45 minutes, two questions. The first five minutes were self-intro, and pretty much the rest of the time was spent coding. Question 1, coded 1091: a 2D grid, get from the top-left corner to the bottom-righ…
Interview experiences · Meta
Meta Software Engineer Interview Experience — Rejected After an Onsite Where the Interviewer Argued Over Big-O Notation
I just got told yesterday that I didn't pass, so I'm reporting back to the forum — and venting a little while I'm at it. Phone: a coding round. OA: a banking-system themed problem. I only passed two rounds, but was told I'd still move on to the onsite. Virtual onsite: System design: the same question as another post I'd already seen on the forum. AI coding: a card game — design a strategy to guar…
Interview experiences · Meta
Meta Software Engineer Interview Experience — the OA Was Basically the Same as a Study Article
The Meta RS OA wasn't too hard. I'd previously studied from an article that turned out to basically be the exact same questions. Q1: You need to find the index computed from rating divided by prices. If two entries tie, keep the one with the smaller index. When comparing, you don't need to compute the actual decimal — just cross-multiply to compare the two fractions directly. Q2: You need to comp…
Interview experiences · Meta
Meta Software Engineer Interview Experience — Three of Four Levels on the Bank System Question
Bank System. This is an old question that has shown up on the forum before. Level 1: implement the createAccount, deposit, and pay methods. Level 2: find the top N activity, based on the sum of deposit and pay amounts. You just maintain a size-N min-heap with a priority queue. Level 3: When you transfer, you hold the money from the source account; when you accept, it actually moves to the target…
Interview experiences · Meta
Meta Software Engineer Interview Experience — Two AI Coding Rounds, a LeetCode System Design, and an AI-Enabled Design Round With No AI
Two AI coding rounds, one traditional system design, one AI-Enabled Design round. AI coding 1: Max Unique Character Subset — given a list of words, find a subset of words where no two words in the subset share any repeated letters, and the subset covers the largest possible total number of unique letters. AI coding 2: Kind of a mess. This round the interviewer opened by telling me he hadn't reali…
Interview experiences · Meta
Meta Software Engineer Interview Experience — Weak Signal on Coding 2 But the Offer Came Anyway
I feel really lucky, I got a great recruiter. From the initial reach out all the way to finalizing the offer they were thorough about everything, kept emphasizing "I'm on your side." In the debrief they told me Coding 2 had a weak signal, but the quorum still generously let it through. The interviewers were all nice too — when I interviewed for an intern role before I ran into people who were dis…
Interview experiences · Meta
Meta UX/UI Designer interview: full loop canceled before schedule
I began with a recruiter phone screen and then met the hiring manager. The hiring manager told me to prepare for the full loop, so I organized around completing the rest of the process. The full-loop interview was canceled one day before it was scheduled because the role no longer existed. I never reached the later rounds. Having completed the early steps and prepared for more, I felt disappointe…
Interview experiences · Meta
Meta UX/UI Designer interview: peer rounds followed by a bench wait
I went through three peer interview rounds with technical and behavioral parts. The format matched what I had seen for this type of role, and the technical questions lined up with the resources I had found beforehand. After those rounds, I expected a decision to move forward. Instead, I was told to wait while they decided which team or role might fit me. I understood it as something like being he…
Interview experiences · Metropolis
Metropolis Interview Experience — Rejected After an HM Screen Filled In by a Senior Staff Engineer
A recruiter from a startup reached out to me on LinkedIn. I figured I'd learn a bit more about it, so I decided to take the interview. The first round was an HM screen, done by a senior staff engineer. He said the team hadn't hired a manager yet, so he was standing in for that role. It was mostly about my projects and behavioral questions. Maybe we just didn't click, because I didn't pass. Here's…
Interview experiences · Micro1
Micro1 Backend Engineer interview: AI-driven screen with Node.js and MongoDB
I went through an AI-driven process that still felt supportive, and it ended with encouragement to continue. During the initial technical screen, I discussed my backend experience with Node.js and MongoDB. The interviewer seemed satisfied but asked me to refine some technical details. I didn't receive an offer from this step. My takeaway was that strong backend examples can still earn genuine pos…
Interview experiences · Micro1
Micro1 Software Engineer fifty-minute Zara AI interview
My process was quick and centered on a Zara AI interview. The question difficulty felt easy to moderate, and the whole interview took about fifty minutes. It started with a short mock interview and then moved into the technical round. The AI's pacing felt straightforward compared with more intense stress-test interviews. It handled the mock portion first, followed by technical problems that didn'…
Interview experiences · Micro1
Micro1 Software Engineer interview: a hostile AI screen with no dialogue
My first Micro1 screen used AI and felt genuinely hostile. The bot rushed through prompts, skipped ahead when I paused, and mispronounced terms in technical questions. It felt less like an interview and more like an automated quiz. What bothered me most was the lack of room for a back-and-forth. I could not really ask questions or clarify anything. Instead, the interaction narrowed into rapid-fir…
Interview experiences · Micro1
Micro1 Software Engineer interview: AI assessment instability
My interview opened with an AI-driven conversational segment before moving into technical tasks. It felt more like an assessment than a human conversation. The sections tested whether I could reason clearly, explain tradeoffs, write code, and debug under time pressure. I worked through live coding and debugging, code-optimization tasks, and API questions. The questions were not vague in the way s…
Interview experiences · Micro1
Micro1 Software Engineer interview: AI coding session with escalating follow-ups
My AI interview felt like a stressful, high-focus testing session. The system asked questions tied to a specific language area before moving into a coding exercise. The whole environment was recorded, including my webcam, microphone, and screen, so I felt like everything was being scrutinized. The questions began at a high level, focusing more on architecture and performance design than on writin…
Interview experiences · Micro1
Micro1 Software Engineer interview: backend and database depth
The Micro1 interview began with React and Node.js fundamentals, then quickly moved into practical backend topics: worker threads, task processing, queues and message services, and using idempotency to make operations safe and repeatable. The discussion continued into distributed systems and PostgreSQL internals, including transactions, isolation levels, concurrency control, query optimization, an…
Interview experiences · Micro1
Micro1 Software Engineer interview experience: AI-guided questions
I began with an assessment, then completed a fully AI-guided interview. The virtual interviewer asked about my programming experience, software engineering fundamentals, and earlier projects. No live person spoke with me. The format was direct. The bot parsed what I said and used that to choose the next question, either confirming my understanding or asking for more detail. That made it feel less…
Interview experiences · Micro1
Micro1 Software Engineer interview: fast Zara AI technical sequence
My first interaction with Micro1 was a Zara AI interview that ramped up quickly. The technical questions became difficult fast, and the flow was so tight that I had little time to pause before the bot advanced. If I did not answer in time, it moved to the next item. It felt as though I had to go through every section. In a stack-related set of questions, I could not effectively skip ahead and had…
Interview experiences · Micro1
Micro1 Software Engineer interview with the Zara AI
I interviewed in a live meeting-style setup with the Zara AI, and the process felt time-boxed from the start. I had to answer questions within a limited window, knowing that I was being recorded and that the recording would be shared with recruiters. I had to stay focused throughout because the AI could miss parts of what I said. When the questions came, the interaction seemed responsive to impor…
Interview experiences · Micro1
Micro1 Software Engineer Zara AI interview with rapid technical questions
My first interaction with Micro1 felt like a pure Zara AI interview, and it ramped up quickly. I faced technical questions whose difficulty increased fast. The pace was so tight that I barely had time to pause and think before the bot moved on. If I didn't respond in time, it went straight to the next question. What caught me off guard was having to go through every section. When a topic didn't c…
Interview experiences · Microchip Technology
Microchip Technology Software Engineer Interview Experience: Full-day onsite and fab tour
The onsite was a long, full-day experience that started early and ran until mid-afternoon. It followed a structured schedule of one-on-one conversations with multiple team members, plus meetings with a director and managers from test engineering, failure analysis, and reliability. I had time to ask questions, saw the lab, and had lunch during the day. The intensity came from meeting so many peopl…
Interview experiences · Micron Memory Malaysia Sdn Bhd
Micron Memory Malaysia Sdn Bhd Software Engineer interview: a short critical-thinking screen
The interviewer spent about twenty minutes on my background, then used the rest of the short conversation for critical-thinking questions. There was very little technical material, although I did have to explain a simple circuit with a voltage supply, resistance, and a capacitor. The logic-focused portion threw me off because it did not feel very engineering-specific. The staged, high-volume form…
Interview experiences · Micron Memory Malaysia Sdn Bhd
Micron Memory Malaysia Sdn Bhd Software Engineer interview: projects, troubleshooting, and shift expectations
The process was organized and centered on my resume and how I worked. I began with a recruiter screen, then met engineering interviewers and later the hiring manager. I also had a hands-on onsite discussion lasting from half an hour to about an hour. The atmosphere was fairly casual, and the interviewer explained what the job would actually involve before asking about past projects and problem so…
Interview experiences · Micron Technology
Micron Technology Software Engineer interview: concise answers in a fast-moving process
After a recruiter call, I quickly moved to a short live interview. I spent about twenty minutes explaining my experience, then answered critical-thinking questions. The technical material was simple, but I still needed to explain the fundamentals clearly: a circuit involving a voltage supply, resistance and a capacitor, plus at least one probability-style question. The high-volume hiring format f…
Interview experiences · Microsoft
Microsoft Applied Scientist interview with a last-minute virtual cancellation and long HR wait
The interview itself seemed technically normal at first, but the communication around it became the hardest part. I was called for a virtual interview, then received an email minutes before it was due to start saying it was canceled. They said they would reschedule, but I never received a new time. Later, I did manage to complete an interview, but it still did not feel like there was closure. HR…