Dashboard
Dashboard
Target: maximize score in 2–3 days by preparing for recognition speed, not deep syllabus completion.
Your test structure
| Module | Questions | Time | Scoring priority |
|---|---|---|---|
| Aptitude | 30 | 30 min | Speed + accuracy |
| Technical | 30 | 30 min | Textbook basics + MCQ traps |
| Pseudocode | 20 | 20 min | Trace tables, loops, arrays |
| Coding | 2 | 30 min | One full solution first |
| Gamified | level-based | ~35 min | Familiarity + calm speed |
Vault navigation
- [[2-3_Day_Crash_Plan]]
- [[Exam_Strategy]]
- [[01_Aptitude/Aptitude_Index|Aptitude Index]]
- [[02_Technical/Technical_Index|Technical Index]]
- [[03_Pseudocode/Pseudocode_Index|Pseudocode Index]]
- [[04_Coding/Coding_Index|Coding Index]]
- [[05_Gamified_Assessment/Game_Based_Methods|Gamified Assessment]]
- [[06_Mocks_and_Question_Banks/Mock_Test_1|Mock Test 1]]
- [[06_Mocks_and_Question_Banks/Mock_Test_2|Mock Test 2]]
- [[07_Revision_Sheets/One_Page_Formula_Sheets|One Page Formula Sheets]]
- [[07_Revision_Sheets/Last_6_Hours_Checklist|Last 6 Hours Checklist]]
- [[09_Sources/Research_Notes_and_Source_Links|Research Notes and Source Links]]
High-yield rule
If time is short, do not prepare all topics equally.
Priority:
- Pseudocode tracing
- Coding arrays/strings/basic math
- Technical fundamentals
- Quant formulas + reasoning templates
- Game-based assessment familiarity
- English grammar and RC
Daily scoreboard
Use this table inside Obsidian and update it after every mock.
| Date | Section | Attempted | Correct | Time used | Main mistake |
|---|---|---|---|---|---|
| Aptitude | |||||
| Technical | |||||
| Pseudocode | |||||
| Coding |