Microsoft (India)

Who can generally apply

• Microsoft states that degree requirements are always listed in the job description under the qualifications section. There is no single global eligibility rule.
• Microsoft runs distinct student tracks, including internships for students at various stages and programmes aimed at first and second year students. Note that some of the named early-year programmes on Microsoft's global pages are based at specific overseas locations, so check whether a given programme is actually open to students in India rather than assuming.
• Microsoft also hires students into non-engineering roles, including product management, technical program management, product design, UX research, and data and applied science.

What you must confirm yourself

• Microsoft does not publish a marks cutoff. Any site quoting one is guessing.
• Eligible graduation windows, locations and degree requirements are specified per posting only.
• Microsoft says to allow up to around ninety days for a decision on an application, so plan your timeline accordingly rather than assuming silence means rejection.

Stages, as Microsoft describes them for students

Microsoft publicly describes a two-stage interview process for students: an initial interview, and if selected, a second and final interview.

• All student interviews are described as virtual.
• Candidates should expect both behavioural and technical or functional questions on the interview day.
• Depending on the role, you may be asked to write code, submit a portfolio, or provide work samples.
• Microsoft says it sends interview preparation details and role-specific guidance to candidates once they are invited to interview, and publishes role-specific preparation videos.

Team matching

Microsoft describes initial screens as assessing candidates for functional roles broadly, with final rounds focused on a specific role within an organisation, and team matching based on interview feedback and candidate preferences. Being technically successful and still waiting on a team match is a normal state, not a failure signal.

What Microsoft says interviewers look for

Microsoft describes its interviewers as trying to discover your foundational knowledge, evaluate your critical thinking, and assess your problem-solving ability and your capacity to learn, focusing on experience and skills that translate to the role.

Caveats

• The two-stage description is Microsoft's own framing for students, but the number of individual conversations inside a stage varies. Candidates commonly report multiple back-to-back technical interviews within a final round, and some campus drives are commonly reported to add an initial online coding round. Neither is a published fixed format.
• Formats differ by role and by year. Read what your recruiter sends you.

Data structures

• Arrays, strings, hash maps and hash sets
• Stacks, queues, linked lists
• Trees, binary search trees, tries
• Heaps and priority queues
• Graphs and their representations

Algorithms

• Sorting and binary search
• Recursion and backtracking
• Breadth-first and depth-first search, shortest paths, topological sort
• Dynamic programming, from one-dimensional up to grid problems
• Greedy techniques and their failure modes
• String algorithms and manipulation
• Complexity analysis, stated clearly for every solution you give

Coding craft

Microsoft interviews weigh how you write code, not only whether it works.

• Correct handling of edge cases: empty input, single element, duplicates, overflow, null
• Clean naming and structure, written the way you would in real code
• Being able to walk through your own code with a concrete example and find your own bug
• Writing code without an IDE, on a shared editor or whiteboard

Computer science fundamentals

• Object-oriented design and design principles
• Operating systems: processes and threads, concurrency, synchronisation, deadlock, memory management, virtual memory
• Databases: schema design, indexes, joins, transactions
• Computer networks: TCP and UDP, HTTP, DNS, latency and caching
• Introductory system design: components, APIs, storage choices, trade-offs, and being able to explain why

Behavioural and communication

Microsoft explicitly says to expect behavioural questions alongside technical ones.

• Concrete stories about projects, teamwork, disagreement, failure and learning something new quickly
• Being able to explain a technical decision to someone who was not there
• Genuine curiosity, since Microsoft names capacity to learn as something interviewers assess

Your own work

• One or two projects you can discuss to real depth: what you chose, what you rejected, what broke, and what you would change

If you have one to three years

• Build data structures and algorithms skill steadily over years, not weeks. This is the core competency and it accumulates slowly. Two or three problems a week from second year beats any final-semester sprint.
• Choose one language and get deeply fluent, including its standard containers and its idioms.
• Practise talking through your reasoning aloud while solving. Microsoft says interviewers assess critical thinking and problem-solving, which means the visible thinking is part of what is scored, not just the final code.
• Practise writing code without an IDE, then check it by hand for edge cases before compiling.
• Actually learn operating systems, databases and networks in your coursework instead of memorising for the exam and discarding. Microsoft interviews probe fundamentals rather than framework knowledge.
• Build one substantial project, ideally with someone else, so you have a genuine story about disagreement, trade-offs and things breaking.
• Prepare for the behavioural half seriously. Microsoft names it explicitly, and strong coders lose offers by treating it as a formality.
• Get comfortable on video calls, since Microsoft states that student interviews are virtual. Test your setup, and practise explaining a diagram without a physical whiteboard.
• Watch Microsoft's own role-specific preparation videos, since they are the closest thing to a published statement of what a given role's interviews look like.
• Apply early in the cycle and be patient afterwards. Microsoft itself says decisions can take up to around ninety days.

The honest caveat

Microsoft publishes what its interviewers look for and the broad two-stage shape for students, and that grounds the advice above. It does not publish a syllabus, a question list, a cutoff, or an India-specific campus process. The topic list above reflects what Microsoft-style fundamentals interviews consistently probe, but it is not a Microsoft-issued syllabus. Check the specific posting and whatever your recruiter sends you.