Scribd
Upload
95 views

Google Step Intern

Uploaded by

ehfhjfhsfhskd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
95 views

Google Step Intern

Uploaded by

ehfhjfhsfhskd
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Google Step Intern

Hiring Process Overview


There are three phases in the Google interview process for any Software Engineer:

• Screen: Minimum technical bar for any engineering role.


• Interview: Known as in-depth Interviews (virtual) with 5 sessions: 4 coding and 1
Googliness and Leadership. Includes systems design for technical leads and domain-
specific questions for specialists.
• Decide: Interview performance is reviewed to make a recommendation on hiring.
Team matching happens with various teams hiring, and there may be multiple team fit
conversations before extending an offer.
Google India Product Areas/Teams include Google Maps, Ads, Search, Next Billion Users,
Engineering Productivity, Cloud, Android TV, Hardware, and more.

Technical Phone Screen


30-45 minutes over Google Meets to check your coding skills with an engineer using Google
Docs coding with syntax highlighting. The engineer will prepare 1-2 questions for you to
solve optimally within the time limit.
Practice medium to hard level questions on platforms like GeeksforGeeks, LeetCode,
InterviewBit, or Google Coding Questions.
Pro Tip: Ask interviewers how many questions they have at the beginning. You’ll likely get
either 2 straightforward questions or 1 open-ended question with follow-ups.

Assessment Criteria
1. Coding Quality: Using data structures & algorithms; no syntax errors, production-
ready.
2. Problem Solving and Communication Style: Clear method, translate ideas to code.
3. Autonomous Attitude and Time Management: Complete 2 medium/hard coding
questions.

Coding Quality

• Write well-structured, clean, and neat code with consistent coding style.
• Use proper syntax/indentation, but clarify uncommon APIs.
• Use meaningful variable/function names and abstract methods when necessary.
• Your code should be readable. No errors/bugs - try to test.
DS & Algorithms

• Study all known time-space complexities using the Big O cheat sheet.
• Propose optimized data structures and algorithms.
• Translate ideas or algorithms to code well.

Problem Solving

• Take a curious approach and try to understand the problem.


• Scope the question by asking 3-4 clarifying questions.
• Do not solve the question before clarifying requirements.

Resources to Use
Company & Topic Wise Prep Resource: https://seanprashad.com/leetcode-patterns/
NeetCode: https://neetcode.io/practice
LeetCode Discuss for recent Experiences: https://leetcode.com/discuss/explore/google
LeetCode Premium Google Questions: https://github.com/hxu296/leetcode-company-wise-
problems-2022?tab=readme-ov-file#google

Difficulty Level
Medium to Hard: Focus on medium to hard level questions, including a mix of
straightforward and open-ended questions.

Preparation Tips

• Practice coding problems regularly.


• Focus on clean, efficient code.
• Understand and implement data structures and algorithms.
• Develop a clear communication style for explaining solutions.
• Practice solving problems independently and managing time effectively.

Key Topics
You'll be expected to know and apply: lists, maps, stacks, priority queues, binary trees,
graphs, bags, and sets.
Important areas are:
1. Binary search
2. BFS/DFS/Flood fill
3. Tree traversals
4. Hash tables
5. Linked list, stacks, queues, two pointers/sliding window
6. Binary heaps
7. Dynamic programming
8. Union-find
9. Ad hoc/string manipulations
10. Other good to know topics: Trie, segment trees/fenwick trees and bitmask etc.
11. For algorithms you'll want to know greedy algorithms, divide and conquer, recursion,
and brute force search.

Interview Tips
Tip 1: Think out loud & Communicate thought process
Tip 2: Ask clarifying questions
Tip 3: Discuss algorithmic complexities & identify all edge cases independently
Tip 4: Ensure good code quality on Google Docs
Tip 5: Dry run the code
Tip 6: Positive independent attitude & be open to feedback

You might also like