Microsoft SWE Intern, Mid 2025: 42 Experiences (Part 4 of 6)

Shared by janebeingjane ·
Company
Microsoft
Reports
42 interview reports
Level
Internship
Stages
OA → Phone screen → Onsite

Microsoft SWE intern reports from July to September 2025: résumé and behavioral questions led, plus the most math and puzzle questions in the series.

At a glance

  • Process: OA, phone screens, then interview rounds; one US candidate had five onsite rounds, ending with an unprepared presentation and demo of a past project.
  • Asked: résumé and project questions in 16 of these 42 reports and behavioral in 14; arrays and hashing (11) and strings (10) led the coding, and 6 had math, bit or puzzle questions.
  • More: the question tables for all 232 reports, the regional notes and the patterns are in Part 1.

Coverage: Internship cohort, Software Engineering Intern role, reports 150–191, dated July 2025 to September 29, 2025. None is from the Security & Identity internship. Locations: India 18, US 13, not stated 4, Ireland 2, China 2, and one each from Canada, Australia and Costa Rica. Stages: OA, phone screens, interview rounds and finals. Dates are report dates unless a report gives an interview date; thirteen reports carry only a month.

In this series

  • Part 1: Software Engineering Intern reports 01–48, July to November 2026. Also has the overview, question tables, regional notes and patterns for all 232 Software Engineering Intern reports.
  • Part 2: Software Engineering Intern reports 49–102, January to June 2026.
  • Part 3: Software Engineering Intern reports 103–149, October to December 2025.
  • Part 4 (current): Software Engineering Intern reports 150–191, July to September 2025.
  • Part 5: Software Engineering Intern reports 192–232, January to June 2025 (plus one dated only to 2025).
  • Part 6: The other internship programs: Explore Intern (1 report), Student Software Engineer roles in Israel and Denmark (10) and one SWE Co-op (1).

What came up

Resume and project questions (16 of 42) and behavioral questions (14) led. On the coding side, arrays and hashing (11) and strings (10) came up most, and this part has the most math, bit and puzzle questions of any part (6).

Topic Reports Last seen
Resume, project and past-internship deep dives 16 of 42 Sep 2025 (report date)
Behavioral and motivation questions 14 of 42 Sep 2025 (report date)
Arrays and hashing 11 of 42 Sep 2025 (report date)
Strings 10 of 42 Sep 2025 (report date)
CS fundamentals (OS, OOP, DBMS, networks) 7 of 42 Aug 2025 (report date)
Math, bits and puzzles 6 of 42 Sep 2025 (report date)
Graphs, BFS/DFS and dependency ordering 6 of 42 Sep 2025 (report date)
Linked lists 5 of 42 Sep 2025 (report date)
Trees, BSTs and tries 5 of 42 Sep 2025 (report date)
Dynamic programming 5 of 42 Aug 2025 (report date)
System and low-level design 5 of 42 Aug 2025 (report date)
Sliding window and two pointers 5 of 42 Jul 2025 (report date)
Design a data structure or class (LRU, trie, setAll, hash map) 4 of 42 Sep 2025 (report date)
Grids and matrices 4 of 42 Sep 2025 (report date)
Stacks, queues and heaps 4 of 42 Jul 2025 (report date)
Greedy and backtracking 3 of 42 Sep 2025 (report date)

A report can count toward several topics. The counts use this part's 42 reports.

Questions we found

These tables cover only this part's 42 reports. Part 1 has the tables for all 232 Software Engineering Intern reports.

Algorithms / Data Structures

