Overall, this was one of the best interview experiences I've ever had.
The process may vary slightly by domain (mobile, front-end, data, etc.), but for me, it started with a recruiter call, a phone screen, and a 4-round virtual onsite. Each round was one hour.
The phone screen involved a multi-stage question that was probably a LeetCode Hard in total. It was very open-ended as to how you solved it, and each question stage built upon the next, so it was important to start with a good, generic base that could be expanded upon later.
The virtual onsite consisted of four rounds: another coding round, a debugging round, systems design, and a behavioral round. The stages at this point felt very practical, closer to how real development feels.
During the coding round, they gave me a sample API to hit, and we worked through a multi-stage set of problems that included some API response parsing and algorithm problem-solving, but it was quite different from a normal set of LeetCode problems. My interviewer gave a few hints here and there.
The debugging round had me resolve some failing test cases in a sample repo. Again, very practical, the real challenge was learning what different elements in the code were meant to do and then finding the bugs. The interviewer was a bit quieter in this round, but I think it's because they wanted to see how I worked to solve problems in a new codebase.
The systems design interview varies heavily by team, but I'll just say it's probably similar to other companies. Design a system that would exist in your domain, discuss trade-offs, etc. The interviewer bounced some ideas, and we discussed pros, cons, and alternatives. It felt almost like a design meeting, in a good way.
Lastly, the behavioral round. This was the most important of the bunch. Pretty similar to other companies, I would say, but Brex puts a lot of emphasis on its values. Describe a time you did XYZ; what were the results? I prepared some stories from my work history that I thought aligned with the Brex values, using the STAR method to help organize my thoughts.
Then, after that, it was feedback, then the offer stage!
The recruiter was very responsive and incredibly helpful in preparing me for each round. The engineers I spoke to during the interviews were transparent about the company, and even though the interviews were very difficult, I thoroughly enjoyed the challenge and conversations that came from each one. Honestly, one of the best interview experiences I've had from start to finish.
nda nda nda nda nda
The following metrics were computed from 26 interview experiences for the Brex Software Engineer role in United States.
Brex's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Brex's Software Engineer interview process in United States.