Close Backend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Close.
Close
Backend Engineer
Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Coding
I applied online and the application itself had some open-ended technical questions, plus it asked why I was interested in the role. After that, I had a phone screen where they asked a few technical questions and presented a hypothetical code review. They sent me a rejection email the very next day. I was kinda surprised to get rejected so fast since I thought I did okay.
Confirmed questions3 questions
- Can you tell me about GET and POST HTTP request headers and CDNs?
- Regarding a hypothetical PR with a server code snippet and an async task that has a race condition, what feedback do you have?
- Can you review this hypothetical PR and provide feedback on the server code and the asynchronous task with a race condition?
Close
Backend Engineer
Mid Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Behavioral Technical Coding
The interview process at Close was really great. It was super clear from the start, and everyone was so thoughtful. The whole thing took about a week. First, I had a quick 15-minute screening call with someone from People Ops. Then, I did a 45-minute technical interview with a Backend engineer. After that, I had a take-home assignment. That was it for my interview process. I got some good feedback, and even though I'm bummed I didn't move forward, I totally get why. It's tough interviewing at a cool company like this – you see how great it could be, but sometimes it doesn't work out. Still, I'm really glad I got to interview with Close! They're definitely setting a high bar for other companies.
Confirmed questions1 question
- Regarding your next career move, what are your goals?
Close
Backend Engineer
Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding
There was a one-hour initial call where we discussed my past experience and they described the role. They mentioned the interview would be recorded. I always explain why I decline offers, like accepting another job, needing to work extra hours, or ethical reasons. I expect the same courtesy back when I don't get an offer. This company doesn't provide feedback or explanations, so be warned before applying.
Confirmed questions1 question
- How would you review this Python code, similar to a pull request review?
Close Backend Engineer Interview Questions
Quoted word for word from Close interview reports.
“Can you tell me about GET and POST HTTP request headers and CDNs?”
Read reports →“How would you review this Python code, similar to a pull request review?”
Read reports →“How would you handle race conditions when making API calls?”
Read reports →“Can you review this hypothetical PR and provide feedback on the server code and the asynchronous task with a race condition?”
Read reports →“Regarding a hypothetical PR with a server code snippet and an async task that has a race condition, what feedback do you have?”
Read report →“What feedback would you provide on a hypothetical pull request, and why?”
Read report →“Regarding your next career move, what are your goals?”
Read report →Formats, difficulty and experience
Across all 6 Close interview reports.