Question Reports Last seen
Maximize the strength sum with one-time adjacent swaps 2: 158, 170 Sep 2025
Climbing Stairs 2: 179, 189 Jul 2025
Union of two arrays 1: 151 Sep 2025
Implement a linked list from scratch 1: 153 Sep 2025
Contains Duplicate 1: 154 Sep 2025
Cut the sticks 1: 158 Sep 2025
Implement quicksort 1: 160 Sep 2025
Rotate a matrix 90 degrees 1: 161 Sep 2025
Remove redundant task-dependency edges 1: 161 Sep 2025
Combination Sum 1: 161 Sep 2025
Split a string by a character, substring or regex 1: 163 Sep 2025
Reverse Nodes in k-Group 1: 166 Sep 2025 (report date)
Best Time to Buy and Sell Stock 1: 165 Sep 2025
Longest Palindromic Substring 1: 167 Aug 2025
Most frequent character in a string 1: 168 Aug 2025
All endpoints of a tree diameter 1: 161 Aug 2025
Reverse a linked list 1: 169 Aug 2025 (report date)
Make grid columns strictly increasing at minimum cost 1: 170 Aug 2025
Count battleships on a board 1: 171 Aug 2025 (report date)
Smallest prime at or above a number 1: 174 Aug 2025
Merge two sorted linked lists 1: 175 Aug 2025
Inorder successor in a BST 1: 176 Aug 2025
Implement a binary tree 1: 175 Aug 2025
Course Schedule 1: 178 Jul 2025 (report date)
OA DP problem modeled on 0/1 knapsack 1: 179 Jul 2025
Find every anagram of a word in a dictionary 1: 181 Jul 2025 (report date)
Digital root of a numeric string in O(1) 1: 184 Jul 2025
Valid Parentheses 1: 189 Jul 2025 (report date)
Text editor with insert, delete and backspace 1: 188 Jul 2025
Stack that also tracks its middle element 1: 189 Jul 2025
Palindrome check in O(1) space 1: 189 Jul 2025
Kth Largest Element in an Array 1: 191 Jul 2025

Low-Level Design (LLD/OOD)

Question Reports Last seen
Design tic-tac-toe 1: 174 Aug 2025

System Design

Question Reports Last seen
Design an inventory management system 1: 175 Aug 2025

Behavioral (BQ)

Question Reports Last seen
Tell me about yourself 1: 159 Sep 2025
Why Microsoft? / Why do you want to join Microsoft? (practice) 1: 165 Sep 2025 (report date)
What would you like to work on? 1: 165 Sep 2025
What was your favorite class in college? 1: 165 Sep 2025
A time you helped debug something in the frontend or backend 1: 164 Sep 2025
What did a past project failure teach you? (practice) 1: 179 Jul 2025
How do you build collaboration in a team? (practice) 1: 179 Jul 2025
A 24-hour deadline collides with a critical bug (practice) 1: 179 Jul 2025
Do you use competitive programming sites? 1: 184 Jul 2025

CS fundamentals (concept questions)

Question Reports Last seen
What happens when you type a URL into a browser? 1: 175 Aug 2025

Other

Question Reports Last seen
Design an A/B test 1: 150 Sep 2025

42 detailed candidate timelines, loops, and screens

150: Canada — an easy string question and a depth check on skills

Report date: 2025-09-29 · Role: SWE Intern · Location: Canada · Result: Offer

Interview 1 (45 minutes, one interviewer)

  1. An easy string coding question.
  2. A behavioral question.

Interview 2 (45 minutes, after a 15-minute break)

  1. Their experience and skills, in technical depth.

151: US — union of two arrays, then an A/B test

Report date: 2025-09-29 · Role: Software Engineer (Internship) · Location: United States · Result: No offer

Interview (on Teams, which took 10 minutes to load)

  1. Union of two arrays.
  2. Design an A/B test.

152: US — five onsite rounds, including a surprise presentation

Report date: 2025-09-26 · Role: Software Engineer Intern · Location: United States · Result: Offer

Three 45-minute technical onsites with engineers on the team

Two behavioral rounds

  1. Experiences and interests.
  2. An unprepared presentation on a past project, with a short demo.

153: Redmond — a systems-heavy role, so build a linked list

Report date: 2025-09-25 · Role: Software Engineer Intern · Location: Redmond, Washington, US · Result: Offer

Two back-to-back interviews on the same day

  1. Implement a linked list from scratch.
  2. Hash map questions. The candidate said these weren't typical puzzle problems because the role was systems-heavy.

154: Dublin — three interviews with 15 minutes of behavioral each

Report date: 2025-09-20 · Role: Software Engineer Intern · Location: Dublin, Ireland · Result: Offer

Three back-to-back 45-minute interviews

  1. Contains Duplicate.
  2. About 15 minutes of behavioral questions per interview.

155: US — one puzzle problem, one implementation problem

