
Curve Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 84 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 84 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Curve.
Product Analyst
The whole process was super fast, from applying to getting contacted by the recruiter and then moving on to interviews. The recruiter emailed me first to ask about salary expectations and things like that. Then, they set up an interview with the hiring manager. That interview went well, and the manager was really nice. The interview itself was focused on technical skills needed for the job.
- What's your approach to prioritizing tasks?
- Can you share an example of when your proactive analysis led to a significant business outcome?
Senior Mobile Developer
It was a 4 stage interview process. First, I spoke with the company recruiter, and we covered some basic questions about me and some questions you could ask for Curve. Then, I had a technical interview with 2 engineers where we looked at and commented on existing code. Next, I had another technical interview with 2 senior engineers, again commenting on existing code, but this time going into more technical detail. After that, I interviewed with a product manager to talk about the product and how it could be improved or other related questions. Finally, I had an interview with the Scrum master - project manager, which was more like an HR interview with open-ended questions about my experiences and character. In the end, I wasn't accepted because I didn't pass the interview with the Scrum master.
- Can you share an instance where you had a significant disagreement at your company?
- What insights do you have regarding Curve?
- Could you identify any issues with the current app architecture?
Product Manager
I reached out to the CEO for an intro to the Curve Product and was invited to apply for a Senior PM role. The process lasted nearly 2.5 months mainly due to the Christmas break. I found the process refreshingly different to other interview processes mainly because of the talent team, Vinny and Dan, and the product team. The talent team made sure that I was prepared for each interview round and gave me detailed feedback promptly. The product team was focused on understanding my product sense while also explaining how the Curve products work. The process included a case study presentation which was based on my previous work and unlike other companies was not fishing for ideas! The process was as below: Initial chat with Talent team --> Interview with Hiring Manager --> Case study presentation and Q&A with Senior PM --> Interview with Designer, Group PM, Business stakeholder --> Interview with CEO + Head of Talent --> Offer discussion.
- Can you tell me about a product launch you were involved in recently?
- How do you balance business goals with customer needs when making decisions?
- Can you share an instance where you collaborated with a senior stakeholder?
Senior iOS Software Engineer
There are 4 stages. They care about teamwork, communication, and excellent iOS development skills. You can do stages 2-4 in one or two days; I suggest two days for a better experience. Stage 1 is an intro call with a mini technical challenge. You'll talk about Curve and their tech stack, then briefly introduce yourself and your past contributions. There's a quick 15-min technical exercise. Stage 2 is a deep dive into code review style. You'll get a buggy project to refactor and improve, and they'll assess your prioritization and problem-solving. It's interactive, so be ready to discuss your approach. Prepare notes on how to tackle issues. Stages 3 and 4 focus on communication and product management through discussion and debate. Stage 3 is the culture interview, more relaxed, focusing on their leadership principles and project management communication. They'll send you the principles after the first phase. Stage 4 is the product interview. Research Curve beforehand; it's a big plus. Being proactive, showing interest, and acing the technical parts are key.
- What are your thoughts on general software and iOS development topics like architecture, memory management, value/reference types, closures, and testing?
- Can you share your perspective on ownership regarding the tech stack and the overall product vision?
- How would you handle a scenario where a colleague disagrees with a solution you strongly believe in?
Curve Interview Questions
Quoted word for word from Curve interview reports.
“What are Go Routines and what are they used for?”
Read reports →“If you could be any animal, which one would you choose?”
Read reports →“Can you explain the distinction between a marketing manager and a product marketing manager?”
Read reports →“Can you explain when to use synchronous versus asynchronous communication between services?”
Read reports →“How do you think you would survive in a zombie apocalypse?”
Read report →“What animal would you choose to be, and what's your reasoning behind that choice?”
Read report →“What are your thoughts on current cyber security threats and mitigation strategies?”
Read report →“Could you discuss your understanding of networking concepts and their relation to cyber security?”
Read report →“In terms of prioritizing, how do you approach choosing between developing a new product feature and resolving technical debt?”
Read report →Formats, difficulty and experience
Across all 84 Curve interview reports.