There are fewer meetings than other companies I've worked for. A lot of decisions are made async, fostering a strong written culture. We use new technologies and tackle lots of cool challenges.
Lots of documents, but some of them are outdated, and it is hard to filter out old and irrelevant information (AI chats seem to help).
Management sometimes feels out of sync with engineers.
Try to really understand what is happening in the teams from a technical perspective too. Morale and well-being are important, but also understand the technical challenges being faced. Showing leadership on that front is important too, to be respected.
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