Real, anonymous reports from people who interviewed for Software Engineer at Braze, newest first and distilled into what to expect across the loop.
My interview journey followed a fairly defined sequence: after an HR-focused call, I moved into coding and system design, and then a dedicated debugging round. The debugging part was the standout in both structure and emphasis—it wasn’t just another task; it felt like they wanted to see whether I could identify patterns and drive fixes across failing tests.
I started with a short recruiter phone screen that lasted about 30–40 minutes. The conversation felt relaxed and mostly revolved around my background, what I’d worked on, and why I was interested in the role. It didn’t turn into a deep technical grilling, and I remember feeling like the goal was just to understand me and set expectations for what came next.
The interview process typically begins with a recruiter call that lasts about 20-40 minutes, focusing on the candidate's background and setting expectations for the technical rounds. This initial conversation is generally relaxed and aims to provide clarity about the upcoming steps.
Candidates often face a technical screen that includes algorithm questions and coding challenges, typically conducted on platforms like HackerRank. The difficulty varies, but many report a focus on straightforward problems with an emphasis on passing tests rather than theoretical discussions.
A significant aspect of the interview process is a dedicated debugging round, where candidates must identify and fix issues in existing code. This round is noted for its pressure and focus on problem-solving under failure conditions, rather than just writing code from scratch.
Onsite interviews typically include system design discussions and behavioral interviews, where candidates are evaluated on their ability to navigate open-ended prompts and articulate their experiences. The atmosphere can vary, with some candidates feeling collaborative while others report a more adversarial tone.
Candidates report mixed feelings about the overall interview experience, with some finding it well-structured and respectful, while others describe it as stressful and lacking in support. The perceived culture of the company can significantly impact candidates' reflections on their fit within the team.
Feedback and communication throughout the process vary widely, with some candidates appreciating the transparency and support, while others feel left in the dark or encounter unprofessional interactions. This inconsistency can affect candidates' overall impressions of the company.
