Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Product engineeringProduct company

Google

Runs Search, YouTube, Android, Chrome, Gmail and Google Cloud, and builds the Gemini family of AI models.

Not known5 stage process documentedFounded 1998
Headquarters

Mountain View, California, United States

Headcount

5,000 and up

5,000 or more people
Work model

Not known

Hiring

Not known

Not enough signal to say. Check the careers page directly.
Where to apply

Ask for a referral to Google

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Open internships

How they hire

Google says the whole process usually takes about six to eight weeks. The decision after the panel can take several weeks because feedback goes through internal review.

  1. 1

    Hiring assessment and coding exercise

    Official
    Online testRemote

    Some candidates take the Google Hiring Assessment, a workstyle questionnaire, and may also be given a role-related exercise such as coding before interviews start.

  2. 2

    Recruiter conversations

    Official
    Recruiter screenRemote

    One or two short calls over phone or video that check key skills for the role, share details about the team and ask about preferences such as location.

  3. 3

    Technical phone screen

    Reported
    Technical interviewRemote

    A data structures and algorithms coding interview. A second screen is sometimes added when the first does not give enough signal.

    Data structuresAlgorithms
  4. 4

    Interview panel

    Official +1
    Panel interview

    A panel of structured interviews, over video or in person, scored against the same rubric for every candidate. For engineers it is mostly coding, with system design added as seniority rises. No brainteasers, and AI tools are not allowed.

    CodingSystem designBehavioural
  5. 5

    Hiring committee and team matching

    Reported +1
    Final HR round

    Interview feedback is reviewed together before a decision, which can take several weeks. Candidates who pass are then matched with a team, with both sides opting in.

What comes up

Recurring themes from candidate accounts, not a question bank. Nobody is served by leaked question lists, least of all you in the interview.

  • Open-ended, role-related problems

    Official +1

    Questions are deliberately open so you can ask for clarification, state assumptions and refine a first answer. Interviewers are watching the reasoning more than the final answer.

  • Behavioural examples in STAR form

    Official

    Behavioural questions look for specific past examples rather than general statements, so a prepared set of short stories helps.

  • Data structures and algorithms

    Reported

    Coding rounds centre on classic algorithm problems. Reaching and explaining the optimal approach counts for a lot, even before the code is complete.

Worth reading before you apply

From the Sefism resource library, matched to the rounds above.

Roadmap
Coding Interview Playbook

A structured learning path through coding interview preparation that brings together data structures and algorithms fundamentals, recursion and the pattern-based approach to coding questions in one order. It totals 77 chapters and 1,054 lessons, with quizzes, flashcards and a certificate. Use it when you have plenty of material but no clear plan for what to study first.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 6 months
SubscriptionDetails
Roadmap
FAANG Coding Interview Roadmap

A bundle of five company-specific question courses covering the problems most often reported from Meta, Microsoft, Amazon, Google and Oracle coding rounds, each split into easy, medium and hard sets with worked solutions. It suits candidates who already know the core patterns and have a loop booked at one of these companies, and want to rehearse on the questions those interviewers are known to ask.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 4 months · Advanced
SubscriptionDetails
Course
Grokking Tech Salary Negotiations

A practical course on negotiating compensation in tech, from preparing and building a strategy to specific tactics, the full package beyond base salary, handling multiple offers and asking for a raise. It has tailored sections for fresh graduates and experienced engineers. It suits anyone with an offer coming, and anyone who has ever accepted the first number out of discomfort.

  • Career
  • Job search
Design Gurus · Career Growth · 1 week
SubscriptionDetails
Platform
AI Mock Interviews

On-demand mock interviews with an AI interviewer for coding and system design rounds. It asks questions, follows up on your reasoning the way a real interviewer would, and ends with detailed feedback and a custom improvement plan. It suits software engineers preparing for technical interviews who want to practise whenever they are free and repeat sessions until their answers feel natural.

  • AI
  • Job search
  • Career
Design Gurus · AI & Machine Learning · 45 minutes per session
Included with annual plan, also sold separatelyDetails
Cheat sheet
Sefism University to Job-Ready Cheat Sheet

The quick-revision companion to the University to job-ready roadmap: OOP, Git and engineering practice, data structures, DBMS, operating systems and networks, then projects, choosing a direction, getting experience and the hiring process. It has editions for first or second year, third year, and final year. Revise a chapter a week alongside your courses and before assessments.

  • Career
  • Job search
  • CS fundamentals
  • DSA
Sefism · Career Growth · Reference · Beginner
Community
ICPC (International Collegiate Programming Contest)

The official site of the ICPC, the university programming contest where teams of three share one computer for five hours and advance from regional contests towards the World Finals. It is where coaches register teams, where the current regional and World Finals rules are published, and where you find contests, results and past problems.

  • DSA
  • CS fundamentals
ICPC Foundation · Other · A season of qualifying contests each academic year
Browse the whole library

What it pays

Nothing collected for this company yet, and nothing worth guessing at. A made-up range is worse than no range because people negotiate against it.

Add to the Google page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Universities they recruit from

No sourced university links yet. A campus drive, a career fair appearance or an internship partnership is what puts a university here.

Add to the Google page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

How to actually get seen

Talk through your approach and assumptions out loud, since the rubric rewards visible reasoning. Do not use AI tools in interviews: Google states they are not permitted.

Sources

Whole profile last checked 2026-09-22.

Interviewed at Google? Fill in what changed.

Processes change, rounds get added, tests get replaced. If what you went through was different from what is on this page, tell me and I will update it.

Want me to refer you here?

Send me the role, your CV and a few honest paragraphs on why you fit it. Where I know someone inside and your profile matches, I will make the introduction. Where I cannot, I will tell you why and point you at the route that does work. You get an answer either way.

Ask for a referral to Google

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Add to the Google page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.