alt Hacker NewsAnother small benefit: Everybody understands this isn't what the job is. Nobody is hiring you to beat Wordle, and you solving this is clearly not somehow on the path to their actual task, they are asking you if you can write software which solves a problem and you're demonstrating that you can do that, which makes sense.
I think "Solve 100 Wordles programmatically" sounds like a lot of work, so that'd probably be a "No" from me unless it was last hurdle for a job I was enthusiastic about but unlike "Write a program to solve this class of graph problem" I at least wouldn't be worried that you're trying to get me to do work for free.
Actually Wordle solver as Code Review task sounds like maybe a more interesting live interview than the one we do today. "Here's this mediocre Wordle solver, what is your feedback in review?" has the advantage that they've probably seen a Wordle puzzle before but it's not an example problem they've seen in fifty textbooks.
Well, the 100 Wordles is just "Solve one Wordle" in a for-loop. If you're an even somewhat decent engineer, it takes under 10 minutes to get it working (inefficiently).
Then we encourage people to do whatever they want next: improve their average score, build a frontend UI for it, solve on Hard Mode, etc.
In the past, we never did technical interview questions like this. We always asked people to bring their own project, and work the way they want to. However, with the addition of AI, we hit a wall: we want people to feel they can use AI in a way that mimics how they'd actually work day-to-day, BUT we also need a simple check to make sure they understood engineering basics.