Interview Process was quite quick.
1. Phone call with internal recruiter to align on expectations
2. Virtual tech screen on valid parenthesis and additional fun stuff. I felt it was a very collaborative process and the interviewer did a great job working along with me on the problem.
3. virtual onsite consisted of system design, hiring manager discussion, and live debugging.
3a. System design was your run of the mill system design session of designing a DB schema, figure out what kind of infrastructure pieces you need to piece together for an async system and the edge cases. One thing that kind of caught me off guard was the expectation to write sql which tripped me a little bit. Overall I felt this session was pretty fair in terms of difficulty and what you're expected to know despite me not doing so well.
3b. Hiring manager discussion I felt was your typical discussion. The manager seemed like they would be great to work under and work with you.
3c. Live debugging. As another review has already stated, the code was very convoluted and I underestimated how unreadable it was. I think the thing that tripped me up the most was that, as the interviewee, if you ask any questions, your interviewer is going to bounce a question back to you in the form of "well where can you find that?" and etc. I felt it was very offputting and feels a lot less collaborative which, to me, added a lot more pressure and tripped me up pretty bad.
Preguntas de entrevista [1]
Pregunta 1
1. Leetcode valid parenthesis
2. typical system design for an async based system
3. live debugging with hard to read code.
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.
Preguntas de entrevista [1]
Pregunta 1
Address my short tenure in my resume (laid off) and my career gap. Not interested in anything else.
Me postulé en línea. Acudí a una entrevista en Braze (São Paulo, ) en ene 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.
Preguntas de entrevista [4]
Pregunta 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.
Acudí a una entrevista en Braze (São Paulo, ) en dic 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
