I applied through a recruiter. The process took 1 week. I interviewed at Onebrief in May 2026
Interview
Strict interview. First, recruiter interview, then second coding interview, failed at the coding exercise at step 2 of the process due to preparing for that exact question. Would not recommend unless you prepare for every possible question.
Other Senior Software Engineer interview reviews for Onebrief
A recruiter reached out and outlined the interview process. After passing an initial screening, I moved on to technical interviews.
The process quickly became disorganized. The recruiter was unable to clearly explain what to expect in the technical rounds, and the interviews did not align with what was communicated beforehand. This made it difficult to prepare and reflected a lack of coordination between recruiting and interviewers.
Following the technical interviews, communication continued to be inefficient. Interviews were rescheduled and canceled multiple times, and updates often required phone calls instead of simple written communication.
Ultimately, I was informed that I would not be moving forward via a call. The overall experience felt unnecessarily time-consuming and poorly managed. While individual experiences may vary, the interview process lacked structure, clarity, and respect for candidates’ time.
Interview questions [1]
Question 1
A JavaScript exercise followed by reviewing a React component.
I applied through a recruiter. The process took 2 weeks. I interviewed at Onebrief (Austin, TX) in May 2025
Interview
The interview process started off well enough. The first two interviews were conversational and seemed to focus appropriately on my experience and qualifications. However, things took a turn during the "coding challenge."
The challenge consisted of vague algorithm questions that had little to no relevance to the actual day-to-day responsibilities of the role. This was surprising, especially given that the initial conversations had aligned more closely with my professional background.
What made the experience particularly unpleasant was the demeanor of the interviewer conducting the coding challenge. Communication was sparse and unhelpful, and the tone throughout felt patronizing, as though I was being talked down to rather than evaluated as a peer. I even was able to get the coding question correct, but i knew i didn't want this job after that interview. It came across as though the interviewer had a superiority complex, which made for an uncomfortable and demoralizing interaction.
Despite earlier indications that the team was very interested in my skills and experience, I was ultimately rejected without much transparency. It left me with the impression that the company might be more focused on gatekeeping than on genuinely assessing candidates for fit.
Overall, this experience felt disconnected from the job itself and left me questioning how candidates are evaluated.
Interview questions [1]
Question 1
Print out the string version of a number from an array