I started with an interview that felt straightforward and respectful, and the recruiter also seemed involved and supportive. Then I moved into a technical coding interview where the interviewer kept requiring me to talk while coding. I found that really counterproductive, because interrupting me constantly made it easy to lose focus, and it added anxiety to an already stressful live coding environment.
Even though I was trying to work through the requirements, the back-and-forth with constant interruption threw me off. The interviewer did interrupt to try to help, but it ended up hindering more than supporting, and I didn’t implement every requirement because the pressure and being observed were too much.
> 1 year
Average Positive Brazil
My process felt pretty reasonable in terms of difficulty for the time I was given—most of the challenge itself wasn’t wildly beyond what you’d expect. But one step stood out because it took five hours total, with three of those hours specifically reserved for the technical challenge.
The technical part was aligned with the time slot, so I didn’t feel like I was being set up with an impossible cutoff. Still, spending five hours doing an interview was exhausting in a way I wasn’t prepared for. By the time I got through it, the fatigue was real, and it colored how I experienced the day more than the actual difficulty of the work. I ended up not getting an offer, and honestly the biggest takeaway for me was that the long, single stretch mattered more than the technical content.
> 1 year
Average Negative São Paulo, São Paulo
This was my second try with Brex. The first time I applied through the careers page and didn’t get any answer, so when things started moving on the se…
> 1 year
Average Positive United States
I started with a recruiter call where the communication was clear and frequent, and I always felt like I knew what was coming next. From there, I did …
Unlock every Frontend Engineer interview experience
