I built this list for myself while going through a full-stack web development journey and preparing for job placement in parallel. If you are in a similar position — actively building things, learning a framework, and trying to keep problem-solving consistent without burning out — this might be useful for you too.
Link: https://leetcode.com/problem-list/wgazxxzm/
What is in the list
191 problems across four categories in this order:
TypeScript (23) → DSA Part 1: Arrays & Hashing, Two Pointers, Sliding Window, Stack, Binary Search → SQL (21) → DSA Part 2: Linked List, Trees, Heap/Priority Queue, Backtracking, Tries, Graphs, Advanced Graphs, DP, Greedy, Intervals, Math & Geometry, Bit Manipulation (143) → Bash (4)
Why TypeScript
My daily stack is Node.js and React. Solving in TypeScript means I am reinforcing types, generics, and interfaces while solving the problem. The language practice compounds with the algorithmic practice instead of running separately. You are not context-switching into a language you do not use — you are practicing the one you already write every day.
The only rule I follow
Spend at least 30 minutes and up to 1 hour each day before starting development. The ceiling is the point. I am building real projects at the same time. Uncapped LeetCode time kills everything else.
Deep work on 191 curated problems beats shallow coverage of 500.
If you are on a similar path — full-stack dev, job hunting, trying to keep everything moving without dropping the ball — feel free to use the list. Would love to hear how others are balancing this.
Top comments (0)