Investment Banks and Fintech Tech Hiring: Goldman Sachs, JPMorgan and More
Updated 28 Oct 2026 5 min read
On this page 10 sections
Overview
Large global banks and financial firms run big technology centres in India. Names you will often see in job listings include Goldman Sachs, JPMorgan Chase, Morgan Stanley, American Express, Visa, Mastercard, Wells Fargo, Barclays and Deutsche Bank, along with Indian fintech companies. The engineering work covers trading platforms, payments, risk systems, data platforms and internal tools.
These employers usually hire for strong fundamentals and reliability: correct, careful code matters, because mistakes in finance are expensive. Roles include Analyst, Associate, Software Engineer and Technology Analyst.
The usual stages
Candidate reports commonly describe the following. Check the specific announcement, as formats vary by firm and year:
- Application, campus shortlisting or referral
- Online coding assessment: often on a platform such as HackerRank or CoderPad. It generally includes two or three coding problems and sometimes MCQs on computer science fundamentals, SQL or quantitative reasoning.
- Technical interviews: usually two or three rounds covering DSA, core computer science (OS, DBMS, networks), SQL, OOP and project discussion. Some firms run several interviews back to back on a single day, sometimes called a "super day".
- Managerial or behavioural round: teamwork, ownership, handling pressure
- HR discussion and offer
For experienced hires, expect system design and detailed discussions about production issues, performance and data consistency.
What gets tested
- DSA: medium problems on arrays, strings, hashing, trees, graphs, heaps and dynamic programming
- Core CS: concurrency, deadlocks, memory management, indexing, transactions, ACID, TCP/IP
- SQL: joins, aggregation, window functions (practice set)
- Object-oriented design and clean-code habits (OOP guide)
- Mathematics and logic: probability and puzzles appear in some quantitative roles
- Behavioural: integrity, accountability and teamwork are valued strongly in regulated industries
Preparation plan
Weeks 1–8: DSA. Follow the study plan; practise under timed conditions (online assessment tips).
Weeks 4–10: fundamentals. Revise core CS subjects and write SQL queries daily.
Weeks 8–12: design and behaviour. Practise object-oriented design problems and, for experienced roles, system design. Prepare stories using the STAR method.
Tips
- In coding tests, read the full problem and constraints; many failures are from wrong assumptions rather than wrong algorithms.
- Always consider edge cases: empty input, large input, duplicates, negative values.
- In interviews, explain trade-offs, for example speed vs memory, or consistency vs availability.
- Show care for correctness. Talk about how you would test your code.
- Learn a little about the domain: what payments, trading or risk systems do at a high level. You do not need finance expertise, but curiosity helps.
Common mistakes
- Focusing only on DSA and neglecting database and OS fundamentals
- Writing code quickly but not testing it
- Giving vague answers about your own projects
- Not preparing questions about the team and technology
Frequently asked questions
Do these firms care about CGPA?
Many campus processes set minimum academic criteria, and some filter on them before the coding test. Experienced hiring focuses on your work and skills instead.
Do I need finance knowledge?
Not for most software roles. Curiosity about the domain helps, but they hire for programming ability and problem solving first.
Which language should I choose for the coding test?
Use the language you are fastest and least error-prone in. Java, Python and C++ are all common choices; confirm that the platform supports yours.
Why is testing and correctness emphasised so much?
Mistakes in financial systems can be expensive, so interviewers like candidates who think about edge cases, validation and testing without being asked.
What is a back-to-back interview day?
Some firms schedule several interviews in a single day. Rest well beforehand, keep water and a short break plan, and treat each interview as a fresh start; one weaker round does not necessarily decide the outcome.
Next steps
Read the Amazon and Microsoft guides for similar big-company processes, and check current experienced and fresher listings. When you receive an offer, read salary negotiation.
What the company's own pages say (checked 28 October 2026)
Goldman Sachs, confirmed on its HackerRank guide and student preparation page:
- Candidates complete a Software Fundamentals challenge (data structures and algorithms, 30 minutes). Engineering candidates also complete a Software Diagnostics challenge (45 minutes) in which they debug an existing Django, Node.js or Spring Boot app, with a limited AI assistant available.
- The student page places a video interview before the HackerRank step, and says campus hires typically have two to five interviews depending on the division. A final round called a Superday is listed, but its format is not described there. The candidate update is expected within about three weeks.
So the "two or three coding problems" pattern in the stages above is a general description, and Goldman Sachs' own assessment is different. JPMorgan, Morgan Stanley, Visa, Mastercard and the other firms named were not verified (our search returned no official process pages for them), so treat their details as candidate-reported.
Latest changes (2025–2026)
Updated 28 October 2026.
- Goldman Sachs's own HackerRank guide says engineering candidates complete a Software Diagnostics challenge in which a limited AI assistant is available but does not give full solutions. Practise debugging unfamiliar code, not only writing new code.
For the wider picture, read how tech hiring has changed in 2025–2026.
Please note: hiring processes change between campuses, drives and years, and companies update their rounds without notice. This guide describes the commonly reported structure so you know what to expect and how to prepare. Always confirm the current process on the company's official careers page or in your invitation email. This site is not affiliated with any company mentioned, and company names belong to their owners.
Found this useful? Share it with a friend.