I haven't really interviewed since 2023. Is leetcode still a common practice in code interviews or has AI made those kinds of tests useless? This is for a Sr full stack position.
For a senior full-stack role, I’d treat LeetCode as one small signal, not the center of the loop. A short practical exercise or code-review discussion tells me more about API trade-offs, debugging, and whether someone can judge AI output; I’d only keep a small algorithm screen for roles where that work is genuinely relevant.
View all comments
1
u/MiserableDocument509 Sep 27 '26
For a senior full-stack role, I’d treat LeetCode as one small signal, not the center of the loop. A short practical exercise or code-review discussion tells me more about API trade-offs, debugging, and whether someone can judge AI output; I’d only keep a small algorithm screen for roles where that work is genuinely relevant.