Live data from Hacker News

Interviewing a software engineer who prepared with AI

kapwing.com

331–340 of 731 posts

Re: Interviewing a software engineer who prepared with AI

#331
post #317

Earlier quoted context omitted.

So fly them to multiple destinations? I was hired 1 year ago and interviewed with ~14 people all living in different locations. That could be paired down, but it won't ever reach the single destination that the OP is referring to.

Yes but it only one face to face meeting is needed in the process to see if someone is using AI to answer interview. The 13 other interviews can then be online.

this is a great suggestion actually!

Re: Interviewing a software engineer who prepared with AI

#332

I keep coming back to this phrase used in this post: "it was scary". Yeah, hiring is scary. Hiring is insanely expensive on all fronts. Firing people is difficult, it's expensive and legally exposing. Hiring the wrong person, allowing them access your systems and potentially exfiltrate your IP to them is a hazardous but necessary venture. The thing is, none of these things really changed with AI. People have been lyi…

In most highly developed countries, there is a probation period for 90+ days for new hires. During this period, you can be fired for any reason. It is not an expensive as people think to fire someone who deceived your hiring process. However, institution inertia is real. That said, I very much agree with your last paragraph. In the late 1990s and early 2000s, a lot of hiring was done this way in the US.

Unfortunately, in very large organizations the onboarding process can take a while. It can be months before you have credentials to the repository. By then, full benefits will kick in, worker protections, etc.

And I’m a hiring manager. I’m trying to slot new hires with the training they will need and give them realistic tasks I know they can accomplish. And it’s not easy. I’m already 30 days in on a new hire that I’ve been able to peer with for 2 days. And I’m constantly apologizing for the lack of time.

Re: Interviewing a software engineer who prepared with AI

#333
post #313
post #281

Earlier quoted context omitted.

First impressions do count but I think the above poster has a point, a suit can actually harm your chances in an environment where no one wears suits.

First impressions do count but I think the above poster has a point, a suit can actually harm your chances in an environment where no one wears suits. There are many ways to wear a suit. If you walking in wearing a suit that doesn't fit, doesn't suite (no pun intended) you, and it obviously makes you feel uncomfortable then that could count against you. But you walk in wearing a suit that fits, makes you look good, a…

If there is a de facto dress code and you knowingly go against it, even if you look good in whatever you do wear, it makes you look like you don't understand the prevailing norms. This could lead to worries you might not align with other team norms either.

Re: Interviewing a software engineer who prepared with AI

#334
post #285

I keep coming back to this phrase used in this post: "it was scary". Yeah, hiring is scary. Hiring is insanely expensive on all fronts. Firing people is difficult, it's expensive and legally exposing. Hiring the wrong person, allowing them access your systems and potentially exfiltrate your IP to them is a hazardous but necessary venture. The thing is, none of these things really changed with AI. People have been lyi…

The industry is probably going to have to consider the concept of a "qualification", that is a test you take once and then present to employers rather than have each employer make up a different one. I worry about the retreat to networks. I think it's an inevitable response to the rise of machine-generated fakes, that people are going to start strongly preferring to be physically next to someone talking to them simpl…

I mean, aren't great degrees such tests, though they don't check the practical knowledge.

We just need some sort of qualification which tests practical knowledge.

Re: Interviewing a software engineer who prepared with AI

#335
post #289
post #281

Earlier quoted context omitted.

First impressions do count but I think the above poster has a point, a suit can actually harm your chances in an environment where no one wears suits.

I'd want to see some actual hard evidence before I believed that. The usual way social cues work is they are devastatingly effective even if people claim they are not. Much like how most interviewers are honestly convinced that their approach is unbiased but in practice they tend to hire people who are like themselves. My expectation is that turning up in a suit would get better results. The effect is probably smalle…

I agree, but I suspect that you’d have much better luck if you wore something that was superficially similar to the kinds of things other people wore, but was much better fitted and higher quality. For instance, if you showed up in a nice pair of chinos and a tailored buttoned shirt (of appropriate formality), that might come across as being really put together rather than ignoring subtle social cues by dressing in something that stands out by not fitting in.

Re: Interviewing a software engineer who prepared with AI

#336

I keep coming back to this phrase used in this post: "it was scary". Yeah, hiring is scary. Hiring is insanely expensive on all fronts. Firing people is difficult, it's expensive and legally exposing. Hiring the wrong person, allowing them access your systems and potentially exfiltrate your IP to them is a hazardous but necessary venture. The thing is, none of these things really changed with AI. People have been lyi…

In most countries, you have trial periods where you can terminate without too much hassle. Here in Germany, that's usually six months and I know of people in pretty senior positions that got screwed over and terminated towards the end of that period. The problem with hiring in IT is that it's a bit of a broken system. On one hand you have companies that are overly picky and are alienating good candidates with their c…

>a string of meh employers

What's a meh employer?

Re: Interviewing a software engineer who prepared with AI

#337

Earlier quoted context omitted.

>When an HVAC company hires a new tech HVAC has certifications you can get. We should strongly consider this in our industry. I don't think its an unreasonable compromise, especially now with the advent of LLMs.

We have some certs. The problem is that software development is about thirty different skills in a trench coat, and half of them we don't know how to evaluate (like slicing, or abstraction.) What ends up happening is that our certs end up being a bunch of multiple-choice questions that check people's ability to memorize trivia. It is more like having a Certified Novel Writer or Certified Mural Painter or Certified Gr…

People do take university courses in doing creative stuff, a fair number of sucessful novelists seem to have done one, RPG proposed that we could have something similar for software [1].

[1] https://dreamsongs.com/MFASoftware.html

Re: Interviewing a software engineer who prepared with AI

#338

Some people think it's perfectly normal to stretch the truth on a resume, and to lie in an interview. Other people think an interview is just a matter of finding the "magic words" to get the job. What I don't understand is, what did the candidate do with AI? Did they use the AI as a coach? Did they use it to suggest edits to the resume? --- I once interviewed a candidate who was given my questions in advance. (I shou…

I was in this situation on the candidate side :) however I started with "I had your question list beforehand and I searched wikipedia for the answers". I got the job

Re: Interviewing a software engineer who prepared with AI

#340
post #146

Earlier quoted context omitted.

I have seen wild things in the last year. People taking minute-long pauses before answering questions. People confidently saying things that are factually incorrect and not being able to explain why they would say that. People submitting code they don't understand & getting mad when asked why they wrote something that way. I get that candidates are desperate for jobs, because a bunch of tech companies have given up o…

I interviewed every single candidate for development positions in a 300-400 company for the last three years and I saw some incredibly crazy stuff. - A candidate who wore glasses and I could faintly see the reflection of ChatGPT. - A candidate that would pause and look in a different specific direction and think for about 20, 30 seconds whenever I asked something a bit difficult. It was always the same direction, so…

> I interviewed someone for an internship who was getting directions from someone whispering to them. I managed to hear it when they forgot to mute the mic a couple times.

What do you do when something like this happens in an interview? Do you ignore it, call out the interviewee, make a joke about it?

Post reply on HN