4 ms·
Anxiety on the first interview maybe? I would love to meet someone who was at ease, could explain code in detail (including talking about looping over arrays)
by 0xDEFC0DE 7y ago
Anxiety on the first interview maybe?
I would love to meet someone who was at ease, could explain code in detail (including talking about looping over arrays) and then NOT be able to produce that code.
The second one flat out cheated, but I bet they wouldn't have been able to explain the take home so you might have caught them.
Kinda weak speculation on my part but I guess I could be wrong. I've literally never met anyone like that.
What is the take home like? Maybe the code/answers have leaked somewhere?
- NeverFade 7y agoYou can cheat by paying someone for the solution, and it also comes with a clear verbal explanation that you can read. What GP describes is more common than you'd think. Not surprising when the prize for cheating is a 6 figure job, and there's no penalty at all for getting caught.
- grogenaut 7y agoI've seen cases where people had a friend, someone they were dating or a cs major roommate who it was very likely did the code for them (they mentioned these people encouraging them in interviews) In the gp scenarios they said they were able to Google almost all of the take home and stich the parts together. The overall solution/problem isn't Googleable, we checked.
- NeverFade 7y agoIt doesn't have to be Googleable. There are many people offering to provide solutions for take-home assignments for pay.
- grogenaut 7y agoThe second one could infact explain it all. And could solve design problems. This happens a lot actually, rusty former coders or people who learned in college and never actually did it so it stuck. The first one could also explain the code fine. Interviews 2 and 3 they were comfortable and able to design decent systems but fell over on code. This why I was given the task of "get any code whatsoever after you put them at ease"