Take-home assignment for freshers

A take-home assignment is a short task you do at home — often a small React, API or DSA mini-project — to show how you code, structure files and write a README. Many give you 24 to 72 hours, and reviewers usually look at whether it works, code quality and how easy it is to run, not just whether it runs once. Submit clean code, a short README and a demo link if you can.

Take home assignment me kya karna hota hai pls samjhao easy me

Usually one of these:

• Mini app: a small React or web app (for example: a to-do, a product list with search and filter, or a URL shortener with a web interface and a simple service behind it). They check component structure, state, error handling and a README with setup steps.
• DSA mini-project or script: a console problem with input/output, limits and edge cases (arrays, strings, hashing, greedy or simple dynamic programming). They check approach, complexity and tests.
• Fix or extend: a small repo with a few failing tests or a TODO list — you make it pass and note what you changed.

Take home assignment me kya denge example batao pls

These are anonymized examples of the shape companies use, not any company’s leaked assignment.

How to check your own submission

Companies rarely publish how they mark a take-home. A simple way to check your own submission before you send it:

• Correctness: does it do what the prompt says, with edge cases handled?
• Code quality: file structure, naming, small functions, no copy-paste, error handling.
• Instructions: can someone run it from your README in 3 steps without asking you?
• Extra care: tests, commit messages, one short design note on what you would improve with more time.

How long do you get, and can you use AI

• Time given: many fresher assignments give 24, 48 or 72 hours from the email; each company differs. Check that email: some ask for a fixed slot, some for “within 3 days”.
• Can you use AI? If the email is silent, assume you may use AI to learn, not to submit AI-written code as your own. Some companies run a plagiarism or AI check and a short live review on your submission. If you used AI for an idea, say so in the README and know the code well enough to explain every line.
• Catch: submitting code you cannot explain in a follow-up call hurts more than submitting a smaller, honest solution.

Checklist before you submit

• Runs from a fresh clone with the steps in your README; covers the sample input and one edge case (check this on the date you submit — requirements vary).
• Keep secrets and keys out of the repository. Add an example configuration file with empty values, then check code style and formatting.
• Commits are small and named (“wait before sending search requests” is clearer than “final”); repo is public or shared with the recruiter.
• One paragraph in the README: approach, complexity, what you would improve next.

Practise with Savyly

• DSA & Coding mode: put the assignment’s problem statement on your screen, press one key, and Savyly explains the idea, the steps and the complexity — then you write the code yourself. AI coding assistant.
• Practice first: type /practice and pick coding — Savyly asks one DSA problem at a time and pushes on complexity and edge cases, like the real review.
• 15 free minutes, no card, then from ₹99 an hour, paid once. Diwali offer until 8 November 2026: ₹99, ₹199, ₹499 and ₹999. Pricing.

Questions

More placement prep

• TCS NQT coding questions — 10 practice problems with tested Python, C++ and Java solutions, and the test pattern from TCS’s own page.
• Infosys and Accenture coding questions — 10 practice problems from strings to greedy and dynamic programming, with each test’s format from the companies’ own pages.
• Wipro coding questions — 8 practice problems on arrays, strings, number logic and grids, with what Wipro’s hiring pages say about Elite, Turbo and WILP.
• Cognizant GenC coding questions — 8 practice problems on strings, counting, stacks and greedy, with what Cognizant’s pages say about GenC hiring.
• Capgemini coding questions — 8 practice problems from number theory and prefix sums to a simple dynamic programming, with Capgemini’s hiring process from its own pages.
• HR interview questions for freshers — 20 common questions, what each one is really asking, and sample answers in English and Hinglish.
• Tell me about yourself: sample answer for freshers — Three sample answers in English with a Hinglish version of each, what the interviewer is really asking and how to make it yours.
• DSA interview questions with solutions — 10 DSA questions students report from campus placements, with the idea, complexity and links to practice problems with tested code.
• Mass recruiter vs product-based strategy — Mass recruiters vs product-based companies: how they hire, what they pay, and how to prepare when you have little time.
• Striver vs Love Babbar DSA sheet — How to pick a sheet for placements, how long each takes, and a week-by-week plan.
• Tier-3 college placement guide — Off-campus channels, projects and a guide to requesting referrals.
• 60% criteria and backlog rules — What TCS, Wipro, Capgemini and Accenture say on their own pages, and how CGPA converts.
• Service bond for freshers — Service bonds for freshers: what the paper says, how long, how much, and how to ask about it in the HR round.
• Backlog and CGPA eligibility — What TCS NQT and other drives allow, and what varies each year.
• System design for freshers — Whether service-based companies ask it, which product rounds do, and what to study in 3 days.
• Cognizant GenC vs GenC Next — How Cognizant describes GenC, GenC Next, Pro and standard tracks, and what current pages do and do not publish.
• Gap year and backlog — how to explain — How to explain a gap year or backlog in an HR interview: three safe narratives, Hinglish and English sample answers, and follow-ups.