Intuit is a global financial software company known for QuickBooks, TurboTax, and related products.
Explore: Online Assessment · Coding Questions · Interview Experience · Preparation Guide · Certifications & Career · Download PDF
Intuit is a product-engineering bar. Clearing the printed CGPA floor only gets you into the funnel - the HackerRank-style OA (and Build Challenge on some paths) decide offers.
Academic requirements
Marks: Typically 7.5+ CGPA or 75% throughout when the JD lists all levels
Degree: B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields
Year of Study: Final-year students and recent graduates
Backlogs: No active backlogs (offer-stage verification is common)
Branch & skills
Eligible Branches: CS, IT, ECE, EE, or related streams
Programming: Strong C++, Java, or Python under time pressure
Design preference: Fresher system-design intuition helps Round 2
Minimum CGPA required (candidate-reported): 7.5+ CGPA or 75% throughout. Treat this as a shortlisting floor - Intuit still filters heavily on assessment and interview performance. Always verify on your drive notice or careers portal. Criteria chatter for 2025 and 2026 is the same band.
| Academic Level | Typical floor (candidate-reported) | Notes |
|---|---|---|
| Graduation | 7.5+ CGPA or 75% throughout | Confirm on campus JD / careers post |
| 10th / 12th | Often aligned when the JD lists all three | Consistency across years matters |
| Backlogs | Usually none active at joining | Offer-stage verification |
What that means day to day: an 8.4 CGPA who cannot finish two medium-hard problems in 90 minutes loses to a 7.6 who ships correct solutions with edge cases. Intuit’s brand looks “fintech productivity,” but the fresher SWE loop is still coding + design (+ build on many off-campus paths).
Good fit: You already solve LeetCode mediums under a timer, you can narrate trade-offs on a simple distributed design, and you have 1-2 projects with real metrics. Off-campus candidates who can ship a small OOP app with DB + tests in a few hours have a clear edge.
Harder path: You only practiced untimed problems; you freeze on “why this data structure?”; your system-design prep is buzzwords without bottlenecks; you have never written unit tests for a personal project.
Branch myth: ECE/EE students clear Intuit when DSA is real. Branch does not replace coding ability.
Locations: Bangalore dominates India engineering chatter. Be honest early if you cannot relocate.
Backlogs and gaps: active backlogs are the usual hard stop. Unexplained multi-year gaps invite questions - prepare a one-sentence ownership answer.
Off-campus reality check: Careers applications without a referral can sit longer, but strong 2025 write-ups show NIT candidates clearing multi-stage paths without referrals. A tight resume with defensible projects beats generic “passionate about fintech” summaries. Referrals help visibility; they do not lower the OA/build bar.
Intern convert path: Intuit internship performance can convert to full-time when headcount exists. Conversion is not automatic - treat the internship like a long interview with real code review standards. If you are targeting convert, ask your mentor early what “hire bar” looks like on that team.
Resume bullets that survive Intuit screens: prefer “built X that processed Y transactions with Z% error rate” over “worked on backend.” List languages you can debug live. Do not claim Kafka/Kubernetes unless you can defend them in Round 2. For Build Challenge paths, a GitHub that matches bullets helps more than a decorative portfolio site.
Download 2026 Intuit placement papers
2026 pattern in detail
2025 placement papers
2024 placement papers
Previous year question papers
Intuit does not publish one permanent “official paper.” Previous-year style packs on placementpapers.app train the timed DSA OA and early technical rounds - medium-hard arrays/strings/trees/graphs/DP - plus enough design flavor for Round 2. Think of papers as simulators for 90-minute stamina, not a question bank to memorize.
| Round (typical) | What to practice |
|---|---|
| Online coding OA | Timed DSA (+ SQL/Bash on some papers) |
| Technical 1 | Live coding + complexity + edge cases |
| Technical 2 | Light system design + project depth |
| Build Challenge | Shipping + defending a small app (off-campus) |
| HR / Craft | Values, motivation, location |
How to use a paper: time a full 90-minute block; mark every problem you guessed; rewrite any solution that would fail hidden tests; spend 20 minutes listing which pattern you missed. Three reviewed papers beat ten skimmed ones.
Year-page cheat sheet:
| Year pack | Use it for | Skip if… |
|---|---|---|
| 2024 | Baseline OA themes | Only 3 days left - jump to timed PDF |
| 2025 | Newer mixes, pattern notes | You have not finished one full timed mock |
| 2026 | Expected pattern + study framing | Still weak on arrays/hashing basics |
2024 vibe: coding OA → DSA tech → design tech → HR; clear rates after coding often cited ~25-35%; packages in ₹30-40 LPA chatter. 2025-2026 vibe: same campus skeleton; off-campus adds build-and-defend stages. Prep implication: do not chase a mythical “AI-only paper” - keep DSA sharp, add one AI-assist design talking point, and practice shipping if your path includes a Build Challenge.
What to practice: timed DSA stamina, triage habits, and the vocabulary of later design rounds. What they do not: guarantee identical HackerRank IDs or replace a Build Challenge rehearsal. Students who only read editorials without typing solutions under a clock still fail hidden tests. Keep an error log with pattern tags (“window invariant”, “graph coloring”, “SQL group-by miss”).
Hackathon / hiring-challenge overlap: some Intuit India outreach looks like timed DSA sets similar to the OA bank. Treat challenge and OA prep as the same DSA core unless your brief is explicitly “build a feature.”
Intuit runs campus drives at selected colleges and off-campus / Careers applications year-round. The bar is product-SWE either way - but off-campus schedules can look very different from the four-round campus summary.
Campus recruitment
Placement cell PPT → resume shortlist → OA → interviews (virtual or onsite).
Intuit careers / off-campus
Apply on careers.intuit.com for SDE-1. Resume screen → HackerRank → multi-stage loop.
Referrals
Referrals improve visibility; OA and Build Challenge bars stay the same.
Resume / campus shortlist (days to ~2 weeks)
CGPA floors, projects, internship signals. Put measurable product work on the resume - “built expense categorizer with X% accuracy” beats “interested in TurboTax.”
Online Coding Round (~90 minutes)
Typical: 2-3 coding questions · Format: online proctored (HackerRank commonly reported) · Languages: C++, Java, Python · Some papers add SQL + Bash.
| Focus | Example themes from candidate reports |
|---|---|
| Arrays / hashing | Subarray sums, frequency maps, two pointers |
| Strings | Windows, parsing, anagrams |
| Trees / graphs | Traversals, shortest path on unweighted graphs |
| DP | Medium 1D/2D DP |
| SQL / Bash | Joins, filters, simple shell tasks (when included) |
Clear rates after coding-first OAs are often cited around ~25-35%. Triage first; bank a solvable medium; custom tests before submit.
Technical Interview Round 1 (~60 minutes)
Live DSA on shared doc: arrays, strings, trees, graphs, DP. Interviewers watch approach, edge cases, and complexity narration. Success among OA survivors often cited ~50-60%.
Technical Interview Round 2 (~60 minutes)
System design + project deep-dive. Topics: scalability, caching, microservices, APIs - often tied to financial workflows. About ~60-70% of Round-1 survivors advance in many reports.
Fresher design bar: actors, data model, bottleneck, one scaling lever. You do not need to invent QuickBooks’ entire cloud.
HR Interview (~30 minutes)
Motivation, Why Intuit?, teamwork, Bangalore location, career goals. Around ~80-90% of tech-clear candidates get offers when logistics are sorted.
Several 2025-2026 SDE-1 write-ups describe a longer path:
If your invite mentions a Build Challenge, treat LeetCode-only prep as incomplete.
| Phase | Duration | Key activities |
|---|---|---|
| Application / shortlist | 1-14 days | Campus cell or Intuit Careers |
| Online Coding Round | ~1 week window | Invite + 90-minute assessment |
| Technical / Build stages | ~1-3 weeks | Interviews and/or Build Challenge |
| HR / manager | 2-5 days | Fit, location, Role Sell |
| Result / offer | 3-5 days | Offer letter |
Total: usually 2-3 weeks for compact campus loops; off-campus multi-stage paths can stretch longer.
Most rejection stories after a green OA sound the same: “I could code, but design felt vague” or “I built something but could not explain trade-offs.” Intuit Round 2 is not asking you to invent TurboTax. It is asking whether you can reason about users, data, and scale for twenty minutes without collapsing into buzzwords. Practice with a friend who interrupts every time you say “we’ll use microservices” without naming the pain those services solve.
If your path includes a Build Challenge, under-prep looks different: incomplete README, no tests, god-class design, and inability to justify schema choices. Rehearse shipping a tiny CRUD + auth + one non-trivial rule (e.g., category mapping) with unit tests under a 3-hour timer at least twice before the real invite.
Campus short window:
Off-campus Build path:
You do not need Intuit product certifications for SDE-1. You do need enough product awareness to sound specific:
Pick one line and prepare a 30-second engineering angle (reconciliation, idempotent payments, document parsing, permission models).
Practice aloud with a timer (25-35 minutes):
For each: requirements, 4-6 boxes, first bottleneck, one scaling lever, one failure mode.
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 Intuit invite is 3-8 weeks out, treat this hub as the map and the nested 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 Intuit sits around ₹30-40 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): Intuit eligibility for freshers 2026 (candidate-reported): typically 7.5+ CGPA or 75% throughout; B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields; final-year students and recent graduates; no active backlogs. Strong timed DSA and defensible projects matter as much as the academic floor. Always verify your campus JD or Intuit Careers posting.
What you are training for: Classic campus-style Intuit loops often run: Online Coding Round (~90 minutes, 2-3 DSA) → Technical Interview 1 (~60 minutes) → Technical Interview 2 (~60 minutes, system design + projects) → HR (~30 minutes). Off-campus SDE-1 paths can stretch into HackerRank (DSA + SQL + Bash), recruiter screen, Build Challenge, defense, Craft Demo, and hiring-manager calls. Follow your invite.
Short version of the prep split: Split prep roughly: DSA ~45%, system design ~25%, timed coding mocks ~20%, CS fundamentals ~5%, interview/HR ~5%. Aim for 300+ medium-hard problems, weekly 90-minute mocks, and finance-flavored design prompts. If targeting off-campus, also practice SQL, Bash, OOP design, and a multi-hour build.
Week 1 - pattern, not vibes. Oa pattern first: sit one untimed paper, then redo it under the real clock. Open the Intuit 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 Intuit 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 Intuit 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 Intuit?” 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 Intuit-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 Intuit story (eligibility, rounds, salary). Use those pages for reps. If a card 404s on your campus mirror, the explore links at the top of this page are the same destinations.
If you do one thing after reading this: schedule three timed Intuit papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Intuit papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Intuit-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Intuit 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 Intuit. 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 Intuit, 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 Intuit mistakes, you are collecting content, not preparing.
Figures below are candidate-reported as of August 2026. Treat them as ranges, not offer letters.
| Level | Experience | Base (approx.) | Total Package | Typical background |
|---|---|---|---|---|
| Software Engineer | Fresher | ₹30-35 LPA | ₹30-40 LPA | Engineering graduates |
| Senior Software Engineer | 2-3 years | ₹40-55 LPA | ₹45-65 LPA | Relevant experience |
Health coverage, stock / ESPP components, professional development, flexible arrangements (team-dependent), global collaboration, and financial planning perks. Bangalore living costs still matter - HR will discuss location explicitly.
How to read the fresher band: ₹30-40 LPA is the Software Engineer range students most often cite for Intuit India. Exact CTC splits (base vs bonus vs RSU) vary by offer letter.
Growth students ask about: SWE → Senior → staff-level tracks vary by org. Product breadth (QuickBooks, TurboTax, AI assist) is a real talking point - if you care about small-business workflows vs consumer tax filing, say that in your own words.
Location & offer logistics students forget to ask: joining timeline, hybrid expectations for the Bangalore team, equity vesting schedule, and whether the role is platform vs product-feature adjacent. Those details affect day-to-day more than a 2 LPA band debate before the offer exists.
How Intuit pay compares in student chatter: often near strong product-company bands, usually below top-of-market Google chatter, typically above mid-tier SaaS and well above classic service-company packages. Pick the product and team, then read the letter.
Hiring trends 2026
AI-driven features across QuickBooks/TurboTax show up in Why Intuit chat. System design stays a real Round-2 filter. OA remains DSA-first.
Process shape
Virtual interviews common. Off-campus Build Challenge + defense remains a distinctive path vs pure OA loops.
Access paths
Campus + Careers + referrals. Internship convert when available is still a strong path.
Company context
Bangalore engineering footprint; financial domain expertise and AI assist features across the suite.
Net for 2026 prep: do not wait for a new pattern rumor. Double down on timed medium-hard DSA, one polished finance-flavored design, and - if relevant - a shippable mini-build with tests.
Also expect more AI vocabulary in Why Intuit answers - generative assist across QuickBooks/TurboTax shows up in student prep notes. You do not need a research paper; you do need one concrete sentence on how AI assists users without breaking trust, latency, or cost budgets.
Calendar planning tip: if your campus Intuit PPT lands mid-semester with two weeks notice, freeze new topics and run OA mocks + error-log repair only. If you have three months, follow the 8-12 week plans above. Panic-adding system-design courses three days out usually hurts sleep more than it helps Round 2. If Build Challenge is on your mail, protect calendar blocks for two timed mini-builds before the real one.
Yes. Free Intuit placement papers PDF download and previous-year style DSA/coding/interview practice (2024-2026) are on placementpapers.app - no registration. Start with the 2026 PDF. Papers train patterns and timing; they are not leaked live exams.
Classic campus shape: Online Coding (~90 min, 2-3 DSA) → Technical 1 (~60 min) → Technical 2 (~60 min, design + projects) → HR (~30 min). Off-campus can add recruiter screens, Build Challenge, defense, Craft Demo, and hiring-manager rounds. Follow your invite.
Many campus reports cite four core stages. Off-campus 2025-2026 write-ups often describe 5-7 stages. Count your schedule.
Common OA report: ~90 minutes, 2-3 medium-hard DSA on a proctored platform; sometimes SQL + Bash. Later rounds emphasize design and projects. Build Challenge paths evaluate shipping, not only puzzle solving.
A 2-4 hour take-home/build session reported on several off-campus SDE-1 paths: OOP, design patterns, DB integration, unit tests, README - then a technical defense. Prepare to ship and explain, not only to code on LeetCode.
Medium-hard DSA, live coding with complexity talk, project architecture, fresher system design (caching, APIs, scale), CS fundamentals, and behavioral/HR (Why Intuit, teamwork, location).
Often yes in Technical Interview 2. Keep it fresher-depth with financial-domain flavor when possible.
Candidate-reported: typically 7.5+ CGPA or 75%; B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related fields; no active backlogs. Verify your JD. Strong OA still decides advancement.
C++, Java, and Python are common. Some assessments also include SQL and Bash. Do not switch primary languages the week of the drive.
Yes when the JD lists ECE/related fields. You still need the same DSA + design bar as CS peers.
Candidate-reported as of August 2026: Software Engineer roughly ₹30-40 LPA CTC in Bangalore. Offer letter wins over blogs.
Split ~45% DSA, ~25% design, ~20% timed mocks, ~5% CS, ~5% interview/HR - plus Build Challenge rehearsal if your path needs it. Details: preparation guide.
Intuit: financial product craft, design/build emphasis, fresher CTC often ₹30-40 LPA. Google: algorithms + scale, often higher bands in chatter. Microsoft: enterprise/cloud productivity. Choose by product interest and written offer.
Rehearse one finance-flavored design with explicit bottlenecks - and if Build Challenge appears, practice shipping a small app with tests under a clock.
The OA is the steepest drop for many campuses (~25-35% clear rates students cite). Off-campus build stages add another stamina filter. Beatable with deliberate timed DSA + design/build habits - not random easy-problem grinding.
Aim for roughly 300+ reviewed medium-hard problems with an error log - not raw attempts. Weekly timed mocks matter more than vanity counts.
A 2025-batch NIT Kurukshetra SDE-1 hire who applied on careers.intuit.com without a referral described a multi-week, seven-stage path: HackerRank (DSA + SQL + Bash), recruiter 1:1, then “a 2-4 hour Build Challenge requiring OOP, design patterns, database integration, and unit tests,” followed by a technical defense, Craft Demo on Intuit values, and a hiring-manager Role Sell call (PapersAdda). Intuit’s process is less “one OA + loops” and more build-and-defend.
An Intuit SDE-1 candidate posting in March 2026 outlined five stages: a 90-minute coding round (DSA + SQL + Git Bash), an AI-focused recruiter 1:1, a 2-4 hour Build Challenge with README/run configs, a detailed discussion defense of that build, and a final hour on projects/system design/behavioral (LinkedIn). Their takeaway: “It wasn’t just about coding - it was about thinking, building, designing, and adapting with AI in the loop.”
What to steal: expect SQL/Bash alongside DSA on some OAs; budget stamina for multi-hour builds; prepare values/Craft language; treat one LinkedIn post as a vibe check - return to timed mocks on placementpapers.app.
A composite pattern from campus and Careers selects: 90-minute OAs with medium-hard string/window/DP items (sometimes SQL/Bash), then live rounds that reopen trees and project trade-offs - or a Build Challenge that punishes incomplete READMEs. Candidates who failed often admit the same two mistakes - over-investing in the hardest OA problem first, and listing frameworks they could not defend. Candidates who cleared usually sound almost boring: triage early, tests before submit, and one project story with a metric.
Build defense phrases that help: “I chose X schema because…”, “this test fails if…”, “under 10x load I would add…”, “I deferred Y to keep the 3-hour scope honest.” Memorizing buzzwords without those sentences fails the defense even if the demo runs.
If you interview this month: map your invite to campus vs build path, schedule two full OA mocks, and rehearse one finance-flavored design aloud. Execution beats PDF hoarding.
Offer-stage checklist: role title, base vs variable vs equity, Bangalore joining, background-verification docs. Celebrate after the letter is signed.
Practice explaining out loud (20-25 minutes each):
For Build Challenge paths, add a sixth drill: ship a tiny CRUD app with tests in three hours, then defend schema choices without opening the code for the first two minutes.
Offer negotiation reality for freshers: product CTC bands leave some room, but inventing numbers from Telegram groups is a bad strategy. Ask about equity vesting, base vs bonus, Bangalore team hybrid norms, and role scope once you have paper.
Competing offers framing: if you also hold Adobe/Microsoft/fintech offers, compare product craft and team - not only LPA screenshots. Intuit interviewers respond better to “I want to build financial workflows at scale” than brand ranking debates.
Spend four evenings on:
Keep drills short. The goal is OA survival and Build Challenge hygiene, not DBA certification. If your invite is DSA-only, keep SQL light and protect design/build time instead.
