Goldman Sachs is a leading global investment bank and financial services firm serving institutional and corporate clients worldwide. Its India technology teams in Bengaluru and Hyderabad build trading, risk management, and platform systems that support the firm’s global operations.
Explore: Online Assessment · Download PDF · Placement Process · Interview Experience · Preparation Guide · Certifications & Career
Highlight systems thinking: concurrency, performance, data integrity, testing. If you built a trading-simulator hobby project or a low-latency toy, say what you measured. If you only have CRUD apps, still discuss indexing, validation, and failure handling honestly - inventing a high-frequency trading internship you did not do will die in managerial rounds.
Quant clubs, math olympiad history, or statistics coursework can support the OA math half - mention them factually, then still practice probability under a timer.
Final-year and early-grad engineers aiming at Technology Analyst (and nearby software roles) through campus drives or Goldman Sachs careers. If you are targeting pure IBD analyst without a coding OA, this page will still help on culture/process, but the drills assume a tech loop.
Academic requirements
Marks: Commonly 70% or 7.0+ CGPA in 10th, 12th, and graduation (student reports)
Degree: B.Tech/B.E./M.Tech in CS, IT, or related fields
Year of Study: Final year and recent graduates (within ~2 years on many tech posts)
Backlogs: No active backlogs at application
Branch & skills
Branches: CS, IT, ECE, EE, and related streams on many drives
Programming: Strong Java, Python, or C++ plus DSA
Experience: Freshers and 0-2 YOE for Analyst-style tech hiring
| Academic Level | Typical floor (candidate-reported) | Notes |
|---|---|---|
| 10th | 7.0 CGPA / 70% | Listed on many 2025-2026 drive notes |
| 12th | 7.0 CGPA / 70% | Same threshold as 10th in most reports |
| Graduation | 7.0 CGPA / 70% | Latest completed semester for final years |
| Active backlogs | Not allowed | Clear before OA/interviews |
| Band | What it usually means |
|---|---|
| 7.0-7.9 | Meets common minimum; OA must be strong |
| 8.0-8.9 | Frequently cited among selected candidates with solid coding |
| 9.0+ | Strong academically - still must clear coding + math |
CGPA opens doors on campus shortlists. HackerRank performance opens interview rooms.
Is 7.0 enough? It meets the commonly reported minimum. Selection still hinges on OA coding, quantitative questions, and interview depth. Candidates in the 8.0+ band show up often in selected pools, but a 7.1 with strong HackerRank performance beats a 9.0 who blanks DP.
There is no single officially published cutoff that never changes - always verify the careers portal / campus JD. 2025 and 2026 chatter uses the same floor language, so you do not need duplicate year-tagged eligibility FAQs.
Who fits: You enjoy medium-hard DSA, you can do probability without panic, and you can talk about systems under latency constraints. Finance interest helps in HR; it does not replace coding.
Who struggles: Aptitude-only prep with weak graphs/DP; zero quantitative practice; design answers that are only buzzwords (“we will use Kafka and Kubernetes”) with no data-flow story.
Campus vs off-campus: Campus drives often come with a printed eligibility table and a fixed OA window through the placement cell. Off-campus careers applications can take longer to screen, then move quickly once OA clears. Technical content stays similar - do not expect an “easier off-campus paper.”
Is ECE/EE eligible? On many technology drives, yes when the JD lists related branches. You still need the same DSA and quant bar. Branch is permission to attempt, not a scoring bonus.
Backlogs and gaps: active backlogs are a hard no in most reports. A gap with a clean explanation (exam year, health, family) is sometimes acceptable within about two years - performance still decides. Do not invent elaborate gap fiction; interviewers ask follow-ups.
Documents to keep ready: 10th/12th/grad mark sheets, ID, and a resume that matches portal entries. Finance-tech employers are picky about consistency.
Download 2026 Goldman Sachs placement papers
2026 in detail
2025 placement papers
2024 placement papers
Previous year question papers
Students repeatedly cite families like:
When you solve one, write the pattern name and two cousins in your log. GS interviews love follow-ups that change constraints slightly - memorized code without the pattern dies.
Previous-year Goldman Sachs papers are simulators for the HackerRank-style OA: a short set of medium-hard coding problems plus a mathematical aptitude block. Interview-year packs also surface DSA follow-ups and finance-flavored design prompts. Themes repeat more than exact clones - finish timed 2024/2025 sets and a 2026 OA will feel familiar even when the DP twist is new.
| Stage | What papers train |
|---|---|
| OA coding | Arrays, strings, DP, graphs under time |
| OA math | Probability, statistics, quantitative reasoning |
| Tech interviews | Spoken DSA + optimization |
| Design | Trading / risk / low-latency sketches |
| Managerial / HR | Impact stories + location fit |
How to use one paper set: run a full 90-minute mock; force yourself to leave ~20-30 minutes for math; review every wrong probability concept the same evening; rewrite the weakest coding solution with complexity notes. Three reviewed OAs beat ten unread PDFs.
Coding half:
Math half:
Related problems to practice:
| OA theme | What to drill next |
|---|---|
| Stock / interval profit variants | Prefix extrema, DP on sequences |
| Graph connectivity / shortest | BFS/DFS, topological ideas |
| String parsing / validation | Stacks, two pointers |
| Probability of events | Conditional probability drills, Bayes lite |
| Expected value word problems | Linearity of expectation intuition |
| Year flavor | What showed up a lot | Prep implication |
|---|---|---|
| 2024 | Medium DSA + probability | Do not skip quant |
| 2025 | Same OA spine; same-day interview packs on campus | Stamina + spoken practice |
| 2026 | Still coding+math OA; design asks latency/reliability | Keep systems vocabulary warm |
Goldman Sachs runs campus and careers-portal hiring for technology roles. Referrals exist. Once you are in process, expect a coding+math OA and a multi-interview ladder. Some campus drives pack interviews into a single day after shortlisting.
Campus recruitment
Placement cell coordinates PPT, eligibility list, and OA. Follow TPO instructions for HackerRank windows.
Online application
Apply on Goldman Sachs careers for Analyst/technology roles. Resume screen precedes OA.
Referral program
Employee referral can help visibility. You still sit the same OA and interviews.
The Goldman Sachs placement process focuses on technical excellence and problem-solving. Understanding the OA mix matters more than collecting twenty unread PDFs.
Coding section reality: medium to hard problems covering arrays, strings, dynamic programming, graph algorithms, and optimization. Focus on time complexity and space efficiency. Partial credit for approach appears in some reports - still aim for full AC.
Mathematical aptitude reality: quantitative reasoning, probability, statistics, and word problems with a finance-adjacent flavor sometimes. This is not a 3-hour CAT paper, but it is also not “two easy percentages.” Students who only ground LeetCode get surprised here.
Languages: C, C++, Java, Python. Pick one primary language for speed. Java and Python are common in GS technology chatter.
Success rate chatter: ~15-20% clear OA in competitive pools - treat that as motivation to mock the full 90 minutes, not as lore that “nobody clears.”
Format virtual/onsite, ~45 minutes, 2-3 coding problems. Passing criteria students describe: solve at least two with clear explanation. Evaluation includes approach, code quality, communication, and complexity analysis. Roughly ~40% of OA candidates advance in many write-ups.
Practice saying your plan before coding. Silent typing with a perfect solution still loses if the interviewer cannot follow your thinking.
Topics that show up: trading platform sketches, low-latency paths, distributed systems basics, database design/optimization, project deep-dives. Evaluation favors structured thinking over tool-name dropping.
A usable fresher template:
Managerial rounds probe impact, collaboration, and leadership scenarios. Prepare STAR stories with numbers from projects, clubs, or internships. HR checks motivation, location (Mumbai/Bangalore), and consistency. ~60% managerial advance and ~80% HR convert are numbers students cite - your mileage varies, but the tone is professional and direct.
Platform: HackerRank or similar · Negative marking: usually none in student reports · Languages: C, C++, Java, Python
| Section | Questions | Time | Difficulty | Focus |
|---|---|---|---|---|
| Coding | 2-3 | 60-70 min | Medium-Hard | Arrays, strings, DP, graphs |
| Mathematical aptitude | 5-10 | 20-30 min | Medium | Probability, stats, quant |
Clear rates after OA are often cited around 15-20% in competitive pools. Budget math time on purpose - finishing two codes and blanking probability is a common fail mode.
| Minute band | Action |
|---|---|
| 0-5 | Skim coding + math; pick coding order |
| 5-35 | Coding problem 1 |
| 35-65 | Coding problem 2 (and stretch into 3 if easy) |
| 65-85 | Math block |
| 85-90 | Sanity pass on edge cases |
2-3 DSA problems. Trees, graphs, arrays, optimization. Passing bar students describe: solve about two problems with clear explanation and complexity. Roughly ~40% of OA qualifiers advance in many write-ups.
System design / deeper technical discussion / projects. Expect trading-platform or low-latency flavored prompts at fresher depth: components, data flow, bottlenecks, failure modes. Database and scalability talk is fair game. About ~50% of Round-1 survivors advance in typical notes.
Behavioral + light technical leadership: impact, teamwork, handling failure, ownership under pressure. Prepare STAR stories with numbers. About ~60% advance in candidate-reported funnels.
Background, motivation, relocation (Mumbai/Bangalore commonly discussed), compensation logistics. Most managerial clears convert if stories stay consistent - often cited around ~80%.
| Phase | Duration | What happens |
|---|---|---|
| Application & screening | ~1 week | Resume filter |
| OA | 1-2 days | Coding + math |
| Technical interviews | ~1 week (or same day on campus) | R1 + R2 |
| Managerial | 2-3 days | Behavioral depth |
| HR | 1-2 days | Offer discussion |
| Result | 3-5 days | Letter / joining details |
| Total | Often 3-4 weeks | Faster for strong campus packs |
Unproctored does not mean casual. Treat it like an exam. Students lose seats to network drops and “I’ll do math later” that never happens.
| Item | Typical GS tech OA |
|---|---|
| Duration | ~90 minutes |
| Coding | 2-3 medium-hard |
| Math | Probability / stats / quant |
| Platform | HackerRank (common) |
| Languages | C / C++ / Java / Python |
Switch from “more random problems” to interview narration: solve aloud, defend complexity, sketch one latency-aware design, and rehearse Why GS + location. If your campus packs interviews same-day, sleep and eat like it is an exam marathon.
If you only remember three numbers: 5 stages, ~90-minute OA, Analyst fresher band often cited ₹18-22 LPA (candidate-reported).
When interviews stack after OA:
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 Goldman Sachs 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 Goldman Sachs sits around ₹18-22 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): From student reports (not one official universal PDF): commonly 70% or 7.0+ CGPA across 10th, 12th, and graduation. Degrees: B.Tech/B.E./M.Tech in Computer Science, IT, or related fields. Final-year students and recent graduates (within about 2 years on many tech posts). No active backlogs at application. Strong Java, Python, or C++ preferred. Always verify on the Goldman Sachs careers portal or campus JD. Criteria s.
What you are training for: Typical technology fresher path: Online Assessment (~90 minutes, coding + mathematical aptitude on HackerRank) → Technical Interview 1 (45 min, DSA) → Technical Interview 2 (45 min, system design / deeper tech) → Managerial Round (45 min) → HR Interview (~30 min). Total often 3-4 weeks from application to offer. Campus drives may compress interviews onto one day after OA.
Short version of the prep split: Split time roughly 40% DSA (arrays, trees, graphs, DP), 30% timed coding practice, 15% system design for trading/low-latency/risk systems, 10% core CS and projects, 5% quantitative aptitude/probability. Practice HackerRank-style OAs that mix coding with math. Use timed papers on this site.
Week 1 - pattern, not vibes. Language fluency: rewrite 10 old solutions in one language until you stop hunting syntax. Open the Goldman Sachs 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 Goldman Sachs 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 Goldman Sachs 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 Goldman Sachs?” 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.
| Slice | Share of weekly hours | What “done” looks like |
|---|---|---|
| Timed papers / OA | ~40% | You finish a Goldman Sachs-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 Goldman Sachs story (eligibility, rounds, salary). Use those pages for timed reps and interview notes.
If you do one thing after reading this: schedule three timed Goldman Sachs papers on three different days, then interview prep on the leftovers.
A TCS/Infosys aptitude deck still helps the quant/logic slice of many Goldman Sachs papers, but do not assume the same cutoff culture. Read the process section on this page once, then swap in Goldman Sachs-specific coding or domain drills from the nested banks. Shared prep is fine; shared assumptions about rounds are not.
Days 1-3: one timed Goldman Sachs 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 Goldman Sachs. 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 Goldman Sachs, 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 Goldman Sachs mistakes, you are collecting content, not preparing.
Sit one more mixed Goldman Sachs 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.
Sit one more mixed Goldman Sachs 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.
Random Goldman Sachs problems feel productive. Timed mocks are what move the needle. If you only have an hour tonight, sit 40 minutes of a previous-year Goldman Sachs set and spend 20 minutes on the three misses. That loop beats an untimed 8-problem grind you will not remember tomorrow.
Do not reread the whole Goldman Sachs hub. Skim eligibility once, open your error log, and recast the two STAR stories you will actually say. If the drive names an OA platform, click around it for five minutes so login panic is not your first round.
When you hold GS vs peer banks:
A slightly lower headline with a stronger engineering team can be the better fresher move.
Figures below are candidate-reported as of August 2026 (total annual package bands). Ranges, not guarantees.
| Level | Experience | Base (approx.) | Total Package | Typical background |
|---|---|---|---|---|
| Analyst | 0-1 years | ₹15-18 LPA | ₹18-22 LPA | New graduates |
| Associate | 1-2 years | ₹20-25 LPA | ₹25-30 LPA | Early experience |
| Vice President | 3-5 years | ₹35-45 LPA | ₹40-50 LPA | Senior engineers |
| Managing Director | 5+ years | ₹50+ LPA | ₹60+ LPA | Leadership tracks |
| Role | Level | Total Package | Notes |
|---|---|---|---|
| Quantitative Analyst | Entry | ₹20-25 LPA | Strong math/stats |
| Risk Analyst | Entry | ₹18-22 LPA | Risk / finance flavor |
Health coverage, performance bonuses (often discussed as a meaningful percent of base), learning budgets, and relocation support toward Mumbai / Bangalore offices. Read bonus and joining details on the letter - headline LPA tweets flatten important splits.
How to talk CTC in HR: know your band, ask clarifying questions politely, and avoid inventing competing offers. Compare total compensation and role scope against other finance-tech offers (JP Morgan, Morgan Stanley) using the same assumptions.
Growth students ask about: Analyst → Associate is the early ladder people describe; pace depends on performance and business needs. Internal mobility across technology teams exists, but do not assume an automatic jump into a front-office fantasy role from a tech Analyst seat.
Bonus reality: performance bonuses are frequently discussed as a meaningful percent of base in public chatter - treat ranges as directional. Read the offer for what is guaranteed vs variable.
| Month band | Focus if Goldman Sachs is on your list |
|---|---|
| Jun-Jul | DSA mediums + start probability notebook |
| Aug-Sep | Weekly full 90-min OA mocks; campus PPT watch |
| Oct-Nov | Interview narration + design sketches; peak drives |
| Dec-Jan | Off-campus applications; keep math warm |
| Feb-Apr | Continue careers-portal attempts; internship conversion paths |
Do not postpone quant until “after I finish 300 LeetCode.” The OA will not postpone it for you.
Hiring trends
Continued emphasis on system design for scalable, low-latency systems. AI/ML exposure helps on some teams but does not replace DSA.
Process shape
Virtual interviews remain common. Behavioral fit shows up earlier. Campus same-day loops still happen after OA clears.
Access paths
Campus ambassador-style programs, hackathons, and referrals appear in student chatter as visibility tools - OA still decides.
Company context
India engineering footprint around trading, risk, and platform tech keeps the interview flavor quantitative and systems-aware.
Net for prep: do not wait for a “GS removed math” rumor. Keep coding sharpness, probability comfort, and latency-aware design explanations. Calendar-wise, budget 3-4 weeks end-to-end and a possible same-day interview crush on campus.
Signal vs noise: AI/ML hiring tweets, “GS freeze” rumors, and contest placement stories will keep circulating. Your controllable inputs are OA mocks with both halves, spoken DSA, one latency-aware design sketch per week, and honest city prefs.
Also expect virtual interviews to remain common even when OA is onsite or at home. Practice coding while sharing a screen and talking - silent typing looks worse than slower narrated progress.
Typical tech fresher path: OA (~90 min, coding + math) → Technical Interview 1 → Technical Interview 2 → Managerial → HR. End-to-end often 3-4 weeks. Campus drives may compress interviews into one day after OA.
Five stages for most Analyst/technology freshers: OA plus two technicals, managerial, and HR. Labels vary slightly by track; the coding+math OA is the constant opener.
Yes. Free Goldman Sachs placement papers PDF and previous-year sets (2024-2026) with solutions live on this site - including the 2026 PDF. No registration for core downloads.
Student reports: 2-3 medium-hard coding problems (~60-70 min) on arrays/strings/DP/graphs, plus mathematical aptitude (~20-30 min) on probability/statistics, usually on HackerRank. Practice both halves in one sitting.
From student reports: commonly 70% or 7.0+ CGPA across 10th, 12th, and graduation; B.Tech/B.E./M.Tech in CS/IT-related fields; final year or recent grad (~2 years on many posts); no active backlogs; strong Java/Python/C++. Not one frozen official PDF - verify careers/campus JD. Same substance as recent cycles.
Candidate-reported: Analyst ≈ ₹18-22 LPA total for new grads. Associate bands often cited higher with experience. Location and team move you inside the band - trust your letter over blogs.
The common fresher technology track in India campus conversations. Selected via the OA + interview ladder. Work depends on team (platforms, risk tech, trading-adjacent systems). Growth titles move toward Associate and beyond with experience.
Rough split: 40% DSA, 30% timed coding, 15% design, 10% CS/projects, 5% quant. Run full 90-minute OA mocks. Details: preparation guide.
C, C++, Java, and Python are typically accepted. Java and Python are common in GS tech. Stay consistent across OA and interviews.
Technology teams care about latency, reliability, and clear data flow - themes from trading and risk systems. Fresher prompts are lighter than senior loops, but “Kafka + microservices” without a failure story will not impress.
Deep IBD knowledge is not the OA filter. Basic curiosity about markets helps in HR and design analogies. Coding, quant aptitude, and systems reasoning decide most early rounds.
All three hire engineers into finance-tech environments. GS often feels quantitative and latency-aware in student reports. Compare team, city, and offer math. Browse JP Morgan, Morgan Stanley, and peers rather than picking from memes.
Both cities show up frequently in fresher conversations, depending on team. HR will ask relocation willingness. Be honest; rigid remote-only answers are a poor fit for many new-grad seats.
Mock the math half of the OA every week. In design chats, lead with assumptions, bottlenecks, and failure modes - not a logo drop of tools. Same-day campus loops need sleep and spoken practice as much as another DP sheet.
Internship/Summer Analyst tracks can use shorter interviews after OA and may convert to full-time later. The OA still mixes coding and aptitude in many campus stories. Prep the same fundamentals; adjust timeline expectations for internship calendars.
Candidate reports generally expect no active backlogs at application / OA. Clear everything before joining either way. Strong coding does not usually override an active-backlog hard filter when the JD forbids it.
Aim for 10-15 timed OA-style mocks minimum with review; more if math is rusty. Quality beats volume - every mock should produce a mistake log entry you redo within three days.
Two blogs that disagree on difficulty usually means pools differ - your mocks still decide your readiness.
On 23 July 2025, an NIT Summer Analyst Trainee candidate sat a ~1.5-2 hour HackerRank OA from home (DSA, aptitude, and a self-story prompt) that drew nearly 800 branch-open applicants, then faced “all interviews conducted on same day” - two ~25-30 minute offline technicals plus HR (GeeksforGeeks). Eight students were selected; the process compresses quickly once you clear the OA.
A Compliance Software Engineer applicant (write-up updated 5 September 2025) got an OA within two weeks of applying - two easy coding problems on the GeeksforGeeks platform - then noted “a few days after clearing the OA, an interview was scheduled,” followed later by three one-hour DSA/engineering rounds (plus managerial if shortlisted) stacked on one day (GeeksforGeeks).
What to steal: once OA clears, assume interviews can stack; keep DSA narration warm; read more on Goldman Sachs interview experiences; treat each write-up as a vibe check, then return to timed mocks.
Common failure modes: finishing two codes and guessing math; memorizing a trading-system blog without being able to draw data flow; managerial answers with no metrics; location bluffs that collapse in HR.
Keep using this site for timed papers and nested guides for drills. Finance-tech prep rewards boring consistency: one OA mock rhythm, one design sketch rhythm, one STAR rehearsal rhythm.
If you are also applying to product companies, keep a separate Meta/Amazon-style values bank - GS managerial stories overlap but are not identical to Leadership Principles or Meta values. Reuse facts; retarget the framing.
JP Morgan · Morgan Stanley · Deutsche Bank · Bank of America · Capital One · Wells Fargo
