Consider pair work (a generalization of pair programming):
Spin up a VM for you and the candidate to SSH into. Start a shared screen/tmux session. Work on some sysadmin task(s) together. Switch between driving/typing and navigating/directing at regular intervals (15 minutes is typical, though a 30 minute interview would require a <10 minute interval).
You'll have to come up with a task (or set of tasks) that deals with the skills you need. The task(s) would ideally be very difficult for an LLM or search engine to provide a complete answer for; but they shouldn't be gotchas, since that might be false negatives.
Test your task(s) with other people in your company first, so you'll be comfortable when doing it with a candidate.
I can't say that this will 100% prevent cheating. But, you will surely learn a lot about the candidate's habits, in terms of reasoning and communication. If the candidate pastes commands, then that's a possible indication of LLM-usage; if the candidate doesn't use tab-completion, then they might be typing text in from somewhere else (e.g. an LLM, a guide).
I enjoy using the command-line, so I suspect I would enjoy this sort of interview.
> All photographs or videos you have seen have been placed there for you to see them.
For those reading the above, wondering about this phenomenon, read Baudrilliard's The Gulf War Did Not Take Place. Even if you don't agree with Baudrilliard's overall thesis, the facts he brings up are still cogent (e.g. a photo from the Exon Valdez spill was used instead of an actual photo of the Iraqi military's destruction of Kuwaiti oil fields). The media has been a critical aspect of war since at least the Falklands War.
Spin up a VM for you and the candidate to SSH into. Start a shared screen/tmux session. Work on some sysadmin task(s) together. Switch between driving/typing and navigating/directing at regular intervals (15 minutes is typical, though a 30 minute interview would require a <10 minute interval).
You'll have to come up with a task (or set of tasks) that deals with the skills you need. The task(s) would ideally be very difficult for an LLM or search engine to provide a complete answer for; but they shouldn't be gotchas, since that might be false negatives.
Test your task(s) with other people in your company first, so you'll be comfortable when doing it with a candidate.
I can't say that this will 100% prevent cheating. But, you will surely learn a lot about the candidate's habits, in terms of reasoning and communication. If the candidate pastes commands, then that's a possible indication of LLM-usage; if the candidate doesn't use tab-completion, then they might be typing text in from somewhere else (e.g. an LLM, a guide).
I enjoy using the command-line, so I suspect I would enjoy this sort of interview.
At any rate, I hope you find a good candidate.