Live data from Hacker News

Interviewing a software engineer who prepared with AI

kapwing.com

291–300 of 731 posts

Re: Interviewing a software engineer who prepared with AI

#291
post #187

Earlier quoted context omitted.

> Nearly every large company I've interviewed with would comply with a reasonable accommodation request for a legitimate disability so neuro divergence isn't a legitimate disability?

> so neuro divergence isn't a legitimate disability? It doesn't really matter if it is or isn't, if being able to function well around other humans is a job requirement, as it often is in technical occupations. Why do you think behavioral questions are often asked during interviews? For the same reason someone who requires a wheelchair could not reasonably be expected to be a firefighter, or a blind person be a pilot…

Yeah but software / digital is a great equalizer, where all kinds of people can contribute even with disabilities or neurodivergence. The whataboutism doesn't really work.

Re: Interviewing a software engineer who prepared with AI

#292

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…

> it's time to buy a suit

Yeah, no. I'd deduct points if the candidate wears a suit. What a huge red flag, missing all sorts of context and appropriateness cues.

Re: Interviewing a software engineer who prepared with AI

#293

Earlier quoted context omitted.

> - And yeah, you guys, it's time to buy a suit. Others have already commented on this, but do you work in tech? IME getting interviewed by directors and even VPs in t-shirts is the norm. I’ve worn jeans to work my whole career. If anything, I think people in tech have a strong prejudice against people in suits (ie “obviously this person isn’t a real software engineer, they’re wearing a suit.”) Anyway, probably not g…

The general rule seems to be if you’re not customer-facing, then no suit is needed. Just wear clean, neat clothes and that’s usually enough. If a suit or uniform is needed, that would be noted up front.

The general rule is to dress one step up from those in the role. Everyone in hoodie and shorts? Wear pants. Everyone in collared polos? Go business casual with maybe a blazer. Showing up a level lower makes you look unprepared. Showing up some levels higher, like in a suit to a hoodie shop, shows lack of research and reading a room.

In start ups, I have seen candidates nearly rejected just on a suit alone. Def started them on the wrong foot impression wise.

Re: Interviewing a software engineer who prepared with AI

#294

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…

No Computer Science degree = forget about it. In the past we took a chance hiring people with non traditional backgrounds but now that everyone thinks they can do complex engineering with the help of AI, we need to know people have truly studied the fundamentals over a period of 4 years at a university.

I'm inclined to agree, but at the same time, I've worked with people who proved themselves in the industry already. My senior developer at the time, had 15 years experience but no formal relevant education.

Re: Interviewing a software engineer who prepared with AI

#295

Earlier quoted context omitted.

You assume we aren't going to end up wearing them daily in order to get promotions. The same elitist power trip that drove RTO is also likely to produce the "dress like us & be rewarded" dynamics that push for conformity.

In more detail, in a glutted market with an unknown percentage of fakers, companies look for costly signals they can use to sort. This particular signal also indicates a willingness to set aside one's individual ego in order to assimilate in the workplace, which is especially valuable to the companies demanding developers abandon good sense in order to push AI adoption. If we want that signals to not be "a suit", it…

Outside of fintech, none of the highest paid devs are in suits. Not sure if it is even still a thing in fintech actually.

I am FAANG/FAANG adjacent. People making 400-700k/yr. I only see suits at holiday parties.

Re: Interviewing a software engineer who prepared with AI

#296

Earlier quoted context omitted.

> Classic bigotry. Hiring is all about finding the best candidate. If you find you cannot function sitting in conference room with three other people for an hour, there is a 100% chance there is a better candidate suited for the role, even if his/her technical skills are less than yours. Jobs have soft skill requirements, and there is nothing bigoted about that.

I'm curious about this. When I've hired, I've always wondered how I can actually tell (a) what soft skills are required for the role and (b) whether a candidate has them. People sometimes think that's a silly thing to ponder: it's obviously obvious! But at most places I've worked, we spend lots of time defining the technical skills required for a job and handwave the rest. I guess people assume "they'll know it when…

I like this idea of making the soft skills explicit. Both to the interviewers and the candidate (i.e. in the job posting itself). This would save everyone involved a lot of time, too!

Re: Interviewing a software engineer who prepared with AI

#297

Earlier quoted context omitted.

There were 30% layoffs at a company I worked at and one of the 'survivors' was so traumatised by it that they took their own life. It's a known phenomenon: https://en.wikipedia.org/wiki/Survivor_guilt

Layoffs are generally random firing. Especially when we talk about % points.

What's your point? The thread is about how other people being fired is stressful.

Re: Interviewing a software engineer who prepared with AI

#298

Earlier quoted context omitted.

You are right about hiring not being that much different but your prognostications are way off IMO. > - people are probably going to have to fly out for interviews, again. Fly where? Many companies don't have offices anymore. > - awkward and/or neurodivergent people are going to have to learn social skills again. Ahh... the age old, "just do better" position for neurodivergent people. Classic bigotry. > - And yeah, y…

> Fly where? Many companies don't have offices anymore. Presumably to meet the boss. And maybe the key people on the team.

You can always rent a conference room for an hour or so somewhere in between.

Re: Interviewing a software engineer who prepared with AI

#299

Earlier quoted context omitted.

The general rule seems to be if you’re not customer-facing, then no suit is needed. Just wear clean, neat clothes and that’s usually enough. If a suit or uniform is needed, that would be noted up front.

The general rule is to dress one step up from those in the role. Everyone in hoodie and shorts? Wear pants. Everyone in collared polos? Go business casual with maybe a blazer. Showing up a level lower makes you look unprepared. Showing up some levels higher, like in a suit to a hoodie shop, shows lack of research and reading a room. In start ups, I have seen candidates nearly rejected just on a suit alone. Def starte…

That's the point. One of my first interviews in tech was with a CEO who dressed with an Iron Maiden t-shirt. That settled to me the question about whether I would need to worry too much about looks at the office! :)

Re: Interviewing a software engineer who prepared with AI

#300
post #11

Potentially important side points, since not everyone knows, and we don't want anyone to learn a mistake by example: 1. Don't use blur to redact documents. Whatever blur was used can probably be reversed. 2. Don't try to hide the identity of someone you're talking about by redacting a few details on their resume. With the prevalence of public and private resume databases, that's probably easy to match up with a name.

There’s a few red flags here on the hiring side too. I’ve given a lot of interviews, candidates will always try to come up with the best story as an answer to your question because “I can’t think of an example” is not an acceptable answer. It’s a demand you’re placing on them. Also having experience puffed up on a resume happens around 100% of the time. The point of the interview is to figure out how much real releva…

> having experience puffed up on a resume happens around 100% of the time

Maybe I am the rounding error. I have zero puffery, exaggerations, embellishments, stolen credit, or lies on my resume.

Post reply on HN