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…
The rise of never-ending job interviews
421–430 of 1001 posts
Re: The rise of never-ending job interviews
#422Earlier quoted context omitted.
did you expect others to have empathy for you?
I think the bigger issue here is that this process has made it too random and dilutive of the candidate pool. Many software engineers have accepted that they have to continually learn and will do so. This process though, makes it impossible to know what to learn with an impossible random and unknown credential set. It's not the same as something like elevator attendants having an obsoleted skillset. It's a combinatio…
At the risk of suggesting you might be dating yourself, I think this is an outdated model. It's simply no longer realistic. I personally believe that having personal expectations of what my adversaries or those outside of my control "should" do will inevitably result in sadness on my part.
Corporations will aim to do what they must to increase profits (given, by definition). Any additional assumptions from that are liable to be faulty. Perhaps you are used to the times when they needed to train staff but that's simply a symptom of the circumstances as opposed to a duty.
Re: The rise of never-ending job interviews
#423Earlier quoted context omitted.
> 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…
Because selecting candidates based on tech stack is almost universally the sign of incompetent tech management. Anybody who understands software, knows that intelligence and master of fundamentals trumps tech stack experience without exception. Linus Torvalds would unquestionably become a better Ruby on Rails developer within four weeks than 90% of people with 10 YoE in it. Good organizations hire talented and bright…
Re: The rise of never-ending job interviews
#424My 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…
To this day I have NO idea what happened. I never heard back from them and the recruiter wasn't able to provide me with any further feedback when I asked.
I thought maybe they saw me on camera taking a photo of the Goldman-branded water bottle on the table while I was bored waiting... Or someone was digging and saw an anti-Trump tweet of mine. Or whatever.
Would have been more fun for me to turn them down after this whole madness (which I fully intended), but I didn't get that pleasure :)
Re: The rise of never-ending job interviews
#425Re: The rise of never-ending job interviews
#426Earlier quoted context omitted.
That confirms that we shouldn't bother if we value our time and energy.
Many people apply to all the FANGS, since the interviewing skillset needed is similar. Moreover, you can reapply every six months. In result, this gives you perhaps 5-10 lottery tickets every year, which means it's very feasible to get in within a year or two (or three).
Re: The rise of never-ending job interviews
#427Earlier quoted context omitted.
I find it… troubling? That a technical interviewer can’t tell for herself whether your code will work. Wouldn’t you ideally want people who actually understand code to be giving the coding questions?
Are you saying that because this interviewer needs to run code to find logic errors, she's somehow not a competent engineer? Because I usually need to run code to find logic errors. Sometimes I use formal verification instead but that's pretty rare. Am I also not a competent engineer?
And if you fail to communicate the requirement for one or the other then you're certainly not a competent interviewer.
You also have to ask what exactly is being tested here? Is it the ability to remember syntax? To remember an algorithm? To improvise an algorithm? To recognise which algorithm is needed?
What, exactly?
Re: The rise of never-ending job interviews
#428I lost so many hours on this interview process that I would like to send them an invoice :)
Re: The rise of never-ending job interviews
#429Re: The rise of never-ending job interviews
#430My 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…
My feedback was that, if the CV is so impressive, according to them, why do I have to endure such interview processes?
Anyway I never bought into the whole do no evil marketing, nor bothered to apply, if it wasn't for their HR reaching out to me in first place.