Onebrief Interview Questions
& Process

The interview process was good and pretty straightforward. It involved some simple LeetCode-style coding questions and then a deeper dive into a project you've previously worked on. The onsite portion included a panel of interviewers who asked a mix of technical and non-technical questions.

A recruiter reached out and told me about the interview process. After passing an initial screening, I moved to technical interviews. Things got messy after that. The recruiter couldn't explain what to expect in the technical rounds, and the interviews weren't what they said they'd be. It was hard to get ready and showed they weren't coordinated. After the technical interviews, communication stayed bad. Interviews were rescheduled and canceled a bunch of times, and I often had to call to get updates instead of just getting an email. In the end, they called to tell me I didn't get the job. The whole thing felt like a waste of time and was badly run. While it might be different for others, the process wasn't structured, clear, or respectful of my time.

This took over 6 weeks, and calling it a process is a stretch. It started with a chat with the Quality Director, which was a good conversation. Then I talked to a manager who wasn't my direct report, just to gauge my fit. This was very similar to the director chat. After that, there was a nearly two-week break because they were off-site. Following that, I had a call with two engineers where we discussed a take-home assessment that didn't really fit my role. They figured that out and after a week, I was asked to do another assessment. Then another talk with two devs, which went well. The next day, I got an email saying I was moving on to the final interview with the VP. On the interview day, just two hours before, they asked if I could meet earlier with the same director and manager again. This call was an hour instead of the planned 30 minutes, and I was hit with a flood of questions for 50 minutes straight. The next day, I received a rejection email. My best guess is they decided to hire internally and just wanted to put someone through the wringer.

My initial chat with the recruiter was great! She really liked me and wanted to speed things up. I put in a lot of work getting ready for the hiring manager chat, really digging into the company's specific situation. But then, just two hours before the meeting, the recruiter cancelled it, saying my experience wasn't a good fit for their current needs. They didn't give any more details, even though they seemed really interested at first. Also, I found out Chris Miller from Project 2025 joined their board, which might be something to consider if you're looking at this company.