What is expected in the coding round (DSA) at SDE 1?

The largest part of the loop: often three coding rounds. Medium problems, sometimes one hard. Correct, clean code and clear reasoning matter more than speed.

What is expected in the coding round (DSA) at SDE 2?

Two or three rounds at medium to hard level. You are expected to reach the optimal approach with fewer hints and to test without being asked.

What is expected in the coding round (DSA) at SDE 3?

Usually two rounds. Same difficulty, but interviewers expect quick, confident problem solving and production-quality code.

What is expected in the coding round (DSA) at SDE 4?

One or two rounds, sometimes design-flavoured (build a small class with several methods). Coding is a bar to clear, not where level is decided.

INTERVIEW ROUNDS

The coding round (DSA)

A 45 to 60 minute live interview where you solve one or two data-structures-and-algorithms problems while explaining your thinking. Interviewers score problem solving, code quality, testing and communication.

What happens

The interviewer gives a problem, often vague on purpose. You clarify the inputs and constraints, propose a brute force, improve it, agree on the approach, write clean code, then walk through tests and complexity. Follow-up questions change a constraint to see how you adapt. Most companies score four things: problem solving, coding, verification and communication.

What is expected at each level

Your level

SDE 1 · New grad to about 2 years: The largest part of the loop: often three coding rounds. Medium problems, sometimes one hard. Correct, clean code and clear reasoning matter more than speed.
SDE 2 · About 2 to 5 years: Two or three rounds at medium to hard level. You are expected to reach the optimal approach with fewer hints and to test without being asked.
SDE 3 · Senior, about 5 to 10 years: Usually two rounds. Same difficulty, but interviewers expect quick, confident problem solving and production-quality code.
SDE 4 · Staff, principal and above: One or two rounds, sometimes design-flavoured (build a small class with several methods). Coding is a bar to clear, not where level is decided.

How to prepare

Work through the patterns on AlgoRung in order, not random problems: each pattern unlocks dozens of questions.
For every problem, say the brute force first, then improve it: interviewers score the path, not just the answer.
Revise on schedule: AlgoRung brings each solved problem back twice so it sticks.
Practise in the language you will interview in; the editor supports Java, Python, C++ and JavaScript.

Common mistakes

Jumping to code without confirming the approach
Not stating time and space complexity
Never testing: walk through one normal case and one edge case
Getting stuck silently instead of asking a clarifying question

Companies that use it

Google · All levels
Junior loops are mostly coding (about 3 rounds); senior loops drop to about 2 as design rounds take their place, and some prompts ask you to build a small class with several methods.
Amazon · All levels
Each round is usually one or two medium problems (sometimes hard), and Leadership Principle questions open or close every technical round.
Microsoft · All levels
Code runs in a tool that compiles and executes it, pseudocode is not accepted, and you are expected to test your own solution; new-grad loops are often three coding rounds.
Meta · All levels
One traditional coding round without AI, usually two problems; interviewers expect you to find your own bugs.
Apple · All levels
Coding rounds focus on edge cases, defensive code and often concurrency, in the language the team uses (Swift, C++, Python, Java, Go).
Netflix · All levels
The technical screen is live coding, usually a practical problem tied to the team's domain rather than a puzzle.
Uber · All levels
The business phone screen mixes coding with some design, and largely sets the level you interview for.
LinkedIn · All levels
The technical phone screen has one or two DSA problems with a main interviewer and a shadow.
Airbnb · All levels
The technical screen requires running code, not pseudocode, on medium-hard problems often framed around bookings.
Stripe · All levels
The technical screen is one long, multi-part, real-world prompt (CSV parsing, ledgers) that you pair-code and test yourself.
Atlassian · All levels
The 'Data Structures' half of the coding interview: an algorithm problem with follow-ups, scored on clean code, naming and testing your own work without being asked.
Goldman Sachs · All levels
Superday DSA rounds, often with two interviewers: mostly medium problems with many follow-ups; Java internals (HashMap, garbage collection) are common.
Salesforce · All levels
Live coding where interviewers often require the optimal complexity before you start coding.
Oracle · All levels
Rounds that mix DSA with grilling on past projects and Java or REST deep dives.
Adobe · All levels
DSA rounds with one or two medium-to-hard problems, plus DBMS, OS and sometimes SQL questions.
Flipkart · SDE 1, SDE 2, SDE 3
Problem Solving & Data Structures (PSDS): usually two medium problems, often DP, trees, recursion or graphs; some candidates get a second PSDS round.
Walmart Global Tech · SDE 1, SDE 2, SDE 3
Two easy-to-medium problems, sometimes wrapped in a REST endpoint with validation and error handling.
PhonePe · SDE 1, SDE 2, SDE 3
PSDS: two problems candidates often rate hard; a well-explained approach can earn partial credit.
Swiggy · SDE 1, SDE 2, SDE 3
Live DSA, usually medium problems (intervals, arrays, graphs, BST).

Other rounds

The online assessment (OA) · The phone screen · The AI-assisted coding round · Low-level design and machine coding · The system design round (HLD) · Team-specific rounds · The behavioral round · The hiring manager round · The bar raiser round · Team match and hiring committee