
Close Customer Support Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 13 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Close.
Customer Support Executive
So, I went through the whole interview process but didn't get the job in the end. Apparently, that happens a lot based on other reviews, so here's another one for the books. Honestly, the conversations themselves were enjoyable. Everyone seemed really nice and passionate about their team. The issue for me was the sheer number of interviews for a small team, and it felt like some were redundant (like 2.5 out of 5 were basically the same), which made parts of it feel like a waste of time. You should definitely have your "Why Close/Why this role" answer ready for every chat. This repetition gets old fast and bumps up the difficulty. I had a general idea of the process, but I wish I'd known more specifics about each conversation. Going in with more details would have helped me prepare better. There were five interviews: a call with the Director of Support about how the team works, a Technical Interview, a Technical Challenge, a chat with People Ops, and a call with the Support Manager. These last two are usually swapped. After all that, there's supposed to be a two-week trial to see if it's a good fit, which they say can be scheduled around your current job. Some folks dislike trial periods, but I've done them before, and it's fine if they're flexible with your schedule. The hardest parts were the Technical Interview and the Challenge. The interview involved theoretical troubleshooting questions to check your logic. The Challenge was a mock customer call where you had to help the interviewer set something up in Zapier. I got almost no info beforehand, so definitely know Zapier, how it works with Close, and its automation features. The process kicked off with an email that arrived a bit before the interview, which was stressful. It was only 15 minutes, but it’s good to know in case you’re juggling other commitments. It was frustrating not getting more prep time or info for this. I don't know Zapier, so teaching a customer how to set it up on the spot with only 15 minutes' notice was impossible. The Founder call was also notable. It's presented as a chance for you to ask questions and learn about the company, but I wish I'd known that, as I would have come prepared with questions instead of repeating why I want to join for the fifth time. The founder was trying to sell me on the company, but when I asked what makes it a great place to work, he didn't really have an answer. It was mostly about me, though, which was okay. I’d recommend looking up the founder beforehand (LinkedIn, etc.) to gauge the conversation. It’s a really thorough process, but it honestly doesn't feel necessary. Repeating the same questions five times is a bad experience and feels like a waste. I was interviewing elsewhere and had more interviews, but they covered a much broader range of topics. It was more engaging than rehashing "Why do you want to work here" and "What's your technical experience" over and over, even with more conversations. Based on that alone, I probably would have declined Close if they had offered.
- Why might a customer report that calls are not clear?
- What could be the reason for Close emails landing in Spam?
- How is a direct phone call different from a call made through a platform like Close, especially if calls are spotty on Close?
Customer Support Executive
Since the company is fully remote, the entire interview process was conducted online. I went through five rounds with five different colleagues to make sure it was a good fit for everyone. Even though there were five rounds, the whole thing happened pretty quickly, in under three weeks. After those five rounds, they contacted three references I had provided.
- Can you tell me about your general background?
- Let's discuss your personality.
- We'd like to conduct a technical interview and a challenge.
Customer Support Executive
Applied to Close in June and heard back 5 weeks later for an interview. Scheduling was easy and they explained the process, which is way too long. Six interviews for a customer support role and they didn't mention salary in the job description? Wild. The interviewer talked super fast and I felt like it went well. I asked about metrics and they said they aren't really metrics driven. Big red flag. How do you gauge success compared to other SaaS support teams? Got contacted the next day saying I wasn't moving forward, then contacted AGAIN the day after by someone else saying the same. Please improve communication with applicants, it's tough out here. Another red flag. Also, 'Executive' title implies over $70K pay, but they're paying less. Wouldn't have been worth more interviews.
- What made you decide to apply for this position?
Close Customer Support Interview Questions
Quoted word for word from Close interview reports.
“What factors cause Gmail to classify an email as spam?”
Read reports →“Why might a customer report that calls are not clear?”
Read reports →“What could be causing spotty calls for a customer?”
Read reports →“What could be the reason for Close emails landing in Spam?”
Read reports →“If an email to Close is going to spam, what are the possible reasons and how would you fix it?”
Read report →“How is a direct phone call different from a call made through a platform like Close, especially if calls are spotty on Close?”
Read report →“Can you explain how to integrate Google Forms with Zapier?”
Read report →“Can you explain how to use the product?”
Read report →“Could you have a call with a funder?”
Read report →Formats, difficulty and experience
Across all 13 Close interview reports.