this post was submitted on 28 Sep 2024
991 points (98.5% liked)

Science Memes

11047 readers
3416 users here now

Welcome to c/science_memes @ Mander.xyz!

A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.

Rules

  1. Don't throw mud. Behave like an intellectual and remember the human.
  2. Keep it rooted (on topic).
  3. No spam.
  4. Infographics welcome, get schooled.

This is a science community. We use the Dawkins definition of meme.

Research Committee

Other Mander Communities

Science and Research

Biology and Life Sciences

Physical Sciences

Humanities and Social Sciences

Practical and Applied Sciences

Memes

Miscellaneous

founded 2 years ago
MODERATORS
[email protected]
[email protected]
[email protected]
991
👣👣👣 (mander.xyz)
submitted 1 month ago by [email protected] to c/[email protected]
41 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 month ago (1 children)

Never do more than 3 interviews. And that's assuming they're relatively short, maybe 1 hour apiece. Any more than that, and they don't want you bad enough.

[–] model_tar_gz 0 points 1 month ago (1 children)

I don’t know if I agree with that. Having been on the hiring side of the table more than a few times.

Hiring a new employee is a risk; especially when you’re hiring at a senior enough level where the wrong decisions are amplified as the complexity of the software grows—and it becomes far more expensive to un/redo bad architectural decisions.

And the amount of time it takes for even an experienced engineer to learn their way around your existing stack, understand the reasons for certain design decisions, and contribute in a way that’s not disruptive—that’s like 6 months minimum for some code bases. More if there’s crazy data flows and weird ML stuff. And if they’re “full stack (backend and frontend) then it’s gonna be even longer before you see how good of a hiring decision you really made. For a $160k+/yr senior dev role, that’s $80k (before benefits and other onboarding costs) before you really expect to see anything really significant.

So you schedule as many interviews as you need to get a feel for what they can do, because false negatives are way less expensive than false positives.

Sometimes people can be cunning: charm, wow annd woo their way past even the savviest of recruiters with the right combinations of jargon patterns.

Sometimes they can even fool a technical round interviewer.

4-5 interviews (esp. if the last is an onsite in which you’ll meet many) seems to be about the norm in my field. Even if it kinda sucks for the person looking for the job.

[–] [email protected] 0 points 1 month ago* (last edited 1 month ago) (1 children)

Yeah, it saves you money...by costing the prospective employee. There's only so much we as employees can or should be willing to give up for free, and it's 3 interviews.

I also question if more than that is really improving the quality of your hires. Far more often (100% of the time, in my experience), multiple interviews are more a symptom of bureaucracy; multiple managers insisting that they get to stick their fingers in the pie, rather than actually learning anything more meaningful about the candidate.

[–] model_tar_gz 2 points 1 month ago (1 children)

I’ve rejected someone on their 4th round before—1st round with me. That candidate had managed to convince the recruiter that they had the chops for a staff engineer (>$200k/yr!) and passed two coding rounds before mine, testing knowledge of relevant techs on our stack—at this level of role, you have to know this coming in; table stakes.

I was giving the systems design round. Asked them to design something that was on their resume—they couldn’t. They’d grossly misrepresented their role/involvement in that project and since they were interviewing for a staff level role, high-level design is going to be a big part of it and will impact the product and development team in significant ways. No doubt they’d been involved in implementing, and can code—but it was very clear that they didn’t understand the design decisions that were made and I had no confidence that they would contribute positively in our team.

Sucks for them to be rejected, but one criteria we look for is someone who will be honest when they don’t know—and we do push to find the frontiers of their knowledge. We even instruct them to just say it when they don’t know and we can problem-solve together. But a lot of people have too much ego to accept that, but we don’t have time for people like that on the team either.

Look, I get what you’re saying and clearly I’ve been on the wrong end of it too, but if we make a bad hiring decision, it costs not just the candidate their job but also the team and company they work on can get into a bad place too. What would you do in that situation? Just hire them anyway and risk the livelihood of everyone else on the team? That’s a non-starter; try to see a bigger picture.

[–] [email protected] 1 points 1 month ago (1 children)

The question that raises from a process improvement perspective then is "were the first 3 rounds really effective tests?" Perhaps a better solution is not more interviews, but more focused interviews conducted by the people that actually have the knowledge and power to make the decision. (And if the knowledge and the power are divided among multiple people, another great improvement would be empowering the people with the knowledge.)

[–] model_tar_gz 1 points 1 month ago (1 children)

Google has done way more research on this topic than both you and I collectively and they settled in on 4 interviews being the sweet spot to get enough signal to be 86% confident, while not wasting any more of anyone’s time than needed chasing after single-point confidence improvements. In my experience, I agree with this. I’ve been through 6-round and 3-round (both to offer). Even as a candidate I guess I feel like i wanted that fourth round. Kinda hard to tell what a company culture is from just three meets. And after six rounds I was just freaking exhausted and didn’t really have a high opinion of that company-they couldn’t seem to figure out a clear mission/vision for their product and I thought their overly complicated and drawn-out interview process was a reflection of that.

Google goes into more depth as to why the three-tech + 1 behavioral/cultural model works for them. They call it a work-sample test.

The best predictor of how someone will perform in a job is a work sample test (29 percent). This entails giving candidates a sample piece of work, similar to that which they would do in the job, and assessing their performance at it.

Both articles linked are well worth the time to read. Hiring is a messy and inconvenient process for both companies and employees.

[–] [email protected] 2 points 1 month ago (1 children)

That strikes me as highly reflective of google's position of power; from the employer's perspective, the point where the diminishing returns are no longer worth it is related to the point where they're losing too many applicants from interview exhaustion. If you're not google, not offering the kind of pay and such that google does, your break-even point is likely much sooner.

Additionally, from the worker's perspective, the only-3-interviews rule is an assertion of our power. And, as an added plus, if enough people adhere to it, it will shift that break-even point even for places like Google, and resist the shifting of that burden onto unpaid workers.

[–] model_tar_gz 1 points 1 month ago

The article I posted pointed out that they’re trying to not waste the candidate’s time, as well. They used to do 12 fucking rounds of interviews—and because it’s Google, people tolerated that crap. One of my best friends is an old-school Googler that got in through that gauntlet.

Keep that in mind when you claim it’s an employer’s power play—in this case, it’s really not. More than four interviews, twelve, sure I can believe that. You should read about what some of the elite tier government special ops groups go through.

At this point we’re quibbling over a delta of one interview—I think we’re probably pretty close, or close enough to say “agree to disagree on the rest.”

Cheers.