Skip to content
QuizMaker logoQuizMaker
Activity
DSA Interview Patterns Roadmap

No lessons available

CONTENTS

Greedy

Reachability, intervals, local choices, and proof-driven greedy patterns.

DSA Interview Patterns Roadmap
Greedy
dsa
coding interview
+4
May 29, 2026
20
A

Learning Outcome

Reachability, intervals, local choices, and proof-driven greedy patterns.

Pattern Recognition

ItemDetail
Core signalA known interview family appears and the constraints reward the standard pattern.
Use whenGreedy works only when the local choice can be proven to preserve an optimal future.
Avoid whenThe required invariant is not monotonic or the input constraints point to a simpler direct scan.

Intuition

Greedy works only when the local choice can be proven to preserve an optimal future.

Exact Practice Question Names

  • Jump Game
  • Gas Station
  • Candy
  • Partition Labels
  • Non-overlapping Intervals
  • Minimum Number of Arrows to Burst Balloons

Interview Approach

  1. Name the exact family.
  2. Write the invariant or state.
  3. Pick the standard container or recurrence.
  4. Dry-run the smallest example.
  5. State complexity and one follow-up.

Pseudocode

identify pattern
initialize state/container
for each input unit:
  update state safely
  update answer when invariant is valid
return answer

Sample Dry Run

Take the smallest Greedy example, track the state after every operation, and verify the final answer before coding.

Edge Cases

  • Empty or single-item input
  • Duplicate values
  • Boundary constraints
  • Large values requiring long/int64

Common Mistakes

  • Memorizing code without naming the invariant
  • Skipping the brute-force baseline
  • Not explaining why the optimized approach is correct

Complexity

ItemDetail
Expected timeUsually O(n log n), O(V + E), or states times transitions depending on the family.
Expected spaceUsually O(n), O(V + E), or number of DP states.

Java, C++ and Python Notes

  • Java: prefer explicit classes and clear helper methods over clever one-liners.
  • C++: use vector, unordered_map, set, priority_queue, and long long when sums can grow.
  • Python: keep state readable with dict, set, deque, heapq, and lru_cache where appropriate.

Quick Revision Checklist

  • Name the pattern before coding.
  • State the invariant or DP state in one sentence.
  • Dry-run the smallest non-trivial example.
  • Close with time and space complexity.

Share this article

Share on TwitterShare on LinkedInShare on FacebookShare on WhatsAppShare on Email

Test your knowledge

Take a quick quiz based on this chapter.

mediumDSA Interview Patterns
Quiz: Greedy
6 questions10 min

0 comments

Please login to comment.
No comments yet.
Completed!
You've finished this course
Back to DSA Interview Patterns Roadmap
Back to moduleCategories