Behavioral and project discussion
Tell a real project story: situation, task, your actions, results and learning.
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
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.
50 companies
No companies match. Clear your search or choose All coverage.
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.
Mid-level · India + global · 12 months before 1 Oct 2026
3 distinct candidate reports · 12 reported questions / topics · SDE II / L5
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.
Tell a real project story: situation, task, your actions, results and learning.
Clarify requirements, model responsibilities and add a new requirement cleanly.
Design a service from requirements through APIs, data, bottlenecks and failures.
Read unfamiliar code, add focused tests and fix a bug. Verify any AI suggestion.
Compare BFS, multi-source BFS and Dijkstra. Explain when each applies.
Solve a binary-search problem and explain the invariant before writing code.
Model a problem as a graph, implement BFS and DFS, and explain visited state.
Practise interval merging and range updates using a difference array.
Practise a string parsing or frequency-counting problem with tricky inputs.
Implement tree traversal and explain the base case and return value.
Round order and duration vary. These are round types mentioned in the reports, not a guaranteed interview sequence.
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.
A custom problem gained multi-source traversal requirements.
The author compared the problem with this LeetCode question.
Model return slots and discuss finding a nearby drop location.
A custom system-design discussion; full requirements were not published.
The follow-up asked for a faster range-update solution.
Discuss ingestion, alerting and backpressure.
Model responsibilities and machine states.
The discussion included token buckets and concurrent updates.
A phone-screen traversal question.
Object-oriented code, corner cases and telemetry were discussed.
The author described a whiteboard discussion of read/write flows.
Exact input constraints were not supplied.
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.
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.
Clarify requirements, model responsibilities and add a new requirement cleanly.
Finish with: Small interfaces, explicit state transitions and testable collaborators.
Open practice topicDesign a service from requirements through APIs, data, bottlenecks and failures.
Finish with: A readable diagram and two defended scaling/reliability trade-offs.
Open practice topicRead 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 topicCompare BFS, multi-source BFS and Dijkstra. Explain when each applies.
Finish with: A justified algorithm choice and one changed-constraint follow-up.
Open practice topicSolve a binary-search problem and explain the invariant before writing code.
Finish with: Correct bounds, termination and empty/single-element tests.
Open practice topicModel 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 topicPractise interval merging and range updates using a difference array.
Finish with: A brute-force baseline, a faster approach and overlapping-range tests.
Open practice topicPractise a string parsing or frequency-counting problem with tricky inputs.
Finish with: Correct handling of repeated characters, nesting and empty input.
Open practice topicImplement 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 topicTell 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.
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 topicDesign 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 topicPractise 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.
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.
· 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.
· 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.
· 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.
Continue your research: Search LeetCode Discuss Search recent Reddit posts
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
Google · Software engineer · L4
Coding · Reported topic · 24 Aug 2026 (report date)
The round also included a graph/matrix follow-up.
Google · Software engineer · L4
Coding · Reported topic · 24 Aug 2026 (report date)
The author described a hard graph problem, without complete constraints.
Google · Software engineer · L4
Coding · Reported topic · 24 Aug 2026 (report date)
The exact problem title was not given.
Amazon · Software engineer · SDE II
Coding · Reported topic · Aug 2026 (interview date)
A custom problem gained multi-source traversal requirements.
Amazon · Software engineer · SDE II
Coding · Reported variant · Aug 2026 (interview date)
The author compared the problem with this LeetCode question.
Amazon · Software engineer · SDE II
Design · Reported topic · Aug 2026 (interview date)
Model return slots and discuss finding a nearby drop location.
Amazon · Software engineer · SDE II
Design · Reported topic · Aug 2026 (interview date)
A custom system-design discussion; full requirements were not published.
Amazon · Software engineer · SDE II
Coding · Reported topic · 27 Jun 2026 (report date)
A phone-screen traversal question.
Amazon · Software engineer · SDE II
Coding · Reported topic · 27 Jun 2026 (report date)
Exact input constraints were not supplied.
Amazon · Software engineer · SDE II
Practical coding · Reported topic · 27 Jun 2026 (report date)
Object-oriented code, corner cases and telemetry were discussed.
Amazon · Software engineer · SDE II
Design · Reported topic · 27 Jun 2026 (report date)
The author described a whiteboard discussion of read/write flows.
Salesforce · Software engineer · MTS · candidate reported 3 years of experience
Coding · Reported topic · 6 Jun 2026 (interview date)
Find the exit order when unfinished withdrawals return to the queue.
Salesforce · Software engineer · MTS · candidate reported 3 years of experience
Coding · Named problem · 6 Jun 2026 (interview date)
The report links this exact problem.
Salesforce · Software engineer · MTS · candidate reported 3 years of experience
Coding · Reported topic · 6 Jun 2026 (interview date)
Random selection must give elements equal probability.
Salesforce · Software engineer · MTS · candidate reported 3 years of experience
Coding · Reported topic · 6 Jun 2026 (interview date)
Count three-part contiguous splits satisfying S2 ≤ S1 + S3.
Salesforce · Software engineer · MTS · candidate reported 3 years of experience
Coding · Reported topic · 6 Jun 2026 (interview date)
Repeatedly halve an element; the candidate used a max heap.
Salesforce · Software engineer · MTS · candidate reported 3 years of experience
Coding · Reported topic · 6 Jun 2026 (interview date)
The author did not remember the exact statement.
Google · Software engineer · Interviewed for L4; reported L3 outcome
Coding · Reported topic · Apr 2026 (interview date)
The author reported an unusual follow-up.
Google · Software engineer · Interviewed for L4; reported L3 outcome
Coding · Reported topic · Apr 2026 (interview date)
No exact question name was published.
Google · Software engineer · Interviewed for L4; reported L3 outcome
Coding · Reported topic · Apr 2026 (interview date)
A follow-up changed the space-efficiency requirement.
Uber · Software engineer · SDE II
Coding · Reported topic · 27 Feb 2026 (interview date)
Optimize the selection follow-up; the reported binary-search attempt missed edge cases.
Uber · Software engineer · SDE II
Coding · Reported variant · 27 Feb 2026 (interview date)
Return original values, not squares. The author used a two-pointer merge.
Amazon · Software engineer · SDE II / L5
Coding · Reported variant · Feb 2026 (interview date)
The follow-up asked for a faster range-update solution.
PayPay · Backend engineer · SDE II · backend
Backend · Reported topic · Feb 2026 (interview date)
Discuss correctness, query performance and concurrency.
Amazon · Software engineer · SDE II / L5
Design · Reported topic · Feb 2026 (interview date)
The discussion included token buckets and concurrent updates.
PayPay · Backend engineer · SDE II · backend
Coding · Named problem · Feb 2026 (interview date)
Linked by the candidate in the technical round.
PayPay · Backend engineer · SDE II · backend
Coding · Reported variant · Feb 2026 (interview date)
Start with downward paths, then allow paths in any direction.
PayPay · Backend engineer · SDE II · backend
Backend · Reported topic · Feb 2026 (interview date)
Explain retry safety and API idempotency.
Amazon · Software engineer · SDE II / L5
Design · Reported topic · Feb 2026 (interview date)
Discuss ingestion, alerting and backpressure.
PayPay · Backend engineer · SDE II · backend
Design · Reported topic · Feb 2026 (interview date)
Discuss APIs, data modelling and concurrent bookings.
Amazon · Software engineer · SDE II / L5
Design · Reported topic · Feb 2026 (interview date)
Model responsibilities and machine states.
Meta · Software engineer · E4 · infrastructure
Practical coding · Reported topic · 23 Dec 2025 (report date)
AI-assisted code repair in several tasks; exact code was withheld.
Meta · Software engineer · E4 · product
Coding · Reported topic · 30 Jan 2025 (report date)
Full input and output constraints were not supplied.
Meta · Software engineer · E4 · product
Coding · Named problem · 30 Jan 2025 (report date)
Named by the candidate in the onsite coding round.
Meta · Software engineer · E4 · product
Coding · Reported topic · 30 Jan 2025 (report date)
An older report named this cache topic.
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.
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.