OnceHub Interview Questions
& Process

So, OnceHub's interview was like a few steps. Started with some chats, then this big take-home thing, and after that, I talked with the CPO, a Senior PM, and the CEO. What was cool was they really cared about how I thought about product stuff with actual problems, not just random questions. The assignment was pretty well thought out and felt like we were checking if it was a good fit for both sides, not just them testing me. It took a bit longer than I thought, but honestly, it was a good experience and felt respectful.

The hiring process with this company was a letdown. The HR recruiter initially contacted me twice about the wrong job, and I had to correct them both times. My first interview with HR was okay, but the second one with the CMO went really well; he actually extended our chat and said he was keen to move forward. After that, though, everything went silent. I waited a week and then emailed HR for an update, but heard nothing back. About ten days later, I got a generic email saying they weren't hiring anyone from my country. It was one of the worst recruitment experiences I've had, mostly because of the messy communication and lack of follow-through from HR, especially after the good feedback I got during the interviews.

The application and interview process was a positive experience. Although a lengthy process, each step had purpose and was necessary. The interviewers go out of their way to accommodate you, even if it is after hours and they purposefully try to make you feel at ease during the interviews. A longer interview process, to me was a good thing as it shows the importance they place on finding a suitable candidate and gives you plenty time to ask questions and make a more informed decision.

It was a 2-week process. First, I had a quick chat with the recruiter, who was really nice and made the company seem great. Then, there was a multi-hour project where I had to use their software to create a specific scenario. This scenario was designed to highlight a weakness in the product, basically making me pretend to be a customer who isn't their main audience and show how the software could be made to work for them with some effort. It could be done quickly if you already knew the software, but if you were new to it, it would take hours to figure out, read documentation, and watch videos because it's not very intuitive. After that, I met with the department manager. This meeting was mostly a review of the project I'd done, with them suggesting alternative approaches. It felt more like user testing done after the fact, which doesn't make sense because they weren't watching me in real-time. I had ideas on how to improve the product, but there wasn't a good way to share them, and I wasn't going to do more free work. There was also a weird part where they watched me type a mock email to a fake customer without giving me any info on company policies or procedures. In a real support job, this is easy because you have templates, know the product, and have past tickets to reference. I'm not sure what they learned from watching me do this hypothetical service. Actually, you could learn a lot from this exercise, but only if you actually discussed it, provided some guidelines, and weren't just distant and robotic. I felt like a test subject, not an interviewee. The manager was cold and uninterested. The questions were strange and scripted, and she wouldn't engage. It was clear she didn't want to talk. I felt like I dodged a bullet. Recruiter: great. Manager: bad vibes.