After a recruiter phone screen, there was a remote code pairing technical interview with two engineers in California.

The tone was set by one of the engineers, who stated that they wouldn't be there if they didn't love their job, unlike others "waiting for an exit." This implied some others were just sticking around, waiting for the company to go public. The engineer also laughed and snickered at the other engineer when, during a recap of work experience, the latter mentioned having previously worked at a big-name company.

I was then asked how I would rate limit a function to prevent it from being called too often. I correctly answered, "use a debounce function."

Funnily enough, I had seen this question asked already in another interview but didn't think they would just reuse the same question.

I quickly implemented a debounce function in CoderPad when asked, which performed correctly. However, I was not on my A-game due to being thrown off by the interviewer's manner and style. I didn't remember to call the debounced function immediately on the initial call of the function, which the interviewer somewhat condescendingly pointed out after I'd written the function.

Overall, it was not a terribly collaborative or pleasant interview experience. It didn't feel like the process was designed to explore any depth of my knowledge or experience.

While I felt that my interview performance was not what I would have liked it to be, the overall tone of the interview didn't make me terribly surprised or disappointed to be told a few days later that they wouldn't be taking the process further.

Write a debounce function.