Google Stockholm interview, decoded.
Updated · Sources at the end
Google runs one loop everywhere, and Stockholm sits it in full: a recruiter screen, one or two technical phone screens, an onsite of four to five rounds (coding, system design from L4, a Googleyness and leadership conversation), a hiring committee that reads the interviewers' notes without meeting you, then team matching with managers who have a headcount. What is Stockholm-specific is the office and the money. The Kungsbron office is Google's Nordic hub for engineering, sales and marketing, with current engineering postings on Google Meet, Google Cloud generative AI and site reliability, and it pays a senior engineer a median of SEK 1.72M in total pay, the highest figure in this city by a wide margin.
Free · 2 minutes · no account
The questions for your exact Google Stockholm role and level.
Interviewing at Google Stockholm? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.
Who Google Stockholm hires
Google Stockholm hires software engineers, site reliability engineers and engineering managers for a small number of product teams, alongside Cloud customer engineers, sales and marketing. Recent postings name web development for Google Meet, AI and ML engineering for Google Cloud generative AI, and an SRE internship; some Stockholm roles state that in-person interviews are required. The office is small next to Spotify or Klarna, so openings come in single digits and team matching can be the slow part.
What is the Google Stockholm interview process?
The loop below is Google's standard one as documented by candidate guides in 2026, and Stockholm candidates report the same shape; the differences are which rounds are in person and how long team matching takes when the office has few teams.
Background, location and visa, which product areas you fit; recruiters increasingly ask about Cloud and AI experience. Level is set here, and level decides the loop.
Experienced candidates usually skip it and go to the phone screen. Separately, Google may send its Hiring Assessment, a work-style questionnaire, before interviews; see the Google Hiring Assessment guide.
A medium-to-hard coding problem, thinking aloud, with time and space complexity said without prompting.
Two or three coding rounds, a system design round from L4 upwards, and a Googleyness and leadership round: collaboration, ambiguity, how you handle disagreement and feedback.
A committee reads every interviewer's written feedback and decides on hire and level. Consistent, well-documented rounds matter more than one brilliant one.
Finding a team with headcount that wants you. In a small office this is the stage that stretches; be open to more than one product area and say so.
What Google Stockholm screens for
Google grades four attributes in every interview and writes them up for the committee; the Googleyness round is the one candidates under-prepare.
- General cognitive ability: how you take an open problem apart, said aloud
- Role-related knowledge: coding fluency and, from L4, systems at scale
- Leadership, including emergent leadership without a title
- Googleyness: comfort with ambiguity, collaboration, a bias to action, doing the right thing
- Consistency across rounds, because a committee compares the write-ups
Google Stockholm interview questions
Candidate-reported themesThe coding and design questions are the well-documented Google set; the themes below are what 2026 guides and Stockholm postings point to.
Behavioural & motivation
- Why Google, and why the Stockholm office rather than a larger one?Listening for: Specificity · Connection · Research
- Tell me about a time you led without being the manager.Listening for: How they noticed · Why it mattered · How they took it on
- Describe a decision you made with incomplete information. What did you do when new information arrived?Listening for: The gap · How they closed it · Cost of being wrong
- Tell me about a disagreement with a teammate about a technical approach and how it was resolved.Listening for: Engagement · Professionalism · Resolution
- Give an example of feedback that changed how you work.Listening for: The feedback, specifically · How you took it · The lasting change
Technical
- Practice: given a grid of land and water cells, count the islands. Talk through your approach and its complexity.Coding, two to three rounds: Graphs, trees, dynamic programming, string and array problems at medium to hard; complexity stated; clean code in a shared editorListening for: Sound approach · Complexity unprompted · Edge cases and clarity
- Practice: design a key-value store that serves low-latency reads for a global product. Walk through storage, caching and consistency.System design, L4 and up: A service at Google scale: storage, caching, consistency, the trade-offs said before the interviewer asksListening for: Requirements and numbers · Storage and caching · Consistency trade-offs
- Code comprehension, piloted 2026: A 60-minute round on an unfamiliar multi-file codebase with Gemini as an assistant, announced in May 2026 for junior and mid-level roles in select US teams; grading prompt use, output validation and debugging. Not reported in Stockholm yet
- Practice: a video call web client drops frames when many participants turn on their cameras. How would you find and fix it?Meet and Cloud domains: Web performance and real-time media for Meet; ML serving and generative AI systems for Cloud, per current Stockholm postingsListening for: Measures first · Likely causes named · Fix and trade-off
- Practice: latency for a service doubles in one region while traffic looks normal. Walk me through how you investigate.SRE: Linux, networking, distributed systems, incident reasoning, for the SRE roles the office hiresListening for: Scopes the problem · Works through layers · Mitigates, then fixes
These are the reported themes, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →
Predict my Google Stockholm questions →Pay
Levels.fyi for software engineers at Google in Greater Stockholm, read on 13 September 2026: the median package is SEK 999K, from SEK 947K at L3 to SEK 2.72M at L6. Stock is the difference from every Swedish employer: an L5 reports SEK 1M base plus SEK 644K a year of stock and SEK 72K bonus, against Spotify's SEK 980K base plus 185K stock at senior. Google's Stockholm ladder starts where Spotify's ends. Our Stockholm salary page puts them side by side.
Google Stockholm software engineer salary in Stockholm, next to the rest of the city →
How to prepare for a Google Stockholm interview
- Prepare the standard Google loop, not a local one. Two to three coding rounds at medium to hard with complexity said aloud, and a system design round from L4, decide the committee's read; there is no Stockholm shortcut.
- Write for the committee. Every interviewer documents you against the four attributes for people who will never meet you, so narrate your reasoning, name trade-offs, and finish each problem cleanly. A quiet correct answer reads badly on paper.
- Prepare the Googleyness round as seriously as the coding. Leadership without a title, ambiguity, disagreement resolved, feedback taken: one story each, with the outcome.
- Ask the recruiter which Stockholm teams have headcount before the onsite, and prepare for that domain (Meet, Cloud generative AI, SRE). In a small office, team matching is the stage that stalls; being open to two areas shortens it.
- Get the level right on the recruiter call. L4 versus L5 decides whether you sit system design and what the offer is worth; know which you are applying for and why.
Google's loop is documented by many guides and this page relies on them for its shape; what is specific to Stockholm (which teams hire, in-person rounds, team-match time) comes from the office's own postings and is thin. Treat the loop as reliable and the Stockholm colour as current at the time of writing. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.
Also interviewing at EA DICE, Paradox Interactive or Spotify? Their guides follow the same format, from the first screen to the offer.
Knowing the questions isn’t the same as answering them out loud. Run a Google Stockholm mock: spoken answers, coached on the spot. Your first mock is free.
Run a Google Stockholm mock →FAQ & sources
What is Google Stockholm's interview process?
The loop below is Google's standard one as documented by candidate guides in 2026, and Stockholm candidates report the same shape; the differences are which rounds are in person and how long team matching takes when the office has few teams. The stages, in order: Recruiter screen; Online assessment; Technical phone screen; Onsite loop; Hiring committee; Team matching.
What does Google Stockholm look for in candidates?
Google grades four attributes in every interview and writes them up for the committee; the Googleyness round is the one candidates under-prepare. General cognitive ability; Role-related knowledge; Leadership, including emergent leadership without a title; Googleyness.
What questions does Google Stockholm ask in interviews?
The coding and design questions are the well-documented Google set; the themes below are what 2026 guides and Stockholm postings point to. Technical themes: Coding, two to three rounds; System design, L4 and up; Code comprehension, piloted 2026; Meet and Cloud domains; SRE.
How do I prepare for a Google Stockholm interview?
Prepare the standard Google loop, not a local one. Two to three coding rounds at medium to hard with complexity said aloud, and a system design round from L4, decide the committee's read; there is no Stockholm shortcut. Write for the committee. Every interviewer documents you against the four attributes for people who will never meet you, so narrate your reasoning, name trade-offs, and finish each problem cleanly. A quiet correct answer reads badly on paper.
- 01TechPrep, Google's interview process (2026)the recruiter screen, the online assessment for L3 and new grads, one or two technical phone screens, the four to five round onsite with system design from L4, the hiring committee reading feedback rather than a single manager, and team matching taking a week to a couple of months
- 02Exponent, Google's AI-assisted coding interview (2026)the May 2026 pilot of a code comprehension round with Gemini for junior and mid-level roles in select US teams, and what it grades
- 03Google Careers, jobs in Stockholmcurrent Stockholm postings including senior software engineer roles for Google Meet web development and Google Cloud generative AI, and an SRE internship; the note that some roles require in-person interviews
- 04Office Snapshots, Google's Stockholm officethe Kungsbron 2 office as the merged Nordic hub for engineering, sales and marketing
- 05Levels.fyi, Google software engineer pay in Greater Stockholmthe SEK 999K median package, the L3 to L6 medians with base, stock and bonus
- 06Glassdoor, Google jobs in Stockholmabout ten open positions in September 2026
Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.
Prep for a real Google Stockholm role
Practise your Google Stockholm interview, out loud.
Paste a real Google Stockholm posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free. Calibrd is built in Stockholm, by a hiring manager who has run engineering hiring here, so this is a loop we know from the other side of the table.
Free to start · No card · Encrypted at rest, never used to train AI, remove anytime