Brex·Full Stack Engineer

Brex Full Stack Engineer interview experience

No offer

Easy

Negative

San Francisco, CAPosted Apr 2020 · Candidate report, summarized by Dataford

My interview sequence had four parts—coding, frontend, system design, and values—and the whole thing revolved around real-world scenarios.

But I left feeling like the overall difficulty and evaluation didn’t match what I expected. The coding and system design questions came across as broad and, honestly, kind of uninteresting, and I answered with that gap in mind.

The frontend question measured performance and was the most engaging part of the day for me. I expected some feedback to be coherent, but the follow-up notes I received didn’t really make sense. The feedback implied I was missing something I could’ve refreshed quickly, and it also felt confusing that the process would test for a gap in React if that was the skill

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Brex Full Stack Engineer interview guideThe full process, round by round, with the question bank Practice Full Stack Engineer interview questionsReal questions from this role across companies All Brex interview guidesEvery role we cover at this company