Google SWE Interview: GHA and Coding OA Guide

Estimated read time: 7-9 minutes

Summary: The Google SWE online assessment stage is not guaranteed for every candidate, but the primary research lists Google Hiring Assessment and coding online assessment variants as possible early filters. This guide explains what the assessment stage can include, how the workstyle and coding formats differ, and how to prepare without assuming your process will look exactly like someone else's.

TL;DR + FAQ (read this first)

At-a-glance takeaways

• The assessment stage is possible, not universal, in the Google SWE process.
• The primary source names Google Hiring Assessment and coding online assessment variants.
• The Google Hiring Assessment is a workstyle or behavioral filter, while coding assessments test data structures and algorithms.
• The slug table marks this as relevant for Intern, New Grad/L3, L4, and L5+ candidates where role-dependent.
• Secondary feedback says assessment formats and timing can vary widely across candidates.
• Prepare for both consistency under a workstyle questionnaire and timed coding under pressure.

Quick FAQ

Does every Google SWE candidate get an online assessment?
No. The primary research says some candidates may receive a Google Hiring Assessment or coding online assessment.

Is the Google Hiring Assessment a coding test?
No. It is described as a workstyle or behavioral assessment.

Is the coding assessment the same as a phone screen?
No. It is timed and online, while the phone screen is a live interview with an engineer.

Should senior candidates expect this stage?
The source is less clear for senior levels. Treat it as possible, then follow your recruiter guidance.

---

1) When the assessment stage appears

The primary research places assessment after application review and before or around recruiter and technical screens. It names the Google Hiring Assessment and coding online assessment as possible steps for some candidates.

That wording matters. Do not assume every Google SWE loop includes this stage, and do not assume skipping it is a signal by itself. The same research notes that Google process ordering can vary by candidate, level, and pipeline.

Level matters here. Intern and New Grad/L3 candidates may be more likely to see early assessments, L4 candidates can see them depending on pipeline, and L5+ candidates should treat them as possible but role-dependent rather than guaranteed.

Takeaway: prepare enough to avoid being surprised, but let your actual recruiter packet define your process.

---

2) Assessment tasks you may face

The assessment stage can involve workstyle questions, coding questions, or both depending on the pipeline. These examples are grounded in the provided source material and secondary notes, and they should be treated as representative rather than guaranteed.

Workstyle assessment questions

• A priority changes late in the project. Do you re-plan privately first, or align with teammates and stakeholders before changing direction?
• You are blocked on a technical issue. How quickly do you ask for help, and what do you try before escalating?
• A teammate's mistake affects delivery. How do you respond in the moment, and how do you prevent the same issue next time?
• You are given an ambiguous problem with no clear owner. Do you wait for clearer instructions, or define a path forward and validate it?

Coding assessment question examples

• Given an array, minimize its amplitude after changing up to a small number of values. Explain which values you would change and why.
• Count the number of ways to split a string under the given validity rules. Then describe how your answer changes if the string is much longer.
• Given two rows of dominoes, find the minimum rotations needed to make one row equal. Return -1 if it cannot be done.
• Given a list of points, return the k closest points to the origin. Now discuss whether sorting all points is necessary.
• Given a sequence of asteroids moving left and right, return the state after all collisions. Walk through a case with repeated collisions.
• Maintain a collection with insert, remove, and query operations, then return how many subsets sum to a target. Explain the state you need to update after each operation.

---

3) How the assessment formats differ

The Google Hiring Assessment is described as a workstyle or behavioral questionnaire. Secondary notes describe a format where candidates answer a sequence of questions and may not be able to go back, so consistency matters.

The coding assessment is different. It is a timed programming test, and secondary feedback points to data structures and algorithms under time pressure. It may include topics like arrays, dynamic programming, sliding windows, stacks, and other core patterns.

Do this now: prepare for both. Have a workstyle mindset that is consistent and honest, and a coding mindset that prioritizes correctness, edge cases, and time management.

---

4) What Google is trying to learn

For the workstyle assessment, Google is looking for judgment, collaboration, comfort with ambiguity, and consistency. The source material frames it as a filter rather than a live interview.

For coding assessment variants, the signal is closer to early technical screening: correctness, speed, data structures, algorithms, and the ability to manage time without live interviewer guidance.

The assessment stage does not replace later interviews. It helps decide whether the process continues and what signal still needs to be collected.

---

5) Failure modes in the assessment stage

Assuming the stage is universal. It is possible, not guaranteed. Do not overread process differences.

Answering workstyle questions inconsistently. If you cannot go back, rushing can create contradictions.

Over-indexing on repeated questions. Secondary feedback says repeat questions are rare at Google, so use representative practice to learn patterns, not to gamble on exact repeats.

Ignoring edge cases in timed coding. Even a familiar-looking problem can hide constraints or follow-up difficulty.

Failing to manage time. A correct but incomplete solution may not be enough if you spend too long on the wrong path.

---

6) How to prepare for the assessment stage

Use two preparation tracks. For workstyle questions, think through how you handle ambiguity, blockers, team conflict, and changing priorities. For coding, rehearse timed fundamentals.

• Practice arrays, strings, stacks, heaps, sliding windows, graphs, trees, and dynamic programming.
• Set timers and practice moving from brute force to optimal reasoning quickly.
• Write down edge cases before you code, especially for simulation and dynamic programming questions.
• For workstyle questions, answer consistently with how you actually work under pressure.
• After each timed session, review whether your code matched your intended algorithm.

The assessment stage is not the whole Google SWE loop. It is one possible filter. Prepare seriously, then keep your broader interview prep focused on live coding, communication, Googleyness, and team matching.

---