I am still a junior but this seems like you are interviewing the AI rather than the candidate. Also why bother with a technical interview if you expect AI to do their job?
https://www.businessinsider.com/coders-keep-laptops-open-in-... ;)))
such as " hiring me will ensure that your AI sessions are few and limited to a couple hundred dollars expense, bare minimum, a human must prompt an AI or it does nothing. as a [professional] i have insight regarding structuring prompts, as well as fast response to code based remediation for incidents involving off the rails output, and abberant alignment adoption."
also: interviews can be more about,how you respond to being knocked off your footing, rather than gathering rote factoids about "you".
People use Leetcode because they believe it tests for programming aptitude.
There are also people who, no matter what, could not live code simple tree traversals or bin search or something, and it filters on that.
Finally, there's a pattern matching aspect to it. Some of the best interview questions I got involved very simple algorithms, but it was obfuscated by the problem. So the 'trick' was to just think through the problem and ask questions. Not to have memorized something obscure.
Basically I read the JD, find some stories from my work that I can tell, brush up the CV for a bit and then that’s it. I don’t prepare for LC interviews and if I get one I just decline.
All else is confidence, experience, nice professional stories, curiosity, good soft skills. People need to like you as a person, to feel unconsciously that working with you will be safe, cool, fun, productive process.
Make this thing that would be impossible without AI. The test is to see if you actually architect it properly and understand principles of how things connect together.
Make this thing that would be impossible without AI. Now make these modifications without any AI.
Make this thing. You may use low quality AI like Composer 3 or none at all, but if you use none, we'll probably think of you as some kind of boomer.
Here's a bunch of technical problems that we don't know the answer to. If you give answers or insights we haven't considered, then you're bringing value to the team (e.g. git/PR policy, microservices, feature flagging, localization, security)
Would love feedback on my HTML-to-PDF API — pdfkitt.dev