Google

Google Software Engineer Technical Screen Questions

34+ questions from real Google Software Engineer Technical Screen rounds, reported by candidates who interviewed there.

34
Questions
8
Topic Areas
10+
Sources

What does the Google Technical Screen round test?

The Google technical screen covers core Software Engineer skills in a structured interview format. Candidates should expect a mix of coding problems, technical knowledge questions, and scenario-based discussions.

Top Topics in This Round

Google Software Engineer Technical Screen Questions

I'd appreciate you guys input on this. Was given a choice between coding or research domain interview for the first round, I'd like to understand how the latter works usually?

Be wary of scams - Buckeye Mountain

Career,Job Search,Scam Warning 2026

Been applying for many jobs like most people here and wanted to warn everyone about a scam I was almost a victim of. I received an email about a potential job offer from Buckeye Mountain, a railroad h

Or have the moved on to a better coding editor? Out of all the document links shared by the recruiting coordinator, the one link opens to something like this (instead of a normal google doc). I wanted

Curious about my google rating for interview

Graph,Breadth First Search,Dijkstra,Shortest Path 2026

This was for early career campus role Interview went as such Interviewer came in Asked some variation on shortest path to destination graph question. I initially said something like DFS but he said I

Help Needed! Google SDE 3 (USA) in 1 week What actually shows up?

Interview Prep,Graph,Dynamic Programming,Binary Tree 2026

Got a Google SDE III interview (USA) in a week. 2x45 min coding rounds on Meet. Been doing LeetCode, but don’t want to grind randomly this close. Want to focus smart. What actually shows up most? * Gr

Google Technical Interview Experience: Hire or Lean Hire Verdict?

Hash Map,Time Complexity,Space Complexity,Interview Feedback 2025

The main problem was solved within 30-35 minutes without hints, but several issues occurred during the session. A small bug remained in the code that could not be identified even after the interviewer

25 essential Stack, Queue, and Linked List problems for technical interviews

Arrays,Dynamic Programming,Graph,Hash Table,Linked List,Queue,Recursion,Sliding Window,Sorting,Stack,Strings,System Design,Two Pointers 2025

Stack Problems **1. Valid Parentheses** - [LeetCode 20](https://leetcode.com/problems/valid-parentheses/) - **Solution Pattern:** Basic stack matching. Push opening brackets; pop and check matching

Hi everyone, I have a Google software engineering interview coming up soon, and I’m brushing up on my Data Structures and Algorithms preparation. I’m trying to prioritize my study time and wanted to g

There are 100 passengers lined up (in a random order) to board a plane. The plane is fully booked, meaning there are exactly 100 seats available. Due to a technical malfunction, the first passenger ch

I came to know about the opportunity through https://www.google.com/about/careers/applications/jobs/results/ Google's website. Applied for the same with my resume. After t...

I had four interview rounds: Googliness Round: This went well. I\u2019m not sure if it was perfect, but I gave good answers. I can confidently say that it wasn\u2019t bad, and...

Gave Interview for Google Intern Oncampus Company: Google Role:SWE Intern Stipend: 1.23LPM Location: Bangalore, Hyderabad, Pune College: DTU (DCE) Branch: CSE No of Rounds: 2 Duration:45 mins Both rounds were Technical. Round-1: Given a graph with n nodes, where one...

This was my 1st round of my Google interview of Machine coding. The interviewer was Indian asked me real time relevant problem. Problem Statement : The application we are building...

I interviewed for google L4 Position almost 2 months ago, and gave 3 rounds of DSA, 2 were planned before-hand, in first round I got a lean-hire, and in the...

Imagine we design a simple file system metadata. There are 2 types of entities: \'file\' and \'directory\'. Each entity is given an integer \'entity id\' and has a \'name\'. File...

Google L4 | 1st Coding round

Dynamic Programming 2024

You are given an array of integers representing the weights of chocolates. Your goal is to minimize the cost of transforming this array into either an ascending or a descending...

I just wanted to let you i got one Strong Hire, Hire and Lean Hire in coding rounds. Strong Hire in Googlyness. Team matching was done and got SOS from...

I was given a log file of conversation like this: "maria: hi, john: hello hi bye bye, maria: pls dont go" and a helper function parse_log that would process the...

I have recently interviewed with Google fot L4 position. I have total 7.7 years of experiances. I have completed all interview rounds at google for L4, after HC dicussion they are saying...

Recently I had a interview with google for screening round. Huffman decoding question asked. I feel it is bit tough for screening round. Question - you are given input as {\'a\':2,...

What to Expect in the Google Technical Screen Round

The Google Software Engineer Technical Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 34+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.

Reports tagged with the Technical Screen round at Google show recurring patterns in difficulty and topic distribution. The Technical Screen round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.

How To Prepare for This Specific Round

Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.

Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.

Technical Screen Round Timing and Format

The Technical Screen round at Google typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.

Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.

Common Failure Modes in This Round

Reports tagged "no hire" at Google Software Engineer Technical Screen commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.

The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.

See All 34 Questions from This Round

Full question text, answer context, and frequency data for subscribers.

Get Access