Live data from Hacker News

The rise of never-ending job interviews

bbc.com

881–890 of 1001 posts

Re: The rise of never-ending job interviews

#881
post #641

Earlier quoted context omitted.

It may be a random walk but I think the goal is to convince whoever gets hired that they’re special and talented and elite members of their discipline.

You think they're doing this to make you feel... good?

Harsh hazing and initiation rituals are a pretty effective way to build team "spirit" and make people believe the group they've joined is special, and being a part of it makes them special or better than non-members. It may or may not be part of why FAANG interviews the way they do, but it is likely part of the outcome.

Re: The rise of never-ending job interviews

#882
The last two jobs I applied for were like this. The first one had 8 interview rounds on 8 separate days. It was a remote company, and I was working in an office at the time, so I had to figure out 8 separate excuses for sneaking away from work for an hour to take video calls. It was ridiculous.

Re: The rise of never-ending job interviews

#883
post #434

Earlier quoted context omitted.

What alternative would be more efficient and acceptable? A typical team of 6-8 replaces two persons per year. The number of resumes per opening is measured in thousands.

> A typical team of 6-8 replaces two persons per year. How is this fact not seen as a complete failure of hiring practices or company/team leadership?

In an industry where the median tenure for a SWE is ~2.5 years, that's "doing no worse than the industry average".

Turns out upper management rates predictability quite high.

Re: The rise of never-ending job interviews

#884

Earlier quoted context omitted.

In terms of topical content it's a good question. The idea that the name is a link stored in a directory entry is a key part of filesystem architecture and anyone familiar with unix filesystems should be able to immediately talk about why. The problem here is that what could be an invitation to showcase knowledge is reduced to a vague, one-dimensional and non-obvious trivia question. There are a ton of valid answers…

> * The file data Except on some filesystems really small files can actually be stored directly within the inode, so even that's not always true.

Yes and that's true of ACLs as well which I think underscores my point: Questions should be an opener to dialogue. A topic, not a conclusion.

Discussion of these whys and hows and whens is the most valuable part of an interview and will more accurately illustrate depth and breadth than any number of fixed questions.

Re: The rise of never-ending job interviews

#885
I don't recognize this at all in my country (Netherlands). I have 2 interviews max. My current employer I actually had one interview with the boss in a restaurant. We had a nice chat and he offered a job on the spot. I signed and never left. As I am a consultant I ofter do interviews and I always stear the conversation to the most important part of IT: communications.

Re: The rise of never-ending job interviews

#886
post #327

Earlier quoted context omitted.

Actually this one might make sense, depending on the code and the position you applied for.

Your IDE can check your syntax. For people who have to switch between languages regularly, precise syntax memorization is difficult and a waste of time.

I'd struggle to code a five-line program that'd compile in languages I've written tens of thousands of lines of code in, in Notepad, that'd actually compile & run on the first try. I might fail that in a language I was writing last week. I mean, I might manage it, but it'd be sheer luck. Decent chance I forget, in the moment and under pressure and without examples to crib off of, IDE support, or the ability to check the manual, the correct way to do comparisons for all types, even, or basic stuff like how to print to the console or what this language's sugar for a "for-each" is, or whether it has such sugar. Reading input? The right calls for file IO? Anything more complicated than that? Oh god, there's no way.

Luckily I never fucking ever have to do that in my actual job. If I did, I might well get good at it. Since I don't, I... don't. I also haven't gotten much better at driving semi trucks or framing a wall, in my over-a-decade career writing software. Go figure.

Re: The rise of never-ending job interviews

#887
post #311

Earlier quoted context omitted.

In terms of topical content it's a good question. The idea that the name is a link stored in a directory entry is a key part of filesystem architecture and anyone familiar with unix filesystems should be able to immediately talk about why. The problem here is that what could be an invitation to showcase knowledge is reduced to a vague, one-dimensional and non-obvious trivia question. There are a ton of valid answers…

