Academic snapshot
Marks: No rigid public CGPA
Degree: B.E. / B.Tech / M.Tech / MCA or as posted
Backlogs: None active preferred
Year: Final-year and recent grads; intern posts vary
Zerodha Placement Papers 2026
Zerodha is India’s largest retail stockbroker by active clients, founded in 2010 in Bengaluru. It is known for products like Kite, Console, Coin, and Varsity, along with a small-team engineering culture. Zerodha recruits selectively for backend, frontend, and platform engineering roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Zerodha in 2026?
Who this hub is for
- For: Students targeting engineering roles around Kite, Console, backend, or adjacent product teams - and anyone willing to submit a real take-home instead of sitting a 90-minute MCQ paper.
- Not the same track: Rainmatter portfolio companies, Varsity content roles, or support/ops openings. Those interviews are not this assignment loop.
- Fresher reality: Zerodha is picky and opening-driven. Freshers do get hired, but there is no annual “Zerodha NQT Friday.” You apply when a post is live, or you get referred.
On-campus vs careers-page
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus / intern post | Timing, college filter, sometimes a shorter coding screen | Assignment or live coding still decides |
| Careers page | You compete with laterals and strong side-project people | Same ownership bar |
| Referral | Resume visibility | You still ship the take-home |
| Rainmatter / ecosystem | Different company, different loop | Do not reuse a Zerodha Why |
Campus cells sometimes list Zerodha. Treat that as a bonus slot, not the default path. Most public notes describe job-post → resume → assignment → interviews.
Degree, CGPA, and “is 7.0 enough?”
Is there a CGPA cutoff? Not a published one that students can quote the way they quote TCS 6.0. Placement-cell JDs may still pre-filter. A 7.2 with a dead GitHub loses to a 6.8 who can explain a Go service they actually run.
Branches: CS/IT/ECE show up most. Non-CS can clear if the assignment is real - Zerodha is not running a “all branches welcome aptitude mill.”
Backlogs: no active backlogs at joining is the usual line. Gap years are less discussed than at GET drives; the assignment will out you faster than a transcript footnote.
What helps the resume screen: one project with users or measurable load, any markets-adjacent tool (even a paper-trading dashboard), Go/Python/JS you can defend, and a README that does not read like a tutorial clone. Listing “interested in fintech” with zero artifacts is how screens die. See certifications after fundamentals - they do not replace the take-home.
Skills they actually filter
Primary: Take-home craft, DSA, systems
Languages: Go, Python, JavaScript
Exam filter: Assignment / interviews, not a mass OA
Differentiator: Markets curiosity + simplicity
Who usually fits and who struggles
Good fit: You like building small tools end-to-end, you can sit with a blank editor and finish a service without a framework zoo, and you are genuinely curious how Kite stays fast when the market opens. Comfortable relocating to Bengaluru. You have at least one project you would be embarrassed to over-explain with buzzwords.
Harder path: You only grind LeetCode hard and skip READMEs; you freeze without Copilot; you think “fintech” means copying a stock-chart tutorial; you refuse Bengaluru; you want a 2,000-person campus drive with a published paper every August.
Branch myth: ECE/IT students are not blocked. They also are not “lucky.” The assignment is the same. Use the missing CGPA wall as permission to apply, not as a free pass past the repo review.
Intern vs FTE: Internship screens can be a shorter coding window plus one technical. PPO is not automatic - they will look at whether you shipped in the intern weeks the same way the take-home asked you to ship. Do not treat an intern offer as a Bengaluru FTE CTC screenshot.
Resume honesty that actually matters: if you list Go, they will ask you to debug a race or a nil pointer in English. If you list “built a trading bot,” they will ask what exchange, what failure mode, and whether you lost imaginary money because of a bug. Delete the line you cannot defend. Zerodha culture talk is allergic to decoration.
CGPA chances if a college still prints a number
Some campus cells invent a floor even when Zerodha’s careers page does not. Use this only as a sanity table, not as law.
| CGPA range | Campus-cell reality | What still decides |
|---|---|---|
| Below 6.5 | May get filtered by the cell | Off-campus + a serious repo can still compete |
| 6.5-7.4 | Usually eligible if the cell allows | Assignment quality |
| 7.5-8.4 | Comfortable on paper | Still lose if the take-home is a tutorial clone |
| Above 8.5 | Helps nothing extra in interviews | Same code review |
A 8.8 who cannot write tests is not “safe.” A 6.9 who can explain a rate limiter they built is the more Zerodha-shaped candidate.
Zerodha placement papers - last few years
Download 2026 Zerodha placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
How these packs train DSA and assignment stamina
Zerodha does not drop an official annual paper the way TCS or Infosys do. “Previous year papers” on this site train the DSA stamina, systems prompts, and assignment themes that interviews reopen. They are simulators - not leaked take-homes from Kite.
Think of a PDF set as a gym for the technical rounds, and a weekend project as the gym for the assignment. If you only do one, do the weekend project.
| Round (typical) | What to practice |
|---|---|
| Take-home | Completeness, tests, README, boring design |
| Technical 1 | Medium DSA, language fluency, edge cases |
| Technical 2 | Systems / your assignment defense |
| Culture fit | Ownership, simplicity, Why Zerodha |
Themes that keep repeating (2024-2026)
Across public prep notes and student chatter:
- Assignment: a small API or CLI, a data transform on tick-like or order-like records, a rate limiter, a simplified matching or book-keeping task, or a dashboard backend. Interviewers care that it runs, has tests, and is not a microservice theme park.
- DSA: arrays/hashes, heaps, binary search, graphs at medium - not FAANG-hard olympiad graphs. Coin change, two pointers, and “debug this under time” show up in practice packs more than red-black trees.
- Systems / product: order flow, idempotency, time-series ingest, why you would not put every tick in a chatty ORM, cache vs correctness when money is involved.
- Culture: “tell me something you owned when nobody asked,” “what would you cut from this design,” “why this broker and not a unicorn with a bigger brand.”
2024-style notes: more laterals in the same queue as freshers; take-homes that looked like “build a tiny HTTP API with auth and a rate limit,” then a technical that opened the rate-limit file first. Students who only practised arrays felt the second interview.
2025-style notes: intern coding screens (90 minutes, two medium problems) showed up in a few college mails; FTE loops stayed assignment-heavy. Product questions leaned “what breaks at 9:15 am” more than “design Netflix.”
2026-style notes: same spine. Careers page still beats any blog that claims a fixed 80-minute aptitude paper. If your college mailer adds an OA, treat it as extra - do not throw away take-home practice.
Sample assignment you can actually build this weekend
Brief (practice only): “Accept a stream of trades {symbol, price, qty, ts}. Expose GET /vwap/{symbol} for the last 15 minutes and POST /trade to ingest. Handle bad timestamps. Document how you would stop a burst of 10k posts from melting the box.”
A passing weekend version: one process, in-memory ring or deque per symbol, mutex or language equivalent, tests for empty symbol and out-of-order ts, README with curl examples, a paragraph on what you would move to Redis later and why you did not do it today.
A failing weekend version: Docker Compose with four services, no tests, README that says “run main.py,” and a VWAP that is wrong on a two-row fixture.
That contrast is the whole Zerodha paper philosophy: previous-year PDFs train the DSA half; this kind of brief trains the half that actually rejects people.
How to use one paper set in a single sitting
- Timed: 60-90 minutes of medium DSA. Honour the clock.
- Untimed review: list every miss as speed vs concept.
- Write a one-page design for “ingest 10k events/sec and show last price” without copying a blog.
- Open yesterday’s take-home and add one test you skipped.
- Speak a 60-second Why Zerodha (Kite, discount brokerage, small teams) without reading.
Related problems to practice
| Theme | What to drill next | Why Zerodha asks it |
|---|---|---|
| Hash maps / two pointers | Timed array sets | Live technical |
| Heaps / top-K | Streaming-ish problems | Tick/order mental model |
| Binary search | Boundaries on paper | Interview calm |
| Rate limit / idempotency | Sketch + tiny code | Assignment follow-ups |
| README + tests | Ship a 200-line service | The actual filter |
| Order / ledger stories | Varsity + Kite as a user | Culture + product |
Zerodha placement process, round by round
How to apply
Careers page
Primary method - zerodha.com/careers. Read the stack. Apply with a resume that points to a real repo.
Campus / intern
Occasional college visits or intern posts. PPT if any, then the same assignment bar.
Referrals
Higher visibility. Still expect a take-home. Do not ask an employee to “just push” a empty GitHub.
Campus vs off-campus in practice: On-campus = rare reserved attention, familiar hall, season-aligned. Off-campus = more attempts per year, thicker mix of laterals, your repo still decides it. Technical content does not get easier because you applied from home.
Round-by-round walkthrough
-
Resume screening (3-10 days)
They scan for shipped work, not CGPA gates. Put the project that proves you finish things above a list of courses. A one-line “built a paper-trading journal in Go with tests” beats “interested in backend.” Keep it honest; the assignment and tech rounds will open the repo.
-
Take-home assignment / role-specific screen (often 2-7 days to submit)
This is Zerodha’s signature filter. Briefs vary: a small HTTP service, a parser, a matching or aggregation toy, a CLI that is actually usable. Evaluation is completeness, simplicity, tests, and whether you over-engineered to impress.
Build order under the clock: (1) make it run, (2) happy path + two edge cases, (3) tests, (4) README with how to run and what you skipped, (5) only then a tiny extra. A working 200-line tool beats a half-broken Kubernetes demo.
Some intern or campus notes mention a timed coding screen instead of a long take-home. Follow the invite. Practice both: a weekend ship and 90-minute DSA.
-
Technical interview 1 (45-60 min)
Live DSA in Go/Python/JS, plus “walk me through your assignment.” Expect “what happens if this input is empty,” “why this data structure,” “how would you test this.” About half of assignment submitters who get interviews still stall here if they cannot narrate.
Practical target: restate, brute force, tighten, edges, then code. Zerodha interviewers reward calm debugging over a memorised optimal one-liner you cannot explain.
-
Technical interview 2 (45-60 min)
Deeper on systems or product: latency, failure modes, what you would not build, how Kite-like traffic differs from a college CRUD app. They may reopen files you hoped nobody would read. If you copied a tutorial structure, this round hurts.
-
Culture fit / ownership (30-45 min)
Small teams, extreme ownership, simplicity, Bengaluru WFO. “Tell me about a project you owned when nobody assigned it.” “When did you delete complexity?” Vague “I like trading apps” answers underperform. Have a specific Why Zerodha.
-
Offer / joining
Location is almost always Bengaluru. CTC bands students cite sit around ₹12-25 LPA for engineering - confirm the letter. Background checks will reopen what you claimed.
Timeline from application to offer
| Phase | Duration | What happens |
|---|---|---|
| Resume screen | 3-10 days | Careers / campus / referral |
| Assignment window | 2-7 days | You ship; they review |
| Interview scheduling | 2-7 days | Two technicals + culture |
| Technical loop | 1-2 weeks | DSA + assignment defense |
| Culture / HR | 3-7 days | Ownership, location |
| Offer | 1-5 days | Letter + Bengaluru joining |
Total: often 2-6 weeks. Faster when a team is urgently hiring; slower when the assignment queue is thick. There is no “result next day after MCQ” rhythm.
What each early round actually asks
- Assignment distribution: one coherent brief, not five LeetCode files. Persistence or a clear in-memory model, input validation, and a README are the quiet requirements.
- Tech 1 types: one medium coding problem you must finish cleanly; follow-ups on complexity; “show me the test you would add.”
- Tech 2 themes: your repo, failure handling, and a product/systems sketch (last price, order ack, reconnect).
- Culture: Why this company, relocation, how you work when the team is three people not thirty.
If you only remember three numbers: 3 major stages after resume, assignment-first, fresher band ₹12-25 LPA (candidate-reported). Everything else is execution.
How the assignment review actually feels
Reviewers are engineers, not a campus vendor scoring MCQs. They clone, they run, they look at git history if you left it messy, they search for copied READMEs. A 4-day commit graph that is “Initial commit” with 2,000 lines is a smell. Small commits with messages like “add vwap window tests” read like an adult.
Time boxing a 4-day take-home that many students use:
| Day | Output |
|---|---|
| 1 | Running happy path; fixture file; README skeleton |
| 2 | Edge cases + tests; no new features |
| 3 | One performance or safety extra (rate limit, validation) |
| 4 | Delete unused files; write trade-offs; sleep before submit |
Submit on day 4 even if you have a “brilliant” extra in your head. Late extras that break the happy path are a classic reject.
Live interview habits that transfer from the take-home
- Narrate state the way you would write a commit message.
- If you do not know a Go idiom, say the Python equivalent and ask if they want you to continue.
- When they change a constraint (“now 10 million symbols”), talk about what breaks before you rewrite.
- Keep a paper list of test cases; interviewers like seeing you think in fixtures.
Zerodha technicals are closer to “pair on a weekday bug” than “contest round 2.” Practice that tone.
Preparation resources for Zerodha
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.
Where your Zerodha prep time should go
If a Zerodha 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 Zerodha sits around ₹12-25 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, Python, C, Go. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Zerodha does not publish a single campus CGPA cutoff. Candidate reports: relevant degree (B.E./B.Tech/M.Tech/MCA or equivalent), no active backlogs preferred, and proof you can ship on a take-home assignment. Skills in DSA, systems, and markets curiosity matter more than a 0.2 CGPA gap. Always verify the job post on zerodha.com/careers.
What you are training for: Typical engineering loop: 1. Resume screen on careers/referral (3-10 days), 2. Take-home assignment or role-specific coding screen (often several days to submit), 3. Two technical interviews on your assignment, DSA, and systems (45-60 min each), 4. Culture-fit / ownership round (30-45 min), 5. Offer and Bengaluru joining. End-to-end often 2-6 weeks. Zerodha is opening-driven, not a mass NQT-style campus factory.
Short version of the prep split: Split time about 40% take-home craft (readable Go/Python/JS, tests, README), 30% medium DSA you can debug live, 20% systems + markets product sense (orders, ticks, risk, Kite/Console), 10% ownership STAR stories. Weekly timed mocks on this site. Do not prep it like TCS NQT aptitude.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Zerodha 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 Zerodha 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 Zerodha 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 Zerodha?” with one concrete product, lab, or business line - not a slogan.
Week 4 - mocks and logistics. Sleep, id photocopies, and a dry run of the oa platform if the invite names one. If you still have energy, redo only the questions you failed in week 2.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Zerodha-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.
Practice pages to open this week
- OA / assessment notes
- aptitude mock quiz
- coding question bank
- interview experiences
- HR question bank
- week-by-week guide
- previous year papers
- 2026 paper page
Use this hub for the Zerodha story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Zerodha PDFs and never sitting one under a timer.
- Switching languages every weekend because a senior used a different one.
- Memorising HR answers before they can finish the OA.
- Ignoring the company-specific quirk on this page (unique round, exam name, or role band) and preparing like a generic service-company drive.
If you do one thing after reading this: schedule three timed Zerodha papers on three different days, then interview prep on the leftovers.
Zerodha compensation & benefits
Figures below are candidate-reported as of August 2026. Treat them as ranges, not offer letters.
Engineering bands students cite
| Level | Experience | Typical CTC (reported) | Notes |
|---|---|---|---|
| Intern / contract | In college | Stipend / short contract | Convert is performance-based |
| Early-career engineer | New grad / 0-2 YOE | ₹12-25 LPA | Bengaluru; team-dependent |
| Mid engineer | 2-5 YOE | Higher, role-posted | Laterals compete on the same assignment bar |
Confirm base / bonus / any equity-like components on the written offer. Private company - do not cargo-cult a levels.fyi screenshot from a different year.
Benefits students care about
- Bengaluru office; most engineering talk assumes WFO / office-first
- Learning by owning a real product surface (Kite, Console, internal tools)
- Health cover and standard India tech benefits as per letter
- Small-team pace - more responsibility, less “training batch of 400”
How to read the ₹12-25 LPA band: the floor is not a campus mass-hire guarantee; the ceiling is not what every intern convert sees. Use it for expectation-setting. Intern stipends are a different conversation - do not annualise them and call it CTC.
Growth students ask about: there is no public MTS → Staff ladder like Zoho’s published chatter. Expect team-level growth, more ownership, and the chance to work close to product. If you want a 10,000-person structured training academy, this is the wrong company.
How to read an offer without getting confused
- CTC vs in-hand: ask for the split. Private brokers are not obligated to match a FAANG blog post.
- Intern stipend: a monthly number × 12 is not FTE CTC. Do not post that on a group chat as “Zerodha package.”
- Joining bonus / ESOP chatter: only counts if it is in the letter.
- Notice / bond: read. Assignment-culture companies still have paperwork.
- Location clause: Bengaluru is not a rumour. If the letter says office, plan rent before you celebrate.
Students sometimes compare Zerodha’s band to PhonePe or Groww in the same week. Different loops, different teams, different years. Use this site bands as context, then wait for paper.
Rainmatter grants and ecosystem startups are a separate compensation world. Do not mix a Rainmatter portfolio CTC into a Zerodha Kite-team expectation. If the JD is Zerodha Broking, the letter should say Zerodha Broking.
What’s changed in Zerodha hiring lately
Hiring shape 2026
Still opening-driven. Take-homes remain the loud filter. Campus slots exist but are not a national paper season.
Stack talk
Go, Python, and JavaScript stay the languages students should pick. “We use whatever” without one strong language fails live debug.
What to practice more
Weekend ships with tests; medium DSA narration; one honest Kite/Console product paragraph.
Offer reality
Treat ₹12-25 LPA as a reported band. Bengaluru relocation is not a soft question.
Net for 2026: do not wait for a leaked “Zerodha OA pattern 2026 PDF” that looks like Infosys. Watch careers, keep a repo warm, and stay assignment-ready year-round.
Also expect more intern coding screens at colleges that finally get a slot. If your placement cell forwards a HackerRank link, do it - then still keep a take-home ready for the FTE path. The bar does not drop because the venue is your seminar hall; only the travel friction does.
Kite and Console keep shipping. Using the products the week before an interview is still the cheapest “domain prep” available. You do not need an engineering blog recitation. You need one specific thing that annoyed you or impressed you as a user, and a sentence about how you would measure it.
Hiring volume vs quality: Zerodha will not fill 200 campus seats to hit a headcount number. That is good news if you can ship, and bad news if you were waiting for a mass shortlist. Plan other product companies in parallel (Groww, Razorpay, PhonePe) so one silent careers inbox does not freeze your season. Keep the take-home repo warm even in months with no open JD - when a post appears, you will not be starting from an empty GitHub.
Varsity as cheap domain prep: you do not need to finish every module. Read order types, margins at a user level, and what Console actually shows after a trade. Then write four bullet notes in your own words. If you cannot explain a CNC vs MIS order to a junior, your Why Zerodha is still a poster.
What “simplicity” means in a design follow-up: they would rather you keep state in one process with a mutex and a test than invent a three-service “event-driven” toy you cannot operate. When they ask what you would add next, give one step (persistence, or a rate limit) - not a platform rewrite. That answer is how culture-fit and tech-2 overlap.
Rainmatter is adjacent, not the same interview. If a posting is a portfolio company, read that JD. Do not reuse a Kite take-home story for a different product with different ownership. Zerodha Broking engineering is still Bengaluru, assignment-first, and allergic to decoration. Keep the repo warm anyway.
Common questions about Zerodha hiring
Process & papers
What is the Zerodha placement process?
Typical engineering loop: resume screen → take-home assignment or role-specific coding screen → two technical interviews → culture fit → offer. End-to-end often 2-6 weeks. Opening-driven, not a mass NQT calendar.
How many rounds are there in Zerodha interview?
About 3 major stages after resume: assignment, technical (usually two conversations), culture fit. Some roles add a recruiter screen. Count the invite.
Can I download Zerodha placement papers PDF?
Yes. Free Zerodha placement papers PDF and 2024-2026 style DSA/assignment practice are on this site. No registration for main downloads. Start with the 2026 PDF or the archive. Pattern trainers, not leaked live assignments.
What is the Zerodha take-home assignment?
The main filter: a real-ish engineering brief and a few days to submit working code, tests, and a README. Interviews reopen the repo. Completeness and simplicity beat a flashy incomplete architecture.
Is there a Zerodha online assessment exam pattern?
There is no single published annual OA like TCS NQT. Some intern/campus screens use timed coding; most engineering notes describe a take-home. Confirm the job post or college email.
Eligibility & offer
What is Zerodha eligibility criteria for freshers 2026?
No rigid public CGPA. Relevant degree, no active backlogs preferred, and proof you can perform on the assignment. Skills in DSA, systems, and markets curiosity matter after the resume. Verify zerodha.com/careers.
Does Zerodha hire freshers on campus?
Sometimes, but it is not a classic mass campus recruiter. Most hiring is opening-driven. Freshers clear when the assignment and ownership bar clear.
What is Zerodha salary for freshers in India?
Candidate-reported ₹12-25 LPA CTC for early-career engineering in Bengaluru (August 2026). Intern/contract is separate. Written offer wins.
Do I have to relocate to Bengaluru for Zerodha?
Yes for most engineering roles students discuss. Culture-fit will ask. Be honest.
Prep & Zerodha-specific
How to prepare for Zerodha placement?
About 40% take-home craft, 30% live DSA, 20% systems + markets product sense, 10% ownership stories. Details: preparation guide.
What programming languages are allowed in Zerodha?
Commonly Go, Python, JavaScript. Pick one you can debug live. Confirm the posting.
Do I need stock-market knowledge for Zerodha?
Curiosity, not a CFA. Know what Kite/Console do, why orders and latency matter, and a non-generic Why Zerodha. Engineering depth still decides the assignment.
Zerodha vs Groww vs PhonePe - which fits better?
Zerodha: broker product, assignment-heavy, Bengaluru, small-team ownership. Groww: broader consumer fintech, often more classic OA + interviews. PhonePe: payments scale, heavier DSA/system design at product-company volume. Share DSA; split the Why and the assignment style.
Any pro tip for Zerodha placement preparation?
Treat the take-home as the interview. Ship a boring, tested, documented solution, then rehearse defending every file. Keep one medium DSA pattern cold.
Where can I read real interview experiences?
Zerodha interview experience on this site, plus public careers notes. Use as maps, not scripts - detailed public fresher write-ups are thinner than for TCS/Zoho.
Is Zerodha placement easy or difficult?
Harder than a service-company aptitude mill, different from FAANG volume. The assignment rejects people who only MCQ. Beat it with deliberate shipping, not 400 random hard problems.
Zerodha - recent candidate experiences
Public fresher write-ups are thinner than Zoho or TCS. That is a signal: Zerodha is not running a national paper that 2,000 people blog. Use the patterns below as prep maps, not as a leaked 2026 assignment.
What “assignment-first” feels like in practice
Students who reach interviews usually describe a take-home that ate a weekend, then two conversations that felt like a code review plus a systems chat. The ones who stall after submit often shipped a demo that only they knew how to run, or could not explain a library they pasted. Takeaway: if a stranger cannot clone and run in ten minutes, you are not done.
A useful fail mode: LeetCode-only
A recurring junior story (from peer groups, not one famous GfG novel): strong contest rating, empty README, generic “I like fintech.” The assignment came back with questions they had not considered (invalid input, time, “why this extra service”). They did not get the second technical. Takeaway: medium DSA is necessary; it is not sufficient.
What to steal for culture fit
InterviewEra-style 2026 notes summarise the loop as take-home → technical × 2 → culture fit, with ownership and simplicity as the culture keywords. Prepare one story where you deleted work, not only where you added a feature. Zerodha’s public engineering reputation is small teams owning large surfaces - “I wait for tickets” is the wrong energy.
A day-of plan you can screenshot
- ID, charged laptop, assignment repo bookmarked
- 10-minute README reread before the call
- Restate the live DSA problem; do not rush the first line
- If they ask markets: be a curious user, not a fake trader
- After: write what they probed; that is your next mock
More: interview experience.
Zerodha vs other Bengaluru product loops
Share: one strong language, medium DSA, a project with metrics.
Split: Zerodha wants assignment craft and markets curiosity; PhonePe/CRED often look more like high-volume product DSA + design; Razorpay leans payments. Do not reuse a “I like startup culture” paragraph unchanged.
A 10-day rescue if you have an invite and a weak repo
Days 1-2: make the existing project runnable with tests.
Days 3-5: one fresh mini take-home under 48 hours.
Days 6-8: medium DSA only, error log.
Day 9: mock defense with a friend who is allowed to be rude.
Day 10: Why Zerodha + sleep.
No new Kubernetes course in this window.
Two composite stories
Story A - intern coding screen, 2025-style: College mailer added a 90-minute HackerRank-like test with two medium problems (array + string). Cut was “both compiling with passing hidden tests,” not 100% efficiency. Next day: 45-minute technical on the second problem plus a project. Culture was 20 minutes on relocation. Takeaway: even when an OA appears, they still want narration and Bengaluru clarity.
Story B - careers-page FTE, assignment week: Candidate spent three days on a Go HTTP service, submitted with tests, then froze in tech 2 when asked how they would persist the window across process restart. They had written “in-memory is fine for the brief” but could not sketch a durable next step. Takeaway: “I skipped X on purpose” is allowed; “I never thought about X” is not.
Neither story is a leaked paper. Both are the kind of miss you can practise: hidden tests, and a one-level-deeper design answer.
What to do the evening you submit
Do not start a new side project. Export a list: how to run, three tests, two known limitations, one metric you would add. That list is your tech-2 cheat sheet. Sleep. The interview is a conversation about work you already did - treat it like a lab viva, not a new exam.
If two friends apply the same week, do not share take-home repos. Zerodha’s filter is whether you can defend the files. A copied assignment that you cannot explain is worse than a smaller original. More notes: interview experience.