How to Prepare for the Goldman Sachs Exam
Preparing for the Goldman Sachs Engineering Analyst Campus Hiring Program requires a structured, stage-wise approach. The recruitment process involves an aptitude test, a technical test, and multiple interview rounds, each testing different skill sets and requiring focused preparation. A clear understanding of what each round evaluates helps candidates allocate their preparation time effectively. The sections below provide round-wise preparation guidance aligned with the Goldman Sachs recruitment process for freshers.
Goldman Sachs Exam Preparation Tips
The following preparation tips are organized by recruitment round to help candidates prepare systematically for each stage of the Goldman Sachs Engineering Analyst hiring process.
1. Aptitude Test
The aptitude test is the first screening round and covers Numerical Computation, Numerical Reasoning, Logical Reasoning, Abstract Reasoning, Diagrammatic Reasoning, and Verbal Reasoning. The test has 66 MCQs to be completed in 90 minutes with negative marking.
Build Speed in Numerical Computation
Practice mental math and basic arithmetic operations without a calculator. Focus on percentages, ratios, averages, probability, and permutations and combinations. Speed and accuracy are critical, as the time per question is limited. Regular timed practice sessions help improve calculation speed.
Practice Data Interpretation for Numerical Reasoning
Work on interpreting data from tables, bar graphs, pie charts, and line graphs. Focus on drawing quick inferences and comparisons from given datasets. Practice solving data interpretation sets under timed conditions to build fluency with numerical data analysis.
Strengthen Pattern Recognition for Reasoning Sections
For Logical, Abstract, and Diagrammatic Reasoning, practice identifying patterns in sequences, shapes, and diagrams. Solve puzzles, coding-decoding problems, and series completion exercises regularly. For Abstract and Diagrammatic Reasoning, focus on recognizing rotations, reflections, and figure transformations.
Improve Reading Comprehension Speed and Accuracy
For the Verbal Reasoning section, read passages regularly to improve reading speed and comprehension accuracy. Practice answering inference-based questions, sentence correction, and fill-in-the-blank exercises. Focus on understanding the main idea and supporting details within a passage quickly.
2. Technical Test (Off-Campus)
The technical test includes 15 MCQs on CS fundamentals and 5 coding/subjective questions, with a duration of 135 minutes. The difficulty level is high and the cut-off is approximately 80%.
Revise Core Computer Science Fundamentals
Review key topics in Data Structures, Algorithms, Object-Oriented Programming, DBMS (normalization, SQL queries, joins), and Operating Systems (process management, threading, memory management, deadlocks). Focus on understanding concepts deeply rather than surface-level memorization.
Practice Coding Under Time Constraints
Solve coding problems on platforms such as LeetCode and HackerRank in C, C++, Java, or Python. Target medium to hard difficulty problems. Practice writing clean, efficient code within a time limit. Focus on getting optimal time and space complexity in your solutions.
Focus on Data Structures and Algorithms
Prioritize Arrays, Linked Lists, Trees (Binary Trees, BSTs), Graphs, Stacks, Queues, and Hash Maps. Practice common algorithm patterns: sorting, searching, dynamic programming, greedy algorithms, and graph traversal (BFS/DFS). Understanding when to apply which data structure is critical for the coding section.
3. Technical Interview Round 1
The first technical interview is 30-45 minutes long and focuses on DSA problem-solving, typically on CoderPad or a whiteboard. One or two medium to hard problems are asked.
Solve Medium to Hard DSA Problems Regularly
Aim to solve at least 150-200 problems on LeetCode, covering key topics such as Dynamic Programming, Graph Algorithms, String manipulation, and Tree/BST problems. Focus on problems tagged under Goldman Sachs or similar financial technology companies.
Practice Thinking Aloud While Coding
During the interview, interviewers evaluate not just the final solution but also the approach. Practice explaining your thought process, asking clarifying questions, and walking through examples before coding. Discuss the data structures chosen, edge cases handled, and the time/space complexity of your solution.
Review Resume and Projects Thoroughly
Be prepared to discuss every project and experience listed on your resume in detail. Practice explaining the architecture, design decisions, challenges faced, and your specific contributions. Interviewers may start with a project discussion before moving to coding problems.
4. Technical Interview Round 2
The second technical interview is 30-45 minutes long and focuses on advanced topics including System Design, OOP, and Design Patterns. This round is considered one of the most challenging.
Study Low-Level Design and Object-Oriented Design
Understand how to design class structures, define entity relationships, and apply design patterns such as Factory, Strategy, and Observer. Practice drawing UML diagrams and explaining your design decisions clearly and concisely.
Prepare for Advanced DSA and Optimization
Be ready for harder DSA problems that require multiple solution approaches. Interviewers may push for optimizations beyond the initial brute-force solution. Practice problems involving KMP, Rabin-Karp, Trie-based solutions, and advanced graph algorithms.
Revise OOP Concepts and Database Scaling
Prepare for rapid-fire questions on OOP principles (encapsulation, abstraction, inheritance, polymorphism), SOLID principles, and database scaling strategies (indexing, sharding, replication). Be ready to explain these concepts concisely with examples.
5. Technical Interview
Technical interviews evaluate problem-solving skills, coding ability, system design thinking, and core CS knowledge. The focus is on live coding and real-time discussion of approaches.
Practice Live Coding on a Platform
Get comfortable coding on platforms like CoderPad or a shared coding editor. Practice without IDE auto-complete features. Focus on writing syntactically correct, well-structured code from memory.
Prepare for System Design Discussions
For candidates reaching advanced rounds, study system design concepts including load balancing, caching, database design, and microservices architecture. Be prepared to sketch out designs and discuss scalability, reliability, and trade-offs.
Revise Core CS Subjects
Revise fundamentals of Operating Systems, DBMS, Computer Networks, and Object-Oriented Programming. Interviewers may ask conceptual questions on any of these subjects in addition to coding problems.
6. HR Interview
The HR interview assesses communication skills, behavioral competencies, and cultural alignment with Goldman Sachs.
Prepare Behavioral Answers Using the STAR Method
Structure your answers using the Situation, Task, Action, Result format. Prepare examples for common themes such as teamwork, leadership, conflict resolution, handling failure, and working under pressure.
Research Goldman Sachs Thoroughly
Understand Goldman Sachs' business divisions, core values, engineering culture, and recent initiatives. Be prepared to articulate why you want to join Goldman Sachs Engineering specifically, and what aspects of the firm's work align with your career goals.
Prepare Questions for the Interviewer
Have 2-3 thoughtful questions ready to ask the interviewer about the team, projects, mentorship opportunities, or engineering culture at Goldman Sachs. Asking relevant questions demonstrates genuine interest and preparation.
Frequently Asked QuestionsFAQ
How should I start preparing for the Goldman Sachs Engineering Analyst exam?
Begin by understanding the recruitment process and the syllabus for each round. Start with aptitude practice for the first round, then move to coding and DSA preparation for the technical test and interview preparation. Allocate at least 2-3 months for structured preparation.
How can I clear the Goldman Sachs exam in the first attempt?
Focus on consistent daily practice across all sections. For the aptitude test, practice timed mock tests with negative marking. For technical rounds, solve at least 150-200 coding problems on LeetCode. Review CS fundamentals and practice live coding regularly.
What skills does Goldman Sachs look for in engineering candidates?
Goldman Sachs evaluates analytical aptitude, problem-solving ability, coding proficiency in languages like Java/Python/C++, understanding of data structures and algorithms, system design thinking, and strong communication skills. Cultural fit and motivation are also assessed.
What should I expect in the Goldman Sachs aptitude test?
The aptitude test has approximately 66 MCQs across Numerical Computation, Numerical Reasoning, Logical Reasoning, Abstract Reasoning, Diagrammatic Reasoning, and Verbal Reasoning. The duration is 90 minutes with negative marking (+5 for correct, -2 for incorrect).
How difficult is the Goldman Sachs technical interview?
The technical interview rounds are considered high difficulty. Candidates are expected to solve medium to hard level DSA problems live, discuss system design concepts, and demonstrate strong understanding of OOP and CS fundamentals.
What topics should I focus on for the Goldman Sachs coding round?
Focus on Data Structures (Arrays, Trees, Graphs, Hash Maps, Stacks/Queues), Algorithms (Dynamic Programming, Greedy, Graph traversal, String algorithms), and System Design basics. Practice problems of medium to hard difficulty on LeetCode or HackerRank.
How should I prepare for the Goldman Sachs HR interview?
Research Goldman Sachs thoroughly, prepare behavioral answers using the STAR method, practice articulating your motivation for joining the firm, and prepare thoughtful questions for the interviewer. Focus on demonstrating clear communication, confidence, and cultural alignment.
