📋 Exam Overview
⏱
90 Minutes
Time Limit
Time Limit
📝
2–3 Coding Qs
Per Session
Per Session
💻
C / C++ / Java / Python
Languages
Languages
✅
No Negative Marking
Always Submit
Always Submit
💰
Partial Marking
3/5 TCs = 15/25
3/5 TCs = 15/25
🏢
Ninja ₹3.36L
Digital ₹7L • Prime ₹9–14L
Digital ₹7L • Prime ₹9–14L
📈 Topic Probability Chart — Likelihood of Appearing
0
Total Questions
0
Completed
0%
Progress
0
Need Revision
| ✅ | # | Level | Question | Topic | Frequency | Difficulty | Status | Date Done | Revision | Notes |
|---|
⏱️ 20-Minute Problem-Solving Strategy
Time
Step
What To Do
0:00
📖 READ
Read the ENTIRE problem once. Extract inputs, outputs, constraints, edge cases.
2:00
🔍 DECODE
Strip story wrapper. Translate to pure algorithm.
4:00
✏️ DRY RUN
Manually trace the sample input. Confirm your algorithm gives expected output.
6:00
💻 CODE I/O
Write input/output handling FIRST. Wrong I/O = 0 marks.
8:00
🔧 CODE LOGIC
Write the core algorithm using your memorized pattern.
13:00
🧪 TEST
Trace with sample input. Check loop limits, off-by-one, overflow, edge cases.
15:00
▶️ COMPILE
Compile ONCE with sample input. TCS compiler takes ~25 sec.
17:00
🐛 DEBUG
If wrong: check I/O format first, then loop bounds, then logic.
19:00
✅ SUBMIT
Verify output matches expected format. Submit. Move to Q2.
🚨 Critical Exam Day Rules
🔴 Rule 1: Write complete solution BEFORE compiling. Budget only 2–3 compiles per question.
🔴 Rule 2: Q1 is your interview ticket. Secure it fully before touching Q2.
🔴 Rule 3: Wrong I/O format = 0 marks even with perfect logic.
🔴 Rule 4: Brute force that passes 3/5 test cases beats elegant code that doesn't compile.
🔴 Rule 5: If stuck > 10 mins, switch to brute force.
🔴 Rule 6: Last 5 minutes — stop coding new logic. Only clean up I/O and edge cases.