Close logo

Close 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

3.1 Rounds average
Average Typical difficulty
33.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Close.

Showing 3 of 15
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

Software Engineer

Engineering

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

This process is a real time sink. They make you do a 6 hour coding project on top of the interviews. Honestly, I'd avoid it because even if your code is perfect and meets all the requirements, they'll still reject you without any explanation. This probably means you'd end up with a manager who's a real jerk and doesn't care about his team. The pay is average and the experience is limited, making it the worst interview I've ever been through.

Confirmed questions4 questions
  • Questions about web technologies
  • Questions about browsers
  • A take-home coding assignment lasting 6 hours

Close Software Engineer Interview Questions

Quoted word for word from Close interview 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 reports

Could you explain the differences between GET and POST requests?

Read report

How can browser tabs effectively communicate with each other?

Read report

How would you approach building a URL shortener service?

Read report

Can you discuss the internal workings of JavaScript functions?

Read report

Formats, difficulty and experience

Across all 15 Close interview reports.

Interview formats

Technical 33.3%
Coding 33.3%
Behavioral 19%
System Design 9.5%
Other 2.4%

Interview difficulty

Easy 13.3%
Average 80%
Difficult 6.7%

Candidate experience

Positive 33.3%
Neutral 20%
Negative 46.7%