Close logo

Close Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 87 interview experiences · FREE TO READ

3.4 Rounds average
Average Typical difficulty
44.8% Positive experience

Which role are you interviewing for?

21 roles · 87 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Close.

Showing 4 of 87
Close logo
Close

Senior Software Engineer

Engineering · more than a year ago

Senior Easy Positive experience No offer 5 rounds
Interview process
Technical screen Recruiter call Take home Technical screen Onsite
Interview formats
Technical Coding Other

The interview process was super clear, they laid it all out in the first email: first a tech screening, then an HR call, followed by a take-home assignment. After that, there was a tech interview and then two more interviews with the director and VP. Everyone I met was really nice and always made time for my questions. The initial tech screening was pretty straightforward. I didn't get past the take-home, which seemed quite simple but I guess it wasn't what they were looking for.

Confirmed questions2 questions
  • Basic technical questions expected of any developer
  • A mock code review exercise
Close logo
Close

Senior Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Technical Coding Behavioral

The interview process was messy, with multiple reschedules and the interviewer showing up late. It jumped right into technical questions without any warm-up. The questions felt like 'gotchas' and were very obscure, similar to what other reviewers mentioned. Some questions were about deep JavaScript internals, like function behavior, which even experienced front-end devs at top companies found difficult to recall. After some technical questions, there was a live-coding session using Leetcode on CodeSandbox in JavaScript. The entire interview lasted about 1 hour and 10 minutes. Although an interview outline was sent beforehand, the subsequent stages included more technical interviews and a take-home assignment. I decided it wasn't worth the time, especially if a company requires 8+ hours of assessment including a take-home. It was a pretty bad experience.

Confirmed questions4 questions
  • When there are two click events, one on a parent element and another on a child element nested within it, what is the order in which they are triggered?
  • Could you explain the concept of event bubbling?
  • Can you discuss the internal workings of JavaScript functions?
Close logo
Close

Senior Frontend Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Technical Coding

I went through 3 out of 4 rounds for this role back in Nov 2023. The interviews were long and impersonal, taking up about 12 hours total. It was a bummer that we never got to meet the team. I was told I didn't make it to the final round because they went with someone with more experience, even though I was told I was a great candidate. The recruiter said they had no feedback to share, just that I was 'very thoughtful and intelligent'. We ended on good terms. I saw the job reposted in Feb 2024 and reached out. The recruiter said there's a year-long cool-off period, which felt weird since I was told I was a great fit. She also said the role is always open, but the job was taken down and reposted, so that wasn't true. Overall, it was a pretty negative experience.

Confirmed questions3 questions
  • string manipulation challenge
  • dom manipulation challenge
  • build a kanban board in React take home challenge
Close logo
Close

Customer Support Representative

Operations · more than a year ago

Entry Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Phone screen Background check
Interview formats
Behavioral Technical Case

This is a lengthy interview process which, to be fair, is made clear from the very beginning. It began with an interview with the team lead which was very pleasant and consisted of a standard CV walkthrough and general questions. Overall, very conversational and laid back. The manager informed me that, should I be ultimately successful, before proceeding with a formal offer I would have to participate in a 2 week trial to ensure that I'm the right fit for the role/ the role meets my own expectations. Personally, I think this approach is very antiquated and inconsiderate of candidate's time (considering that if one reaches this point they have already dedicated hours of time to interviewing, presumedly whilst also juggling a full-time job). Following this, there is a 'technical' interview with one of team's support engineers. This essentially consists of standard intro questions and hypothetical, situational questions that are designed to determine how you would approach a customer's queries and tackle rudimentary troubleshooting. Following this, there is a call with HR which, in my opinion, is somewhat redundant. The HR manager was very nice and enjoyable to speak to, however, most questions were repeats from the prior two interviews i.e. general CV/career goal queries. The purpose of the call is to offer an opportunity to ask any culture-related questions you may have, as well as to give HR a chance to provide more details regarding the specifics of the employment contract. It was during this call that I was informed that the role would require me to be employed as a contractor due to being located outside of the USA. In my country, this comes with a slew of complications and expenses so this news caused me to rescind my application. To my knowledge, if I had proceeded, the next step would have been another technical interview although I'm uncertain what would have followed that. I would highlight that all employees I spoke with were very nice and encouraging. I understand that the extensive interview process is in place in order to ensure they find the right candidate but in my opinion, it's overkill.

Confirmed questions7 questions
  • Can you walk us through your CV?
  • Tell me about yourself.
  • What are your career goals?

Close Interview Questions

Quoted word for word from Close interview reports.

Can you implement a function that extends all string objects, for instance, 'xyz'.myfunc()?

Read reports

If a string came from user input, how would you make sure it's safe to insert into HTML?

Read reports

When there are two click events, one on a parent element and another on a child element nested within it, what is the order in which they are triggered?

Read reports

Describe the implementation of 3 endpoints for rate limiting statistics.

Read report

Can you explain the difference between CPU utilization and load?

Read report

Create a Zap with Zapier integration to trigger email sequences for leads

Read report

What could be the reason for Close emails landing in Spam?

Read report

Formats, difficulty and experience

Across all 87 Close interview reports.

Interview formats

Technical 33.5%
Behavioral 31.1%
Coding 16.7%
Presentation 8.1%
Other 5.3%

Interview difficulty

Easy 18.4%
Average 58.6%
Difficult 23%

Candidate experience

Positive 44.8%
Neutral 17.2%
Negative 37.9%

Reports by job function

Engineering 42
Operations 19
Sales 13
HR 7
Marketing 3
Product 2