My one and only Google interview went this way years ago. Each round they'd send me more books to study, which frankly I couldn't be bothered to read given the circumstances. My experience ended when an interviewer in round 3 or 4 asked me an obviously scripted question. I answered sarcastically, he got peeved, and I never heard from them again. I'm not claiming I'm Google caliber, whatever that means. Obviously I'm…
And yet if they ask you for an answer to a quirky question like "why are manhole covers round?", they expect a clever answer like "they can't fall in", rather than a pedestrian answer like "well, probably they just started making them that shape for some simple production reason, and then everyone else just kinda of did the same thing because it worked."
The rise of never-ending job interviews
181–190 of 1001 posts
Re: The rise of never-ending job interviews
#182Earlier quoted context omitted.
Google is infamous for jerking people around in the interview process. I had a very similar experience, as did several people I know. They do it because they know they can get away with it, but I do wonder if they have a backup plan if the lustre of working for Google ever fades, because it's an open secret that their interview process is a fucking nightmare for no reason.
That lustre has faded already.
Re: The rise of never-ending job interviews
#183Earlier quoted context omitted.
Devil's advocate. Every bad hire costs the company $50,000 - 200,000. Sometimes more. They can also sink or demoralize teams. Many of the people conducting interviews are new to the process and don't know how to extract signal. Sometimes scales don't line up. When you have a revolving door of employees (because that's the way things are these days), have trouble scheduling interviews (busy engineers trying to get the…
Yes, every bad hire is really bad. However, companies generally don't put in any effort into seriously evaluating your publicly available work. I have reams and reams of open source code companies can take a look at, and I've never seen any evidence that any company I've ever interviewed at has looked at that work. That's a result of companies being completely incompetent at evaluation and disrespecting their candida…
If I submit some “open source” code as some proof that I can code, how do you know I didn’t copy the code from somewhere?
Also, writing code for the sake of writing code doesn’t tell a hiring manager if the person can take requirements and translate that to an automated process. It just say that person isn’t that busy and can, excuse my language, shit out code for the sake of appearing productive.
Writing code can be a hobby, sure, but that’s only a small part of a software job and no amount of open source code can tell a company if the candidate can work with others and solve problems.
Re: The rise of never-ending job interviews
#184Earlier quoted context omitted.
Devil's advocate. Every bad hire costs the company $50,000 - 200,000. Sometimes more. They can also sink or demoralize teams. Many of the people conducting interviews are new to the process and don't know how to extract signal. Sometimes scales don't line up. When you have a revolving door of employees (because that's the way things are these days), have trouble scheduling interviews (busy engineers trying to get the…
This is mostly management speak for: don't blame us, we're just incompetent . If you run a company and you have a "revolving door of employees" (ie: we can't retain talent), your managers "are new to the process" and don't know what they're looking for (ie: we hire inexperienced managers), and you "can't get enough skilled interviewers on a panel" (ie: "we don't hire enough engineers and we're too cheap and shortsigh…
Re: The rise of never-ending job interviews
#185In domains in which the underlying domain is complex, with an irreducible informational complexity, as well as rich and frequently highly significant interactions, there's a frequent emergence of faddish, or ritual-driven, behaviours. Both seek to reduce risks and accountability, as well as to increase credible signalling of traits. Both sides of the technical recruiting transaction (job-seeking and recruiting) exhib…
> I've speculated that one of the justifications for the ancient Egyptians to build pyramids was as a combination of a skills-development, skills-retention, skills-demonstration, and brain-drain-mitigation programme. From what I've read there's at least some independent informed speculation along similar lines. Brain drain mitigation? Brain drain just wasn't a possibility 4400 years ago.
Pharonic Egypt circa 2580 was not without neighbours and there was both trade and warfare in North Africa and across the Levant and Mediterranian, notably with Syria, Canaan, Lebanon ("cedars of Lebanon" are a significant reference, as Egypt had virtually no timber), Ethiopia, and Nubia, amongst others. There's also the prospect of defection to internal factions. The Old Kingdom seems to have been generally peaceful with little internal or foreign warfare, at least until the First Intermediate Period, which was largely an internal rivalry. But it wasn't entirely without defence concerns.
https://en.wikipedia.org/wiki/Ancient_Egyptian_trade
https://www.worldhistory.org/Egyptian_Warfare/
I'm very happy to admit that my hypothesis is just that, and that there's no evidence and only a very little external support, though there is some. But if you're going to develop an advanced skill that would be of use throughout the region, it might be advisable to find ways to hold on to it, and as a pragmatic explanation for what was an absolutely immense effort ... there's some sense in the concept.
Re: The rise of never-ending job interviews
#186I’ve never had a company string me along. Four separate phone screens or interviews seems to be the limit. I’ve even been hired after one video conference interview.
I once was given a “we want to hire you, but we need to get the funds together before we can give you the offer” spiel during the great post-mortgage economic recession, but they did hire me after about a month.
After five separate rounds (again, talking to multiple teams on the same day after one or two technical phone screens and one recruiter call doesn’t count; that’s standard practice with many companies), I would tell a company they need to either, as my father put it, “shit or get off the pot”.
In terms of take home assignments, I have no problem doing them, as long as the employer has no problem having me put my answers on a public GitHub repo. I will not do Codility tests, because my experience is that employers who do those kinds of tests are Unicorn hunters.
Re: The rise of never-ending job interviews
#187Earlier quoted context omitted.
This a hundred times over. I still remember in 2020 multiple places asking me "I see you've used .NET core, what *version* have you used?". I had a kind of career crisis/breakdown, where I realised no one gave a shit about anything except my utility as a walking set of tech keywords. Accepting that it wasn't working for me was one of the best things I've done for my career.
> where I realised no one gave a shit about anything except my utility as a walking set of tech keywords. I am genuinely asking. Why is this objectionable? Why do people find it so horrible that their labour is a commodity? To me that just tells me I should treat my labour like a merchant treats his goods. Always be checking the market to ensure you have something worth selling and while you might sign long term deal…
Re: The rise of never-ending job interviews
#188Earlier quoted context omitted.
LOL. He was obviously way smarter than me. He probably told his colleagues about how some dummy was talking about dinosaurs in an inode. I feel the smartass part of my brain eternally dooms me...
This makes me thing of the time I was interviewed by three bankers. I'd probably be rich and miserable had I answered non sarcastically :/
Re: The rise of never-ending job interviews
#189Re: The rise of never-ending job interviews
#190Earlier quoted context omitted.
Manhole covers are round because they minimize the circumference per area that must be cut to make the cover fall in.
Obligatory https://sellsbrothers.com/12395