Android & iPhone apps are coming soon. Log in for a plan and reminders made for you β†’

Day 70EasyLeetCode (448)

Find All Numbers Disappeared in an Array

In-Place Marking

Asked at 7 companies

3 recent

  • Google
  • Amazon
  • Microsoft
  • Tinkoff
  • Bloomberg
  • tcs
  • Meta

Community-reported Β· source Β· updated 2026-10-08. ● asked in the last 6 months.

  1. 1Basics
  2. 2Paper
  3. 3Code it
  4. 4Watch
  5. 5Visualize
  6. 6Accepted
  7. 7Review

Go step by step: try it yourself before the video and the visual. Progress saves on this device.

0 / 110 pointsSolved (Easy) 0/20Reviews 0/50Mastered 0/25Practice steps 0/15

Step 1

Know these before you start

Practise each one here, or tick what you already know

Concept video

Step 2

Try it on paper

5–10 minutes, no code yet

In the wild Β· Every β€œSort by” button: Sorting a spreadsheet by price, then by name, needs a stable sort, which is why Python and JavaScript both use merge-sort-based TimSort.

ProblemProblem statementGiven an array nums of n integers where each value is in the range [1, n], return an array of all the integers in [1, n] that do not appear in nums.

Problem Statement

Given an array nums of n integers where each value is in the range [1, n], return an array of all the integers in [1, n] that do not appear in nums.

Added 2026-11-05 from Srujan's LeetCode Recent AC list (photo) β€” not previously in the repo.


Input / Output

Input:  nums = [4,3,2,7,8,2,3,1]
Output: [5,6]

Input:  nums = [1,1]
Output: [2]

Input:  nums = [1,2,3]
Output: []

Code it here

Tab / Shift+Tab indent · Backspace removes a whole indent · ⌘/Ctrl+Enter runs · Esc leaves the editor

Step 6

Get it accepted

All test cases pass

Step 7

Review it so it sticks

Re-solve from memory after

The step that matters most: without reviews most of a solved problem fades within weeks. Three short re-solves, each just as you start to forget, are what make it yours.

Your notes

Three lines in your own words. They come back with this problem's reviews, so you can check yourself after recalling the solution.

Solve it yourself before you look

Reading the solution first feels like progress, but it makes the next similar problem β€” and the interview version β€” much harder, because you skipped the part where you figure it out. Give it an honest 20–30 minutes. Stuck? Re-read the pattern, watch the concept video, or try the brute force first.

Hidden: approach Β· solution code Β· optimal solution

Stuck? One hint at a time.

    or find it yourself with the pattern finder

    Revising this one?

    • β†’Solve it from memory before peeking
    • β†’Say the pattern out loud, not just the code
    • β†’Explain it like you would to a friend
    • β†’Try it again in a different language