upvote
The last job I got (couple months ago), the main technical interview was a bring-your-own-tools pair programming style interview, AI included, where they gave me a repo and a README detailing some desired features to add and bugs to fix. I didn't write a single line of code myself; I talked through my thought process and asked questions about what to consider from a technical and product perspective, while steering Claude through breaking the tasks into independent plans, reviewing the plans, coaching it to add specific tests, reviewing and iterating the tests, and steering it while it wrote the code. I got an offer the next morning.

Apparently at least one of the other candidates just tried to get Claude to 1-shot the whole thing, which went off the rails, and left him unable to make progress.

Based on my sample size of 1, the expectation right now is absolutely that you can leverage these tools to speed up your workflow, but if you try to offload the entire thing to a single hands-off prompt it leaves them justifiably wondering why they should hire you to do something they can do themselves.

reply