Non-CS Student's Goldman Sachs Internship: 12-Month Roadmap

The Non-CS Advantage: Breaking Into Elite Tech

You're sitting in electronics engineering lectures while dreaming of coding at Goldman Sachs. The syllabus feels irrelevant, peers dismiss your ambitions, and campus placement stats seem grim. This was Naman Umar’s reality at SVNIT Surat—until he landed that coveted internship offer. His journey proves non-CS backgrounds can leverage unique strengths: rigorous analytical training and systematic problem-solving honed in core engineering subjects. After analyzing his 5-round selection process, we’ve distilled actionable insights for every non-CS student targeting top fintech firms.

Naman’s 12-Month Preparation Blueprint

Balancing Core Engineering With Tech Mastery

Naman’s electronics engineering curriculum demanded 70% of his time, but he engineered a counter-strategy:

• Academic prioritization: Used seniors’ PYQs (previous year questions) to ace exams with focused 15-day prep windows, maintaining an 8.7 CGPA
• Peer leverage: Built study groups where CS students explained concepts like API integration in exchange for his circuit theory expertise
• Development before DSA: Started with web development (HTML/CSS/JavaScript) in semester 2 for quick project wins before diving into data structures

The Goldman Sachs Gauntlet: 5 Rounds Decoded

Round 1: The Aptitude Filter

Goldman’s 70-question test in 90 minutes eliminated 90% of candidates. Naman’s approach:

• Targeted practice: Focused on numerical reasoning and logical sections using platforms like Toggl Plan
• Accuracy over completion: Attempted 54 questions with zero errors to avoid negative marking

Technical Rounds: Where Non-CS Students Shine

Naman’s electronics projects became unexpected assets:

Interviewers grilled me on deploying cross-domain APIs for my appointment system. My analog circuit debugging experience helped explain fault tolerance clearly.
His coding rounds emphasized:

• Real-time problem-solving: Solved medium-level string/hashmap problems on coder pads
• Conceptual clarity: Justified MongoDB choice over SQL for flexible schema needs

Beyond DSA: The Full-Stack Edge Most Candidates Miss

Why Development Skills Trump Competitive Coding

Naman’s critical realization: "I missed hackathons in third year because I delayed web development. Non-CS students must front-load dev skills." His revised timeline:

Semester	Focus Area	Key Actions
1-2	Web Dev	Build 3 projects with React/Node.js
3-4	DSA + OOPS	Solve 300+ LeetCode questions
5	CS Fundamentals	Master OS/DBMS via Stanford’s online modules

Communication: The Silent Game-Changer

Naman used ChatGPT’s voice feedback tool to refine responses. His formula:

1. Record answers to behavioral questions
2. Analyze filler words using Otter.ai
3. Practice mirror sessions twice weekly

Toolbox: Non-CS Readiness Checklist

Immediate actions from Naman’s journey:

1. Join coding clubs early—even as non-technical member
2. Attend fintech meetups on Meetup.com to understand industry needs
3. Contribute to open-source electronics projects on GitHub
4. Schedule weekly DSA mock interviews on Pramp

Resource recommendations:

• Delta 3.0 course: Ideal for structured web dev learning with community support
• Blind 75 LeetCode problems: Critical for interview pattern recognition
• Tech Interview Handbook: Behavioral question frameworks for non-traditional candidates

"Your branch doesn’t define your tech potential—your projects do." - Naman’s parting advice

What’s the one hurdle in your non-CS journey? Share below—we’ll tailor solutions in our next case study.