55 ms·

Okay, so he got the interviews, but did he pass them? In the place I work for, when engineers are going to conduct technical interviews, the only preparation m

Okay, so he got the interviews, but did he pass them? In the place I work for, when engineers are going to conduct technical interviews, the only preparation material they are given is the candidate's resume. So we try to ask questions based on their experience in the places they claimed to have worked for. It's not super hard to realize the job description in the resume is embellished once you start asking questions, but yes this is not fool-proof. Still, the best candidates will often have very interesting discussions about challenges they had in their previous jobs and be able to properly articulate what they did and why and how. If you're gonna lie, you better back it up very well.

NewUser76312 2y ago
I'm curious about this more from an employer's perspective, especially as a smaller operation (contracting firm). If somebody claims to have worked at Amazon as a product manager for 2 years, and rehearses a story they wrote with ChatGPT (who maybe has data from blogs of related product managers)... Then I'd probably get fooled, if the candidate was reasonably well-spoken and confident. Similarly, I don't have the time or patience to contact a university to try and get real verification for a transcript. Just being honest...
- TeMPOraL 2y ago
  Ironically, for some roles (more on the people and marketing side), a candidate that managed to convincingly act out a fabricated employment history would be demonstrating the very skills required for the job they're interviewing for.
  - ChrisMarshallNY 2y ago
    I remember telling an interviewer that I could provide links to decades' worth of repos, with full, high-Quality source code for multiple shipping apps, and very detailed checkin history. I could also reference Web sites, with many years' worth of extremely well-written blog entries and tutorial series. I was told they weren't going to look at it, because I "probably faked it." It was at that point, that I realized that no one wanted me, and I gave up looking. I guess that I could have said that if I had been able to fake that stuff, they should hire me right away, because I'm a leet wizard, but I'm sure they said that, to evoke exactly the reaction they got, and I was better off, not working there. I won't go, where I'm not wanted.
- dyingkneepad 2y ago
  On the technical side, if you have actually worked with certain stuff you will have gone through certain experiences that everybody else has gone through. Some tools are absolutely necessary but horrible to work with in certain ways. Some libraries are a pain in the back to use, but are unavoidable. Compiling certain components may be a huge pain. Stupid example: the person claims they know CSS, and you bring up the subject of aligning a div for the first time.

NewUser76312 2y ago

I'm curious about this more from an employer's perspective, especially as a smaller operation (contracting firm). If somebody claims to have worked at Amazon as a product manager for 2 years, and rehearses a story they wrote with ChatGPT (who maybe has data from blogs of related product managers)... Then I'd probably get fooled, if the candidate was reasonably well-spoken and confident. Similarly, I don't have the time or patience to contact a university to try and get real verification for a transcript. Just being honest...

TeMPOraL 2y ago
Ironically, for some roles (more on the people and marketing side), a candidate that managed to convincingly act out a fabricated employment history would be demonstrating the very skills required for the job they're interviewing for.
- ChrisMarshallNY 2y ago
  I remember telling an interviewer that I could provide links to decades' worth of repos, with full, high-Quality source code for multiple shipping apps, and very detailed checkin history. I could also reference Web sites, with many years' worth of extremely well-written blog entries and tutorial series. I was told they weren't going to look at it, because I "probably faked it." It was at that point, that I realized that no one wanted me, and I gave up looking. I guess that I could have said that if I had been able to fake that stuff, they should hire me right away, because I'm a leet wizard, but I'm sure they said that, to evoke exactly the reaction they got, and I was better off, not working there. I won't go, where I'm not wanted.
dyingkneepad 2y ago
On the technical side, if you have actually worked with certain stuff you will have gone through certain experiences that everybody else has gone through. Some tools are absolutely necessary but horrible to work with in certain ways. Some libraries are a pain in the back to use, but are unavoidable. Compiling certain components may be a huge pain. Stupid example: the person claims they know CSS, and you bring up the subject of aligning a div for the first time.