Report date: 2025-09-18 · Role: Software Engineer Intern · Location: United States · Result: Offer

Two back-to-back 45-minute interviews (one problem each)

  1. An easy-to-medium algorithm problem.
  2. An easy-to-medium problem that leaned on implementation more than tricks.
  3. Explain the past experiences on your resume.

156: India — brute force, then the trade-offs

Report date: 2025-09-09 · Role: Software Development Engineer (SDE) Intern · Location: India · Result: No offer

Online assessment

Two DSA interviews

  1. An array problem: brute force first, then an optimized version, with a time vs. space trade-off discussion.
  2. Resume projects.

157: A hard opener, then an optimal finish

Report date: 2025-09-09 · Role: Software engineering intern · Location: Not stated · Result: Not known when posted

Two back-to-back rounds (no problem text shared)

Round 1

  1. A hard problem. They explained the approach and the interviewer agreed, but they didn't finish the code. The follow-up asked how to improve the algorithm itself, not its complexity.

Round 2

  1. They wrote the optimal solution.

158: OA — cut the sticks and a one-swap strength sum

Report date: 2025-09-08 · Role: Software engineering intern · Location: Not stated · Channel: Applied online · Result: Failed the OA

Online assessment (2 problems)

  1. Cut the sticks: each round, remove every stick of the current shortest length and cut that length off the others; return how many sticks are left at the start of each round. For [1, 1, 3, 4] the answer is [4, 2, 1].
  2. Maximize the sum of arr[i] × (i + 1) using adjacent swaps, with each element in at most one swap. For [2, 1, 4, 3] the best order is [1, 2, 3, 4].

159: Redmond — an easy problem with follow-ups and a hard matrix one

Report date: 2025-09-07 · Role: Software Engineer Intern · Location: Redmond, Washington, US · Channel: Applied online · Result: No offer

A resume screen led straight to the finals.

Two final rounds

  1. Tell me about yourself.
  2. An easy problem with follow-ups.
  3. A medium-to-hard matrix problem.

160: Hyderabad campus — quicksort and a math riddle

Report date: 2025-09-07 · Role: SWE Intern · Location: Hyderabad, India · Channel: On campus · Result: Offer

Coding round (2 easy-to-medium problems)

Two technical interviews

  1. Implement quicksort.
  2. A riddle you could solve with simple math.

161: Azure Virtual Desktop off-cycle intern, China — three rounds

Report date: 2025-09-02 (rounds 1–2 posted 2025-08-29) · Role: Software engineering intern, off-cycle · Team: Azure Virtual Desktop · Location: China · Result: Verbal offer

Round 1

  1. Deep questions on a previous internship.
  2. Rotate a matrix by 90 degrees.

Round 2 (relaxed)

  1. Internship and project chat.
  2. Combination Sum: given an array and k, return every combination that adds up to k, with elements reusable any number of times.

Round 3

  1. Five minutes of small talk, then about 25 minutes on internship work, including how a strength they'd claimed on the resume showed up on the job.
  2. An open scenario: remove redundant task-dependency edges. A file lists dependency pairs. Some edges are implied by others: if d depends on both a and c, and c already depends on a, the direct d-to-a edge adds nothing. Those extra edges make the file grow fast. Any angle was fine, not just an algorithm, and the interviewer cared more about the thinking than a perfect answer.

The same author later said a separate Microsoft interview of theirs was for a vendor role. Whether this AVD role was a direct hire isn't stated.


162: Bengaluru — greedy and graph OA, graph and tree interview

Report date: 2025-09-02 · Role: Software Development Engineer (SDE) Intern · Location: Bengaluru, India · Result: Offer

Online test (120 minutes, 2 problems around medium-hard)

  1. A greedy problem.
  2. A graph problem.

Interview (about 60 minutes, 30 per problem)

  1. A medium graph problem.
  2. A medium tree problem.

HR round

  1. Resume projects and technologies.

163: Redmond — a hash table problem and a string splitter

Report date: September 2025 · Role: Software Engineer Intern · Location: Redmond, Washington, US · Result: Offer

Interview 1 (1 problem)

  1. A hash table coding problem.

Interview 2 (1 problem)

  1. Write a function that splits a string by a character, a substring or a regular expression.

