Candidates applying for Sr. Software Engineer roles take an average of 14 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Braze overall takes an average of 21 days.
Common stages of the interview process at Braze as a Sr. Software Engineer according to 1 Glassdoor interviews include:
Phone interview: 25%
One on one interview: 25%
Presentation: 25%
Group panel interview: 25%
Here are the most commonly searched roles for interview reports -
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.
Interview questions [1]
Question 1
Address my short tenure in my resume (laid off) and my career gap. Not interested in anything else.
I interviewed at Braze (São Paulo, São Paulo) in Dec 2025
Interview
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
I applied online. I interviewed at Braze (São Paulo, São Paulo) in Jan 2026
Interview
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.
Interview questions [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.