Find a lesson, question or project

Start typing to search published content and planned structures.

↑ ↓ moveEnter openEsc close

Prepare for the company.
Learn beyond the question.

Software and backend prep for 50 priority companies. Read source-linked company research, then build a practical plan for your role and level.

Find company questions · General practice prompts · Strict role/date question browser

Reviewed snapshot · 1 Oct 2026 · India + global · Live fetching is not active yet

Company research library

136 reported questions/topics across 27 companies. Four more have official guidance; 19 have research gaps. Read each account’s role, location and date limits before applying it to your interview.

Read company research
Browse all 50 companies and their research coverage

50 companies

Build a timed role-specific brief

These filters use 6 narrowly scoped reviewed profiles. Broader research above includes accounts with unknown dates or levels; those are not forced into a matching brief.

Location, report window and preparation time

Report windows are measured from the snapshot date, not a live feed. Specific location filters exclude reports with an unknown location.

Reviewed examples:

Amazon · Software engineer

Mid-level · India + global · 12 months before 1 Oct 2026

Read broader company research and source limits

3 distinct candidate reports · 12 reported questions / topics · SDE II / L5

What these reports suggest

Counts describe this small sample, not the probability that a question will appear. Read the sources before treating a topic as a priority.

SDE II / L5. Reports differ in assessment format and round order. Confirm the current loop and AI-tool rules with your recruiter.

Round types reported

  • Assessment 3 of 3 reports
  • Coding 3 of 3 reports
  • Low-level design 2 of 3 reports
  • System design 3 of 3 reports
  • Behavioral 3 of 3 reports
  • Phone screen 1 of 3 reports

Round order and duration vary. These are round types mentioned in the reports, not a guaranteed interview sequence.

Questions people reported

Named problems, variants and broad topics are labelled separately. A related practice link is an analogue, not proof that the exact LeetCode problem was asked.

Your 14-day preparation plan

Our suggested allocation for 90 minutes a day, based on the filtered reports. It is a starting point, not the company’s syllabus. Adapt it to your recruiter’s advice and your own gaps.

Each day: 15 min read / recall · 50 min practise · 25 min test / review. Keep a mistake log outside this page.

  1. Day 1

    Set a baseline and confirm your interview loop

    Ask your recruiter about rounds, team scope and allowed tools. Attempt one coding problem, outline one design and list your weakest areas.

    Finish with: A confirmed format, a gap list and a short list of real project stories.

    Evidence behind this session
  2. Day 2

    Object-oriented and low-level design

    Clarify requirements, model responsibilities and add a new requirement cleanly.

    Finish with: Small interfaces, explicit state transitions and testable collaborators.

    Open practice topic
    Evidence behind this session
  3. Day 3

    System design

    Design a service from requirements through APIs, data, bottlenecks and failures.

    Finish with: A readable diagram and two defended scaling/reliability trade-offs.

    Open practice topic
    Evidence behind this session
  4. Day 4

    Code reading, testing and debugging

    Read unfamiliar code, add focused tests and fix a bug. Verify any AI suggestion.

    Finish with: A reproducible failing test, a minimal fix and a clear explanation.

    Open practice topic
    Evidence behind this session
  5. Day 5

    Shortest paths and graph follow-ups

    Compare BFS, multi-source BFS and Dijkstra. Explain when each applies.

    Finish with: A justified algorithm choice and one changed-constraint follow-up.

    Open practice topic
    Evidence behind this session
  6. Day 6

    Binary search and arrays

    Solve a binary-search problem and explain the invariant before writing code.

    Finish with: Correct bounds, termination and empty/single-element tests.

    Open practice topic
    Evidence behind this session
  7. Day 7

    Graphs and traversal

    Model a problem as a graph, implement BFS and DFS, and explain visited state.

    Finish with: Working traversal code, edge cases and time/space analysis.

    Open practice topic
    Evidence behind this session
  8. Day 8

    Intervals and difference arrays

    Practise interval merging and range updates using a difference array.

    Finish with: A brute-force baseline, a faster approach and overlapping-range tests.

    Open practice topic
    Evidence behind this session
  9. Day 9

    Strings, stacks and hashing

    Practise a string parsing or frequency-counting problem with tricky inputs.

    Finish with: Correct handling of repeated characters, nesting and empty input.

    Open practice topic
    Evidence behind this session
  10. Day 10

    Trees and recursion

    Implement tree traversal and explain the base case and return value.

    Finish with: A dry run on a skewed tree and a complexity explanation.

    Open practice topic
    Evidence behind this session
  11. Day 11

    Behavioral and project discussion

    Tell a real project story: situation, task, your actions, results and learning.

    Finish with: A specific three-minute story with honest evidence and follow-up answers.

    Evidence behind this session
  12. Day 12

    Timed follow-up: Object-oriented and low-level design

    Clarify requirements, model responsibilities and add a new requirement cleanly. Repeat without notes and change one constraint.

    Finish with: Small interfaces, explicit state transitions and testable collaborators.

    Open practice topic
    Evidence behind this session
  13. Day 13

    Timed follow-up: System design

    Design a service from requirements through APIs, data, bottlenecks and failures. Repeat without notes and change one constraint.

    Finish with: A readable diagram and two defended scaling/reliability trade-offs.

    Open practice topic
    Evidence behind this session
  14. Day 14

    Run a mixed mock and review your gaps

    Practise a coding/design round aloud. Test the code and answer follow-ups. Review mistakes without memorising answers.

    Finish with: A timed explanation, tested solution or design, and three specific next steps.

    Evidence behind this session

Original reports and limits

Manually reviewed on 1 Oct 2026. This page does not fetch new posts when you submit the form. Dates below distinguish interview dates from publication dates.

  1. Amazon SDE II · Bengaluru · August 2026

    LeetCode Discuss · SDE II · Bengaluru, India

    · Interview date · Month only; exact day not stated

    A candidate described graph follow-ups, low-level design, configuration-sync design and Leadership Principles throughout the loop.

  2. Amazon SDE II · Redmond · June 2026 report

    Reddit · SDE II · Redmond, United States

    · Report publication date; interview date not confirmed

    A US candidate reported practical coding, a storage-system design round, behavioral questions and an AI-assisted refactoring assessment.

  3. Amazon SDE II · February 2026

    LeetCode Discuss · SDE II / L5 · Location not stated

    · Interview date · Month only; exact day not stated

    The report combines interval/range-update coding, systems design, object-oriented design and detailed behavioral follow-ups.

Browse the strict role/date question sample

Find a question to practise

This browser uses the existing date/level-confirmed sample, not the broader 50-company research library above. Search by company, role and category. These are short reported questions/topics—not complete problem statements or a difficulty-rated question database. Related practice links are labelled separately.

35 reviewed questions / topics · Full reviewed sample · Snapshot 1 Oct 2026

Browse 50 priority companies · 145 total companies · 24 role families

All 50 priority companies have general software/backend starter plans, from intern through staff, and a research page linked below. The 6 reviewed examples above have filterable reports for their specific role and level. Other roles and management remain pending. This is not a list of current vacancies or every employer.

Your 50-company shortlist

More companies · research pending

Fintech

Enterprise software

Consumer technology

India product companies

Financial services

Hardware & systems

Data & infrastructure

AI companies

Consulting & services

Quantitative trading

Role families

Seniority

Intern · Entry / new graduate · Mid-level · Senior · Staff / principal · Engineering manager

Job titles and levels differ by employer. This page keeps role and seniority separate instead of treating SDE II, L4 and E4 as universal equivalents.