this post was submitted on 21 Feb 2025
52 points (93.3% liked)
Technology
63082 readers
3853 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My favourite tech interview technique was the code review style. Give them some code with a range of deliberate issues and ask them to code review it live on the call.
Tests their code comprehension and as you can ask them questions live, it's reasonably AI proof (I think). You can ask them to refactor things on the call, which tends to be something AI is weak at. It also requires no take home work for the applicant.
My company has just said that AI use in the interview is fine, but we will be asking questions as they work through it to check they actually understand things.
There's probably a few things you can do live on a call.
I always wanted to try passing a common function through a minifier then a beautifier. Show them the code with unhelpful variable names, and ask them what name they would give the function.
A good programmer would be able to identify a string compare function or an IP bitmask eval function pretty quickly.
I probably wouldn't, because I call a library to do it for me. That's because I'm not a C programmer and it's easy to use libraries in other languages since they have package managers that just import all the other packages