Fui entrevistado pela Braze (São Paulo, SP) em dez. de 2025
Entrevista
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
Candidatei-me online. Fui entrevistado pela Braze (São Paulo, SP) em jan. de 2026
Entrevista
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.
Perguntas de entrevista [4]
Pergunta 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.
Candidatei-me online. O processo levou 3 semanas. Fui entrevistado pela Braze (Milpitas, CA) em set. de 2025
Entrevista
Applied to Braze via Indeed. The recruiter reached out by email to schedule an initial phone call, and their scheduling system made providing availability simple and intuitive. We spoke for about 20–30 minutes; the recruiter was friendly, helpful, and clearly explained the process, emphasizing the importance of preparing for the technical screen.
The technical screen itself went smoothly, and scheduling the virtual on-site interviews was equally seamless.
Although I didn’t prepare as thoroughly as I should have and one of the intensive sessions exposed some major deficiencies on my part, both interviewers were friendly, flexible, and encouraging throughout.
Overall, it was a very positive experience. I appreciated having the chance to meet with real developers rather than relying on online assessments or timed GitHub challenges.