How a Non-CS Student Cracked Google Internship: 1200+ DSA Solved

content: The Unconventional Path to Google

When Achut Chikhaliya told his parents he'd secured a Google software engineering internship, their shock mirrored his own. As a third-year electrical engineering student at IIT Guwahati—a non-computer science background—he'd defied expectations. After analyzing his journey, I believe his 1,200+ solved data structure problems and strategic consistency hold universal lessons for aspiring coders. His story proves domain expertise matters less than systematic preparation.

Breaking Down Google's Interview Process

Google's on-campus selection had no minimum CPI requirement but internally prioritized candidates above 7.5 CGPA. Achut cleared three rigorous rounds:

• Online assessment: Two algorithm problems (DP, arrays) in 60 minutes
• Technical Round 1: Medium-level binary search question + follow-up approach design
• Technical Round 2: Array algorithm and comparator implementation

Critical insight: Interview questions were solvable with LeetCode Medium-level practice—contrary to perceptions of extreme difficulty. From 20+ candidates in Achut's circuit branches cohort, only a handful secured internships.

The 3-Year Preparation Blueprint

Achut's consistency patterns reveal why starting early matters:

1. Pre-college: Completed 20-30% of Alpha DSA course before joining IIT
2. Year 1: Restarted DSA consistently after initial gap, finished Alpha course
3. Year 2:
   • Competitive programming (CodeForces Specialist)
   • Web development via Delta course (MERN stack)
   • Summer break: Revised 375+ DSA sheets
4. Year 3: Cracked Google internship

Key mistake he fixed: "Had I started development in first year instead of second, I could’ve participated in hackathons earlier." His advice? Start DSA and development parallelly—don’t sequentialize them.

Non-CS Advantages and CP Strategy

Despite electrical engineering's rigorous academics, Achut faced no unique disadvantages:

• Language myth busted: Solved CP problems in Java despite occasional TLE issues
• Stack selection: Chose MERN for startup relevance and easier future transitions
• CP foundation: Solved 30-40 easy problems before advancing; dedicated 2-3 daily hours

His project strategy targeted interview leverage:

1. Algorithm visualizer (DSA-focused)
2. Gemini API browser extension
3. Delta course capstone project

Actionable Framework for Aspiring Candidates

Based on Achut’s journey:

• Immediate checklist:
  • Solve 5 DSA problems daily
  • Join coding contests weekly
  • Build 1 project quarterly
• Resource recommendations:
  • Beginners: Alpha course (structured DSA foundation)
  • Intermediate: Delta (full-stack projects)
  • Advanced: CodeForces (real-interview problem patterns)
• Interview hack: "Drive interviews toward your stronger skill—DSA or development—through project choices."

content: The Mindset Differentiator

Achut’s 8.47 CGPA wasn’t accidental. He scheduled academics ruthlessly:

• Quiz prep: Dedicated 1 day for 10-15% weightage exams
• Mid/end sems: Focused 1 week prior, pausing coding

His friend group’s contest discussions post-competition built collective consistency—proving environment trives talent.

Overcoming Placement Season Realities

2024 placement declines at IIT Guwahati highlighted systemic issues:

• Online assessment cheating: Skewed shortlisting, favoring offline interviews
• Delayed seriousness: Most students start preparing only before internship season

Achut’s counter-strategy? Start DSA the day you decide on tech careers. Gaps erase foundational knowledge rapidly.

content: Your Roadmap Starts Now

Achut’s journey underscores one truth: Domain barriers crumble before consistent problem-solving. Whether electrical or computer science, your 1,200th solved question matters more than your branch.

"I focused where interviews focused—DSA. That’s the only factor."

Final question: Which step in Achut’s framework seems most challenging for your current preparation? Share your situation below!