← Back to Directory

Brex interview notes, page 2 of 2

Mid-sized

Screna has 14 Brex interview write-ups. The most reported round is the technical phone screen (5).

14 interview notes · updated Jul 2026

Brex·Software Engineer·Technical Phone Screen

Jun 2026
Brex frontend coding round, one meaty React question that took up the whole session. The problem itself was well-scoped but the trade-offs discussion at the end is where things got interesting.
  • Build a React component that lets users multi-select colors from a dropdown, shows a count of selected colors, and renders a table of properties for each selected color. Also discuss trade-offs around state shape, performance with large lists, and accessibility.

“I jumped straight into useState for the selected set and felt pretty good about that.”

View Post

Brex·Software Engineer·Recruiter / HR Screen

Jun 2026
Short behavioral screen for a software engineer role at Brex, just the one question about strengths.
  • What are your strengths or main advantages as a candidate?

“Pretty standard opener but I still fumbled it a bit.”

View Post

Brex·Software Engineer·Take-home Assignment

Jul 2026
Brex take-home for a software engineering role. You build a small full-stack app that handles monetary transactions, and they want the whole thing: API, frontend, persistence, validation, tests, and a README. More involved than it sounds.
  • Using an AI coding assistant, build a minimal full-stack web application that supports basic monetary transactions and account balances. It should expose a REST or GraphQL API for creating credit and debit transactions, persist data, include a simple frontend to submit and view transactions, validate inputs, prevent negative balances, and come with basic tests and a README.

“The scope feels contained until you actually sit down with it.”

View Post

Brex·Software Engineer·Technical Phone Screen

Jul 2026
Coding round at Brex for a software engineer role. The problem was a card game purchase system, which sounds simple but has enough edge cases in the discount logic to trip you up if you're not careful.
  • Implement canPurchase and purchase methods for a gem-based card game, where players get discounts based on previously purchased cards and must pay the remaining gem cost from their current inventory.

“The discount logic is where I got sloppy at first.”

View Post