Live data from Hacker News

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

news.ycombinator.com

511–520 of 735 posts

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

#511
not a problem yet - we still start asking hard question first - on differences on TCP and UDP and which one is better and why - very deep rabbit whole I must say. Then simple questions - how do you manage k8s clusters and what you suggest for multi DC setups

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

#512
post #68

Earlier quoted context omitted.

I recently interviewed for my team and tried this same approach. I thought it made sense because I want to see how people can actually work and problem solve given all the tools at their disposal, just like on the job. It proved to be awkward and clumsy very quickly. Some candidates resisted it since they clearly thought it would make them judged harsher. Some candidates were on the other extreme and basically tried…

Over the years, I've walked from several "live coding" interviews. Arguably though, if you're looking for "social coders" maybe the interview is working as intended? But for me, it's just not how my brain works. If someone is watching me, I'll be so self-conscious the entire time you'll get a stream of absolute nonsense that makes me look like I learned programming from YouTube last night. So it's not worth the time.…

Ironically this is exactly how I am too. Even at work, if I'm talking through a problem on a presentation or with my boss, I'm much more scatterbrained, and I'll try to dodge those kinds of calls with "Just give me 30 minutes and I'll figure it out." which always goes better for me.

That said, now we're just talking about take home challenges for interviews and you always hear complaints about those too. And shorter, async timed challenges (something like "Here's a few hours to solve this problem, I'll check back in later") are now going to be way more difficult to judge since AI is now ubiquitous.

So I really don't think there's any perfect methodology out there right now. The best I can come up with is to get the candidate in front of you and talk through problems with them. The best barometer I found so far was to set up a small collection of files making up a tiny app and then have candidates debug it with me.

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

#513
post #478

Earlier quoted context omitted.

I stopped using AI for code a little over a year ago and at that point I'd used Copilot for 8-12 months. I tried Cursor out a couple of weeks ago for very small autocomplete snippets and it was about the same or slightly worse than Copilot, in my opinion. The integration with the editor was neat but the quality of the suggestions were no different than what I'd had with Copilot much earlier, and the pathological case…

The cursor auto complete? It's useful but the big thing is using sonnet with it.

I tried it with Claude Sonnet 3.5 or whatever the name is, both tab-completed snippets and chat (to see what the workflow was like and to see if it gave access to something special).

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

#514
post #463

Earlier quoted context omitted.

When I was interviewing candidates at IBM, I came up with a process I was really happy with. It started with a coding challenge involving several public APIs, in fact the same coding challenge that was given to me when I interviewed there. What I added: 1. Instead of asking "do you have any questions for me?" at the very end, we started with that general discussion. 2. A few days ahead, I emailed the candidate the pr…

What, what? Harmonicas are tunable? TIL...

Oh yes, they are!

You just need a small file, like a point file. Any gasheads remember those? And a single edge razor blade or the like to lift the reed.

To raise the pitch, you file the end of the reed, making it lighter so it vibrates faster.

To lower the pitch, you file near the attached end of the reed. I am not sure on the physics of this and would appreciate anyone's insight.

The specific tuning I've done many times is to convert a standard diatonic harp (the Richter tuning) to what is now called the Melody Maker tuning.

The Richter tuning was apparently designed for "campfire songs". You could just "blow, man, blow" and all the chords would sound OK.

Later, blues musicians discovered that you could emphasize the draw notes, the ones that are easy to bend to a flat note to get that bluesy sound. This is called "cross harp". For example, in a song in G you would use a C harp instead of one tuned in G.

The problem with cross harp is that the 7th is a minor 7th and you have no way to raise it up to a major 7th if that would fit your song. And the 2nd is completely missing! In fact you just have the tonic (G in this case) on both the draw and blow notes where you might hope to hit the 2nd (A). There is no A in this scale, only the G twice.

To imagine a song where this may be a problem, think of the first three notes of the Beatles song All My Loving. It starts with 3-2-1. Oops, I ain't got the 2. Just the 1 twice.

This is where the file comes in. You raise the blow 1st to a major 2nd. And you raise the minor 7th to a major 7th in both octaves.

Now you have a harp with that bluesy sound we all love, but in a major scale!

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

#515

My company, a very very large company, is transitioning back to only in-person interviews due to the rampant amount of cheating happening during interviews. As an interviewer, it's wild to me how many candidates think they can get away with it, when you can very obviously hear them typing, then watching their eyes move as they read an answer from another screen. And the majority of the time the answer is incorrect an…

So far 3 of the 11 people we interviewed have been clearly using ChatGPT for the >>behavioral We actually allow using AI in our in-person technical interviews, but our questions are worded to fail safety checks. We'll talk about smuggling nuclear weapons, violent uprising, staging a coup, manufacturing fentanyl, etc. (within the context of system design) and that gives us really good mileage on weeding out those who…

