■ 4-Week Software Developer Prep Plan (LeetCode
with Links)
This plan includes direct LeetCode links for each daily problem so you can start solving
immediately.
■ Week 1 — Core Data Structures & Warm■Up
1 Day 1: Arrays & Two Pointers — Two Sum , Container With Most Water
2 Day 2: Hashing & Frequency — Group Anagrams , First Unique Character in a String
3 Day 3: Sorting & Binary Search — Search in Rotated Sorted Array , Find Minimum in Rotated
Sorted Array
4 Day 4: Strings — Valid Anagram , Longest Substring Without Repeating Characters
5 Day 5: Linked Lists — Reverse Linked List , Linked List Cycle
6 Day 6: Stack & Queue — Valid Parentheses , Evaluate Reverse Polish Notation
7 Day 7: Full Mock Set — Mix easy/medium problems across topics.
■ Week 2 — Patterns & Medium Complexity
1 Day 8: Sliding Window — Minimum Window Substring , Maximum Subarray
2 Day 9: Prefix Sum / Cyclic Sort — Product of Array Except Self , Missing Number
3 Day 10: Recursion & Backtracking — Permutations , Subsets
4 Day 11: Dynamic Programming — Coin Change , Longest Increasing Subsequence
5 Day 12: Trees — Maximum Depth of Binary Tree , Lowest Common Ancestor of a BST
6 Day 13: Graph Basics — Number of Islands , Course Schedule
7 Day 14: Mock Interview — 1 graph or DP + 2 mixed problems
■ Week 3 — Mixed Sets + Fundamentals
1 Day 15: Arrays (sliding window / two pointers)
2 Day 16: Hashing / Maps
3 Day 17: Linked List / Stack
4 Day 18: Tree / Graph
5 Day 19: DP / Backtracking
6 Day 20: Harder problem from weak areas
7 Day 21: Full Mock Interview (3 problems + theory Qs)
■ Week 4 — Final Sprint & Interview Practice
1 Day 22–27: Each day, simulate a mini-interview with 2 problems (45–60 mins).
2 Include: coding + complexity discussion + verbal explanation.
3 Day 28: Final Mock — 2 problems + 20 mins CS fundamentals + 15 mins behavioral Qs.
■ Notes:
• Solve problems directly on LeetCode (Blind 75 + DSA Patterns).
• Timebox problems: 30–40 mins early, then move to 90■min full mock sessions.
• Think out loud and explain reasoning to simulate interview environment.
• Reflect after each mock: note weak areas and re■practice.
