# How a Cold Referral Got Me Into Microsoft (SDE-1, 2026)

> Microsoft interview experience: recruiter call, online assessment, then 3 interviews: DSA, DSA plus low-level design, and an AA round with a senior manager.

Canonical: https://devsunite.com/blog/how-a-cold-referral-got-me-into-microsoft-sde-1-2026
Last updated: 2026-10-15

- Author: Awadhesh
- Published: 2026-10-15
- Read time: 10 min

## Microsoft interview at a glance

- **Rounds**: Recruiter call, online assessment, then 3 interviews: DSA, DSA plus low-level design, and an AA round with a senior manager
- **Online assessment**: Codility, 2 coding questions in 90 minutes
- **Timeline**: Offer in week 9 of the author's timeline, with all three interviews within one week
- **Outcome**: Offer, SDE-1, with 1.5 years of experience

A year and a half ago, I was working at a tier-2 company, fixing bugs and building internal APIs, and Microsoft felt completely out of reach. No big-tech name on my resume, nobody I knew inside Microsoft, and every direct application I sent went unanswered.

What changed everything was one cold referral on LinkedIn. In 2026, I cleared the Microsoft SDE-1 interview with 1.5 years of experience. In this blog, I’m sharing everything: how I got the cold referral, how I fixed my resume, every interview round, the questions I was asked, and how I prepared while working a full-time job.

### My Background Before Microsoft

I joined a mid-sized tier-2 company as a backend developer right after graduation. My work was mostly building and maintaining REST APIs, writing SQL queries, fixing production bugs, and occasionally owning a small feature end to end.

The job taught me a lot about real-world code, but after about a year, I felt stuck. The scale was small, the tech stack wasn’t changing, and I knew I wanted to work on products used by millions. That’s when I decided to seriously aim for Microsoft.

The hardest part wasn’t the preparation. It was getting someone at Microsoft to even look at my resume.

### How I Got a Cold Referral at Microsoft

Applying directly on the Microsoft careers portal without a referral got me nowhere. My applications either went unanswered or got auto-rejected. So I switched to cold referrals, and this is the exact process I followed.

#### Step 1: Shortlist the Right Job IDs

I picked 3 to 4 SDE-1 openings on the Microsoft careers site that matched my experience (backend, cloud and services roles) and noted down their job IDs. Asking for a referral without a specific job ID makes it harder for the other person to help you.

#### Step 2: Find the Right People on LinkedIn

I searched LinkedIn for Microsoft software engineers in India, focusing on:

- Engineers in the same team or org as the job posting
- People who had moved to Microsoft from similar tier-2 or service companies
- Engineers with 1 to 4 years of experience, since they tend to reply more often than senior leaders

#### Step 3: Send a Short, Specific Message

Long messages don’t get read. This is roughly the message that worked for me:

```
Hi [Name], I'm a backend developer with 1.5 years of experience 
working on REST APIs and SQL-heavy services. I came across the 
SDE-1 role at Microsoft (Job ID: XXXXXX), and it matches my 
experience closely. Would you be open to referring me? I've 
attached my resume. Happy to share anything else you need. 
Thank you for your time!
```

#### Step 4: Follow Up Once, Politely

If someone didn’t reply in 4 to 5 days, I sent one short follow-up. Never more than that.

#### My Numbers

I messaged around 40 people over three weeks. About 8 replied, and 2 agreed to refer me. One referral was enough. A few days later, I got an email from Microsoft asking me to complete my application for the job ID.

**Lesson:** Cold referrals are a numbers game. Most people won’t reply, and that’s normal. Keep your message short, specific and respectful.

### Fixing My Resume Before Applying

Before sending any referral requests, I rewrote my resume completely. A referral gets you seen, but your resume decides whether you get shortlisted.

What I changed:

- **Kept it to one page.** I removed college clubs and irrelevant certifications.
- **Added impact with numbers.** Instead of “worked on APIs”, I wrote “built and maintained 12 REST APIs serving 50K+ daily requests” and “reduced query response time by 40% by optimizing indexes.”
- **Matched keywords from the job description**, such as distributed systems, REST, SQL, Azure, debugging and ownership.
- **Put ownership up front.** Bullets showing I owned something end to end went at the top of each section.

### Microsoft SDE-1 Hiring Process 2026: Overview

