One of my favorite interviews (as an interviewer) was when a SDET candidate provided a link to their website. When I visited it there was an issue loading some page. So I asked him about it and how he would troubleshoot, then asked him to come back on Monday with a solution. On Monday, the site was fixed, and he explained to me what happened in AWS, how he figured it out, etc. So he was hired, going on 2 years now and doing very well.
I don’t need robots who can recite what a b-tree is (ChatGPT can do that). I need people who will work hard, can understand the big picture and how to approach problems, while being a good personality on the team.
We were hiring students for a temp position. We're a Controls Engineering company, but my department is dealing with more traditional languages for supporting applications and needed extra help for a bigger project. I know the tech we use isn't standard in the university so the interview was asking students about how they approached their major projects and their methodology for learning new tools/languages.
The first guy who straight up said "I already know enough of C++ and Java, I suppose I'd just google how to do x in c# and branch from there" got the job. Because...yeah, that's about it. We talked about a 4th year project and what his responsibilities in the team where, problems faced, solutions found, etc.
My other favorite is very open-ended questions. I mostly do ops-y interviews, and my favorite question is "what happens when you type 'curl https://google.com' in a terminal and hit enter?"
The question is so broad there isn't a "correct" answer to Google, and it crosses enough domains that any article they find is going to be too long to skim. Then I ask them to really zero in on some aspect of it they feel comfortable with and give detail. What syscalls happen to start up curl? How does the OS know how to communicate with the local router? What's the entire flow to translate "google.com" to an IP?
It's also just fascinating to see which parts candidates latch on to. I had one person spend like 30 minutes just talking about TLS and PKI. Another person delved into kernel packet handling for a while.
MANY super cool convos spun out of this question (interviewed around 60 people). One of them never actually got to the network request part bc we went DEEP into event handlers in a GUI etc. Another candidate was all over the place with key exchange protocols and what and how can go wrong.
I usually don't ask further questions to "corner" them, let them go into any of the details they want.
Ah, I am so happy I am not the only one who invented this interview method :-)
Thing about "Google.com" (I used Facebook/Gmail) is that when server side stuff is of interest (as it was for this cloud engineer job), then I also want to hear about geo DNS, reverse proxies, LBs, CDNs, eventual consistency, distributed storage, etc, all the complexity that is happening once that cat video appears in the browser.
Then again we can go back to JS, CSS, JIT and others' space
Researchers' fields/interests are too narrow, by far, for companies to find enough candidates. Machine learning departments go from low thousands (FANG) to maybe a dozen individuals on the low end (small regional banks, ...). That adds up to let's say 40.000 jobs worldwide.
Plus there's the non-cheating cheating. The majority of conferences (including ICLR/NIPS/CVPR) are still presentations by companies about how they "innovated" by letting an intern use 10-year old techniques, in an established library (ie. not pytorch, but an "integrated" solution, sometimes going as far as an Oracle tool) to look at their own proprietary data (in medical, social sciences, sometimes chemistry). This then delivers them a "paper", goes into the conference proceedings, and they make sure this delivers dozens, sometimes hundreds of citations for all individuals involved.
Don't get me wrong. Delivering a major paper at those conferences is a major, incredible accomplishment that's beyond me, for example. But there's 20-30 people on a yearly basis that "really"/honestly do that and over 5000 total presentations at those conferences. And there's 10000 or more candidates needed to fill positions at companies.
And then the question is: who would you rather hire? A math phd, or frankly even a CS master with no relevant machine learning papers, or that intern?
I had several bad experiences right out of school - I would regularly do programming exercises for recruiters and wasted a lot of my time I will never get back. Some of those exercises would take 3 to 5 hours, and I was told I was one of the faster candidates :/
Once I was able to build a resume and show off projects I told myself I would never go through that experience again.
I don't know if this comment will help you at all, but good luck to you! If you are in the Midwest area I know of a recruiter or two that are great people and can help get you pointed in the right direction. My email is in my profile.
Interviewing is a bit different, since there's no book, but when we looked for a junior dev, the applicants got a laptop with VS Code, the common browsers, internet access and an empty (macOS guest) account, and a few (short!) tasks to show if they understood the questions and were able to start formulating an answer. We also looked for a personality match (we're a small company) and signs of general intelligence. Worked out reasonably well.
I really dislike the more extreme approaches to interviewing that one sometimes comes across, like leet code scores. That's just too disconnected from the actual work. Unless you need your employee to grind leet code questions, of course.
Life insurance companies (in the USA 20 years ago when I sold it) would require a medical exam for every life insurance application. If the applicant commits fraud by having someone else take the examination (usually a blood draw, height and weight measurement, and maybe a heart EKG for bigger policies), the policy is considered valid after two years. Even if the insurance company finds out fraud was committed, the benefit payout is guaranteed after two years.
Taken back to the fraud in interviews, you could make the same argument that after some time working on the job and not gettimg fired, the risk of getting someone not actually qualified did not come to pass, so its more useful to look at the employees current performance than their original fraudulent interview.
This is true not only because of status quo bias, sunk cost etc., but also because employers will often try really hard and be very patient, in the hope that an employee's performance will improve.
So perhaps the medical exam stuff should be swapped around; everyone can get life insurance, but if you want payout for certain things to kick in before two years, you get a medical and pass.
Also, there are some policies that do have limited benefits the first two years. This is especially common for any type of insurance that doesn’t require a medical exam. They tend to be very expensive for the amount of insurance they provide, but maybe have a manageable monthly payment because the amount of coverage is relatively low. This type of insurance is usually “I can’t qualify for anything else” coverage, or it’s for a very specific purpose, like paying for funeral expenses when for some reason the person didn’t have the desire to just save that money in the bank.
- higher premiums for everyone because the pool of applicants aren’t that healthy
- the super sick people simply die in the first two years
- the semi sick people can hang on for years, but weak health may me limited ability to pay because of limited employment prospects
- the not sick people will find better prices or simply realize the insurance is overpriced and cancel it
I suspect you're right.
There certainly are desperate people who go to Vegas, lose their entire savings, and choose to end their life because they're not willing to put in the work to continue trying to survive for another, say, 40 years, starting with zero assets.
There are also people with severe mental illness (poor/no executive function, prone to psychotic episodes, imbalances in their brain chemistry) who make poor choices or don't even consciously make choices but their body is nonetheless doing things, who end up also choosing to end their lives.
There is overlap between these two groups. How could an insurance company decide which is which? If cancer can kill you and they pay out for that, why would they not pay out for deaths due to mental illness? Because they can. We're becoming more willing to talk about mental health, but there's still a ways to go.
There's a ton of stuff that can go wrong with the mind and I couldn't hazard a guess at what proportion of people are 100% okay.
(The free will vs determinism is obviously overly simplistic above)
Basically become a PM for a team of four Vietenamese kids and pull in pay from 3 gigs.
I later did some contracting on the side of a full-time job in 2018 and it was hard -- confusion and burnout set in quickly. But still think about the offshoring approach sometimes...
The new person started and we realized the person that came in had no more information on what/how we had talked about in the interviews than we did. What was done easily over a screen share was well outside of what this person was capable of. In the interview, solid yanking/putting in VIM - in person, unable to save/close, for example. He was present -- we did wonder if the recruiter we worked with had a paperwork mistake, so asked a few bits about our interview and while he could parrot bits of the answer and our discussion, he could not come close to actually hitting the why or next steps like he did in the interview.
That was the point where a camera was required for the interview, for us.
What happens during the actual in-person interview that follows ??
Google Meet is cheaper than a flight & hotel room.
I'm always amazed at the extent people go to to cheat. It gets to the point that you're putting in more effort than you would have to be successful without cheating.
I sometimes feel some people simply enjoy cheating too much. Its not about accomplishing a goal by any means necessary, its something about doing something wrong that certain people seem to enjoy.
This became kind of a business where a person sells his services to help you cheat by appearing instead of you in the video interview and also helps you with the work after you got the job.
If they can still answer the question and show evidence that they understand it, what's wrong with reference materials and googling?
Context matters. If you're looking to see "have you really done security stuff?" by mentioning some OWASP Top 10 vulns and asking for a quick description, for somebody that has indeed done any security at all that will be trivially easy and anybody else will need to google it. Can they skim google and get you an intelligeable answer? Maybe but that's not what you're looking for, the question itself is a proxy for something else.
For most of my interviews I tell folk up front to google whatever they need to. But at the very very earliest stage of the interview loop we do a quick "programmer is a big field, what kind are you?" round so we know how to place people and the questions we use for it are all trivially easy for somebody even remotely familiar with the fields we're looking at and also trivially googleable for anybody else. The goal with that piece isn't to challenge people it's just to round their skillset to the nearest role that we have. I've caught people retyping code, pretending to be inventing it, from what's clearly the first article they found when they googled the keywords. It was never intended to be a hard problem, just something to quickly tell an infrastructure from a frontend engineer. It was more or less bitwise identical to the article they were retyping from and they couldn't explain the code or modify it. That doesn't even accomplish what they want, even if it worked we'd then go on to interview them for a job they couldn't do.
Again you can argue about whether that's a good practise or not but it's still not licence to simply cheat on it. You're conflating these and and I think it's not the right thing to do.
- If the answers are so basic and guessable that one can both find and then deal with a printer to commit it to slow-RAM physical legacy memory, then the problem is not with the candidate
- People with such little self awareness that fail to perceive this problem have demonstrated why you don't want to work with them. The problem is not the fact that they were hotfixing answers straight to prod
- This was just a reverse racial discrimination security test. By identifying the non-authenticated user, you both demonstrated exemplary awareness of identity phishing attacks as well as a base standard that 2 people aren't the same based on their protected identity criteria
* developer attempts to pass something off as video lag, as he attempts to lip sync someone else's answer.
* developer had printed all the 'common' answers on the wall behind his computer, and would look up to them for reference as we were talking. Then the tape came off and covered him in a a paper stack overflow.
* the glorious mechanical keyboard, as they google for an answer.
* interviewed one person and had a different one show up.