Six weeks is a realistic Turbo plan for a student who already codes a little. Split the time 50 / 30 / 20 between coding, aptitude and communication, and prepare for Elite and Turbo together — the paper is the same and Turbo simply asks you to score at the top of it.
Six-week plan
| Week | Coding (≈ 1.5 h/day) | Aptitude (≈ 45 min/day) | Communication (≈ 30 min/day) |
|---|---|---|---|
| 1 | Arrays and hashing: two sum, missing number, majority element, sock merchant — write the O(n) version even when O(n²) would pass | Percentages, profit & loss, SI / CI, ratio and ages | One 300-word essay every second day, checked for errors |
| 2 | Strings: longest substring without repeats, anagram grouping, longest common prefix, backspace compare | Time & work, pipes, time–speed–distance, circular tracks | Read aloud 10 minutes daily; record and listen back |
| 3 | Stacks and searching: valid parentheses, next greater element, binary search variants, count inversions | Number series and wrong-number series, coding–decoding, blood relations | Synonyms / antonyms — 15 words a day from Wipro papers |
| 4 | DP-lite and maths: Kadane, prefix sums, counting valleys, GCD / LCM, sieve, Pascal's triangle | Seating arrangements, syllogisms, data sufficiency, assumptions | Error spotting, voice and narration rules |
| 5 | Two timed 60-minute mocks (2 problems each) every other day, in the exam editor format (stdin / stdout) | Full 48-question, 48-minute aptitude mocks | Two essays per week under a 20-minute timer |
| 6 | Revisit every problem you failed; write complexity notes for each | Mixed mocks, error log review | Mock business discussion with a friend; resume walkthrough |
The Turbo habit
Every practice problem gets two lines at the bottom: the complexity of what you wrote, and the complexity of the best-known approach. If the two differ, you are not done. This single habit is what separates Turbo shortlists from Elite ones — and it is exactly what the business discussion probes when it asks about your online-test code.
Test-day tactics
- Aptitude first pass: sure-shot questions in each section, then return; guess anything left in the final ten seconds — no negative marking is reported.
- Essay: outline four paragraphs in two minutes, write for fifteen, proof-read for three. Stay inside 200–400 words.
- Coding: read both problems before touching the keyboard; solve the easier one fully, submit, then move to the harder one. Get a passing brute-force version in early only if the optimal idea is not coming — then optimise.
- Test your own edge cases before submitting: empty or single-element input, all-equal values, maximum sizes, negative numbers.
Resources on this site
- Turbo-level: coding questions, aptitude questions, interview questions.
- Elite-level foundation: coding, placement paper, WriteX essays, how to prepare for Wipro.
- Same-difficulty practice from other companies: TCS CodeVita for contest-style coding, Infosys for a second aptitude bank.
Keep the Elite registration alive even if your institute has a Turbo drive — the preparation is identical, and two shots at the same paper are better than one.