Building the internal tools that power Coinbase's customer support agents

A full-stack engineering role on Coinbase's Enterprise Applications and Architecture (EAA) org, building the platforms CX agents use to resolve customer issues, using Golang, gRPC, TypeScript, and React. Requires 3+ years of experience shipping user-facing web apps plus hands-on Go backend work with gRPC, event-driven architectures like Kafka, and production operations on AWS with Kubernetes and Terraform.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Coinbase is piloting AI-run initial screening interviews with dynamic conversation, alongside an AI note-transcription tool for human interviewers.

What this interview tests

Full-stack development: React/TypeScript frontend + Go/gRPC backend
Event-driven architecture and messaging (Kafka or similar)
Production reliability patterns (rate limiting, caching, circuit breakers)
Third-party API/SaaS integration in production systems
AWS operations with Kubernetes, Terraform, CI/CD
Responsible use of generative AI copilots in daily workflow

Common question themes

Walk through a full-stack feature you shipped end to end, React frontend to Go/gRPC backend

Describe integrating a third-party vendor API or SaaS platform into a production internal tool

How have you implemented rate limiting, caching, or circuit breakers on a production service

Tell me about an event-driven system you built using Kafka or similar

How do you use generative AI tools in your daily engineering workflow, and how do you validate their output

Describe explaining a technical tradeoff or risk to a non-technical CX or product stakeholder

How candidates describe it

Real Software 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 Coinbase Software Engineer interviews

All Coinbase interviews