Build the auth, billing, and Playground systems that let Cohere customers self-serve frontier AI

Cohere's Inference team is hiring a full-stack engineer to work across the platform layer that lets customers understand, trust, and pay for Cohere's models — improving auth/billing/payment systems, extending the interactive Playground, and building deployment management features. The role requires 5+ years writing clean backend code (Golang/React stack) and real experience with payment or subscription/usage-based SaaS systems, plus comfort writing minimal, low-resource, security-constrained code without leaning on the most popular libraries.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Payment/billing systems: subscription or usage-based SaaS, freemium models
Full-stack ownership across Golang backend and React frontend
Writing minimal, dependency-light code for low-resource, security-constrained environments
Auth and platform security for a customer-facing developer product
Reading and fixing code outside one's own module/codebase
Operating in fast-paced, shifting-priority environments

Common question themes

Design or debug a billing/payment system edge case (proration, metering, failed charges)

Full-stack feature you shipped end-to-end in Go/React or an equivalent stack

A time you had to avoid popular libraries due to security/low-resource constraints and built it yourself

Fixing an issue in code outside your usual area of ownership

Extending a self-serve product surface (like a Playground) for a new customer need

Navigating shifting priorities/ambiguity in a fast-moving team

How candidates describe it

Real Full-Stack 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 Cohere interviews