Ask HN: What is interviewing like now with everyone using AI?

> I don't understand how people don't see that AI can give them "superpowers" by leveraging a developers least productive time into providing their highest value.

I'm unwilling to write code^1 that's not correct, or at least as correct as I'm able to make it. The single most frustrating thing in my daily life is dealing with the PoC other devs cast into the world that has more bugs than features, because they can't tell it's awful. I've seen code I've written at my least productive, and it's awful and I'm often ashamed of it. It's the same quality as AI code. If AI code allows me to generate more code that I'm ashamed of, when I'm otherwise too tired myself to write code, how is that actually a good thing?

I get standards for exclusively personal toy projects, and stuff you want others to be able to use are different. But it doesn't add value to the world if you ship code someone else needs to fix.

^1 I guess I should say commit/ship instead, I write plenty of trash before fixing it.

Also human judgement is loaded with bias. Height influences outcome and this is a statistically proven phenomena. Ask any interviewer in this thread and they will claim height and good looks aren’t a factor but the statistics prove them wrong.

The literal only way to get rid of that is quantitative tests.

> firing people for outright lying about their abilities very quickly

I assume your from the US? The issue with firing people quickly after hiring them is:

* You need to pay whatever headhunter or other personnel that is involved. Some offer a cashback or reduced rate to find a new person, but your still out of the pocket. Do it a few too many times and the headhunter dump you.

* You just wasted a ton of time of other employees, setting up this persons accounts, social benefits, contract negotiation, training time, and more. Again, this is not free.

* Now you are back to looking for other people. You know those people that you rejected, well, the change is reduced that they will come back to your company, maybe they got hired somewhere else, maybe your rejection left a bad impression as you hired that lying person over a actually well qualified person that just did not ace the interview (happens to so many people, often because of nerves).

The trick is, to have a that person (and others in the interview process) work a few days in your company, but this is not covered by a official work contract but a interim contract (of course, you pay those people, some companies are real bastard and do not pay).

That can weed out the people that are good at lying about their skills. But to be honest, if you can not spot them during the interview stage, ...

We had people coming in for Senior positions, and their CVs looked good, they knew how to talk the talk. But when asked for some incredible basic SQL question, they fumbled so much, because they used ORMs their entire life. But loved to place SQL skills on their CV. Seen multiple of those... And so often they then switch to going after the interviewer, thinking that by attacking the interviewer before the boss, that will help them. Yea, "Senior material"...

With AI its going to be the same. People get comfortable using AI, but when you ask code questions without that AI to back them up, that skill gap will exposé themselves very fast during the actual interviews.

I love using AI because it can remove so much boilerplate / repeat / great for finding doc info but you need to know your language. If you grew up with only AI, and do not grow beyond AI to solve every issue, your nothing more but a copy/past dev (AI is just a extension of that dev type).

> Or someone who likes to over abstract everything.

No no, the most annoying ones are those that come in and then want to implement everything into a style they are familiar with! Code rewrites to fit them, framework changes because they are familiar with them... Nothing more fun as hiring somebody to write Angular for 13k/month (talking almost 10 years ago), and then this person pushing Vue, to even rewriting part of the codebase into Vue. Like, we hired you with a insane salary because we are desperate for a Angular developer, if we wanted to rewrite everything to Vue, we will have hired somebody cheaper.

Don’t run code in your head. Run it in reality and step through it with a debugger.

> For somebody who knows their stuff it'll have zero impact

I just tried and it's: hard. It feels like being ask to keep one's breath like writing something.

I need to focus too much on keeping my eyes closed, I don't have enough bandwith left to thing about anything relevant.