Academic snapshot
Marks: 7.0+ CGPA / 70% (when listed)
Degree: B.Tech/B.E./M.Tech/MCA CS/IT/ECE/related
Year: Final year + recent grads (~1-2 years)
Backlogs: None active preferred
SAP Placement Papers 2026
SAP is the global leader in enterprise ERP and business applications, founded in 1972. It builds cloud ERP, analytics, and industry solutions used by large enterprises worldwide. Major India engineering hubs in Bengaluru, Pune, and Gurugram make SAP a strong campus recruiter for software and cloud roles.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
SAP eligibility & CGPA (2026)
SAP Labs hires like an enterprise product shop, not a mass IT services drill. The printed CGPA floor gets you into the funnel; the 90-minute coding OA and SQL-heavy technicals decide whether you see an offer.
Who this hub is for
- For: Final-year and early-career engineers targeting Developer / Associate Developer / Software Engineer roles on cloud ERP, analytics, and platform teams.
- Not the same bar: Pure sales, consulting delivery without coding, or support-only roles - different funnels entirely.
- Scholar paths: Some SAP Labs Scholar drives open to BCA and related degrees - still expect coding + SQL depth.
Degree, CGPA, and branch reality
| Item | Typical expectation (candidate-reported) | Reality check |
|---|---|---|
| CGPA / % | 7.0+ CGPA or 70% in 10th, 12th, graduation when listed | Higher GPA helps resume screen; OA still decides |
| Degree | B.Tech / B.E. / M.Tech / MCA in CS, IT, ECE, or related | Scholar tracks may list broader degrees |
| Backlogs | None active at application / joining | Clear before offer paperwork |
| Experience | Freshers and ~0-2 years | Intern / Scholar conversion also appears |
| Languages | Java, Python, C++ | ABAP is a plus, not an OA prerequisite |
| SQL | Expected in technicals | Skipping SQL is a common fail mode |
Is 7.0 enough? It matches the commonly reported floor. A 7.1 with clean timed coding and crisp join explanations beats an 8.8 that freezes on graphs or indexes. Treat CGPA as a gate, not a scoreboard.
Skills bar
Primary filter: Medium DSA under time
Interview differentiator: SQL + enterprise design
Languages: Java, Python, C++ (ABAP plus)
Hubs: Bengaluru, Pune, Gurugram
Who usually fits and who struggles
Good fit: You can finish two medium coding problems cleanly, write a multi-join SQL query without panic, and explain one project’s data model for 15 minutes. Comfort relocating to Bengaluru, Pune, or Gurugram helps.
Harder path: You only practiced aptitude MCQs; you skip SQL because “coding companies don’t ask DB”; you cannot explain normalization or indexes. SAP’s OA is not Infosys-scale aptitude - it is a coding filter with a database follow-up.
Campus shortlists vs off-campus reality
SAP Labs campus volume is selective. Some colleges see Scholar or Developer drives; many students enter through careers or referrals:
- Fewer seats means OA cutoffs feel harsher even when problems look “fair.”
- Referrals improve resume visibility; they do not soften Codility hidden tests.
- Scholar programs may widen degree eligibility without lowering DSA expectations.
If your college does not have SAP on the calendar, start a careers + referral plan early.
Campus JD checklist before you apply
Print or screenshot your placement notice and tick:
- Exact CGPA / percentage floors for 10th, 12th, graduation
- Branch list and whether MCA / dual degree is included
- Backlog policy at application vs joining
- Bond, service agreement, or training clauses if any
- Role title (Developer vs Scholar vs Associate) - titles change CTC chatter
If any line is missing, ask your placement cell in writing. Guessing from a senior’s 2024 WhatsApp forward is how people get rejected at documentation.
Why SQL weight surprises DSA-only grinders
SAP product work is data-shaped. Interviewers use SQL as a proxy for:
- Whether you can reason about grain (one row per order vs per line item)
- Whether you understand constraints (unique keys, null handling)
- Whether you can connect a business question to a query plan at fresher depth
You do not need DBA-level tuning. You do need to write a correct multi-join query and explain an index choice in plain English. Schedule SQL like a subject, not a footnote.
Building ERP intuition without an abap internship
You do not need ABAP certification to clear Round 2. You do need enterprise vocabulary backed by diagrams:
- Pick one business flow (order-to-cash or procure-to-pay) and sketch entities
- Map where a multi-tenant SaaS module would store tenant data
- List three failure modes (partial order update, reporting lag, auth mismatch)
- Propose one SQL index or cache that would help
Do this once a week for a month. Interviewers can tell the difference between someone who memorized “S/4HANA” as a buzzword and someone who thought about enterprise data.
Coding + SQL themes mapped to SAP
| Theme | Why SAP-like loops use it | Cousin drills |
|---|---|---|
| Arrays / strings | OA stamina | Two pointers, sliding window |
| Trees / graphs | Live coding | BFS/DFS, LCA |
| DP | Medium OA problems | LIS, knapsack light |
| SQL joins / subqueries | Technical 1 | Multi-table reporting queries |
| Indexing / normalization | Schema talk | Explain EXPLAIN plans at fresher depth |
After every mock miss, pull cousins from coding questions and rewrite one SQL query from scratch.
Behavioral signals SAP interviewers notice
- Clarity when explaining trade-offs in enterprise systems
- Data thinking - keys, constraints, consistency
- Ownership on projects without buzzword soup
- Relocation honesty for India hub cities
Offer-stage checks
- Confirm city (Bengaluru / Pune / Gurugram) and hybrid norms in writing
- Read stock / bonus components carefully
- Do not resign until the written SAP letter lands
- Background verification expects consistent CGPA dates
SAP previous year papers & PDFs
Download 2026 SAP placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Comments & Suggestions
What SAP previous year papers actually train
SAP does not publish a permanent official paper bank. Sets on this site are pattern trainers for the OA and early technical rounds - not leaked live assessments. Full archive: previous year question papers.
| Round (typical) | What to practice |
|---|---|
| Online coding | 90-min stamina on 2-3 medium DSA problems |
| Technical 1 | Live DSA narration + SQL joins / schema |
| Technical 2 | Enterprise design: multi-tenant SaaS, reporting pipelines, order flows |
| HR | Why SAP?, relocation, career goals |
Themes that keep repeating (2024-2026)
- 2024: Arrays/strings and tree problems on OA; interviews already probing SQL heavily. Students who only did LeetCode and ignored joins stalled in Round 1.
- 2025: More notes stress clean code + SQL depth together. Design chats lean toward cloud ERP modules and scalable reporting. Scholar write-ups still show four-round shapes.
- 2026 prep expectation: Keep medium DSA warm; budget real weekly time for SQL; learn enough ERP vocabulary to talk about business objects without faking ABAP fluency.
How to use one paper set in a sitting
- Timed: 90 minutes, 2-3 coding problems, same language as test day.
- Untimed review: rewrite cleaner solutions; list edges you missed.
- Spend 20 minutes on two SQL problems (joins + aggregation).
- Sketch one order-to-cash or multi-tenant module aloud for 15 minutes.
- Log one STAR story the session reminded you of.
SAP hiring rounds in 2026
SAP Labs hires through campus, careers portal, and referrals. Campus volume clusters in placement season; off-campus runs more continuously. Same technical bar either way.
How to apply
Campus
Placement cell PPT → resumes → online coding → virtual/onsite interviews.
Direct apply
SAP Careers with resume. Resume screen then OA invite when roles are open.
Scholar / referral
Scholar programs and referrals can widen the path; coding + SQL bar remains.
Round-by-round walkthrough
-
Online Coding Round - ~90 minutes
Section Questions Time Difficulty Focus Coding 2-3 90 min Medium Arrays, strings, trees, graphs, DP Platform is often HackerRank or Codility. No negative marking. Aim to solve at least two problems with acceptable complexity. Languages: Java, Python, C++.
Time boxing: lock one sure problem first, then the second for a clear bar, then attempt the third.
-
Technical Interview 1 - ~60 minutes
Live DSA plus SQL: joins, subqueries, indexing, schema design, and project questions. Interviewers watch approach narration and data thinking. Roughly 40-50% of OA survivors advance in student reports.
-
Technical Interview 2 - ~60 minutes
System design / ERP / cloud concepts and deeper project discussion: multi-tenant modules, reporting pipelines, scalability. About 50-60% of Round 1 survivors move on in many write-ups.
-
HR - ~30 minutes
Motivation, Why SAP?, relocation to Bengaluru/Pune/Gurugram, compensation discussion. Most candidates who reach HR with clean prior rounds receive offers if logistics and integrity checks pass.
Timeline from application to offer
| Phase | Duration | What happens |
|---|---|---|
| Application & screening | 3-5 days | Resume review |
| Online coding | 1 day | Assessment + evaluation |
| Technical interviews | 5-7 days | Round 1 + Round 2 |
| HR | 1-2 days | Offer discussion |
| Result | 2-3 days | Offer letter / onboarding |
Total: often 2-3 weeks once you are actively in process.
What interviewers listen for
- OA: Correctness first, then complexity.
- SQL: Correct joins, awareness of indexes, clear schema reasoning.
- Design: Business objects and data flow - not buzzword clouds.
- Projects: Metrics and trade-offs.
SQL round: what “good” sounds like
Weak answer: “I know SELECT * FROM table.”
Stronger answer: “I’d join orders to customers on customer_id, filter last 30 days, aggregate revenue by region, and index (order_date, region_id) if that query is hot - here’s the trade-off on write cost.”
Practice aloud. Silence while writing SQL is fine; silence when asked why an index helps is not.
Managerial / HR language that works at SAP
Enterprise interviewers dislike empty “I love technology” answers. Prefer:
- “I want to build systems where a wrong update has financial impact - that’s why I care about constraints and testing.”
- “In my project we had duplicate rows because of missing unique keys; here’s how we fixed it.”
- “I’m open to Bengaluru / Pune / Gurugram; my constraint is X.”
Honesty about location beats a fake “anywhere” that collapses after offer.
Codility / HackerRank day logistics
- Stable power + wired internet if possible
- Close Slack/WhatsApp; proctoring flags matter
- Use the language you practiced, not the one your friend prefers
- Submit only after a quick mental edge pass: empty input, single element, large N
Comparing SAP to other enterprise prep
| Company vibe | Prep you can reuse | What to add for SAP |
|---|---|---|
| Oracle | SQL + DSA | ERP business-flow vocabulary |
| ServiceNow | SaaS design | Deeper SQL + ERP objects |
| Microsoft | Medium DSA | Enterprise data modeling talk |
Study resources on this site
- Online assessment for format notes
- Coding questions for theme cousins
- Interview experience for round flavor
- Preparation guide for longer week plans
- Year pages (2024, 2025, 2026)
Download the 2026 PDF for offline timed runs.
Preparation resources for SAP
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 SAP drive
If a SAP 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 SAP sits around ₹18-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): SAP eligibility for freshers 2026 (from student reports): typically 7.0+ CGPA or 70% in 10th, 12th, and graduation; B.Tech/B.E./M.Tech/MCA in CS, IT, ECE, or related; final-year students and recent grads (within ~1-2 years); no active backlogs. Strong coding plus SQL/database depth helps after the academic gate. SAP does not publish one universal cutoff - verify on Careers or your campus JD.
What you are training for: Typical SAP Labs loop: Online Coding Round (90 min, 2-3 DSA problems on HackerRank/Codility) → Technical Interview 1 (DSA + SQL, ~60 min) → Technical Interview 2 (system design / ERP / projects, ~60 min) → HR (~30 min). End-to-end often 2-3 weeks. Scholar and some campus tracks may tweak round names but keep the same skills bar.
Short version of the prep split: Split time roughly: DSA ~40%, SQL/databases/ERP basics ~25%, system design ~20%, timed coding mocks ~10%, projects/HR ~5%. Drill medium DSA; practice joins, indexing, and schema design; sketch multi-tenant SaaS / order-to-cash style flows aloud.
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 SAP 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 SAP 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 SAP 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 SAP?” 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 SAP-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 SAP story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
Common ways students waste a month
- Collecting 12 SAP 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 SAP 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 SAP papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in SAP-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 SAP 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 SAP. 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 SAP, 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 SAP mistakes, you are collecting content, not preparing.
Extra drill block (1)
Sit one more mixed SAP 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.
SAP compensation & benefits
Figures below are candidate-reported as of August 2026. Treat them as bands, not offer letters. Location (Bengaluru, Gurugram, Pune) and role shift totals.
Software roles
| Level | Experience | Total package | Typical background |
|---|---|---|---|
| Software Engineer / Developer | 0-1 years | ₹18-28 LPA | Strong DSA + SQL freshers |
| Senior Software Engineer | 2-3 years | ₹30-45 LPA | Ownership + design depth |
| Associate / Scholar tracks | Entry | Often overlaps lower end of SE band | Confirm JD role title |
Benefits candidates care about
Health cover, learning budget, stock/bonus components where offered, hybrid norms on many teams. Read the offer letter - do not negotiate from blog averages alone.
Location and culture questions
- Willing to relocate to Bengaluru / Pune / Gurugram?
- Interest in enterprise software vs consumer apps?
- Example of debugging a data issue end-to-end?
How to read an SAP offer letter
- Split fixed, variable, and stock/bonus
- Note probation and variable payout conditions
- Confirm joining location and any relocation support
- Compare against Oracle / ServiceNow offers on the same calendar week, not LinkedIn flex posts
- Ask HR clarifying questions in email so you have a paper trail
Final 72 hours
| Time | Do | Do not |
|---|---|---|
| T-72h | One light mock + SQL drill | Start a new ABAP course |
| T-48h | Project rehearsal aloud | Sleep debt |
| T-24h | Error-log skim + Why SAP? | Caffeine experiment |
| Morning | ID, charger, water | New LeetCode hard |
Deep dive: what “SAP-aware design” means for freshers
When Round 2 asks you to design a module, they are not expecting a staff engineer’s multi-region saga. They want to see:
- Actors - customer, employee, admin, integration system
- Core objects - order, invoice, material, tenant
- Operations - create, update, approve, post
- Data store choices - transactional DB vs analytics store
- Failure modes - partial update, duplicate post, late message
Practice one 45-minute whiteboard on “design an invoice posting service for multiple companies (tenants).” Speak in sentences. Draw boxes. Name one metric (posting lag, error rate). That is fresher-passing design at SAP.
Parallel prep if you are also sitting Oracle
| Shared | SAP-specific add-on |
|---|---|
| Medium DSA OA stamina | Business-flow vocabulary (order-to-cash) |
| SQL joins / indexes | Multi-tenant + ERP module talk |
| Project defense | Why enterprise software (not only “scale”) |
Do not maintain two completely separate prep worlds. One DSA error log, one SQL notebook, two Why-company stories.
Documents folder to keep ready
- Marksheets (10th, 12th, all semesters)
- ID proof and address proof
- Updated resume PDF (one page preferred for freshers)
- Internship certificates if claimed on resume
- Passport-size photo digital copy
Offer delays often come from missing paperwork, not from HR drama.
Sample technical follow-ups you should rehearse
- How would you detect duplicate payments in a ledger table?
- What index would you add for “orders by customer in last 30 days,” and what is the write cost?
- Explain ACID in one minute with an order-update example.
- Your OA solution is O(n^2) - how would you improve it, and when is O(n^2) acceptable?
Answer out loud. Written notes that you cannot speak will not help in a 60-minute technical.
Recent SAP placement trends
Hiring shape 2026
Engineering hiring continues across cloud ERP, platform, and analytics teams in India hubs.
Process notes
Coding OA + SQL-heavy technicals remain the core bar. Scholar paths widen degree eligibility, not the skills filter.
Company context
Bengaluru, Pune, and Gurugram stay primary. Confirm live openings on Careers before assuming campus volume.
Prep implication
Double down on timed medium DSA and weekly SQL - do not wait for a “new pattern” rumor.
Common questions about SAP hiring
Papers & downloads
Can I download SAP placement papers PDF?
Yes. Free SAP placement papers PDF with previous-year style coding, DSA, SQL, and ERP design themes are on this site - no registration. Start with the 2026 PDF and year pages. Papers train patterns; they are not guaranteed clones of your live OA.
Process & rounds
What is the SAP placement process?
Typical loop: Online Coding (90 min, 2-3 DSA) → Technical 1 (DSA + SQL, ~60 min) → Technical 2 (design / ERP / projects, ~60 min) → HR (~30 min). End-to-end often 2-3 weeks.
How many rounds are there in SAP interview?
About four core stages for many fresher Developer tracks. Scholar or managerial variants may add a behavioral chat.
What is SAP exam pattern 2026?
Usually ~90 minutes, 2-3 medium coding problems, arrays/strings/trees/graphs/DP, on HackerRank/Codility, no negative marking. Aim for at least two solid solutions.
Does SAP ask SQL in interviews?
Yes. Technical Round 1 commonly mixes live DSA with SQL joins, subqueries, indexing, and schema design. Skipping SQL is a frequent fail mode.
SAP Labs Scholar vs Developer - what changes?
Scholar tracks may widen degree eligibility (including some BCA paths) but still run coding + technicals + HR. Read your notice; do not assume a softer DSA bar.
Interview content
What questions are asked in SAP technical interview?
Live DSA; SQL and database design; system/ERP design; project deep-dives; HR motivation. Interviewers watch narration and data thinking as much as the final answer.
Eligibility & languages
What is SAP eligibility criteria for freshers 2026?
From student reports: 7.0+ CGPA / 70% when listed; B.Tech/B.E./M.Tech/MCA in CS/IT/ECE/related; final-year or recent grads; no active backlogs. Verify your JD.
What programming languages are allowed in SAP?
Java, Python, or C++ for coding. ABAP is a plus for some teams. SQL is tested in interviews separately.
Are backlogs allowed at SAP?
Active backlogs are the usual blocker. Cleared historical backlogs are generally fine if the notice does not say otherwise.
Salary & comparison
What is SAP salary for freshers in 2026?
Candidate-reported: Software Engineer ~₹18-28 LPA; Senior ~₹30-45 LPA (2-3 YOE). Confirm written offers; city and role move bands.
SAP vs Oracle vs ServiceNow - which is better?
SAP - enterprise ERP / business apps. Oracle - databases and enterprise cloud. ServiceNow - workflow/ITSM SaaS. Overlapping CTC chatter - choose on domain and city.
Prep tip
How to prepare for SAP placement?
Rough split: DSA 40%, SQL/ERP 25%, design 20%, timed mocks 10%, projects/HR 5%. Weekly OA simulations + aloud SQL practice beat passive videos.
Any pro tip for SAP placement preparation?
Budget real time for SQL and enterprise data talk. Clean DSA plus crisp join explanations beats memorizing ABAP keywords you will not use on OA day.
Is relocation required for SAP India roles?
Most fresher engineering offers assume Bengaluru, Pune, or Gurugram. HR will check willingness - answer honestly.
Do I need ABAP before applying?
No for most fresher OA clears. ABAP helps some product conversations later. Prioritize DSA + SQL first; add ABAP basics only after those are solid.
Is 7 CGPA good for SAP?
Yes - it meets the commonly reported floor. Selection still depends on OA and SQL/interview performance. An 8.5 with weak SQL is not safer than a 7.1 with strong timed coding.
Real SAP interview notes from candidates
A SAP Labs Scholar select (BCA, September 2025 on-campus) outlined four rounds - coding, two tech, then HR/managerial - on GeeksforGeeks. Takeaway: Scholar branding changes the program name, not the need for clean coding and database fluency.
Across 2024-2026 write-ups, the same failure modes repeat:
- OA incomplete - one perfect solution and two empty editors
- SQL freeze - candidate can talk normalization theory but cannot write a join under time
- Project vagueness - “we used MySQL” without schema or trade-offs
- Location surprise - rejecting Gurugram/Pune after clearing technicals wastes a seat
If you are targeting SAP alongside Oracle or ServiceNow, reuse DSA mocks ruthlessly but keep a dedicated SQL night twice a week. Enterprise loops punish the “I’ll learn databases after I get the offer” plan.
Students repeatedly note that SQL shows up even when the OA was pure DSA - prepare both. Relocation questions for Bengaluru/Pune/Gurugram appear late in the loop; decide your answer before HR day, not during it.
Night-before checklist
- Laptop charged; backup hotspot tested
- Language template ready (fast I/O only if you truly need it)
- Two STAR stories rehearsed once each - not ten times until they sound fake
- City preference sentence prepared
- Sleep by a fixed time; set two alarms
SAP loops reward steady students. Cramming a new DP pattern at 2 a.m. rarely moves the offer needle.
After a reject: what to change in 14 days
- Re-read feedback if any (edge cases? SQL? communication?)
- Run three timed OAs and two SQL sessions
- Rebuild one project explanation with metrics
- Re-apply via careers/referral only after those reps - not the next morning
A reject is data. Ignoring it and spamming applications is how the same miss repeats.
One-week intensive if the drive is sudden
If you get only seven days notice:
| Day | Plan |
|---|---|
| 1 | Two timed mediums + SQL joins night |
| 2 | Full 90-min OA mock + error log |
| 3 | Graphs/trees weak spots only |
| 4 | SQL schema + one ERP sketch aloud |
| 5 | Peer live coding + Why SAP? |
| 6 | Light mock + project rehearsal |
| 7 | Sleep, documents, logistics |
Do not start a new textbook. Protect mocks and SQL. Sudden drives punish unfocused panic more than low CGPA alone today.
If you’re also targeting…
Oracle · Salesforce · ServiceNow · IBM · Microsoft · Adobe