J'ai postulé via une agence de recrutement. J'ai passé un entretien chez Braze (New York, NY) en mai 2021
Entretien
Was referred to Braze via a third party recruiter. Informational round was pretty standard, and then I had a technical round with a backend engineer. He was nice, but there was a strong emphasis on the prompt being intentionally vague to test my collaboration skills. This meant that during the questions, he would refuse to define or write what he wanted me to do, it could only be discovered through examples. This took up a significant amount of time, and since I was one line away from solving it, it was too bad I didn't pass because of their own process.
Questions d'entretien [1]
Question 1
1. Test if a string containing parentheses and other characters is balanced with its parentheses
2. Return the "depth" of a balanced parentheses string, meaning the maximum number of nested parentheses
3. Return the "breadth" of a balanced parentheses string, meaning return the max number of parentheses together along the same depth. This part is confusing and took about 20 minutes to explain in their roundabout way, but basically with the following input, "( () () () ) ()", your function should return 3 due to the number of closed parentheses at a depth level of 1.
Didn't even get that far. Was scheduled with a recruiter, and then last minute cancelled and introduced to another person who rescheduled me with a new person. The new recruiter was outright rude and unprofessional. I then found out that my original recruiter was fired. Seems like red flags all around. Avoid.
Questions d'entretien [1]
Question 1
Address my short tenure in my resume (laid off) and my career gap. Not interested in anything else.
J'ai postulé en ligne. J'ai passé un entretien chez Braze (São Paulo, ) en janv. 2026
Entretien
Check the comments about toxic culture and the interview process, because this company really fits that description. The interviewers have terrible people skills and ask puzzle-style questions for a senior role.
I passed the first algorithm interview and was then scheduled for four more. The debugging interview was a complete joke and again focused on puzzle-style questions instead of real-world problems.
The interviewers don’t help when you ask questions. They are only there to judge you and make the process harder. The culture seems like they are only looking for yes-men.
Questions d'entretien [4]
Question 1
The "debugging" interview was a Caesar cipher puzzle. Each character was shifted by some +/− offset, but the code was badly written: heavy ASCII character mapping, non-descriptive variable names, and messy logic. It felt like a trick puzzle, not real debugging work you’d do in a senior role.
The first algorithm interview was about removing fields or detecting changes in object fields. There were three questions that could basically be solved by tweaking the first solution, but they wanted me to reimplement it each time instead of reusing or adjusting what I had already written. Basically, we were counting how many changes exist between two objects recursively.
System design interview for google search, you have a list of 1 million keywords and you have to create a web scraper to search each keyword on google every day.
J'ai passé un entretien chez Braze (São Paulo, ) en déc. 2025
Entretien
Default interview process + debugging round: HR Interview, Coding interview, System design, Debugging interview.
Focusing on the debugging round is essential -> They expect you to be able to identify patterns and fix them on failing tests