My complete process looked like this:

1. Recruiter call
2. Online assessment
3. Round 1: DSA interview
4. Round 2: DSA + low-level design
5. Round 3: AA (As Appropriate) round with a senior manager

All three interviews were virtual and happened within one week.

### Recruiter Call

About 10 days after the referral, a recruiter called me. It was a 15-minute conversation about my current role, notice period, why I wanted to join Microsoft, and my comfort with relocation. They also explained the interview process.

**Tip:** Keep your notice period answer clear and honest. If you can negotiate an early release, mention it.

### Online Assessment

The OA was on Codility, with 2 coding questions in 90 minutes.

- **Question 1:** An array-based problem using a sliding window. Find the longest subarray satisfying a given condition. Medium level.
- **Question 2:** A graph problem similar to finding connected components in a grid with a small twist. Medium level.

I solved both with all test cases passing in about 65 minutes and used the remaining time to check edge cases. For Microsoft, clean and correct solutions matter more than speed.

### Round 1: DSA Interview

The interviewer was a senior engineer, and the round lasted about 60 minutes. After a quick introduction, we went straight into coding.

**Question 1: Design and implement an LRU Cache**\
I started by explaining why a HashMap alone isn’t enough, then moved to a HashMap + Doubly Linked List approach with O(1) get and put. The interviewer asked follow-ups about thread safety and what would change if multiple threads accessed the cache.

**Question 2: A variation of Merge Intervals**\
Given meeting time slots, find the minimum number of rooms required. I first explained the sort-and-compare approach, then optimized it using a min-heap. I wrote clean code and walked through two test cases on my own.

**What went well:** I talked through my approach before writing a single line of code. The interviewer told me at the end that they liked how I handled edge cases without being asked.

### Round 2: DSA + Low-Level Design

This round was split into two parts.

**Part 1: DSA (25 minutes)**\
Serialize and deserialize a binary tree. I used preorder traversal with null markers. The interviewer asked me to dry-run my code on a skewed tree and asked about the time and space complexity of both functions.

**Part 2: Low-Level Design (35 minutes)**\
Design a notification system that can send messages through email, SMS and push notifications.

My approach:

- Created a `Notification` model and a `NotificationChannel` interface
- Built separate classes for `EmailChannel`, `SMSChannel` and `PushChannel`
- Used the Factory pattern to create channels and the Strategy pattern for retry logic
- Discussed how to add a new channel without changing existing code

The interviewer then asked how I’d handle failures and retries, and how to avoid sending duplicate notifications. My work experience helped a lot here, because I had handled retry logic in my current job.

### Round 3: AA (As Appropriate) Round

This was the final round, with a senior engineering manager, and it lasted about 50 minutes. At Microsoft, the AA round is often the deciding round.

**Questions asked:**

- Walk me through the most complex feature you’ve built at your current company.
- Tell me about a production issue you handled. What went wrong, and what did you learn?
- Describe a time you disagreed with a senior engineer.
- Why Microsoft, and why now?
- Where do you see yourself in two years?

There was also a small design discussion about how I’d scale one of my current company’s APIs if traffic grew 100 times. I talked about caching, database indexing, read replicas and rate limiting.

I answered behavioral questions using the STAR method and used real examples from my job. The manager seemed most interested in ownership: how I handled things when nobody told me exactly what to do.

### Result and Timeline

- **Week 1 to 3:** Sent cold referral messages
- **Week 4:** Referral submitted, completed application
- **Week 5:** Recruiter call
- **Week 6:** Online assessment
- **Week 7:** All three interview rounds
- **Week 9:** Received the offer

The two weeks after the final round were the hardest part of the whole journey. I got a call from the recruiter with the good news, and the offer letter followed a few days later.

### How I Prepared While Working Full-Time

Preparing with a full-time job was tough, so I kept the plan simple and consistent.

**Daily routine:**

- 1.5 hours before work for DSA
- 1 hour after work for revision or design
- 5 to 6 hours on weekends for mock interviews and LLD practice

**DSA (about 4 months):**\
I solved around 300 problems, mostly medium level, focused on arrays, strings, trees, graphs, heaps, dynamic programming and sliding window. Instead of solving random problems, I followed a curated sheet and revised old problems every weekend.

