High compensation for their roles (or at least used to be).
Easy requirements, easy problems to solve.
Need to involve way more people to build consensus for simpler tasks.
Excessive architecting and internal debating via passive async document writing process, similar to Google.
The interview process included several rounds: HR screening, a code challenge, a debugging challenge, system design, and a final alignment call. It was a very good assessment, apart from the multiple steps. All the interviewers were really nice and
Accessible and with a YouTube video to indicate what the process will be like on the Brex Br channel. It's a different process due to the debugging interview, but it's quite fun. It's worth doing.
The first step was a problem-solving task on CodeSignal within a 70-minute timeframe. I wanted to be honest, so I didn't try to find answers or algorithms on the internet. LeetCode-based problems basically don't tell anything about your lifetime expe
The interview process included several rounds: HR screening, a code challenge, a debugging challenge, system design, and a final alignment call. It was a very good assessment, apart from the multiple steps. All the interviewers were really nice and
Accessible and with a YouTube video to indicate what the process will be like on the Brex Br channel. It's a different process due to the debugging interview, but it's quite fun. It's worth doing.
The first step was a problem-solving task on CodeSignal within a 70-minute timeframe. I wanted to be honest, so I didn't try to find answers or algorithms on the internet. LeetCode-based problems basically don't tell anything about your lifetime expe