cswork / libraryOpen practice workspace

Articles · Goldman Sachs

Goldman Sachs India Hackathon 2026: HackerRank, Eligibility, and Technical Preparation

Review the closed Goldman Sachs India Hackathon 2026: separate CS and Quant windows, track eligibility, individual rules, PPI limits, and preparation.

Registration for Goldman Sachs India Hackathon 2026 is over: the published deadline was May 10, 2026. As of September 6, 2026, this guide is a retrospective of the official format and transferable preparation, not an invitation to register for the 2026 event. The Goldman Sachs event page lists separate Quant and CS dates and track-specific eligible-college lists.

This hackathon is also distinct from the company's ordinary recruiting assessments.

The 2026 timeline and eligibility

MilestoneOfficially listed date or condition
RegistrationApril 22–May 10, 2026
Quant challengeMay 23, 2026, 9 AM–9 PM IST
CS challengeMay 24, 2026, 9 AM–9 PM IST
Participant cohortsEngineering students graduating in 2027 or 2028, subject to the relevant college list
Later stagesMentorship and an in-person finale were scheduled for June

Each track had a 12-hour window. This was not a single 12-hour allowance split arbitrarily between two days. The official page gives different eligible-school lists for CS and Quant, so being eligible for one did not automatically establish eligibility for the other.

These are published dates and rules, not independent confirmation that every scheduled later stage occurred. No next-cycle deadline should be inferred from the 2026 page, even if an old “Apply” button remains visible.

Could candidates enter both tracks? Was this a team contest?

The 2026 FAQ says candidates eligible for both tracks could select both and receive separate links. It was an individual HackerRank event; team entries were not permitted. The FAQ also required submission within the window and said late submissions would not be considered.

The FAQ narrows the PPI opportunity to eligible finalists graduating in 2028. That qualification matters alongside the event page's broader PPI wording. Participation itself was not an employment or internship offer, and a leaderboard lead did not guarantee a win.

For an unresolved 2026 participation question, use the organizer contact listed on the official page and FAQ. Do not assume the ordinary summer-analyst recruiter owns this event's results or eligibility exceptions.

How CS and Quant preparation should differ

The following are original practice exercises aligned with the advertised technical and quantitative domains. They are not recovered contest questions or a claim about a future year's format.

Practice trackConstructed exerciseWhat to inspect before improving the result
CSProcess timestamped records, deduplicate updates, and compute an aggregateInput validity, deterministic ordering, complexity, and repeatable output
QuantSimulate a simple random process and compare the estimate with a tractable caseSampling assumptions, numerical stability, and error across repeated runs
EitherPackage a reproducible baseline and one measured improvementWhether the submitted artifact reproduces the claimed result

For the CS exercise, include two records with the same identifier but different arrival times. Decide whether they are duplicates or revisions before writing the aggregation. A faster algorithm is not useful if it silently discards a legitimate correction.

For the Quant exercise, choose a simple case with an analytically checkable expectation, then compare several simulation sizes. If the estimate changes dramatically across seeds, investigate variance before claiming a signal. This is a practice check, not financial advice or a trading strategy.

A long-window submission routine

Read the supplied brief and allowed tools first. Build a baseline you can run end to end, record the metric and configuration, and make one change at a time. Keep a short local experiment log only where the contest rules permit local work. Reserve time to verify packaging and the submission receipt.

The useful distinction from a compact OA is the risk of spending hours on an improvement that never becomes a valid submission. A practice log might contain four fields: version, change, validation result, and reproducibility check. It should make it possible to select the last working version without guessing.

Sources and Further Reading

Documentation checked: September 6, 2026.