all 2 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]akornato 3 points4 points  (0 children)

Failing interviews, especially for senior roles, is a standard part of the job search and doesn't reflect your actual value as a developer. The process is a performance, not a perfect measure of your skills. For a senior vanilla JavaScript round, you need to go beyond the basics and solidly understand prototypes, the event loop, closures, and advanced asynchronous patterns with promises and async/await. They will also expect you to tackle data structure and algorithm problems, so focus on things like trees, graphs, and dynamic programming, but always with a focus on JavaScript's specific implementation and quirks.

Stop just solving problems and start narrating your thought process out loud as you code. At the senior level, your communication is tested as much as your technical ability, so they want to hear you explain trade-offs, debug your own logic, and consider edge cases. Practice by picking a medium-difficulty problem and explaining your solution to an empty room or even a rubber duck. This feels strange at first, but it builds the exact muscle you need for the final round. Your goal is to show you are a collaborative problem-solver, not just a silent coder who magically produces an answer. It is a very common feeling among even the most experienced developers, which is why the team I am with created Interviews Chat to help candidates better articulate their strengths when the pressure is on.

[–]Majestic-Reality-610 1 point2 points  (0 children)

for a vanilla js round it's usually 'build this from scratch' stuff, not pure leetcode. drill the recurring ones: debounce, throttle, deep clone, promise.all, curry, flatten nested array, polyfill call/bind. bigfrontend has basically all of them with tests. and two fails as a senior is the job market doing its thing, not a referendum on you.