164: Sydney — a debugging story, traced end to end

Report date: September 2025 · Role: Software Engineer Internship · Location: Sydney, Australia · Result: Not known when posted (marked no offer)

Two interviews, with an hour's break between them

  1. Describe a time you helped debug something in the frontend or backend. Follow-ups: how did the bug spread, and what was your debugging process?

165: Redmond — stock prices, pattern matching and favorite classes

Report date: September 2025 · Role: Software Engineer (Internship) · Location: Redmond, Washington, US · Result: Offer

Online assessment

Interviews. Across them:

  1. Best Time to Buy and Sell Stock.
  2. A pattern-matching problem.
  3. A binary-tree traversal problem.
  4. Why Microsoft?
  5. Tell me more about your previous experience.
  6. What would you like to work on?
  7. What was your favorite class in college?

166: Hyderabad — k-group reversal on HackerRank

Report date: September 2025 · Role: SDE-intern · Location: Hyderabad, India · Result: No offer

Interview (on HackerRank)

  1. Reverse a linked list in groups of k.

167: India — longest palindromic substring, 20 days after the OA

Report date: 2025-08-31 · Role: SDE-intern · Location: India · Result: No offer

Online assessment (2 medium questions, done in 40–50 minutes)

Interview, 20 days later (2 problems)

  1. Length of the longest palindromic substring.
  2. A hashing question.
  3. Behavioral questions and a project discussion.

168: OA — most frequent character and every diameter endpoint

Report date: 2025-08-29 · Role: Software engineering intern · Location: Not stated · Channel: Applied online · Result: Passed the OA

Online assessment (75 minutes, 2 problems; the candidate rated it easy)

  1. Return the most frequent character in a string.
  2. Find a tree's diameter and return every node that can be one of its endpoints.

169: New Delhi — reverse a list both ways

Report date: 2025-08-28 · Role: Software Development Engineer (SDE) Intern · Location: New Delhi, India · Result: No offer

Online interview (3 questions)

  1. Reverse a singly linked list with no extra space, explaining both the iterative and recursive versions and their complexity.
  2. Array and string problems.
  3. Their resume achievements.

170: Redmond summer 2026 OA — column costs and the strength sum again

Report date: 2025-08-28 · Role: SWE summer 2026 intern · Location: Redmond, Washington, US · Result: Not known when posted

Online assessment (75 minutes, 2 problems; the candidate found both easy)

  1. Make every column of a pixel-intensity grid strictly increasing from top to bottom. You can only raise values, at a cost of 1 per unit; return the minimum total cost. For [[2,5],[7,4],[3,5]] the answer is 9.
  2. getMaximumSumOfStrengths, the same adjacent-swap task as report 158. For [2, 1, 4, 3] the answer is 30.

171: US — battleships, then deep OS and BIOS questions

Report date: 2025-08-27 · Role: SWE Intern · Location: United States · Result: Offer

Interview (1 problem)

  1. A medium battleship problem on a 2D grid.
  2. Deep operating-systems and BIOS questions.

172: Bengaluru area — speed decided the shortlist

Report date: 2025-08-18 · Role: Software Engineer (Internship) · Location: Bengaluru area, India · Result: No offer

