I linked this to my team and got back "I had almost identical experience with some candidates though no one admitted faking" and "One candidate just disconnected and was never heard back from after being asked to remove virtual background". Interviewing is hard. Over the years the one thing I have learned is that for a technical role you want to interview people for how they THINK and REASON. This is hard and require…
Interviewing a software engineer who prepared with AI
571–580 of 731 posts
Re: Interviewing a software engineer who prepared with AI
#572"Preparing with AI" sounds like an issue here, and it's not. The issue is lying about your experiences, which people have done since the beginning of time. I "prepare with AI" by having it help give me hints when doing leetcode problems, which is very helpful. Interviewing is not a presentation, it's a conversation, and having a simulated other side can be helpful. This shouldn't be surreal at all. A candidate just w…
>The issue is lying about your experiences Side note, as far as a job requirements goes the bigger issue is asking for impossibly diverse experience and asking for things that can be easily learnt. This promotes lying because the liars are the ones that are rewarded with an initial interview. I was talking to a fresh graduate with some volunteer experience who was having difficulty getting a job, and all I could hesi…
This are not school exams, company wants to hire the best candidate. If all fail then best failing is still the best candidate, and this can be measured and/or perceived by skilled interviewers.
Re: Interviewing a software engineer who prepared with AI
#573Earlier quoted context omitted.
>The issue is lying about your experiences Side note, as far as a job requirements goes the bigger issue is asking for impossibly diverse experience and asking for things that can be easily learnt. This promotes lying because the liars are the ones that are rewarded with an initial interview. I was talking to a fresh graduate with some volunteer experience who was having difficulty getting a job, and all I could hesi…
My compromise here is invisible words in the PDF. I pack it with every freaking keyword I can think of because I have absolutely no issues with lying to a robot and don't feel the need to a respect a hiring process where they can't be bothered to so much as read my resume. Funny enough I often get offers after that even when I don't have some specific technology. That said, my personal ethics don't let me lie to an a…
Re: Interviewing a software engineer who prepared with AI
#574Earlier quoted context omitted.
> I "prepare with AI" by having it help give me hints when doing leetcode problems I've been really impressed with how much a of performance lift working on leetcode with AI is. It's so much easier to focus on developing rapid problem decomposition skills and working with an interviewer during the problem. Unfortunately it's also necessary to improve this process because the current standards for the companies still…
English is not my first language, and yet I'm fluent, but some of the questions I've been asked to solve are insanely confusingly worded and so I have a harder time because the interview process at some places is unrealistic.
Re: Interviewing a software engineer who prepared with AI
#575Re: Interviewing a software engineer who prepared with AI
#576Earlier quoted context omitted.
Too real. I once got turned down by the Apple Store for a retail position because I wore a collared shirt to the interview (after being told in advance not to wear anything formal). Interviewer let me know I came off as too formally dressed to get their vibe. The discrimination/bias was real.
I mean, if they said not to wear something formal, that doesn't really seem like bias as much as just not following instructions. If I showed up to an interview where they said to wear a suit and I was in jeans and a polo, I'd expect to get turned down too.
Re: Interviewing a software engineer who prepared with AI
#577It's really easy to catch these scammers. Ask for a non-trivial code or work sample, something they have written. Actually take the time to read through the code and understand at least a part of it. In an interview, ask them some questions about it. People who actually wrote the code or did the thing can talk at length about about what they did, the history behind it, trade offs, have colorful stories about it, etc.…
If I just have to give a code example of mine on the spot during an interview with no prep, I'm sure as hell not going to remember why I took a certain approach unless there are comments.
Re: Interviewing a software engineer who prepared with AI
#578Earlier quoted context omitted.
Spending a few hours to write some open source code seems like a reasonable tradeoff to get a high paying job. It is surprising to me that folks looking for a new job would not do this proactively.
Because interviewers don't care. I have tons of code on my personal github page and even thought it's listed on my resume/linkedin, no interviewer has ever looked at it. This includes contributions to a widely used OSS project. YMMV, but all the high paying jobs I've received were due to knowing the tech stack they used and being able to walk through the projects that I've done in detail. Admittedly, the last time I…
Re: Interviewing a software engineer who prepared with AI
#579Earlier quoted context omitted.
Well, let's see you do it! Can you deblur something like the first 2-3 letters of a name?
> Well, let's see you do it! That's a bit rude to be making demands when I was just trying to provide some helpful info. If you want to learn more, you can google it. I'm not the person who invented deconvolution. It's not secret knowledge.
Re: Interviewing a software engineer who prepared with AI
#580Earlier quoted context omitted.
>The issue is lying about your experiences Side note, as far as a job requirements goes the bigger issue is asking for impossibly diverse experience and asking for things that can be easily learnt. This promotes lying because the liars are the ones that are rewarded with an initial interview. I was talking to a fresh graduate with some volunteer experience who was having difficulty getting a job, and all I could hesi…
> Side note, as far as a job requirements goes the bigger issue is asking for impossibly diverse experience and asking for things that can be easily learnt. Really? That's the bigger issue? Company wants to pay money to someone in exchange for services. They have unreasonable expectations. So that makes it OK for people to deceive them in order to have them believe that their unreasonable expectations have been met?…