Interview Prep
Tech Interview Prep Planner
Get a personalised, timeline-based study plan for your next technical interview — DSA topics by category, system design, behavioural prep, and a day-by-day schedule.
Get a personalised, timeline-based study plan for your next technical interview — DSA topics by category, system design, behavioural prep, and a day-by-day schedule.
Most interview prep fails for a boring reason: people practise what they are already good at. The Tech Interview Prep Planner starts from the other end. You tell it the role, your experience level, how many weeks you have, the kind of company you are targeting, and — most importantly — where you are weak. It returns a week-by-week plan that spends your time where it moves the result.
A product company’s loop, an Indian IT services interview and an early-stage startup’s take-home test reward different things, so the plan changes with the company type you pick rather than handing everyone the same list of 150 problems.
Large product companies usually run several rounds of data structures and algorithms, followed by system design for anyone with a few years of experience, and a behavioural round. Speed and clarity on medium-difficulty problems matter more than occasionally solving a hard one.
IT services firms and GCCs (global capability centres) tend to weight fundamentals — OOP, SQL, the language on your resume, and the projects you list — and often include an aptitude or online assessment first. Startups are more likely to give a practical exercise or ask you to walk through something you built. If you do not know the format, ask the recruiter; it is a normal question and the answer saves weeks.
With two weeks, do not try to learn new topics. Revise the patterns that come up most — arrays and hashing, two pointers, sliding window, tree and graph traversal, basic dynamic programming — and practise explaining your approach out loud before you code. With six weeks or more you can close genuine gaps, and it is worth adding one or two mock interviews with another person, because solving silently and solving while being watched are different skills.
Keep a short log of every problem you get wrong and why. Re-attempting those a few days later is worth more than twenty new problems you solve comfortably.
Interviewers read your resume shortly before they meet you and ask about it. Be ready to explain every project and technology you list: what you built, what you would change, and one thing that went wrong. Anything you cannot talk about for two minutes is better removed.
Describe the target
Role, experience level, timeline and the type of company you are interviewing with.
Be honest about weak areas
List what you are unsure of and what you are confident in, so the plan weights your time correctly.
Follow the weekly plan
Get topics, practice focus and milestones for each week until the interview.
It depends on your starting point. Someone who practises regularly can be interview-ready in two to three weeks of focused revision; someone returning after a long gap usually needs six to eight weeks. The planner builds around whatever timeline you give it.
Usually not in depth. Freshers and junior engineers are mostly assessed on problem solving, fundamentals and projects. System design becomes expected at around two to four years of experience, depending on the company.
Yes. Choosing the company type changes the weighting — more fundamentals and aptitude for services and GCCs, more algorithmic depth and design for product companies, more practical and project discussion for startups.