Coding assessment (2 problems; the stage isn't named)

  1. A probability question.
  2. A DP question.

They solved both but slowly and weren't shortlisted, which they put down to speed.


173: Windows 365 off-cycle intern, Suzhou — five interviews across two teams

Report date: 2025-08-16 · Role: Software engineering intern, off-cycle (backend) · Team: Windows 365 · Location: Suzhou, China · Channel: Applied through a job post on a social app · Result: Offer

The candidate summed up five interviews across two departments instead of going round by round.

  1. Coding prompts were in English and mostly well-known standard problems. They had to write their own test cases, and coverage counted.
  2. Some system design questions, which they found the hardest part.
  3. Project discussion and behavioral questions.
  4. Little rote fundamentals; only one interviewer pushed on them.

All five interviewers were friendly. The team works in C# and TypeScript.


174: Redmond — tic-tac-toe and the next prime

Report date: 2025-08-13 · Role: Software Engineer (Internship) · Location: Redmond, Washington, US · Result: No offer

Two back-to-back interviews

  1. Build a tic-tac-toe game (framed as a systems question).
  2. Given a number, return the smallest prime at or above it.

175: Hyderabad — OS, a merge, and an inventory system

Report date: August 2025 · Role: Software Engineer (Internship) · Location: Hyderabad, India · Result: No offer

Technical interview

  1. Operating systems: multitasking, process management, inter-process communication.
  2. Implement a binary tree.
  3. Merge two sorted linked lists.
  4. Spot the errors in a piece of code.
  5. How would you build an inventory management system?
  6. What happens when you type a URL into a browser?

HR interview

  1. Personality, goals, motivation, teamwork and decision-making.

176: India — next larger value in a BST

Report date: August 2025 · Role: SDE-intern · Location: India · Result: No offer

Online assessment

Technical interview

  1. Find the next larger value (the in-order successor) in a BST.

HR round


177: Costa Rica — a 75-minute string task

Report date: August 2025 · Role: Software Engineer (Internship) · Location: Costa Rica · Result: No offer

Coding assessment (about 75 minutes, 2 problems; two weeks to prepare before starting)

  1. A string-manipulation exercise.

178: Redmond — straight to the final, Course Schedule first

Report date: 2025-07-30 · Role: Software Engineer Intern · Location: Redmond, Washington, US · Result: Offer

They went straight to the final round.

Final 1

  1. Course Schedule (graph, topological sort).
  2. A small systems question.

Final 2

  1. An easy-to-medium sliding-window array problem.

179: India, summer 2026 — knapsack-style OA and Climbing Stairs done four ways

Interview date: 2025-07-27 (both interviews) · Role: Software Engineering Intern · Location: India · Result: Offer, about 3 hours after the last interview

OA (2 questions)

  1. A medium two-pointer problem.
  2. A DP problem modeled on 0/1 knapsack. The report names the model but not the actual items or values.

Interview 1, DSA and projects

  1. Climbing Stairs: from plain recursion to memoization, then tabulation, then O(1) space.
  2. Full-stack projects: why that stack, state-management trade-offs, the hardest bug, and how they'd re-architect for scale.

Interview 2, technical and HR (no coding reported)

  1. A backend project's architecture, SQL vs. NoSQL, everyday debugging habits, and how they learn an unfamiliar codebase.
  2. Growth-mindset scenarios: building collaboration in a team; what to do when a 24-hour deadline runs into a critical bug; and what a past project failure taught them.

180: Dublin — three onsites, one problem each, plus math

Report date: 2025-07-25 · Role: SWE Intern · Location: Dublin, Ireland · Channel: Applied online · Result: Offer

Online assessment

Three onsite interviews (one problem each, behavioral and experience questions in each)

  1. A common two-pointer / hash map question.
  2. Two math-related questions.

181: India off-campus — anagrams from a dictionary

Report date: 2025-07-24 · Role: Software Development Engineer (SDE) Intern · Location: India · Channel: Off campus · Result: No offer

Online assessment

Technical interview

  1. Given a dictionary, find every anagram of a given word.

The candidate listed the off-campus pipeline as a resume screen, the OA, one or two technical interviews, then HR.


182: SDE intern, short account — graph and DP in a 70-minute OA

Report date: 2025-07-23 (report date; the interview may be older) · Role: SDE Intern · Location: Not stated · Result: Not stated

  1. OA (70 minutes): two medium-to-hard problems, one on graphs and one on DP. They believed that passing about 70% of all test cases was enough for an interview call.
  2. Technical interview 1: standard DSA from almost any topic, plus core CS subjects.
  3. Technical interview 2: some DSA, mostly project discussion, maybe a few HR questions.

183: New Delhi — explain a monotonic stack, then code it

Report date: 2025-07-16 · Role: SDE-intern · Location: New Delhi, India · Result: No offer

Interview (35–40 minutes for the coding task)

  1. A monotonic-stack problem: explain the logic first, then code it.

184: India on-campus — HackerRank OA, then projects and a digit-sum trick

Interview date: 2025-07-14 · Role: SWE Intern · Location: India (on-campus; interviewers in Hyderabad) · Result: Offer, the same evening

OA (HackerRank; 1.5 hours inside a 2-hour window)

  1. A subsequence problem.
  2. A graph traversal problem (DFS/BFS).

Both were done in about 40 minutes. The interview invite came with a form to rank three preferred teams out of about ten.

Technical interview (senior engineer, about 1 hour, coding on HackerRank)

  1. A past internship at a logistics company in detail, with behavioral questions mixed in, plus their GitHub history.
  2. A team project and how the team coordinated.
  3. A few CS fundamentals.
  4. A DSA question on a basic math idea tied to binary addition, with a few follow-ups.

Managerial and technical interview (manager, about 1 hour 20 minutes, in their own editor)

  1. Skills on the resume: JavaScript, TypeScript, MongoDB.
  2. The team project's overall design; once Kafka came up, broader high-level design ideas.
  3. Whether they use competitive programming sites, and more on the past internship.
  4. Digital root of a numeric string: keep adding the digits until one digit is left, in O(1). For example, 28 gives 10, then 1. A few follow-ups.

They were placed in a healthcare-domain team rather than one of their Azure picks.


185: US — a coding phone screen, then two interviews

Report date: 2025-07-07 · Role: Software Engineer Intern · Location: United States · Result: Offer

Phone interview (coding)

Two back-to-back interviews

  1. Coding questions such as backtracking and DP.
  2. A couple of behavioral questions and questions about which teams and orgs interested them.

186: San Francisco — stopped at the assessment

Report date: July 2025 · Role: Software Engineer (Internship) · Location: San Francisco, California, US · Channel: Recruiter at the university · Result: No offer

Assessment (2–4 medium-to-hard problems)

They didn't pass, so the later HR and technical rounds (motivation, system design) never happened. A recruiter visiting their university started the process.


187: Bengaluru — two problems with dry runs, then SQL and OOP basics

Report date: July 2025 · Role: SWE Intern · Location: Bengaluru, India · Result: No offer

Interview (under an hour)

  1. Two easy-to-medium coding questions, each with time and space complexity and a dry run.
  2. SQL, OOP and DBMS basics, such as primary keys and friend functions.
  3. A few questions on resume projects.

188: Bengaluru campus — a text editor in the OA

Report date: July 2025 · Role: SWE Intern · Location: Bengaluru, India · Channel: On campus · Result: No offer

Online assessment (2 easy problems, solved in about 25 minutes)

  1. Build a text editor that supports insert, delete and backspace.

They weren't shortlisted and felt the shortlist after the OA looked random.


189: New Delhi — an SDE 2, then a Principal Engineering Manager

Report date: July 2025 · Role: SDE-intern · Location: New Delhi, India · Result: No offer

Online assessment (2 easy-to-medium problems on graphs and sliding windows)

Technical round 1 with an SDE 2 and technical round 2 with a Principal Engineering Manager (2 problems each). Across them:

  1. Balanced parentheses.
  2. Climbing Stairs.
  3. A palindrome check in O(1) space.
  4. A stack built on a linked list that also tracks its middle element.
  5. A project review (round 2).

190: New Delhi — a deque and a fixed-size window

Report date: July 2025 · Role: SDE-intern · Location: New Delhi, India · Result: No offer

Online assessment (2 problems)

  1. A medium-easy array / deque problem.
  2. A medium-hard fixed-length sliding-window problem.

Interviews 1 and 2: standard medium coding problems in both.


191: Bengaluru — an easy heap, then one they couldn't optimize

Report date: July 2025 · Role: Software Engineer (Internship) · Location: Bengaluru, India · Result: No offer

Interview (2 problems)

  1. Kth largest element, an easy heap question.
  2. A second problem they couldn't optimize.

Common questions

Does Microsoft repeat SWE intern OA questions?

In this part, reports 158 and 170 got the same adjacent-swap OA task (maximize the sum of arr[i] × (i + 1), each element swapped at most once) in late August and early September 2025.

Keep practicing

In this series: Part 1 · Part 2 · Part 3 · Part 4 (current) · Part 5 · Part 6

Sources: Anywhere useful interview info can be found.

Next in this seriesMicrosoft SWE Intern, Early 2025: 41 Experiences (Part 5 of 6)
0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.