Great company and great people
Great company and great people
In general, I like working at Brex, and the people I work with are nice. The work-life balance is great; the company respects the off time.
The fintech industry as a whole is a little bumpy recently. Brex often tends to pivot a lot, so many reorgs can disrupt your flow.
Additional Ratings
Was this helpful?
Brex Interview Questions
Brex Interview Experiences
Software Engineer
I got in touch with the recruiter a few months back, but I wasn't really looking for a change at the moment. Recently, I came across a YC interview with the CEO and was impressed. So, I asked the recruiter and booked a technical phone screen. The te
Software Engineer
The interview process was very quick and well-streamlined. 1. Apply online 2. Recruiter call 3. One-hour coding phone call 4. Onsite (done remotely) with one behavior, one coding with API calls, one debugging, and one system design.
Software Engineer
The interview process was fair. The questions checked for normal ability to engineer, focusing on debugging and building API endpoints rather than LeetCode style problems. System design was surprisingly not transaction-based. The interviewers were en
Software Engineer
San Francisco, California, United StatesMay 1, 2019I got in touch with the recruiter a few months back, but I wasn't really looking for a change at the moment. Recently, I came across a YC interview with the CEO and was impressed. So, I asked the recruiter and booked a technical phone screen. The te
Software Engineer
San Francisco, California, United StatesSeptember 1, 2021The interview process was very quick and well-streamlined. 1. Apply online 2. Recruiter call 3. One-hour coding phone call 4. Onsite (done remotely) with one behavior, one coding with API calls, one debugging, and one system design.
Software Engineer
San Francisco, California, United StatesJune 1, 2022The interview process was fair. The questions checked for normal ability to engineer, focusing on debugging and building API endpoints rather than LeetCode style problems. System design was surprisingly not transaction-based. The interviewers were en