**Low-level design (about 1 month):**\
I practiced designing common systems like a parking lot, LRU cache, notification system, rate limiter and splitwise-style expense sharing. I focused on SOLID principles and patterns like Factory, Strategy, Observer and Singleton.

**Behavioral prep:**\
I wrote down 6 to 7 stories from my job covering ownership, failure, conflict, a tough deadline and learning something new, then practiced telling each in under two minutes.

**Mock interviews:**\
I did around 10 mock interviews with friends and on peer mock platforms. This helped me get comfortable thinking out loud.

### Mistakes I Made Along the Way

- **Applying without referrals at first.** I wasted almost two months sending applications that nobody saw.
- **Ignoring LLD early on.** I focused only on DSA for the first few months and had to rush design prep at the end.
- **Writing long referral messages.** My first few messages were paragraphs long and got zero replies.
- **Undervaluing my work experience.** I assumed my tier-2 company work wouldn’t matter, but it was the strongest part of my AA round.

### Tips for Getting Into Microsoft from a Tier-2 Company

- Your company’s name matters less than what you did there. Show impact with numbers.
- Cold referrals work if you message enough people and keep it short.
- Use your real work experience in design and behavioral rounds. It sets you apart from freshers.
- Be consistent. Two focused hours daily for a few months beats random long sessions.
- Don’t skip LLD if you have 1 to 3 years of experience. Microsoft expects it.

### Frequently Asked Questions

#### **How do I get a cold referral for Microsoft without contacts?**

Find Microsoft engineers on LinkedIn, especially those in the relevant team or with a similar background, and send a short message with the job ID and your resume. Expect a low reply rate and keep messaging consistently.

#### **How many rounds are there in the Microsoft SDE-1 interview 2026 for experienced candidates?**

In my case, there was an online assessment followed by three interviews: a DSA round, a DSA + LLD round, and the AA round with a senior manager. The number of rounds can vary by team.

#### **Can I get into Microsoft from a tier-2 company?**

Yes. Microsoft looks at your skills and impact, not just your company’s brand. A strong resume, a referral and good preparation matter much more.

#### **What is the AA round in Microsoft?**

The AA (As Appropriate) round is the final interview, usually with a senior manager. It covers your past work, behavioral questions and sometimes a design discussion, and it often plays a big role in the final decision.

#### **How long does Microsoft take to give results?**

For me, the result came about two weeks after the final round. Timelines can vary from a few days to a few weeks depending on the team.

### Conclusion

Getting into Microsoft from a tier-2 company with 1.5 years of experience wasn’t about luck. It took a better resume, dozens of cold messages, months of consistent preparation after work, and using my real job experience in the interviews.

If you’re in a similar position right now, sending referral requests that go unanswered and studying after long workdays, keep going. Your background doesn’t decide where you end up. Your preparation does.

## Related

- [Microsoft jobs hiring now](https://devsunite.com/companies/microsoft)
- [Microsoft coding interview questions](https://devsunite.com/resources/faang-interview-questions/microsoft)
- [Microsoft interview process](https://devsunite.com/interview-process/microsoft-interview-process)
- [AI mock interview practice](https://devsunite.com/mock-interview)
- [FAANG coding interview questions by company](https://devsunite.com/resources/faang-interview-questions)
- [Striver's A2Z DSA Sheet](https://devsunite.com/resources/dsa-sheets/striver-a2z)
- [Love Babbar DSA Sheet](https://devsunite.com/resources/dsa-sheets/love-babbar)
- [My Microsoft SDE Interview Experience as a Fresher (2026)](https://devsunite.com/blog/my-microsoft-sde-interview-experience-as-a-fresher-2026)
- [My Amazon SDE-1 Interview Experience as a Fresher (2026)](https://devsunite.com/blog/my-amazon-sde-1-interview-experience-as-a-fresher-2026)
- [My Zepto SDE-1 Interview Experience as a Fresher (2026)](https://devsunite.com/blog/my-zepto-sde-1-interview-experience-as-a-fresher-2026)
- [Getting Hired at Sarvam AI: My Fresher Interview Story](https://devsunite.com/blog/getting-hired-at-sarvam-ai-my-fresher-interview-story)
- [Share your interview experience](https://devsunite.com/share-interview-experience)
- [All blog posts](https://devsunite.com/blogs)
