Build the data pipeline infrastructure powering Google's Threat Intelligence Group

Join the Data Pipelines team within Google Threat Intelligence Group (GTIG)-Tech, building and scaling infrastructure that ingests threat data sources and delivers intelligence to analysts and security teams across Alphabet. Requires software design/architecture experience plus hands-on background building software for data privacy or security.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Google SWE loop: recruiter screen, technical phone screen(s) with coding, onsite loop covering coding, system/data pipeline design, and Googleyness/leadership; hiring committee review follows.

What this interview tests

Bulk data pipeline design for large-scale ingestion
Security/privacy-aware software design (identity and access management)
Data storage and normalization tradeoffs (SQL vs NoSQL)
Testing, launching, and maintaining production software

Common question themes

Design a data pipeline to ingest and normalize large volumes of threat data

Tell me about building software with security or privacy as a core design constraint

Data structures and algorithms coding problem

How do you choose between SQL and NoSQL storage for a given pipeline

Describe testing and launching a software product, including what broke post-launch

How candidates describe it

Real Software Engineer III interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Google Software Engineer interviews

All Google interviews