How the Amazon SDE II Online Assessment Works, and What to Practise

Amazon’s SDE II online assessment consists of two technical questions to be solved in 90 minutes, followed by a loop of four 55-minute interviews. This structure demands a specific preparation strategy focused on speed, code correctness, and core algorithmic patterns rather than broad but shallow coverage.

The 45-Minute Reality

The most critical constraint is the time allocation. With two questions in 90 minutes, you have an average of 45 minutes per problem. This is not a relaxed environment for exploring multiple approaches. You must identify the optimal solution within the first ten to fifteen minutes. If you spend twenty minutes writing a brute-force solution that works for small inputs but fails on large ones, you have already lost the round. The system evaluates your code against hidden test cases, including edge cases and large inputs that will time out inefficient algorithms.

This means your practice sessions must mimic this pressure. Do not practice by reading solutions. Practice by setting a timer for 45 minutes and attempting to write a complete, compilable solution from scratch. If you cannot solve a medium-difficulty problem in that window, you are not ready. The goal is not to solve every possible problem, but to recognize patterns quickly. For example, if you see a problem involving finding the shortest path in a weighted graph, you should immediately think of Dijkstra’s algorithm. If you hesitate for ten minutes trying to derive it, you will run out of time for the second question.

Code Quality Over Pseudocode

Many candidates make the mistake of writing pseudocode or incomplete snippets. The assessment requires full, compilable code. This includes proper function signatures, variable declarations, and handling of input/output formats. A common failure point is not the logic itself, but syntax errors or missing imports that cause the code to fail compilation.

Consider a problem where you need to merge two sorted arrays. A candidate might correctly describe the two-pointer approach in their head but fail to write the loop conditions correctly in Java or Python. The compiler does not care about your intent; it cares about syntax. During practice, always run your code. Do not just look at it. Ensure it handles empty arrays, single-element arrays, and duplicate values. These edge cases are frequently tested and are the difference between a passing score and a rejection.

Priority Topics for SDE II

Amazon’s own resources list data structures and algorithms first, and for good reason. The SDE II level expects proficiency in core topics that appear in a high percentage of assessments. You should prioritize the following areas in this order:

1. Arrays and Strings: These are the foundation. Problems involving sliding windows, two pointers, and prefix sums are common. You must be able to solve these in O(n) time and O(1) space where possible.
2. Hash Maps and Sets: These are essential for solving problems in linear time. If you find yourself using nested loops to check for existence, you are likely missing a hash map solution.
3. Trees and Graphs: Binary trees and graph traversals (BFS and DFS) are frequent. You need to be comfortable with recursion and iterative approaches. For graphs, understand when to use adjacency lists versus matrices.
4. Dynamic Programming: This is often the hardest part for many candidates. Focus on standard patterns like knapsack problems, longest common subsequence, and grid path problems. You do not need to master every DP variant, but you must recognize the state definition and transition logic quickly.

Do not waste time on obscure data structures or advanced math problems unless you have already mastered the core topics. The assessment is designed to test your ability to apply standard algorithms to new problems, not to test your knowledge of rare data structures.

The Interview Loop

After the online assessment, you face four 55-minute interviews. These are not just coding rounds. They include system design, behavioral questions, and additional coding. The coding interviews are similar in difficulty to the online assessment but allow for more discussion. You can ask clarifying questions and discuss trade-offs. However, the expectation for clean, efficient code remains the same.

A key difference is the interaction. In the online assessment, you are alone. In the interview, you are expected to think out loud. If you get stuck, explain your thought process. Do not go silent. Interviewers want to see how you approach problems, not just the final answer.

Final Preparation Steps

Check Amazon’s official career page for the most current details on the SDE II process. Formats can change, and specific question types may vary by region or team. Do not rely on outdated information from forums or social media.

To prepare, use a platform that provides timed practice with real coding environments. DSA Tracker offers such resources, allowing you to simulate the pressure of the 90-minute window. Focus on consistency. Solve one or two problems daily, reviewing your mistakes. The goal is to build muscle memory for common patterns so that you can spend your time on the logic, not the syntax.

Start by solving one medium-difficulty array problem in under 30 minutes today. If you cannot, identify where you got stuck and review that specific pattern. Repeat this until it becomes automatic.