Close interview questions

I truly cannot say enough good things about the interview process at Close. From the get-go, the process was exceptionally clear, and the people were beyond thoughtful. My interview process unfolded over the course of approximately a week. I had an initial 15-minute screening call with someone in the People Ops department, which led to a 45-minute technical interview with a member of the Backend engineering team. I then completed a take home assignment, after which my interview process came to an end. The feedback I received was thoughtful, and though I'm heartbroken, I know exactly why I didn't advance to the next step. This is the double-edged sword that comes with interviewing at an awesome company: You get a glimpse of what you future could look like, but some times that glimpse doesn't materialize. Nevertheless, I'm still so happy I got to interview with Close! They set the standard high for other companies; they really did.

The application was thorough and required a quick coding challenge in addition to a few questions. They lay out the interview process right away, which was helpful. I had a very nice intro call with people ops before entering the formal interview process (to ensure my goals aligned with theirs). I was unfortunately rejected after the first Technical interview. There was some miscommunication in the technical interview prep email where I was told I would be doing a "code review and communal discussion". I totally misunderstood that as a "pairing pull request session" rather than what it actually was, which was two live coding challenges. I didn't feel like I bombed the interview by any means, but I suppose I didn't hit the marks they required/were looking for. If you're very interested in Close I would suggest ensuring you have a solid foundational understanding of frontend security and performance, and be able to speak about that in great length.