Daily Execution
North Star
The goal is not to study all day.
The goal is to become interview-ready through consistent reps:
- solve clearly
- design clearly
- explain projects clearly
- tell stories clearly
- stay healthy enough to repeat tomorrow
Rule Book
- No zero day: show up, even if it is only one useful rep.
- Consistency beats intensity.
- Sleep is part of preparation.
- Exercise is part of preparation.
- Food, water, and sunlight are part of preparation.
- Use Foqos during deep work.
- Keep the water bottle on the table twice: morning and post-lunch.
- Take supplements / Whoop routine as planned.
- Apply to jobs daily when actively searching.
- No social media or X for politics/news loops.
- Instagram only in moderation.
- Use evenings for recovery, reflection, or light review.
- Sunday is off unless there is an urgent interview need.
Daily Minimum
If the day is messy, do this and call it a win:
| Area | Minimum Rep |
|---|---|
| Coding | 1 problem, 1 revision, or 20 minutes of pattern review |
| System design | 15 minutes on one concept, component, or design prompt |
| Behavioral | 1 story opening or 1 project explanation out loud |
| MSFT | 5 minutes reviewing Company Info or “Why Microsoft?” |
Minimum day target: 45-75 focused minutes.
Target Day
| Time | Focus |
|---|---|
| Morning | Wake up, breakfast, coffee, water, Engg discussion of the day |
| First deep block | Coding or system design |
| Midday | Exercise, lunch, walk, job applications if needed |
| Second deep block | System design, project articulation, or behavioral |
| Late afternoon | Light stack / engineering discussion review |
| Evening | Dinner, recovery, short revision, shutdown |
Target day output:
- 1 coding rep or revision
- 1 system design / engineering discussion rep
- 1 behavioral or project articulation rep
- 1 small MSFT-specific touch
Deep Work Blocks
Use 60-90 minute blocks.
For each block:
- Pick one concrete output.
- Start a timer.
- Avoid switching buckets mid-block.
- End with a 2-minute note: what improved, what is still weak.
Good outputs:
- solved and explained one coding problem
- revised one weak pattern
- designed one subsystem
- practiced one project story out loud
- wrote one STAR answer
- prepared three interviewer questions
Weekly Rhythm
A prep week runs Monday through Saturday. Sunday is off / reset / gentle planning only.
| Day Type | Intent |
|---|---|
| Heavy day | Coding + system design + one communication rep |
| Medium day | One major bucket + one light bucket |
| Light day | Revision, company research, behavioral, recovery |
| Saturday | Catch-up, mocks, review, weak-area repair |
| Sunday | Off / reset / gentle planning only |
Weekly checkpoints:
- Did I do enough reps, or only reading?
- Did I practice speaking answers out loud?
- Did I review mistakes?
- Did I protect sleep and energy?
- What is the one weakest area for next week?
Shutdown
End the day by writing:
- Done today:
- Weak spot:
- Tomorrow’s first rep:
Then stop. Recovery is not laziness; it is how the next good rep happens.
Reaffirmation
I already have meaningful engineering experience.
My work now is to make it easy for an interviewer to see:
- how I think
- how I communicate
- how I handle ambiguity
- how I influence people
- how I build reliable systems
- how I learn and improve
Keep moving.