Candidatei-me online. O processo levou 1 dia. Fui entrevistado pela Close (Jackson Hole, WY) em nov. de 2024
Entrevista
Call the technical leadership that's supposed to be non-technical and followed by additional interviews. The first interview had odd open-ended questions about the details of HTTP. Interviewer was a tad difficult to understand what they were asking.
We really appreciate you taking the time to share your feedback. Wishing you the absolute best in your search!
Entrevista com nível médio de dificuldade
Candidatura
Fui entrevistado pela Close em mai. de 2026
Entrevista
The first interview was with a recruiter, the interview was on zoom. The conversation was pleasant, I received all of the information on the position and the company.
The second interview was with a tech lead, very down to earth conversation where I had to describe a project I did in the past.
The third interview was a classic leetcode interview.
Candidatei-me online. Fui entrevistado pela Close em abr. de 2024
Entrevista
Where do I begin? The interview itself was re-scheduled multiple times. The interviewer was still late. The interview started and there was no "get-to-know-you" and or "ice-breaker" It was hey how's it going, here's how the interview is going to go, ready to begin?
Then came the questions that while a lot of developers can know, they really weren't required to know. They definitely seemed like "gotcha"-type questions. I read the review of other Glassdoor, and I agree, some of the questions they asked were really esoteric and strange they asked them. Yes, you could know them but I know multiple front-end developers at Facebook/Netflix who I asked that opined that it'd been a while since they knew the answer. It's one of the questions that asked about the internals of JavaScript functions. In fact, you've probably used some of these paradigms in your code, just didn't know the name of it.
After a few technical questions, it was time for a live-coding! Leetcode time. Time and time again, live-coding itself has been seen as a false positive indicator of abilities and just not accurate. Not only that, but leetcode as well?
I got through the problem on the codesandbox provide, which was in JavaScript -- not TypeScript but still. The whole interview took about 1hr and 10 minutes.
I know that they send an interview outline before the first interview but then I looked at the rest... MORE technical interviews and a take home.
I realized that this was not worth my time. If it takes a company 8+ hours after multiple assessments and a takehome on a hire, then I'd rather work somewhere else.
Just yikes. Definitely one of the worst interview I've had in a long time.
I didn't get an offer because I emailed our point-of-contact that I withdrew my candidacy for the role.
Perguntas de entrevista [2]
Pergunta 1
Q: If you have two click events, one inside a parent and one inside a child div, which one comes first?
Thank you for your feedback and we’re really sorry you had a negative experience interviewing with us. To be as transparent as possible, we outline the entire interview process in the initial email along with the length of time for each step. That said, we will absolutely take your feedback into account as we improve our process going forward.