Coinbase Software Engineer, Compliance CXAE — full-stack Golang/React

Interview prep for Coinbase's Software Engineer role on the EAA Compliance CXAE team, building the internal platforms and tools that power compliance/KYC agent workflows. Expect full-stack questions across Golang and React, distributed-systems fundamentals (caching, event-driven architecture, observability on AWS/Kubernetes), and how you use generative AI responsibly in your engineering work. Solid prep for mid-level full-stack engineering interviews at fintech/crypto platform teams — note Coinbase publicly pilots an AI-conducted initial screening round.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

Likely format

Coinbase publicly discloses it pilots an AI-conducted initial screening interview round plus an AI note-taking/summarization tool for later human interviews.

What this interview tests

Full-stack feature ownership across Golang and React
Distributed systems: caching, event-driven architecture, observability on AWS/Kubernetes
Third-party tool/vendor integration decisions
Compliance/KYC-adjacent engineering rigor (correctness, auditability)
Responsible use of generative AI in the engineering workflow

Common question themes

Walk me through a full-stack feature you owned from design to production

How would you design a high-traffic service with caching and event-driven architecture on AWS/Kubernetes

Tell me about evaluating or integrating a third-party tool into an existing platform

How do you approach code quality and mentoring when your work affects compliance-sensitive workflows

Describe how you use generative AI tools in your day-to-day engineering while maintaining human oversight

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