> I find that absolutely insane, if you cannot hold a basic conversation about your life without using AI then something is terribly wrong.

I'm genuinely curious what questions you ask during the behavioral interview. Most companies ask questions like "recall a time when..." and I know people who struggle with these kinds of questions despite being good teammates, either because they find it difficult to explain the situation, or due to stress. And recruitment process is not a "basic conversation" — as a recruiter you're in far more comfortable position. I find it hard to believe anyone would use an LLM if you ask them question like "what were your responsibilities in your last role", and I do see how they might've primed the chat to help them communicate an answer to a question like "tell me about a situation when you had a conflict with your manager"

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

#516
post #493

Earlier quoted context omitted.

Is your job consulting for hiring technical positions?

I have a consultancy - we mostly do development, but I also do quite a bit of "consulting CTO" work. Quite often, that means helping with hiring. But hiring is nowhere near my full time job, thankfully :D

That’s cool. My main job is being a research scientist but i also work at a computational science consultancy that essentially builds numerical simulations for hire along with other software consultancy jobs. I occasionally have been asked to serve as an outside consultant for hiring data science positions. I’ve been wondering how to grow that a bit into more regular work because I enjoy it. Any thoughts on that?

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

#517
post #68

Earlier quoted context omitted.

I recently interviewed for my team and tried this same approach. I thought it made sense because I want to see how people can actually work and problem solve given all the tools at their disposal, just like on the job. It proved to be awkward and clumsy very quickly. Some candidates resisted it since they clearly thought it would make them judged harsher. Some candidates were on the other extreme and basically tried…

> "You can even use ChatGPT as long as you're not just directly asking for the solution to the whole problem and just copy/pasting, obviously." No, it's not "obvious" whatsoever. Actually it's obviously confusing: why you are allowing them to use ChatGPT but forbidding them from asking the questions directly? Do you want an employee who is productive at solving problems, or someone who guess your intentions better? I…

See my answer to the other comment on this question. We figured there were some good use cases for AI in an interview that weren't just copy/pasting code, it's not about guessing intentions. It seemed most helpful to potentially unstick candidates from specific parts of the problem if they were drawing a blank under pressure, basically just an easier "You can look it up on Google" in a way that would burn less time for them. However we quickly found it was just easier for us to unstick them ourselves.

> If AI is an issue for you then just ban it.

Yes, that was the conclusion I just said we rapidly came to.

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

#518
post #127
post #68

Earlier quoted context omitted.

I recently interviewed for my team and tried this same approach. I thought it made sense because I want to see how people can actually work and problem solve given all the tools at their disposal, just like on the job. It proved to be awkward and clumsy very quickly. Some candidates resisted it since they clearly thought it would make them judged harsher. Some candidates were on the other extreme and basically tried…

Did you tell them that you “want to see how people can actually work and problem solve given all the tools at their disposal, just like on the job”? Just curious.

Yup, we told them exactly that.

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

#519
post #305

Earlier quoted context omitted.

AI gives super powers because it saves you an insane amount of typing. I used to be a vim fanatic, I was very efficient but whenever I changed language there was a period where I had to spend getting efficient. Setup some new snippets for boilerplate, maybe tweak some LSP settings, save some new macros. Now in cursor I just write "extract this block of code into its own function and set up the unit tests" and it does…

> AI gives super powers because it saves you an insane amount of typing. I must be very different, as very little of my coding time is spent typing.

I think that spending a lot of time typing is likely an architectural problem. But I do see how AI tools can be used for "oneshot" code where pondering maintainability and structure is wasted time.

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

#520
post #305

Earlier quoted context omitted.

AI gives super powers because it saves you an insane amount of typing. I used to be a vim fanatic, I was very efficient but whenever I changed language there was a period where I had to spend getting efficient. Setup some new snippets for boilerplate, maybe tweak some LSP settings, save some new macros. Now in cursor I just write "extract this block of code into its own function and set up the unit tests" and it does…

> AI gives super powers because it saves you an insane amount of typing I feel like I'm going a little bit more insane whenever folks say this, because one of the primary roles of a software engineer is to develop tools and abstractions to reduce or eliminate boilerplate. What kind of software are you writing, where generating boilerplate is the limiting factor (and why haven't you fixed that)?

> because one of the primary roles of a software engineer is to develop tools and abstractions to reduce or eliminate boilerplate.

Is it? Says who? Not only do I see entire clans of folk appearing who say ; DRY sucks, just copy/paste, it's easier to read and less prone to break multiple things with one fix vs abstractions that keep functionality restricted to one location, but also; most programmers are there to implement crap their bosses say, that crap almost never includes 'create tools & abstractions' to get there.

I agree with you actually, BUT this is really not what by far most people working in programming believe one of their (primary) roles entail.

Post reply on HN