Academic requirements
Campus floor: Often 7.0 CGPA
Degrees: B.E./B.Tech/M.Tech/MCA
Backlogs: None active
Year: Final year / recent grad
Groww Placement Papers 2026
Groww is a Bengaluru-based investment platform that lets users trade stocks, mutual funds, F&O, and other financial products through a simple mobile app. Founded in 2016, it is known for a rigorous SDE hiring process that expects strong data structures and algorithms skills.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Who can apply to Groww in 2026?
Groww does not publish one CGPA that covers every intern and SDE requisition. Campus cells print a number; off-campus intern JDs talk more about projects. Treat the table below as candidate-reported as of August 2026.
Who this hub is for
- For: Final-year students targeting SDE intern / SDE-1 on Groww’s Bengaluru engineering teams (app, web, backend).
- Also for: Off-campus applicants to web, React Native, backend, or AI intern roles who will face assignments instead of (or before) a classic OA.
- Not the same track: Sales, CA/CS campus, or pure content roles.
Degree, CGPA, and “is 7.0 enough?”
7.0 CGPA is the floor students quote for many campus SDE shortlists. It is not a selection guarantee. A 7.1 who finishes two OA mediums and can explain a trading-adjacent project (even a paper-trading clone done properly) beats an 8.9 who stalls on hashing.
Off-campus intern posts are softer on printed CGPA and harder on shipping. If you cannot demo an assignment in 48-72 hours, do not count on the “no cutoff” rumour.
On-campus vs off-campus
| Route | What usually changes | What stays the same |
|---|---|---|
| Campus SDE/intern | Batch OA, 7.0 language, PPT | Medium DSA bar |
| Off-campus intern (web/RN) | Take-home assignment, stack grill | Still need clean code + Why Groww |
| Referral / hackathon | Faster screen | Interviews do not get easier |
| Intern → FTE / PPO | Conversion loop may skip OA | You defend internship work |
Campus is not “easier DSA.” Off-campus is not “no DSA.” Several intern write-ups still include two medium LeetCode problems in TypeScript after the assignment.
Detailed eligibility criteria breakdown
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA | 7.0+ on many campus lists | Off-campus intern more portfolio-led |
| Degree | B.E./B.Tech/M.Tech/MCA | Related computing degrees |
| Branch | CS, IT, ECE+ | App/web intern roles care about stack proof |
| Year | Final year; 2025-2026 batches on intern JDs | Recent grads for some FTE |
| Backlogs | None active | Clear before joining |
| Location | Bengaluru WFO | Non-negotiable in most stories |
| Languages | Java/Kotlin/Python/JS/TS | Match team after OA |
Skills that filter
Campus: Medium DSA first
Intern off-campus: Assignment quality
Then: JS/Kotlin/backend depth
Always: Bengaluru joining
Who usually fits and who struggles
Good fit: You like building consumer product, you can sit with a medium DSA pair under a clock, and you have opinions about app vs web (if you did both). Fintech curiosity helps - you do not need a CFA.
Harder path: You only solve Easy problems, you submit a half-broken assignment APK, or you refuse Bengaluru. Culture rounds are friendly and still drop people who cannot say why Groww specifically.
Tier myth: Tier-1 campus helps for SDE intern volume. Off-campus RN/web intern roles are how many non-campus students get in - via a brutal assignment, not via sympathy.
Selection feel by CGPA band
| CGPA range | Rough chances | Reality check |
|---|---|---|
| Below 7.0 | Often filtered on campus | Off-campus intern + strong assignment |
| 7.0-7.4 | Meets many printed floors | OA / assignment decides |
| 7.5-8.5 | Common shortlisted chatter | Still two mediums to clear |
| 8.5+ | Helps resume piles | Does not skip live coding |
Groww previous year papers & PDFs
Download 2026 Groww 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
Groww does not publish a permanent official paper. Packs on this site are OA and interview simulators - not leaked live tests.
Campus papers train timed medium DSA. Off-campus intern prep should still use them, then add a weekend assignment build.
| Round (typical) | What to practice |
|---|---|
| Campus OA | 2-3 mediums in 60-90 min |
| Tech 1 | Live DSA + OOP/DBMS/OS |
| Tech 2 / EM | Projects, light design, one more DSA |
| Assignment track | Not a PDF - you build and demo |
| Culture / HR | Why Groww, unstuck stories, location |
Themes that keep repeating (2024-2026)
- 2024 intern off-campus: OA with 3 mediums in some loops; Tech 1 mixed two more mediums with backend/SQL/OS; EM asked design concepts plus one DSA. Entire process in ~3 days for a few candidates.
- 2025 web intern: Assignment first (TypeScript codebase stories - Groww’s JS → TS shift comes up). 90-minute technicals that felt “toughest JS interview” to some candidates: output questions, then culture fit.
- 2025-2026 RN intern: Take-home app + demo video → DSA in TypeScript + RN/JS grilling → managerial on architecture/WebSockets/Redux. Rejections after weak machine-coding of Redux-from-scratch are a pattern.
- 2026 expectation: Campus stays DSA-first. Off-campus intern stays assignment-first. Fintech vocabulary (orders, holdings, SIPs, market hours) is a plus in HR, not a substitute for code.
How papers transfer to assignments: a sliding-window PDF problem is the same muscle as “unique users in the last W minutes on a websocket feed.” If you are on the RN intern track, still do two timed DSA papers a week so TypeScript coding in the interview is not your first clock. If you are campus-only, still build one tiny order-API weekend project so EM design concepts have a home.
What not to memorise: exact GfG prompts from 2024. Groww reuses families (hashing, heaps, graphs, JS output). A new medium on the same family should feel familiar. Three reviewed papers beat ten unread GitHub dumps.
How to use one paper set
- Timed: 90 minutes, 2-3 coding prompts in your OA language.
- Review: rewrite the cleaner solution; list two fintech cousins (pending orders, unique users in a window).
- Map misses to families; pull cousins from coding questions.
- 15 minutes: explain an order-placement happy path + one failure (duplicate debit).
- Log a STAR story.
Related problems to practice
| Theme in a set | Drill next | Why Groww asks it |
|---|---|---|
| Sliding window | Unique users / ticks in last W | Market data windows |
| Heaps / Top-K | Top movers, watchlist sort | Home feed |
| Hashing | Idempotent order ids | Double-tap place order |
| Graphs | Dependency of modules | Portfolio graphs (rare) |
| DP | Knapsack-ish allocations | Occasional campus OA |
| Intervals | Market session windows | Trading hours logic |
Groww placement process, round by round
Groww hires through campus cells, careers.groww.in / job posts, referrals, and hackathon/HR pipelines. After shortlisting, you are on one of two shapes: OA-first (campus SDE) or assignment-first (many off-campus intern teams).
Application methods
Campus recruitment
PPT → OA → two technicals → HR. Stronger at colleges Groww already visits.
Off-campus intern
Apply → resume screen (sometimes 6-7 days) → assignment → 60-90 min technical → culture/managerial.
Referral / hackathon
Some web intern stories start from a Groww-powered hackathon HR contact, then an assignment.
1. Resume screen
7.0+ when printed, internships, GitHub that is not empty. Put one line that proves you shipped (API, app screen, load test) - “passionate about fintech” is noise.
2. Online Assessment - 60-90 min
| Component | Typical shape (reported) | Focus |
|---|---|---|
| Coding | 2-3 medium | Arrays, hashing, trees, graphs, DP |
| Duration | 60-90 min | HackerRank / similar |
| Languages | Java, C++, Python, JS/TS | Confirm invite |
| Advance bar | Often ≥2 full AC | Optimal preferred |
Time box: 5 min skim → lock the solvable medium → second full solution → third only if 1-2 are safe.
Deeper: Groww Online Assessment.
3. Technical 1 - ~60 min
Two more mediums is common, then a slide into your internship: backend, SQL, OOP, OS. They want narration, not mute typing.
4. Technical 2 / em - ~60 min
Resume deep-dive, system design concepts (you may not draw a full HLD), one more DSA. Some EMs stay conceptual (“what is caching, what is idempotency”) rather than “design Groww.”
Worked mini-outline - place equity order:
- Client tap → validate market hours + funds → create order id (idempotent) → send to broker/OMS → persist states (pending/open/rejected).
- Failure: network retry must not double-buy.
- Read path: holdings vs orders eventually consistent; say what you would show the user.
- You are a fresher - name the states; do not invent 15 microservices.
5. Culture / HR - ~20-30 min
Why Groww, developer journey, app vs web preference, what you do when stuck, Bengaluru, stipend/CTC. Chill tone, real filter.
| # | Campus round | Duration | What they check |
|---|---|---|---|
| 1 | OA | 60-90 min | Timed medium DSA |
| 2 | Tech 1 | ~60 min | DSA + CS fundamentals |
| 3 | Tech 2 / EM | ~60 min | Projects + light design |
| 4 | Culture / HR | 20-30 min | Motivation + location |
Off-campus intern variant
- Assignment (2-5 days): build a small app, sometimes WebSockets, submit APK/demo. This is the OA.
- Long technical (60-90+ min): DSA (sometimes in TypeScript), JS output/debugging, React/RN internals (
useMemo, Redux, native bridge), assignment autopsy. - Managerial (30 min): architecture choices, scalability talk, Why Groww.
Machine-coding “implement Redux / Promise utilities from scratch” has ended otherwise strong RN loops. Practise that if you apply to app intern.
Timeline from application to offer
| Phase | Campus (typical) | Off-campus intern (typical) |
|---|---|---|
| Screen | 3-10 days | 5-10 days |
| OA / assignment | 1 day / 2-5 days | Assignment dominates |
| Interviews | 2-10 days | Often 1-3 days once scheduled |
| Result | 1-5 days | 2-3 days common in write-ups |
| End to end | ~2-3 weeks | ~1-3 weeks (some 3-day sprints) |
Practice map for Groww placements
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.
What to practise before a Groww drive
If a Groww 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 Groww sits around ₹15-28 LPA (candidate-reported - confirm the letter). Languages students mention most often: Java, C++, Python, C. Pick one and stay with it in OA and interviews.
Eligibility reminder (from student reports): Campus SDE/intern posts commonly prefer about 7.0+ CGPA, a B.E./B.Tech or related computing degree, no active backlogs, and final-year or recent-graduate status. Off-campus intern tracks (web, React Native, backend) are more portfolio- and assignment-driven. Bengaluru joining is the default. Verify the careers page or campus JD.
What you are training for: Campus SDE intern/FTE loops usually run: resume screen → online assessment (2-3 medium DSA problems) → Technical 1 (more DSA + CS fundamentals) → Technical 2 / EM (projects, light design, more DSA) → culture/HR. Off-campus web/app intern roles often replace OA with a take-home assignment, then a stack-heavy interview and a culture round. Timeline: a few days to about 3 weeks.
Short version of the prep split: Campus path: 50% medium DSA, 20% timed OA mocks, 20% CS fundamentals (OOP, DBMS, OS) plus light fintech design, 10% Why Groww and projects. Off-campus web/RN path: add a serious assignment (TypeScript, WebSockets, Redux) and JS output questions. Do not treat Groww as a services aptitude company.
A four-week plan that actually gets used
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Groww 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 Groww 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 Groww 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 Groww?” 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.
Where the hours should go
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Groww-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 Groww story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 Groww 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 Groww papers on three different days, then interview prep on the leftovers.
If you are starting from a service-company prep base
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Groww papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Groww-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
10-day crash version
Days 1-3: one timed Groww 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 Groww. 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.
What to carry into the interview room
Know your project at the level of what broke and what you changed, not only the tech list on the resume. For Groww, 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.
Tracking that does not become a second job
A single note with date, paper name, score/time, and three misses is enough. If you cannot name your last three Groww mistakes, you are collecting content, not preparing.
Extra drill block (1)
Sit one more mixed Groww set this week: 20 minutes aptitude or MCQ if the drive has it, then one coding problem you have not seen since last month. Explain the solution out loud in 90 seconds. If you cannot, the interview will feel the same way. Then stop - more volume after that usually turns into tired guessing.
What Groww pays freshers (candidate-reported)
Candidate-reported as of August 2026. Stock, joining bonus, and intern vs FTE change the number a lot.
| Band | Typical reported | Notes |
|---|---|---|
| SDE intern stipend | ₹50,000-₹80,000 / month | 4-6 months, Bengaluru; some posts lower |
| Intern → SDE-1 / PPO | ₹15-28 LPA | Wide because of ESOPs and year |
| Direct SDE-1 chatter | Same wide band | Confirm base vs equity |
Do not quote ₹28 LPA as a promise. Read the offer: base, variable, ESOPs, cliff. Intern stipend is not CTC.
Benefits students ask about
- Bengaluru office (assume WFO/hybrid with office days)
- Health insurance on FTE letters
- Learning by shipping on consumer scale - the real perk, and the real stress (market hours, money movement)
- Intern conversion is performance-based, not automatic
Groww hiring updates for 2026
Two funnels, two preps
Campus DSA vs intern assignments. Mixing them wastes weeks.
TypeScript showed up
Web/RN interviews ask TS/JS output and the JS→TS migration story.
Speed once you are in
Some intern loops finish in 3 days. Keep a packed calendar once OA clears - do not book a trip.
Bengaluru stays the hub
Do not prep as if remote fresher SDE is the default.
Net: 2026 is not a new exam. It is the same medium DSA plus a higher bar on intern take-homes.
Groww placement FAQs
Process & papers
What is the Groww placement process?
Campus: screen → OA (2-3 medium DSA) → Tech 1 → Tech 2/EM → culture/HR. Off-campus intern: screen → take-home → long technical → culture. End-to-end often 1-3 weeks.
How many rounds are there in Groww interview?
Usually 3-4 after you are shortlisted. Assignment-track roles may look like 3. Trust the mailer.
Can I download Groww placement papers PDF?
Yes. Free PDFs and 2024-2026 style sets on this site. Start with the 2026 PDF. No registration. They train themes, not tomorrow’s live OA.
What does the Groww OA look like?
Candidate-reported campus OAs: 2-3 LeetCode-medium problems, 60-90 minutes. Off-campus intern may skip OA for an assignment.
Eligibility & offer
What is Groww eligibility criteria for freshers 2026?
Commonly 7.0+ CGPA on campus lists, computing degree, no active backlogs, Bengaluru joining. Off-campus intern JDs emphasise projects. Your notice wins.
What is Groww salary for freshers?
Reported SDE-1 ₹15-28 LPA (wide, equity-sensitive). Intern stipends often ₹50-80k/month. Written offer only.
Do I have to relocate to Bengaluru?
For almost every engineering fresher story, yes. Say so in HR before you waste both sides’ time.
Prep & Groww-specific
How to prepare for Groww?
Campus: medium DSA + mocks + CS fundamentals. Intern: assignment quality + stack depth + enough DSA to not freeze. Details: preparation guide.
What languages can I use?
OA: typically Java, C++, Python, JS/TS. Interviews then follow team stack (Kotlin, React/TS, Java/Python backend).
Groww vs Zerodha vs PhonePe?
Groww = consumer investing product + intern funnel. Zerodha = broker culture, fewer classic SDE campus seats. PhonePe = payments scale, heavier design/DSA at many levels. Compare Zerodha · PhonePe · Razorpay.
Is a take-home assignment common?
Yes for many off-campus web/RN intern roles. Treat it as the exam. Campus SDE more often uses OA.
Will they ask system design?
Intern/EM rounds may ask concepts (caching, idempotency, WebSockets) more than a 45-minute HLD. RN loops have asked LLD-style socket managers.
Any pro tip for Groww?
Campus: two full OA ACs beat a heroic third fail. Intern: demo video + be ready to rebuild the assignment’s hardest module live. Why Groww needs a real product detail (orders, SIPs, watchlists).
Where can I read real experiences?
Groww interview experience plus public intern write-ups (GfG, LinkedIn). Maps, not scripts.
Does a referral skip the OA?
Referrals and hackathon HR contacts improve screen speed. Campus OA and intern assignments still happen. Prepare as if nobody referred you.
Intern PPO - is conversion automatic?
No. Conversion is performance-based in every story students tell. Treat the internship as a six-month interview: ship, ask for feedback, keep DSA from rotting if FTE conversion has a coding loop.
Groww - recent candidate experiences
Off-campus SDE intern - assignment then 90 minutes
A GfG web-intern story: hackathon HR contact → take-home → next-day interview with two senior SDEs on web fundamentals + assignment (~90 minutes, described as tough JS) → culture fit (journey, Why Groww, app vs web, what you do when stuck) → select after a few days. Steal the lesson: read Groww’s TS migration story so you can ask a real question at the end.
Off-campus SDE intern - 3-day OA loop
A LinkedIn note (6-month intern): OA with 3 mediums (all solved) → 1 hour Tech (2 mediums + internship → backend/SQL/OS/OOP) → 1 hour EM (resume, design concepts, one DSA) → done in three days. Steal: keep DSA hot even when you “already cleared OA.”
React native intern - assignment + ts DSA + redux machine coding
2025-2026 RN posts describe APK + demo video, then TypeScript DSA with complexity grilling, then RN/JS output questions, then managerial. People stall on Redux-from-scratch and multi-WebSocket LLD. If that is your track, practise those two on a weekend, not the night before.
After OA / assignment - 48-hour plan: two mediums, rewrite assignment notes, one Why Groww out loud, sleep.
What selected intern profiles usually show: two OA mediums or a demo that does not crash, one internship or project with a metric, and a Why Groww answer that names a surface (orders, SIPs, watchlists) instead of “fintech unicorn.” Empty GitHub with a 9.2 CGPA still dies on live JS output questions.
What hurt people in 2025-2026 write-ups: assignment submitted without empty-state handling; could not rebuild Redux/store; DSA in TypeScript after only practising Java; refusing Bengaluru in the last round; treating culture fit as “chill HR” and having no story for getting unstuck.
Experience story bank
| Story type | Prompt | Metric |
|---|---|---|
| Ownership | Feature you shipped | Latency, crash-free sessions, users |
| Bug | Production or demo break | Time to detect → fix |
| Trade-off | REST vs websocket, SQL vs cache | What you measured |
| Ambiguity | Unclear intern spec | How you scoped |
| Unstuck | How you debug without a senior | What you read / tried |
If a story has no number, it is not ready for the EM.
Mini OA drill
Prompt: Given a stream of trade events (userId, ts, value), return the top-K users by traded value in the last W minutes.
- Clarify late events and ties.
- Brute: filter window, aggregate, sort.
- Better: sliding window + hash + heap of size K.
- Edges: empty stream, K > uniques, duplicate event ids.
- Say complexity before coding.
Speak the plan in 60 seconds, then timebox 25 minutes. That transfer skill matters more than memorising a PDF story.
After you clear OA or submit the assignment
- Two timed mediums every other day - protect trees/graphs/hashing.
- Rewrite internship schema / RN architecture on paper.
- 90-second Why Groww + Bengaluru.
- If RN/web: re-implement the assignment’s hardest module once.
- Sleep.
Do not start a new framework the night before Tech 1.
More: Groww interview experience.