Build the data pipeline infrastructure that powers Google's Threat Intelligence Group

On the Data Pipelines team within Google Threat Intelligence Group (GTIG)-Tech, you'll build and scale infrastructure that ingests threat intelligence data sources and delivers them to analysts, Alphabet security teams, and customers. Expect deep security/privacy software experience plus large-scale data pipeline engineering.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Google SWE process typically: recruiter screen, 1-2 technical phone screens (coding), then an onsite loop covering coding, system design, and Googleyness/leadership behavioral rounds

What this interview tests

Designing and scaling threat-intelligence data ingestion pipelines
Building software for data privacy/security (e.g., identity and access management)
Data storage methodologies: SQL/NoSQL, normalization, bulk pipelines
Production-grade software design and architecture
Technical leadership and cross-team influence on security-critical systems

Common question themes

Design a data pipeline that ingests and normalizes threat intelligence from many heterogeneous sources at scale

Describe a time you built software for identity and access management or another security/privacy-critical system

How would you choose between SQL and NoSQL storage for high-volume, evolving security data

Walk through a production issue you triaged in a data pipeline and how you traced the root cause

Tell me about a time you influenced a technical design decision on a security system without formal ownership

How candidates describe it

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

Bloomberg · Senior Software EngineerOffer

Bloomberg Senior Software Engineer Interview: Five Rounds, Offer

A Senior Software Engineer candidate applied to Bloomberg's London office through the company's careers site and, after an initial screen, went through five separate on-site conversations covering coding, system design, a recruiter chat, and a hiring-manager round, ultimately accepting an offer.

Interviewed October 2022 · London, United Kingdom

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

View the original posting

All Google Senior Software Engineer interviews

All Google interviews