A sustainable week
A flexible weekly schedule for DSA, projects, interviews, applications, and rest.
Use this schedule as a starting point. It plans about 45 hours, including a five-hour buffer. Most weeks should fit within 40 to 45 hours. Use extra time only for a deadline or a live interview, not as the normal pace.
Weekly hours
| Track | Hours | What to do |
|---|---|---|
| DSA | 12 | Follow the current A2Z module, review misses, and log each result |
| Project | 12 | Work on the current core milestone; stop when the planned scope is done |
| CS fundamentals and LLD | 4 | Split between spoken fundamentals practice and one design or coding exercise |
| System design | 2 | Start in week 4; study one building block and explain one design aloud |
| Contest and mock practice | 4 | One contest and one mock or focused interview drill |
| Applications and referrals | 3 | Start outreach in December; apply only to roles that fit your eligibility |
| Reading | 2 | Read a few relevant posts each week and write short notes |
| Writing and portfolio | 1 | Update one project artifact when there is real progress to report |
| Buffer and rest | 5 | Absorb delays, review the week, and protect time away from study |
| Total | 45 | The hours vary by phase. Do not remove the buffer every week. |
Before applications start, use that block for role research or extra rest. Before system design starts, leave those hours open. When an interview is scheduled, replace planned practice with preparation for that loop.
DSA pacing
Use the weekly problem target on the A2Z calendar. The time budget includes reading the prompt, solving, reviewing a missed approach, and logging the lesson. There is no fixed rule to solve exactly two new problems each day.
If the weekly target does not fit, record the actual count and keep moving through the sheet in order. Revise the next week based on your available hours. Do not silently claim the cumulative target is complete.
Project pacing
Use the current project's milestone as the scope limit. Reserve time for tests and a working demo. Do not add a feature because it sounds impressive if it blocks a finished release.
The detailed project options are choices for after the core portfolio. They do not add hours to this template until you select one.
Do and don't
- Schedule DSA on several weekdays so practice does not depend on one long session
- Keep one evening free and use the buffer when a task takes longer than expected
- Log actual time and progress once a week
- Reduce scope before reducing sleep
Keep a minimum, not a perfect streak
Aim for at least 12 DSA hours in a normal week. During exams, illness, or active interviews, record the reduced schedule and resume when you can. A short reset is better than trying to repay every missed hour.