this post was submitted on 07 Oct 2026
-23 points (23.3% liked)
Programming
28764 readers
452 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
ok i re-read. i see. i still never gave code based interviews. i found that people who could go i to theor projects with depth had a solid understanding.
yeah, i get that. but i think what i’m more interested in is problem navigation.
once someone joins a company, they’re not always going to be working on things they’ve already seen before or can talk about from past experience. they’ll get dropped into unfamiliar systems, weird bugs, new constraints, and have to figure out what matters.
so part of the value to me is seeing how someone behaves when they don’t already know the terrain, where they look first, what assumptions they make, how they narrow things down, and how quickly they build enough understanding to make a good decision.
i think that’s probably part of why leetcode-style interviews survived this long too. for all their flaws, they give you a problem the candidate hasn’t necessarily seen (sometimes) in that exact form and let you watch how they navigate it.