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

Day 69EasyLeetCode (1365)

How Many Numbers Are Smaller Than the Current Number

Counting Sort / Prefix Sums

Asked at 6 companies

4 recent

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

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

  1. Basics
  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

Watch the concept video if the pattern is new to you.

Step 2

Try it on paper

5–10 minutes, no code yet

ProblemProblem statementGiven the array nums, for each nums[i] find out how many numbers in the array are smaller than it. Return the answer in an array.

Problem Statement

Given the array nums, for each nums[i] find out how many numbers in the array are smaller than it. Return the answer in an array.

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


Input / Output

Input:  nums = [8,1,2,2,3]
Output: [4,0,1,1,3]

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

Input:  nums = [7,7,7,7]
Output: [0,0,0,0]

Code it on LeetCode

There's no editor for this one here yet, so solve it on LeetCode, with its own tests. Then tick My code passed below, and it joins your reviews. With your LeetCode account linked, that happens on its own.

Solve on LeetCode

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

Stuck? One hint at a time.

    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