If your question has that "gotcha there is just one right answer"-feel to it, you are doing it wrong. I had a teacher once who constantly asked questions like these in such an imprecise fashion there was no way anybody could have guessed how the question was even meant to be answered. I still cringe when I think about it, because the only purpose of these questions was to show us that he is really clever and we don't…

Yes, absolutely.

Personally, I have always approached interviews as an opportunity to either teach or learn. I pick a subject and drill down until either the interviewee reaches their limit of knowledge, or I do. Why is it like that? How does that work?

Then, we have a discussion. One (or both) of us is learning and we work out the whys and hows together. If I'm the one learning, and I hope that I am, I fact check the discussion after the interview. If not, I get a strong indicator not just for the technical level of the candidate but also how they operate at the edge of their comfort zone. I've found this can be a strong predictor of future growth.

Re: The rise of never-ending job interviews

#888
post #593

Ah Amazon... 14 interviews, an additional 5 hour technical test, spanning a total of 3+ months. Only to be informed at the end that I was too technical for the role they had in mind but they were offering me a Senior Principal SDE role instead. By the time we got to the end of the process I'd already concluded that the hiring process was a reflection of their internal decision making and that this was not a company (…

I honestly think this is a product of large corporations being essentially incapable of firing bad resources. Companies are terrified of litigation and bad PR so the only control mechanism is the interview process.

This is not the case at Amazon. They are known for PIPing engineers. They’re not shy about it.

Also all of these big tech companies can just not refresh your stock if they don’t want to bother with firing you, which effectively halves your compensation.

Re: The rise of never-ending job interviews

#889
I know BBC is writing this from the perspective of a new interviewer. However anybody who is preparing for FAANG or even hangs out on Blind knows that getting into any of these big companies, now includes multiple leetcode style programming tests and system design interviews . Just as a point of reference, CTCI is now on its 6th edition and it is still playing catch up to the ever changing interview processes at these companies.

In fact if you spend time on leetcode , you would get a fair idea of what companies ask LC medium/hard, which ones ask Dynamic Programming and which one will specifically ask questions that are not on LC

Re: The rise of never-ending job interviews

#890

Earlier 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…

> Why is this objectionable? [to reduce an employee to "utility as a walking set of tech keywords"] > Why is it important to you that your employer view you as a person?

If what you mean is that it can be rewarding (intrinsically and extrinsically) to think about skill, craftsmanship, and other ways to make your labor a great value add, sure. Most of us benefit by thinking about that.

If you're really asking about why keywordification is a problem, well... keywordification of job roles indicates a way in which companies are quite possibly struggling to actually model the roles they're hiring for and identify what makes make an individual productive within them.

This happens on at least two levels:

1) Technological. Engineering decisions are sometimes "we have a specific problem, specific tech is the solution to our problem, therefore we need expertise in specific tech." In that case, the keywords regarding that tech are meaningful. But for non-trivial use cases, engineering problems are very, very rarely just that, they're commonly the aggregation of off-the-shelf + consideration of how to mix them with what tradeoffs + in-house custom solutions embedded in an organization attempting to understand and model its domain problems and fit/reshape all those solutions to those models. This is not exactly a keyword-driven process. Keywords represent the shallow end of the pool.

2) Human. While labor clearly is something bought and sold on the market, even from a point of view of a value system which is OK thinking of humans primarily as industrial inputs, it turns out that's a significantly leaky abstraction and most of us have all kinds of "compiler flags" or other inputs of our own that make us more or less productive. Some might consider this to be too warm and fuzzy; they might find it comforting that it can be approached from as a-humane and manipulative point of view as one might approach tweaking a database to get it to perform better: https://www.youtube.com/watch?v=HkFztAgK-8U

As for whether it's OK to think of humans primarily as inputs to any process on a moral level... like Terry Pratchett's character Granny Weatherwax said “Sin, young man, is when you treat people like things. Including yourself. That’s what sin is.” What are the consequences when social institutions consideration human beings primarily as inputs to institutional purposes? Generally, individual life, liberty, and pursuit of happiness become valued less, and individual suffering is more freely disregarded. Not super desirable under my value system. YMMV.

Post reply on HN