I'd like to give the counterpoint to these tips as I have been both interviewer and interviewee.
Exceptional Resume: I agree with most all except the last on the 10+ years - It would depend on how they got that experience. If we're talking a wunderkind who started programing C++ on Linux at 13 and has the bones to show it through sample code/walkthrough sessions, then it's likely legit.
Video vs Voice: This I found cuts both ways. If an interviewee isn't able to get their camera working for some reason, then I would at least begin to talk culture fits, tech, and other details. There should be more than one person in an interview decision so if it's up to just you, I would schedule a follow-up. Frankly, as the interviewee, if someone insists on it and won't even start talking about the job, it's not a place I would want to work at.
Even if the person has the same picture on LinkedIn as onscreen, there are ML-assisted projects on GitHub that will emulate a person so again I wouldn't even stress that much over this part.
And even if it was a legit person, who says they're not going to subcontract out their efforts? Haven't you heard the stories of the engineer who outsourced his work somewhere else and was actually doing that across 4-5 jobs? Even in voice/video meetings, he would be sure to give some "comfort noise" or whatever. But hey, the work got done, and was only fired when they found out that it was not him but his contractors impersonating him in their networks.
Team-coding sessions are legit but I'm looking at how they come to the answer, not just the answer itself.
Now where I see some companies going overboard are obscenely hard or time-intensive pre-screen code sessions of "known programming questions" that have answers on GitHub that they make you go through. *AND THEN* try to paint you into a corner by not giving you access to a web browser.
WHAT TECH JOB DOES NOT ALLOW YOU TO REFERENCE THE INTERNET FOR ANSWERS?!?!?!
If StackOverflow were to shut their doors tomorrow, would you be able to trudge your way through a new API stack or remember every syntax of a library or DB/.SQL command set effectively enough to not have it impact your performance? What if it's a language you are having to pick up as they only do Kotlin or Spring at this shop, not Python? You'd be f'ed.
DevOps is not meant to be a replacement for either Developer or a seasoned Systems Engineer. These are very detailed disciplines of training that are supposed to work hand in hand. Nobody is a full-stack engineer overnight. And even if they were, it's a rare individual to know every facet completely without using a reference.
BS. But today's "hiring" is one big BS anyway :-| At least from experienced developer point of view... Better to put efforts, to be hired in NO-BS-way, for example: https://mikhail.io/2020/07/best-interview-is-no-interview-get-jobs-without-applying/
I'd like to give the counterpoint to these tips as I have been both interviewer and interviewee.
Exceptional Resume: I agree with most all except the last on the 10+ years - It would depend on how they got that experience. If we're talking a wunderkind who started programing C++ on Linux at 13 and has the bones to show it through sample code/walkthrough sessions, then it's likely legit.
Video vs Voice: This I found cuts both ways. If an interviewee isn't able to get their camera working for some reason, then I would at least begin to talk culture fits, tech, and other details. There should be more than one person in an interview decision so if it's up to just you, I would schedule a follow-up. Frankly, as the interviewee, if someone insists on it and won't even start talking about the job, it's not a place I would want to work at.
Even if the person has the same picture on LinkedIn as onscreen, there are ML-assisted projects on GitHub that will emulate a person so again I wouldn't even stress that much over this part.
And even if it was a legit person, who says they're not going to subcontract out their efforts? Haven't you heard the stories of the engineer who outsourced his work somewhere else and was actually doing that across 4-5 jobs? Even in voice/video meetings, he would be sure to give some "comfort noise" or whatever. But hey, the work got done, and was only fired when they found out that it was not him but his contractors impersonating him in their networks.
Team-coding sessions are legit but I'm looking at how they come to the answer, not just the answer itself.
Now where I see some companies going overboard are obscenely hard or time-intensive pre-screen code sessions of "known programming questions" that have answers on GitHub that they make you go through. *AND THEN* try to paint you into a corner by not giving you access to a web browser.
WHAT TECH JOB DOES NOT ALLOW YOU TO REFERENCE THE INTERNET FOR ANSWERS?!?!?!
If StackOverflow were to shut their doors tomorrow, would you be able to trudge your way through a new API stack or remember every syntax of a library or DB/.SQL command set effectively enough to not have it impact your performance? What if it's a language you are having to pick up as they only do Kotlin or Spring at this shop, not Python? You'd be f'ed.
DevOps is not meant to be a replacement for either Developer or a seasoned Systems Engineer. These are very detailed disciplines of training that are supposed to work hand in hand. Nobody is a full-stack engineer overnight. And even if they were, it's a rare individual to know every facet completely without using a reference.