Monthly readiness review
A monthly check of practice, projects, and job-search progress.
Use this review once a month to decide what to change. Compare your results with your own previous month. These measures show progress; they do not predict an offer or a salary.
Progress signals
| Signal | How to check | What to do with the result |
|---|---|---|
| DSA accuracy and time | Solve five unseen problems at a realistic time limit; log hints and clean solutions | Pick the weakest pattern for next month's revision |
| A2Z progress | Count completed problems in the source sheet | Update the upcoming pace from the actual count |
| Fundamentals | Answer a small sample aloud without notes | Revisit concepts you could not explain clearly |
| LLD and machine coding | Review the working result, tests, and time used | Repeat one exercise where requirements or execution broke down |
| Project progress | Check that the demo, tests, docs, and results match the current code | Finish or cut scope before starting another project |
| Mock practice | Record the prompt, feedback, and one change for next time | Practice the repeated weakness |
| Applications | Track role fit, eligibility, response, and interview stage | Adjust target roles or application materials when a pattern appears |
| Referrals | Track messages, replies, referrals, and outcomes | Improve personalization; do not infer a promise from reply counts |
| Behavioral stories | Keep examples with your role, actions, result, and lesson | Add only real examples and measured results |
| Rest and schedule | Record hours, missed work, and days off | Reduce scope if the schedule is unsustainable |
Use weekly counts as planning aids, not quotas. Do not force an application to meet a total, invent project numbers, or chase a contest rating at the cost of interview practice.
Run the review
Copy the current values into your tracker on the same date each month.
Compare the values with last month and note one clear improvement and one gap.
Change one part of the next month's plan. Keep the change small enough to review.
Update your public portfolio only when it reflects work you completed.
If a measure falls for two reviews, reduce optional work and address the cause. Check exams, sleep, project scope, and interview load before adding hours.