Senior

Senior SRE for Pinterest's Compute SRE team, building the future on Kubernetes/EKS

Join Pinterest's Compute SRE team ensuring every workload runs smoothly on Kubernetes at massive scale, with hands-on work like implementing Karpenter on EKS. This Toronto-based, mostly-remote role (1-2 office days per half) requires 4+ years of Python/Golang, deep EKS/Kubernetes debugging skill, and demonstrated fluency using AI coding tools like Cursor/Copilot/Claude as part of daily engineering work.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Pinterest publishes its AI-in-hiring philosophy; expect interviewers to probe how you think and explain your approach, including how you use AI tools, not just the final answer.

What this interview tests

Kubernetes/EKS deploy patterns, rollout safety, debugging
Infrastructure automation with Terraform, Buildkite, ArgoCD
AI-assisted engineering workflow with critical verification
SLI design and toil reduction
Capacity and performance management at scale
Cross-team collaboration on shared infra

Common question themes

Walk me through a Kubernetes/EKS incident you debugged end to end

Describe implementing or improving an autoscaling system like Karpenter

Give an example of using Claude/Copilot/Cursor and how you verified its output

How do you design an SLI that's actually actionable, not vanity

Tell me about automating away a recurring source of operational toil

How would you manage capacity for a workload spanning public and private cloud

How candidates describe it

Real Sr. Production Engineer 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 Pinterest interviews