Microsoft Security & Identity intern: resume questions
Tue Nov 10, 2026. Two 45-minute rounds on Teams (1:00 and 2:00 PM ET), each with resume and behavioral talk, then a LeetCode medium in HackerRank. This site is the resume half. Every question has an answer you can open. Anything marked check is my best guess from your notes; fix it if it is wrong.
What the resume part looks like
- Two people who did this exact loop on Nov 5 said both rounds had resume and behavioral questions, "pretty random, depends on the interviewer." The offer holder said the rounds were standard, a medium each plus questions about projects and past experience, and the interviewers were chill.
- Your interviewers are software engineers on an identity team, not network engineers. Nobody asks lane counts or EVPN. They ask: what did you build, why that design, how did you know it worked, what broke, how did you work with people, and anything that smells like identity, secrets, isolation, or trust.
- Budget 5 to 10 minutes of resume talk per round before the coding question. Expect them to pick the bullet you least expect, so every bullet gets a 30-second version.
- Cisco is the bullet they are most likely to open, because it is the most recent and the longest on the page. That is why the Cisco page is the deepest.
Rules for every answer
- 30 to 60 seconds, then stop. Let them pull. The offer holder "yapped" and still got the offer, but the interviewer should steer.
- Problem, then your decision, then the proof. Numbers only if they are real.
- Say "simulator," "software TPM," and "BMC mock" plainly. Never let them believe you touched hardware you did not.
- Product names only: Hyperfabric, UCS, ConnectX, BlueField, Redfish. No internal codenames.
- If you do not know, say what you would check and what the result would mean. That still scores.
- Once per round, connect something to identity without being asked. The TPM, the Docker socket rule, Atrax credentials, or the MCP server all work.
The 60-second intro
"I'm Rishabh, a CS student at Penn State, graduating 2028. Last summer I interned at Cisco on AI infrastructure. I extended the production simulator for their cloud-managed data center fabric in Go and Python: device telemetry for switches, servers and BMCs, live port breakout on a virtual Linux network, and a proposal I ran with seven engineers for simulating customer servers end to end, including a software TPM for device identity. Before that I built internal AI tools and an MCP server at a bank, so I spent a summer inside compliance reviews. On my own I built Atrax, a platform where coding agents deploy apps with their own databases and URLs, and that is where I kept running into the problem I want to work on: identity and permissions for things that are not people. That is why Security and Identity."
Keep the IIT Madras degree for the education question only. Do not open with hackathons or TrendFlip.
Drill sprints
Same as the coding sprints: one question per column, out loud, 60-second timer, then the next. Three tonight, three Monday, Sprint 0 as the Tuesday warm-up. Open the answer only after you have said yours.
Only you can answer these
Each is marked check where it appears. Five minutes each, written down, before Tuesday.
- Breakout: watcher mechanism, interface types, exact tool and duration behind "0% dropped."
- 60%: exact weeks planned vs actual, and one real thing an agent got wrong that a test caught.
- Telemetry: the hardest fixture and why.
- Server proposal: the one contested open question and how it was resolved.
- Mashreq: where the models ran, what left the bank's boundary, how MCP callers authenticated, how the portal did login and roles.
- Atrax: per-app credentials or shared, migration bookkeeping, how tenants are isolated today, who holds the deploy token.
- One real failure with the change you made after it.
- One PDFSpacer production incident.
- One NotionBench finding that surprised you.
- Whether you ever saw real Hyperfabric hardware or only the simulator. Say it plainly either way.