Short answer: if you are a final-year student or a fresher applying in India, plan for the live format. Mass recruiters run a timed online test and then interviews where you solve a problem in front of a person. Some product companies and startups still send a take-home project, but many teams are moving to live or hybrid rounds because a submission written at home with an AI assistant is hard to grade, and because unpaid candidate time has become a complaint on both sides.
This guide is for the candidate, not the hiring manager. It explains what each round measures, which one you are likely to meet, how to prepare for the live round when there is no take-home buffer, and what to do if a take-home does arrive.
What a take-home assignment is
A take-home is a small project you build on your own machine over a few days: a REST API with two endpoints, a parser for a data file, a small front-end with a filter. The reviewer reads your repository, runs it, and asks you about it in the next round. It measures code quality, structure, how you scope a task and how you document decisions.
Its weaknesses are the reason it is losing ground. It takes hours of unpaid time, candidates with other offers drop out, and reviewers often cannot tell how much of a clean submission was written by the candidate and how much by an assistant. The follow-up discussion now carries most of the weight, which makes it a live round in disguise.
What a live coding interview is
A live coding round is thirty to sixty minutes in a shared editor or on a whiteboard. You get a problem, you talk through it, you write code while the interviewer watches, you test it, and you discuss trade-offs. It measures how you reason in real time, how you handle a hint, and whether you can explain what you are doing while you do it.
Its weakness is stress. Capable people freeze. Interviewers know this, which is why the format rewards a steady process more than a brilliant first idea. A working brute-force solution explained clearly beats a half-finished clever one.
Which one you will actually face in India
- IT service companies and other mass recruiters: a timed online test (aptitude, reasoning, one or two coding problems), then technical and HR interviews. There is no take-home anywhere in this pipeline. See how the rounds run at placd.in/companies/tcs and the other company pages at placd.in/companies.
- Product companies and funded startups: a short screening, then live rounds. A few still send a take-home or a timed "machine coding" round where you build a small working program in ninety minutes while sharing your screen. Treat machine coding as live: the clock and the screen share make it so.
- AI-assisted rounds: a growing number of teams now let you use an assistant during the live round and grade how you direct it and verify its output. That round has its own guide at placd.in/blog/ai-assisted-coding-interview-2026.
So for a fresher the planning question is not "take-home or live" but "how do I perform live, on a clock, with someone watching".
How to prepare for the live round
1. Clarify before you code. Repeat the problem in your own words, ask about input size and edge cases, and state the output format. One minute here saves ten later.
2. Say the brute force out loud, then write it. A correct O(n squared) solution that you can explain is a pass in most fresher rounds. Optimise only after it works.
3. Narrate. "I am using a set here so lookups are constant time" is the sentence interviewers are listening for. Silence reads as being stuck even when you are not.
4. Test on the screen. Walk one normal input and one edge case through your code by hand before you say you are done.
5. Practise on a clock against a judge that runs your code. Reading solutions does not build the reflex. Write code, submit it, see Accepted or Wrong Answer, repeat. The practice problems at placd.in/products/dsa run your Python in the browser and compile C++ and Java on most problems.
6. Sit a full scored mock before the real one. The AI mock interview at placd.in/products/mock-interview runs an intro round, a coding round where your Python is run against test cases, technical questions and a behavioral round, then grades the whole thing. One full mock is free when you sign up and confirm your email.
If a take-home does arrive
- Ask for the expected time budget and the deadline before you start, and stay inside the budget. Over-engineering is the most common way a good candidate loses a take-home.
- Ship a README that says how to run it, what you chose and why, what you left out, and what you would do next.
- Handle the obvious edge cases and write two or three tests. Reviewers read tests first.
- Be ready to defend every line in the follow-up. If you used an assistant, be able to explain and modify what it wrote. The follow-up is where the decision is made.
A two-week plan with no take-home buffer
- Days 1 to 3: one timed problem a day on arrays, strings and hash maps, spoken out loud to an empty room. Ten minutes of aptitude practice after each.
- Days 4 to 7: two timed problems a day, adding two pointers, sorting and simple recursion. Start every attempt by restating the problem and the plan before typing.
- Days 8 to 10: one problem a day plus a twenty-minute walk through a project you built, as if a stranger were asking you to explain it. This is the discussion round for both formats.
- Day 11: the free readiness check at placd.in/readiness, two minutes, to see which part is weakest.
- Days 12 to 13: fix the weakest part only.
- Day 14: a full scored mock interview, then read the scorecard and note the one thing to change before the real round.
FAQs
Are take-home assignments disappearing in 2026? They are becoming rarer and the follow-up discussion is carrying more of the decision, for the two reasons above: assistant-written submissions are hard to grade and candidates drop out of unpaid work. They have not vanished, and some small companies still prefer them.
Which is harder for a fresher, a take-home or a live round? Most freshers find live harder because of nerves, and most freshers will face live anyway. Prepare for live first; a take-home then becomes the easier case.
Can I use ChatGPT in a live coding interview? Only if the interviewer says so. Some teams now run an AI-assisted round on purpose and grade how you use the assistant. In every other case, assume it is not allowed and that the interviewer is watching your screen.
How long should a take-home take? Ask. If the company says three to four hours, spend three to four hours and write down what you cut. A thirty-hour submission for a four-hour task signals poor scoping, not dedication.
Where do I start if my campus drive is next month? Take the free two-minute readiness check (the Start free button below), then do the two-week plan above with the days compressed to fit.