this post was submitted on 05 Oct 2026
99 points (97.1% liked)
Programming
28702 readers
426 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
That right there is the difference between a shit interviewer and a golden interviewer. And that goes for a lot of technical roles, far too many just throw a "whiteboard" at you and just expect you to figure it out without any outside help, even though it goes against how even experts get things done in the real world :/
There’s nothing worse than killing all momentum and dialogue while you wait for someone stressed out to waste 5 minutes google something and find the right documentation page. It just sucks.
I also made it clear I’d hire people no matter how far they got as long as they communicated their plan and were able to solve problems. It’s not a real task, in real life you message your boss and say you need more time. I’m looking for “would I work with this person” and “what skills do they have, where can they improve, where would they fit on the team”.
You could make good money teaching people how to do a proper interview.