Brex interview, decoded.

Brex does not publish its interview process, so the stages below come from candidate reports. PracHub's summary puts the loop at about three to five weeks, with the onsite taken in one day or split across two. Candidates also report slow, disorganised processes and a recruiter call of under fifteen minutes, so ask the recruiter for the rounds and the timeline up front. None of the sources say whether the loop changed after the Capital One deal.

Brex publishes six values on its careers page, and its manifesto adds the tone: Brex is not a place to coast, and its CTO still codes.

• Dream big: think 10x, not 10%
• Ownership: if it's broken, you fix it
• Impatient optimism: move fast, stay positive
• One Brex: no silos, no egos
• Customer obsession: build something loved
• Growth mindset: ask questions relentlessly

The coding problems recur across years and have their own section below. The behavioural questions follow Brex's values.

These come from candidate posts on LeetCode Discuss between 2021 and September 2026 and from PracHub's list of Brex questions. Most are problems in parts: a first version, then new rules. Keep the design open enough that each part is an addition and not a rewrite.

• Splendor: can a player afford this card?: Write can_purchase() for a card with a gem cost and a player's gems. Start with a straight comparison per colour, then add the part that follows: discounts from the cards the player already owns, which reduce the gems each new card costs. The September 2026 follow-up asks what changes when the same player sends several purchase requests at once: talk about locking or versioning the player's gems and making each purchase atomic.
• A task scheduler with prerequisites: Reported for a phone screen in February 2025, built in steps: add, complete and get the next task, then prerequisites, then a full completion plan. Keep tasks and their dependencies in maps, compute what is ready from in-degrees, and turn the plan into a topological sort that reports a cycle if there is one.
• Suspicious activity: at least k matching attributes: Reported from 2021 to 2022. A new activity is suspicious if it shares at least k attribute values with any known suspicious one. Compare attribute by attribute and stop as soon as k match; if the known list is large, index it by attribute value so you only compare candidates that share something.
• Transactions from a live API: Page through the endpoint until there is no next page, then answer each part from the list you built: the count, the card with the highest spend, and merchants with a charge every seven days or every month. For the recurring check, group by merchant and card, sort by date and test the gaps, with a tolerance for months of different lengths.
• Fix five failing tests without refactoring: Run the tests first and read what each expects. Explain in business terms what the code is supposed to do before you change anything, then make the smallest fix for each failure and rerun. The reported codebase was a holiday and delivery-date calculator, so watch weekends, holidays and off-by-one errors on dates.
• A string calculator: '5 times (20 plus 30)': Reported in October 2024 with addition and multiplication. Tokenise the words into numbers and operators, then evaluate with operator precedence and parentheses, using two stacks or recursive descent.
• A multi-select colour dropdown in React: An input that opens a list, lets the user select and deselect several colours, and shows the selection. Keep the selected set in state, make it usable with the keyboard, and close the list on an outside click.

PracHub also reports, from August 2025, a round where you build a small full-stack transactions app with an AI coding tool such as Cursor and prevent negative balances. No other source confirms it, so ask the recruiter whether it is part of your loop.

Levels.fyi figures for Brex software engineers, from snapshots taken in 2025 before the acquisition and read on 25 September 2026: a US median of $330K, $395K in the San Francisco Bay Area, $285K in New York, CA$362K in Canada and R$713K in Brazil, on small samples. Brex posts base ranges on its ads: $152K to $190K for software engineer II, $192K to $240K for senior and $240K to $300K for staff, with the same ranges posted for Vancouver. São Paulo ads post no range. Calibrd benchmarks the pay on any posting you scan against its level and location.

1. Do the Splendor purchase problem in parts, then answer the concurrency follow-up out loud: what locks, what is atomic, what happens on a retry.
2. Practise paging through a real API and aggregating the result in under an hour, including a recurring-charge check by merchant.
3. Rehearse a debugging round: open an unfamiliar repo, run the tests, explain what the code is for, and fix the failures with the smallest change.
4. Prepare a payments design: card points earned and redeemed, or a transfer that stays correct through retries, crashes and concurrent requests.
5. Talk while you code. Candidates are scored on communication as well as on how many parts they finish.

This guide covers Brex's software engineering loops. Sales, product, legal and risk roles run different processes. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

• 01LeetCode Discuss, Brex SWE II looprecruiter, a task scheduler phone screen, then the transactions API round, the debugging round (five failing tests, one or two line fixes, no refactor), a points system design and a hiring manager round; February 2025
• 02LeetCode Discuss, Brex software engineer interviewthe Splendor purchase problem with a concurrency follow-up; September 2026
• 03LeetCode Discuss, Brex phone interviewcan_purchase() for a card and a player's gems; April 2022
• 04LeetCode Discuss, Brex phone screen: suspicious activitya new activity matching at least k values of a known suspicious one; 2022, also reported in 2021
• 05LeetCode Discuss, Brex technical rounda calculator for addition and multiplication from a string; October 2024
• 06PracHub, Brex interview questionsthe discounted card purchase, a peer-to-peer transfer design, card points from transactions, a React colour multi-select, a debugging round and an AI-assisted full-stack build (August 2025); an aggregator, so single-source items are marked as such in this guide
• 07PracHub, Brex software engineer interview guideabout three to five weeks, the onsite in one day or two, and candidate complaints about slow processes and a short recruiter call
• 08Brex job board (Greenhouse)258 open roles on 25 September 2026, 61 in engineering, the three office days and posted base ranges
• 09Brex careersthe six values, the San Francisco and Salt Lake City offices, and 'a wholly owned subsidiary of Capital One'
• 10Brex manifesto'Brex isn't a place to coast' and 'Our CTO still codes'
• 11TechCrunch, Capital One acquires Brex$5.15B in cash and stock, less than half the last private valuation of $12.3B; 22 January 2026
• 12Levels.fyi, Brex software engineer (archived August 2025)the $330K US median and the per-level figures
• 13Wikipedia, Brexfounded on 3 January 2017 by Henrique Dubugras and Pedro Franceschi

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.