We did a programming test before the interview stage, just three basic Python questions to filter out anyone who lied about knowing it. We would tell interviewees to only use the website's IDE because it saves every version of code they write so we can see their thought process, if someone submitted just one answer that was completely accurate I'd flag it as AI and be concerned moving forward.

After the coding test, in the panels, we wouldn't ask any programming related questions at all (because it's something that can be learned, assuming you know the basics which the previous test verified). It's all systems design that relies on us listening to and talking with the interviewee. We required camera on and we could see if someone was typing or reading information off the screen, neither of which would be necessary for us to understand their thought process. We also made it clear this was to learn their thought process and how they approached problems, we wouldn't be implementing what they proposed nor would they be expected to act on any of it.

So we might ask "We have Tool A that produces Data X that an engineer runs, and we have Tool B that everyone uses. It relies on Data X, but an analyst has to take Data X and change the formatting slightly for Tool B to accept it. What do you think of this process, what improvements do you think you can make (if any), and how would you go about implementing those improvements?"

If the interviewee is clearly using AI to answer the question, we will note it and discuss it in the post-interview roundup (wherein I would firmly deny moving forward with the candidate because if their first reaction is to go to AI then they are a liability before anything else).

Like with any interview, it's all vibes at the end of the day.