How the interview process has turned into a generic ChatGPT template. Event loop, microtask¯otask,arrow-functions, var vs const&let, memory leaks detect

Roberto Umbelino

Figma

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The current landscape of technical interviews for Senior Frontend Developers often includes questions that fail to assess practical experience and real-world problem-solving skills. Common questions like the workings of the Event Loop, differences between arrow functions and regular functions, or memory management often focus on rote memorization rather than actual expertise. The post argues for more meaningful, experience-based questions that better evaluate a candidate’s ability to apply theoretical knowledge practically.

Bad questions for Senior Frontend Dev Interview

Everything described below is my subjective opinion

WAT?! No data structures and algorithms :D
<code>Dance a BubbleSort</code>

console.log(1);
setTimeout(() =&gt; console.log(2));
Promise.resolve().then(() =&gt; console.log(3));
Promise.resolve().then(() =&gt; setTimeout(() =&gt; console.log(4)));
Promise.resolve().then(() =&gt; console.log(5));
setTimeout(() =&gt; console.log(6));
console.log(7);
So answer is 1726354?

It depends, whether you want one for development, or one for coaching juniors.

I went for a Senior position where the only question they asked me was about Closures. Of course I got schooled. Great learning experience, but otherwise it makes you wonder what teams look for in Senior developers: either experienced coders who have standards for code structure, or leaders for junior devs.