I had a quick phone interview with a recruiter after being contacted on LinkedIn. This was primarily a non-technical discussion about the company and roles available, followed by a very quick technical screen including basic JavaScript concepts.

Around a week later, I had a technical phone interview with a current UI developer. This was done with a shared Coderpad session for programming questions.

Overall, the interview seemed a bit disorganized and the interviewer couldn't seem to decide if he wanted to keep the tone conversational or technical. In the end, we probably chatted too much and ran out of the time apparently allotted for the programming questions before finishing the last question, which he originally presented as a 'bonus' or 'while we're on the topic' sort of question rather than a core part of the interview.

He also seemed confused on how to present the problems, resorting to pasting badly formed ASCII art into the shared session to describe what he wanted implemented rather than explaining it in what I would consider to be standard industry terms (Event, Debounce, Throttle, etc). This question explanation took much more time than should have been required.

I got my feedback about a week later over the phone, and was told that since I did not complete the last question in time, I was not being considered further. Ultimately, I am disappointed in the lack of organization from the interviewer. During similar interviews with both large and small companies, I have solved and discussed much more complex topics than were handled in my Facebook interview simply because the interviewer kept on topic and led the interview with his personal time requirements in mind.

I attribute the poor interview experience to poor training on the interviewer's part.

Implement a basic EventEmitter.

Implement Debounce and Throttle using setTimeout.