Zoho is a leading Indian SaaS company, renowned for its suite of business, productivity, and collaboration tools. Founded in 1996 by Sridhar Vembu, Zoho is known for its “Made in India, Made for the World” philosophy, rural development initiatives, and a unique, learning-focused work culture. Zoho values practical skills, long-term growth, and hires from all backgrounds.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Academic requirements
Marks: No strict cutoff; consistent academics are a plus, not mandatory
Degree: B.E./B.Tech/MCA/M.Sc (any branch/discipline)
Year of Study: Final year students and recent graduates (within 1 year)
Backlogs: No active backlogs preferred; 1 active backlog may be allowed case-by-case (must clear before joining)
Branch & programming
All Branches: CS, IT, ECE, Mechanical, Civil, and other engineering/science streams
Programming: C is mandatory; C++/Java is a plus
Experience: Freshers and up to ~1 year experience for entry-level MTS
Minimum CGPA required (candidate-reported): no strict CGPA cutoff. Consistent academics help a little on the resume screen, but C programming skill decides written and application rounds. Always verify your drive notice.
If you can write real C (not just MCQs), Zoho is more open than most product companies. There is no strict CGPA cutoff - marks help a little on the resume screen, but they will not save you in the written or application rounds. Criteria for 2025 and 2026 are the same, so you do not need a separate year-tagged eligibility FAQ.
What that means day to day: a 7.5 CGPA with shaky pointers usually loses to a 6.5 who can hand-trace ptr++ bugs and finish an address book with file save/load. Zoho’s “skills over pedigree” story matches how drives feel - mechanical and civil students clear MTS when C practice is deliberate, not a three-day crash course.
Good fit: You like building small tools end-to-end, you can sit with a notebook and dry-run pointer code, and you are open to Chennai or a rural Zoho office. Internships help on the resume screen but are not a substitute for Round 1 tracing. If you already debug segfaults without panicking, you are ahead of half the written pool.
Harder path: You only practiced MCQ aptitude plus online judges with autocomplete; you freeze without printf debugging; you refuse relocation. Zoho’s HR round is friendly but blunt on location and long-term commitment - treat those as real filters, not soft talk. A high CGPA with weak C usually dies in output prediction; a mid CGPA with strong C often survives.
Branch myth: Non-CS students are not “extra lucky” at Zoho - they simply are not auto-rejected. You still need the same C bar. Use the no-cutoff policy as permission to attempt, not as a free pass past Round 2.
Gap years and backlogs: a gap over about one year between 10th and graduation is the usual hard stop students report. One active backlog may be discussed case-by-case; plan to clear it before joining either way. Full-time degrees only - part-time paths are not the fresher MTS route described here.
Download 2026 Zoho placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Zoho is skills-first: heavy weight on C, light aptitude, and a long multi-round process (written → coding → application build → tech → HR). Previous-year papers mainly train the pen-paper written test and early coding rounds - C output prediction, pattern printing, arrays/strings/pointers in C - plus enough aptitude so you do not burn time there.
Think of papers as simulators for Round 1 stamina, not as a question bank you must memorize. Zoho reuses themes more than exact clones. If you can finish a 2024 paper cleanly under time, a 2026 written will feel familiar even when the pointer puzzle is new. Keep the 2026 PDF for timed full runs and year pages for deeper solution walkthroughs.
| Round (typical) | What to practice |
|---|---|
| Aptitude & C written | Output prediction, basic aptitude |
| Basic programming | 5 C-style coding problems; clear ~3/5 |
| Application round | Mini console app (file I/O, menus) |
| Interviews | Code review + C depth + culture fit |
Across recent drives, the same families show up again and again:
Use year pages for pattern depth; use the PDF for timed drills.
How to use a paper (not just “solve it”): time the written block at 90-120 minutes; mark every output question you guessed; rewrite any coding answer that would not compile on paper; then spend 20 minutes listing which pointer/array idea you missed. Three reviewed papers beat ten skimmed ones. When an application-style prompt appears in a year pack, actually implement it once - reading someone else’s menu code does not build the muscle Zoho tests.
Zoho’s output questions rarely need exotic libraries. They stack:
int* / char*break/continueIf you can narrate memory state line by line on paper, you are practicing the real skill. If you only “recognize the pattern,” you will miss the twisted middle questions.
Zoho runs both campus and off-campus hiring. Off-campus drives happen roughly monthly at Chennai (and sometimes Tenkasi / other rural offices). Same technical bar either way - campus often feels slightly easier because of reserved slots and a familiar environment; off-campus is open year-round and usually more competitive.
Campus recruitment
College visits via placement cells. PPT → resume through the cell → written on campus (often pen-paper) → programming + interviews on campus or at Zoho. Typical window: August-December placement season.
Off-campus drives
Zoho Careers portal for monthly drives; walk-ins at Chennai/Tenkasi need pre-registration. Resume screen (2-5 days) → test at office → same remaining rounds.
Internal referrals
Employee referral for campus and experienced hiring. Still expect the same C-heavy evaluation.
Campus vs off-campus in practice: On-campus = reserved seats, college support, season-aligned. Off-campus = more attempts per year, merit-heavy pool, office venue. Many students try both. Technical content does not change - C mastery still decides outcomes.
Campus path (typical): college registers → PPT → resumes via placement cell → written on campus (often pen-paper) → programming rounds on campus or at Zoho → tech + HR → offers. Advantages: familiar hall, peer energy, sometimes college quotas. Timeline usually tracks placement season (often August-December).
Off-campus path (typical): register on Zoho Careers → resume screen 2-5 days → written at Chennai/Tenkasi → same programming + interview ladder → offer. Advantages: monthly cadence, open to recent grads whose campus drive missed Zoho. Expect a denser applicant mix; your paper and app still decide it.
Rural offices: Tenkasi, Renigunta, and similar locations show up in HR conversations. Same technical process and usually the same MTS salary bands; living costs differ. If you only want metro Chennai, say so early - better than accepting and freezing later.
Resume Screening (2-5 days)
They scan for C/project signals, not CGPA gates. All branches are welcome. Roughly 60-70% of applicants pass this screen. Put C projects and console apps on the resume if you have them - a one-line “built library management in C with file storage” beats a vague “interested in coding.” Keep the resume honest; later rounds will open your code.
Aptitude & C Programming Test (90-120 min, pen-paper or online)
Questions: ~25-35 · Negative marking: none · Platform: Zoho proprietary or classic pen-paper (most campus drives still use paper).
| Section | Questions | Time | Difficulty | Focus |
|---|---|---|---|---|
| Quantitative Aptitude | 10-15 | 30-40 min | Easy-Medium | Percentages, ratios, basic math |
| C Output Prediction | 10-15 | 40-50 min | Medium-Hard | Pointers, arrays, loops, recursion |
| C Coding | 2-3 | 20-30 min | Medium | Pattern printing, array logic |
No MCQs - write outputs, show working, and write complete short programs. Clear rate after this round is often ~30-40%. Full format notes: pen and paper test guide.
Time boxing that works for many students: ~35 minutes aptitude (do not chase perfection), ~50 minutes C tracing (this is where ranks separate), ~25-30 minutes short coding. Skip a stuck tracing question, mark it, and return - blank pages from overthinking one pointer puzzle are a common fail mode.
Pen-paper tips that matter: practice handwriting full C programs; syntax errors will not get a compiler nudge; keep handwriting readable; for output prediction, show step-by-step pointer/state reasoning; indent consistently so evaluators can follow loops.
Why Zoho still likes paper: it removes IDE autocomplete and forces fundamentals. Candidates who only ever typed inside VS Code with Copilot-style hints feel this round hardest. Treat notebook practice as non-negotiable for two weeks before any drive.
Basic Programming Round (2-3 hours)
Five coding problems in C (C++/Java optional extras). Expect patterns, string/array work, and logic builders. You typically need at least 3/5 correct. Evaluators look at correctness, approach, structure, and edge cases. About 40-50% of written qualifiers move on.
Practical target: lock two “sure” problems first (often a pattern + a simple array), then invest in a third for the clear bar, then attempt the fourth if time remains. Leaving four half-broken solutions is worse than three clean ones. Name variables clearly; Zoho interviews later may reopen this code.
Advanced Programming / Application Round (90-120 min)
This is Zoho’s signature filter: build a working mini-application, not another isolated LeetCode problem.
Common briefs: Address Book (CRUD + file save/load), Banking System (accounts + transactions), Quiz App (MCQs + scoring + file-based questions), Library / Inventory (issue-return or stock).
They score completeness, modular structure, logic, console usability, and real file I/O. Roughly 50-60% of basic-round qualifiers advance. Practice one full app per week until you can ship menus + validation + persistence under two hours.
Build order under the clock: (1) define structs and menu skeleton, (2) implement add/list paths, (3) wire file save/load early - do not leave persistence for the last ten minutes, (4) add search/update/delete, (5) harden input validation. A partial app that saves and reloads beats a flashy UI with everything in RAM only.
Evaluation checklist students forget: empty input, duplicate IDs, file-not-found on first run, and quitting without crash. Mention these in comments or a tiny README note if the format allows - it signals production instincts.
Technical Interview (30-45 min)
Code review of your earlier rounds, deep C (pointers, memory, recursion), data structures in C (lists, stacks, queues, trees), light OOP if you used C++/Java, and project discussion. About 70-80% of application-round survivors clear this.
Expect “why this loop?”, “what if malloc fails?”, “how would you avoid this memory leak?”, and “redraw this as a linked list.” If you cannot explain your own application’s file format, that is a red flag. Bring the same calm tracing habit from Round 1 into spoken form.
HR Interview (20-30 min)
Background, relocation to Chennai or Tenkasi, Why Zoho?, learning mindset, and long-term commitment. Communication and culture fit matter. Around 90% of tech-clear candidates get offers if HR concerns (location, commitment) are sorted.
Prepare a specific Why Zoho (product breadth, learning culture, rural/Made-in-India story - pick what is true for you). Vague “I like coding” answers underperform. If you need time before relocating, say so clearly rather than bluffing.
| Phase | Duration | What happens |
|---|---|---|
| Resume Screening | 2-5 days | Initial filter |
| Written Test | 1 day | Aptitude + C |
| Programming Rounds | 1-2 days | Basic + application |
| Technical Interview | 1 day | Code review + C depth |
| HR Interview | Same day | Final culture/location check |
| Result / Offer | 2-3 days | Offer letter, background check |
Total: usually 2-3 weeks end to end (faster for strong candidates). Off-campus monthly drives and rural-office postings (Tenkasi, Renigunta, etc.) use the same ladder; rural roles keep the same salary bands with lower living costs and a tighter community culture.
Learning culture signals that show up later: Zoho University-style internal training, product switching, and long-tenure talk appear in HR and manager chats. You do not need to memorize program names - you do need a credible story about wanting to learn in-house for years, not hop in six months.
What to practise in each early round:
If you only remember three numbers: 6 rounds, clear ~3/5 in basic coding, MTS fresher band ₹5-7 LPA (candidate-reported). Everything else is execution detail.
Online assessment
OA format, timing, and question types.
Coding questions
DSA patterns for OA and technical rounds.
Aptitude / mock quiz
Quant, logic, and timed mock quiz.
Interview experiences
Candidate stories and round notes.
HR interview questions
Common HR questions, sample answers, STAR tips.
Week-by-week prep
Study plan and round-by-round strategy.
If a Zoho invite is 3-8 weeks out, treat this hub as the map and the linked practice pages as the drills. Do not reread eligibility ten times. Check the JD once, then spend hours on the filter that actually rejects people.
Typical fresher CTC chatter for Zoho sits around ₹5-7 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Zoho eligibility criteria for freshers 2026: No strict CGPA cutoff - Zoho welcomes candidates from all backgrounds. Degree: B.E./B.Tech/MCA/M.Sc (any branch/discipline). Year of Study: Final year students and recent graduates (within 1 year). Backlogs: No active backlogs preferred, but 1 active backlog may be allowed case-by-case. Gap Years: Maximum 1 year gap between 10th and graduation. Programming: C programming i.
What you are training for: Zoho placement process includes: 1. Resume Screening (2-5 days), 2. Aptitude & C Programming Test (90-120 min) - Quantitative aptitude, C output prediction, C coding, 3. Basic Programming Round (2-3 hours) - 5 coding problems, must solve at least 3/5, 4. Advanced Programming/Application Round (90-120 min) - Build mini-application, 5. Technical Interview (30-45 min) - Code review, C concepts, data structures, 6. HR Interview (20-30 min) - Personal background, company fit. Total duration: 2-3 weeks.
Short version of the prep split: To prepare for Zoho placement: 1. Master C programming (50% time) - pointers, arrays, strings, recursion, 2. Practice programming (30% time) - pattern printing, array/string manipulation, build console applications, 3. System/Application Design (15% time) - file handling, modular code, menu-driven programs, 4. Aptitude & Communication (5% time) - basic aptitude, HR preparation. Focus on hands-on coding and building real applications.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Zoho previous-year sets on this site and mark which sections ate your time. Write the timing on a sticky note. That number is more useful than a 200-problem LeetCode streak you never timed.
Week 2 - the steep filter. Most Zoho drives fail people on the first timed paper or OA. Do three timed sits this week. After each one, log every miss in a two-column note: topic and why (slow, wrong formula, bad edge case, panic). The next sit should only add problems from that log.
Week 3 - talk tracks. Technical interviews at Zoho usually want a clean project story, one or two CS fundamentals, and (if the process has it) a behavioral or values round. Write STAR stories on paper, not in your head. Practise “Why Zoho?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Star stories + one project walkthrough recorded on your phone. If you still have energy, redo only the questions you failed in week 2.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Zoho-style sit without guessing the clock |
| Coding / role technical | ~30% | You can explain a solution out loud in your chosen language |
| Fundamentals / domain | ~20% | You can teach one OS/DBMS/networks (or domain) topic to a friend |
| Stories + HR | ~10% | Two STAR stories and a specific Why-this-company answer |
If you only have 10 days, keep the same ratios and cut volume, not the timed sits.
Use this hub for the Zoho story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Zoho papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Zoho papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Zoho-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Zoho paper each day plus error log. Days 4-6: only the topics you missed, plus 4-6 coding problems in one language. Days 7-8: project + STAR + Why Zoho. Day 9: one more full mock. Day 10: light review and sleep. This is worse than four weeks, but it beats rereading notes the night before.
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Zoho, interviewers often poke the same hole the OA already tested - be ready to re-solve a warm question on a shared editor or whiteboard. If you used AI to draft code while practising, you still need to type it yourself on the day.
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Zoho mistakes, you are collecting content, not preparing.
Figures below are candidate-reported as of August 2026 (total annual package bands). Treat them as ranges, not offer letters.
| Level | Experience | Base (approx.) | Total Package | Typical background |
|---|---|---|---|---|
| MTS | New Grad | ₹5-7 LPA | ₹5-7 LPA | Fresh graduates, all branches |
| Software Engineer | 1-2 years | ₹6-8 LPA | ₹7-10 LPA | 1-2 years experience |
| Senior Software Engineer | 3-5 years | ₹10-14 LPA | ₹12-18 LPA | Senior devs, team leads |
| Staff Engineer | 6+ years | ₹16-22 LPA | ₹20-28 LPA | Architects, specialists |
| Role | Level | Total Package | Notes |
|---|---|---|---|
| Technical Support Engineer | Entry | ₹3-5 LPA | Communication + tech aptitude |
| QA Engineer | Entry-Mid | ₹4-7 LPA | Testing focus |
| Business Analyst | Mid | ₹6-10 LPA | Business + analytics |
| Product Manager | Mid-Senior | ₹12-20 LPA | Product + tech background |
Flexible hours, health insurance for employee & family, subsidized food/transport, internal learning (Zoho University-style upskilling), profit-sharing bonus, and clearer internal mobility across 50+ products. Rural offices (Tenkasi, Renigunta, etc.) usually match Chennai salary bands with lower living costs - HR will still check relocation willingness explicitly.
How to read the MTS band: ₹5-7 LPA is the fresher technical offer range students most often cite for Member of Technical Staff. Exact CTC splits (base vs bonus vs benefits) vary by offer letter and year - use the band for expectation-setting, not negotiation theater before you have an offer. Support/QA tracks list lower in public chatter; do not assume every Zoho role is MTS pay.
Growth students ask about: MTS → Software Engineer → Senior → Staff is the common technical ladder people describe. Internal mobility across products is a real talking point in HR - if you care about not being stuck on one module forever, say that in your own words.
Hiring trends 2026
More campus visits to tier-2/3 colleges. C coding + application building remain the real filters. All branches stay welcome when C is strong.
Process shape
Still mostly descriptive/code answers (not MCQ banks). Programming rounds stay long. Application round is still the differentiator vs service companies.
Access paths
Monthly off-campus drives in Chennai/Tenkasi. Skill-first screening. Typical 2-3 week decision cycle once you are in process.
Company context
50+ products, global customers, rural-office footprint, and a learning/internal-mobility culture that shows up in HR questions.
Net for 2026 prep: do not wait for a “new pattern” rumor. Double down on handwritten C, 3/5 coding reliability, and one polished file-backed app. Process length and monthly off-campus access matter for planning your calendar; they do not replace fundamentals.
Also expect more tier-2/3 campus coverage than older seniors remember - if your college finally gets a Zoho PPT, treat it as a real shot, not a side quest. The bar does not drop because the venue is new; only the travel friction does.
Yes. Free Zoho placement papers PDF download and previous year question papers (2024-2026) with solutions are on this site - C programming, aptitude, coding rounds, and interview questions. Aptitude PDF practice from the written section is included. No registration. Start with the 2026 PDF and the archive.
Six stages: Resume Screening (2-5 days) → Aptitude & C Programming Test (90-120 min) → Basic Programming (2-3 hours, 5 problems, clear ~3/5) → Advanced Programming/Application Round (90-120 min mini-app) → Technical Interview (30-45 min) → HR (20-30 min). End-to-end is usually 2-3 weeks. Same ladder for campus and off-campus; venue and competition differ.
Six eliminatory rounds from resume to HR (details in the hiring rounds section above). You need all six cleared for an offer. Written clear rates are the steepest drop (~30-40% after the C test).
Zoho’s traditional written format: write outputs and full C programs by hand without IDE help. Typical mix - Quantitative Aptitude (10-15), C Output Prediction (10-15), C Coding (2-3) over 90-120 minutes. Most campus drives still use paper. Practice handwriting compilable C, not pseudocode. See the pen and paper guide.
Advanced Programming Round: 90-120 minutes to build a mini console application (address book, banking, quiz, library/inventory) with menus, validation, and file persistence. Scoring emphasizes completeness, structure, logic, and usability - not clever one-liners.
Placement cell registration → PPT → resumes through the cell → pen-paper (or occasionally online) written on campus → programming rounds → tech + HR (campus or Zoho office) → offers. Same technical bar as off-campus, often with college-reserved seats and a familiar venue. Season-aligned (often Aug-Dec).
Typically 2-3 weeks: resume 2-5 days, written 1 day, programming 1-2 days, tech + HR often same day, results in 2-3 days. Strong candidates can move faster inside a packed drive week.
C output prediction; C coding (patterns, arrays, strings); application building with file I/O; tech depth on pointers/memory/DS in C; HR on Why Zoho?, relocation (Chennai/Tenkasi), learning mindset, and long-term goals. Everything circles practical C skill.
Re-read your code from earlier rounds - Zoho does code review. Be ready to explain pointer choices, complexity, edge cases, and how you would refactor. Implement lists/stacks/queues in C cold. Practice explaining aloud, not only coding silently.
Know the Made-in-India / rural-office story and why that appeals to you specifically. Have a clear answer on relocating to Chennai or Tenkasi. Emphasize learning mindset and multi-year commitment; Zoho screens for people who stay and grow internally.
No strict CGPA cutoff. Degrees: B.E./B.Tech/MCA/M.Sc (any branch). Final-year students and recent grads (within 1 year). No active backlogs preferred (1 may be allowed case-by-case; clear before joining). Max ~1 year gap between 10th and graduation. C is mandatory; C++/Java helps. All branches eligible. Same bar as 2025 - no separate year-specific CGPA change.
C is mandatory across written, coding, and application rounds. C++/Java are optional extras. Expect output prediction, coding, and apps in C, plus interview depth on pointers, arrays, strings, recursion, and DS in C.
Prefer zero active backlogs. One active backlog may be considered case-by-case, but you must clear everything before joining. Strong C demos matter more than a perfect transcript - still, do not treat backlog leniency as a free pass.
No. Mechanical, Civil, ECE, and other branches clear Zoho when C fundamentals are real. Branch does not replace coding ability; it also does not block you if coding is strong.
Candidate-reported (August 2026): MTS ₹5-7 LPA for new grads; Software Engineer ~₹7-10 LPA (1-2 YOE); Senior ~₹12-18 LPA (3-5); Staff ~₹20-28 LPA (6+). Totals include base, bonuses, and benefits in the bands people share publicly.
Member of Technical Staff - the main fresher SWE track. Selected via the 6-round process. Day-one focus is product coding and learning; growth path typically MTS → Software Engineer → Senior → Staff.
Split time ~50% C fundamentals/output prediction, ~30% coding + apps, ~15% modular/file design, ~5% aptitude/HR. Write on paper. Ship end-to-end console apps. Use timed previous papers. Full plans: preparation guide.
Minimum 10-15 timed papers; 20-25 if you want buffer. Quality beats volume - review every miss. Simulate 90-120 minute blocks the way the written test actually runs.
Written is medium-hard if C is weak (~30-40% clear). Tech interview is moderate if you can defend your own code. Overall harder than typical service-company aptitude mills, but very beatable with deliberate C + app practice - not random DSA grind.
Practice writing code on paper and building end-to-end mini-projects. Zoho wants developers who can solve real problems, not just answer MCQs.
Product work across 50+ apps, Made-in-India philosophy, learning culture, rural-office options, no CGPA wall, internal mobility, flexible hours, and solid fresher MTS bands. Pick it if you want product depth over pure services staffing.
Usually yes - Chennai (main) or Tenkasi / other rural offices. HR will ask directly. Be honest; location mismatch is a common late-stage drop.
Zoho: product, MTS ~₹5-7 LPA, C-heavy, no CGPA cutoff, learning/rural culture. TCS: services, ~₹3.5-4 LPA fresher bands often cited, aptitude + basic coding, CGPA filters common. Infosys: services, ~₹4-4.5 LPA bands often cited, IRT-style aptitude+coding, CGPA filters common. Choose Zoho for product + C craft; choose TCS/Infosys for large-services paths and structured training at scale.
In a September 2025 on-campus pool SDE drive, a candidate wrote: “The first round was a classic offline test… We were given one hour to solve 20 questions, split into two sections” - ten moderate-to-hard C tracing/pointer questions and ten aptitude items (Medium). Clearing that pen-and-paper gauntlet led to an L2 algorithmic interview with multiple Java implementations; Zoho’s process still rewards hand-tracing patience before IDE comfort. Takeaway for juniors: even when later rounds allow Java, the opener still filters on careful offline reasoning.
A Zoho Software Developer Intern+FTE select (2025) applied online, was shortlisted in ~10 days, and took a 90-minute written test at Zoho’s Chennai campus before basic coding, module implementation, technical+puzzle, and managerial/HR rounds (GeeksforGeeks). Of five finalists, they reported: “On the same day, I got a call from HR saying I was selected for the Internship and would be moved to Full-Time after 6 months based on performance.” Off-campus patience (shortlist wait) plus same-day finale intensity is a combo you should emotionally budget for.
Another pattern students keep repeating in 2024-2026 write-ups: the application/module round is where “I can solve patterns” candidates stall if they have never built file-backed menus under a clock. If your prep stops at tracing and five coding problems, add at least two full apps before the drive. Candidates who cleared often mention boring strengths - readable menus, working save/load, and being able to explain every function in the tech round - more than clever algorithms.
What to steal from these stories: practice offline; expect module/app work; keep HR ready for internship-to-FTE or relocation talk; and do not treat one Medium/GfG post as a fixed paper template - use it as a vibe check, then return to your own timed mocks.