Curebase Interview Questions
& Process

The interview process was incredibly quick for me, as I received an offer in a matter of days. They were incredibly accommodating of my timeline and I thought it was a green flag that a company was willing to work with me before even extending an offer for something that was within my best interest, though there were of course benefits for them, too. I spoke with a few different people and enjoyed my conversations with all of them; the interviews had a very laid back feel to them instead of up-tight and corporate. It was easy to speak candidly to the team, which I think reflects a good company culture. It was a great first impression! My interview process started with a screening call, then I spoke to the hiring manager for the position, and lastly I had a panel-style interview with the hiring manager and two other people in other departments where I had to complete an assignment. They don't give you much information on what you'll have to do, so there honestly isn't much preparation you can do. The assignment is pretty vague when you get to it, but ultimately it was described to me as a typical assignment you would get in this position and you'll walk through your strategy; you can write it down or speak out loud. Basically, it shows that you know what you're talking about when it comes to skills you'll need to succeed in this position. Lastly, it's very easy to schedule interviews with them through their scheduling link.

Applied online and got scheduled pretty quickly for a first interview with the Chief of Staff, which was appreciated as it skipped the usual HR screen. That chat covered general culture fit and some light questions about how I'd approach solving company problems. The second interview was an hour with the hiring manager; the first half focused on my experience with general questions, and the second half was an abstract exercise about improving revenue in a hypothetical situation. After that, I was scheduled for an hour-long "business case" exercise. I was given the general scope of what to discuss beforehand, but the specifics of the exercise were only revealed 15 minutes prior. This felt like an odd setup for a homework assignment and potentially a "gotcha" situation. I usually withdraw from roles with homework because I've seen it used for free work, but I was interested in Curebase's work and decided to go through with it. The case review was with the hiring manager, plus three other employees (design, product, engineering) over Zoom. The hypothetical wasn't directly related to Curebase's business. While the exercise itself wasn't overly challenging, the scope of what I had to cover in an hour made it hard to showcase my skills properly. I had to rush through product process steps from discovery to rollout, likely giving the impression I didn't know the topics in depth, when really it was just the time constraint. It didn't feel like a good way to demonstrate anything beyond knowing the general PM process. The case review felt strange because only the hiring manager was actively involved; the others just said hello and then nothing. It was more like a presentation (on a topic I'd only had 15 minutes to prepare for) than a discussion. I was told a few days later I didn't get the role. Despite the negative business case experience, the HR staff at Curebase did a great job scheduling and running things efficiently and in a friendly manner.

The interview process was super smooth and I really enjoyed it. They were really fast and worked with my schedule since I had another offer pending. They let me know about my candidacy quickly after the last interview parts. I met with the team and other people involved in the company and also did a really fun design exercise. They made interviewing for a job feel really welcoming and friendly, which can be a pretty daunting thing. Everyone I met was easy to talk to and helpful, making this one of the best experiences I've had.

The interview process was great and fun. It basically had three steps. First, an intro interview combined with a tech interview which was high-level, just a conversation. Second, a code exercise that was simple and related to the role, not complex algorithms, more like daily stuff. Third, other interviews, including an architecture interview and another code exercise. During this phase, you'll meet more team members, like Product People and Managers. The architecture interview involves discussing architectural questions and providing the best possible answers. The new code exercise is a bit bigger than the first one but also relates to real-world issues. Overall, the whole process is great and fun, offering a chance to meet people from the company and ask plenty of questions.