MockVita is TCS's official practice contest, opened to all registered participants a few weeks before Round 1. It runs on the exact CodeVita platform with the same six-problem, six-hour format — the only difference is that nothing you do in it counts. Skipping MockVita is the single most common regret in first-timers' write-ups.
Why it matters more than another practice site
- Platform familiarity. The compile-and-run panel, custom-input box, language dropdown and submission history all look different from LeetCode or HackerRank. Learn them where mistakes are free.
- Input/output discipline. CodeVita reads from standard input and judges standard output character-for-character. MockVita is where you discover that your language prints
3.0where3was expected. - Six-hour stamina. Most students have never coded for six hours straight. Use the mock to plan breaks and problem order.
- Difficulty calibration. MockVita problems are drawn from past seasons — if you solve four of six comfortably, you are in Round 2 territory.
A practice plan around MockVita
| When | What to do |
|---|---|
| 8–6 weeks before Round 1 | Finish the syllabus topics; 2 problems a day on any judge. |
| MockVita week | Attempt the full six hours in one sitting, exactly as on contest day. |
| Week after MockVita | Upsolve every problem you missed; write down the pattern you did not spot. |
| Last week | Re-solve the previous year questions from memory; rest the day before. |
MockVita has no bearing on your rank or on TCS hiring — so use it to take risks: try a new language feature, test fast-I/O templates, and deliberately submit wrong answers to see how the judge reports them.