Curve Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Curve.
Curve
Software Engineer
Entry Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Background check Offer
Interview formats
Technical Behavioral
I applied on their website and then talked with a recruiter via email a bit before scheduling a technical interview. This interview was with 2 backend engineers, and we talked about my experience and the tech I've used. They seemed alright. Same day, I got an email saying they wanted to move me forward to an HR call, which was unusual because that's normally the first step. The HR call was about my motivation and general experience. I was then rejected, surprisingly after passing the technical part.
Confirmed questions1 question
- What testing strategies have you used in your previous roles?
Curve
Software Engineer
Entry Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Technical Coding System Design Behavioral
The interview process was quick and efficient. The recruiter was really responsive and easy to work with, which made scheduling a breeze. There were 4 rounds in total. First up was a technical screening with an engineer, focusing on Go programming knowledge. Then, I had a technical challenge that was like a code review; I was given some code and asked to discuss potential changes and demonstrate how I'd implement them. The next stage was a standard system design interview where we discussed design principles and I did some diagramming. The final round was a chat about company culture.
Confirmed questions3 questions
- Can you explain the purpose of Go's channels?
- What are Go Routines and what are they used for?
- Tell me about the functionality of select statements in Go.
Curve
Software Engineer
Senior Easy Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Group
Interview formats
Technical System Design Behavioral
I applied for the Senior Software Engineer role at Curve and the interview process involved a few steps: a chat with the internal recruiter, an initial technical interview focusing on my experience, a system design interview, and finally two culture fit interviews. Overall, it was a pretty straightforward and enjoyable experience. I was a bit surprised there wasn't a coding exercise, but the system design interview, where I had to design a small, realistic part of Curve's system, seemed to cover that. The process concluded with two behavioral interviews focused on cultural alignment. I received comprehensive feedback after each stage.
Confirmed questions1 question
- Can you explain when to use synchronous versus asynchronous communication between services?
Curve Software Engineer Interview Questions
Quoted word for word from Curve interview reports.
“Can you explain the purpose of Go's channels?”
Read reports →“What are Go Routines and what are they used for?”
Read reports →“Tell me about the functionality of select statements in Go.”
Read reports →“Can you explain when to use synchronous versus asynchronous communication between services?”
Read reports →“Tell me the meaning of some acronyms.”
Read report →“Could you match these acronyms?”
Read report →“How do you approach frontend security?”
Read report →“What were the strange technical questions asked?”
Read report →“Describe how you would design a system architecture.”
Read report →Formats, difficulty and experience
Across all 15 Curve interview reports.