Backend engineer on Brex's Credit Limit Engineering team, building the systems behind credit decisioning and risk management

Interview for a Software Engineer II, Backend role on Brex's Credit Limit Engineering team, owning underwriting engine, bank-connectivity, and credit-decisioning systems. Expect deep technical questions on distributed systems, event-driven architecture, and serving ML models with strict latency requirements in a regulated fintech environment.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Backend systems in Kotlin/Micronaut
Real-time financial data pipelines
Event-driven credit decisioning architecture
Serving ML risk models in production with latency constraints
Bank connectivity integrations (Plaid/Finicity/Teller)
Operational ownership (on-call, observability) for mission-critical systems

Common question themes

Design a real-time pipeline for processing millions of financial transactions with sub-second decisioning latency

How would you integrate a PD/affordability ML model into a live underwriting flow without breaking SLAs?

Walk through a time you owned a problem end-to-end, from API design to data model to production observability

How do you approach testing and reliability for systems that manage large amounts of financial exposure?

Experience with Kafka/event streaming and distributed systems trade-offs

Your experience in a regulated or fintech domain and what changes about how you build there

How candidates describe it

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

All Brex interviews