Episode 127
How to Get Hired for Microsoft AI Roles Without Applying in 2026 using Recruiter Inbound Playbook - w/ Shrey
Shrey Shah never applied to Microsoft. Microsoft executives watched him give a talk on AI coding workflows, then reached out.
How Shrey got hired for a Microsoft AI role without applying.
In this episode, Shrey explains how he joined Microsoft's AI team as a senior software engineer through recruiter inbound rather than a cold application. The conversation covers why traditional job applications are weaker in an AI-saturated market, how a conference talk on AI coding workflows led to the Microsoft conversation, what a no-LeetCode AI interview tested instead, and how developers can build durable visibility through Cursor, v0, agents, skills, subagents, LinkedIn, X, and real projects.
- Shrey says he did not apply for the Microsoft role; the opportunity came inbound after a Microsoft executive heard his talk on AI coding workflows.
- The episode says Meta also reached out for similar AI engineering and workflow-change work.
- Shrey says his Microsoft process included four interview rounds, with two technical rounds that were not standard LeetCode interviews.
- The technical interview tested how he solved a hard issue while communicating, context switching, and managing agent-like workflows.
- Shrey argues that AI has weakened traditional resume-based job applications because many candidates can now generate similar tailored resumes.
- He recommends building projects that solve real problems, then posting the learning journey and point of view on LinkedIn or X.
- The conversation distinguishes skills, MCP servers, and subagents as parts of modern AI coding workflows.
- Shrey predicts software, product, research, and automation responsibilities will keep merging as AI tools become more capable.
Who this is for
- You are trying to get hired without sounding like everybody else in the pile.
- You would rather hear Shrey's version while the mess is still fresh than get another polished hindsight sermon.
Key takeaways
- Get Hired for Microsoft AI Roles Without Applying in 2026 using Recruiter Inbound Playbook - w/ Shrey
- How to Get Recruiter Inbound in Tech
- Shrey says his interview was different because the role was different. The role was still software engineering, but it...
Fast scan timestamps
Read the complete transcript
The edited transcript keeps the speakers' ideas, timestamps, and specific details while removing repetition and filler.
Transcript-backed moments
A few lines worth stealing before you hand over the full hour.
This episode is about how Shrey got hired into a Microsoft AI role without cold applying. Naman frames the conversation around a job market where traditional applications, ATS submissions, and generic resumes are weaker than they used to be. The hook is simple: Shrey says Microsoft came inbound after hearing his work on AI coding workflows, and Meta also reached out for similar work.
Shrey says he did not get a Microsoft callback because he had not applied for the job at Microsoft in the first place. The opportunity was inbound. He had given a talk at a conference about AI coding workflows, building agents, and bringing security, testing, and AI together. A Microsoft executive heard the talk, found it interesting, and that started the conversation that led to the interview process.
After the conference conversation, Shrey went through a couple of interview rounds and joined Microsoft. He says he had not applied for a job in roughly seven years. That becomes the core lesson of the episode: if the market already knows what you are unusually good at, the best opportunities can come through reputation and visibility rather than cold applications.
Naman asks whether the Microsoft interview felt like a normal big-tech software engineering loop with LeetCode. This matters because many candidates still prepare for AI roles as if the interview is only data structures, algorithms, and whiteboard problem solving.
Shrey says his interview was different because the role was different. The role was still software engineering, but it was also about helping bring a culture change around AI workflows inside Microsoft. The interview tested whether he could do things differently, do them more efficiently, and build for the kind of work that is coming rather than only for older interview formats.
Show notes
Shrey Shah never applied to Microsoft. Microsoft executives watched him give a talk on AI coding workflows, then reached out. Meta came knocking not long after, asking for something similar. Here's the part that stings a little: that wasn't luck.
FAQ
How did Shrey get hired for a Microsoft AI role without applying?
Shrey says the Microsoft opportunity came inbound after he spoke at a conference about AI coding workflows, agents, security, and testing. A Microsoft executive heard the talk, started a conversation, and that led into the interview process.
Did the Microsoft AI interview use LeetCode?
According to Shrey, his technical rounds were not standard LeetCode. They tested how he solved a hard engineering problem, communicated with interviewers, context-switched, and used AI-style workflows to produce reliable code.
Why does Shrey say traditional job applications are broken?
He argues that AI has made resumes and applications easier to mass-produce and tailor, so candidates who only rely on ATS submissions are hard to distinguish. His alternative is public proof: useful projects, visible opinions, networking, and consistent posting.
What should engineers post online to attract recruiter inbound?
Shrey recommends posting what you are learning, your point of view on AI tools, and projects that solve real problems you actually care about. He says generic portfolio projects are weaker than proof that you can think, build, and explain your work.
What is the difference between a skill and a subagent in Shrey's AI workflow explanation?
Shrey describes a skill as reusable instructions for how to do something, while a subagent handles a dedicated piece of work, often with context isolation and parallelism. He says understanding skills, subagents, hooks, rules, and MCP servers gives developers a major advantage with AI coding tools.
More in Get Hired
Same mess. Different guest. Pick the next conversation that feels closest to your real life.