2-3 Day Crash Plan
2–3 Day Crash Plan
This plan assumes you have very little time and need the highest practical score improvement.
If you have 3 days
Day 1: Concept compression
| Time | Task | Output |
|---|---|---|
| 60 min | Read [[01_Aptitude/Quant/Formula_Sheet | Quant Formula Sheet]] |
| 60 min | Practice quant examples | 25 solved |
| 45 min | English grammar rules | Error spotting accuracy |
| 45 min | Reasoning templates | Series/coding/blood relation |
| 120 min | Technical basics | DS + OS + Networking |
| 90 min | Pseudocode tracing | 30 traces |
| 90 min | Coding arrays/strings | 4 working solutions |
Day 2: Timed practice
| Time | Task | Output |
|---|---|---|
| 30 min | Aptitude mini mock | 30 questions |
| 30 min | Review mistakes | Mistake log |
| 90 min | Technical MCQ question bank | 80 MCQs reviewed |
| 60 min | Pseudocode timed set | 20 questions |
| 120 min | Coding practice | 6–8 programs |
| 45 min | Gamified drills | Memory + numeracy + switch |
| 45 min | Formula revision | One-page recall |
Day 3: Exam simulation
| Time | Task | Output |
|---|---|---|
| 30 min | Aptitude mock | Full section |
| 30 min | Technical mock | Full section |
| 20 min | Pseudocode mock | Full section |
| 30 min | Coding mock | 2 questions |
| 60 min | Review only wrong answers | Error patterns |
| 60 min | Final sheets | Memory consolidation |
| 30 min | Calm gamified practice | Avoid panic |
If you have only 2 days
Cut low-yield theory. Use this order:
- Pseudocode: 2.5 hours
- Coding: 3 hours
- Technical: 3 hours
- Aptitude: 2.5 hours
- Gamified: 1 hour
- English: 45 minutes
If you have only 1 day
Use a survival plan:
- 90 min: pseudocode tracing
- 120 min: top coding templates
- 120 min: DS + OS + Networking + QA one-liners
- 90 min: quant formulas and examples
- 45 min: reasoning shortcuts
- 30 min: English rules
- 30 min: gamified familiarization
Non-negotiables
- Do not leave MCQs blank if there is no negative marking.
- In coding, solve the easier question completely before touching the harder one.
- In pseudocode, always make a trace table.
- During mocks, use real section timing. Untimed practice gives false confidence.