I was expecting different dungeon master: https://thefinalrumble.miraheze.org/wiki/Van_Darkholme
Becoming a dungeon master for an interview
21–30 of 181 posts
Re: Becoming a dungeon master for an interview
#22Here's how to recruit software developers. 1: define the requirements for the job 2: devise questions that attempt to give insight into how well the candidate might meet that requirement 3: note down the candidates suitability out of ten for each question 4: TALK to the candidate in a free flowing and open discussion about their work, what they have done, how they built it, why they built it that way, their role in t…
[deleted]
Re: Becoming a dungeon master for an interview
#23Earlier quoted context omitted.
I feel like leetcode is a Goodhart's Law thing. When nobody was cramming for it, then at some places it was a good measure. Coding is more like weight lifting sometimes then running. There are some weights that some people just can't pick up. And so if the job involves lifting things that are usually light but occasionally heavy, then a squat becomes a good measure for candidate. But once everyone knows a big squat i…
> Goodheart's law breaks things, because now you have a bunch of people optimized for a task that isn't exactly the job. Companies lose another way too. Folks who might be darn good at picking things up decide it isn't worth the focused training to get into companies that only seem to care about squatting, so they don't apply.
Yeah, I feel like any measure like this starts as a way to measure a proxy for IQ. But as it becomes a known thing, people train for it and it becomes a measure of conscientiousness (In the big five sense, aka diligent trainers rise to the top).
Re: Becoming a dungeon master for an interview
#24Earlier quoted context omitted.
> was willing to submit to it for the approval of this company I abstain, myself. I have too much real work that I'd like to push forward to be able justify spending weeks of free time on fake work.
Great! Isn’t that the point? That some people who really don’t want the job won’t invest a bit of their time and people who do really want the job will?
That selects for people who aren’t holding productive jobs currently.
It’s a reasonable filter for junior positions, but seems counterproductive if you’re looking to fill a position where experience would be valuable.
Re: Becoming a dungeon master for an interview
#25Earlier quoted context omitted.
> was willing to submit to it for the approval of this company I abstain, myself. I have too much real work that I'd like to push forward to be able justify spending weeks of free time on fake work.
Great! Isn’t that the point? That some people who really don’t want the job won’t invest a bit of their time and people who do really want the job will?
I doubt it?
My willingness to practice leetcode isn't correlated with my interest in new work or the work any given job post describes. It's also not correlated with my willingness to invest time in exploring the position.
6 hours of leetcode practice teach me nothing about a position, the work it entails, the problems the company is grappling with, and the people I'd be in the trenches with. 6 hours in conversation or working close to real problems are higher leverage.
I have meaningful open source work with real users in the queue, and blog posts that won't write themselves. I feel like it's pretty reasonable to sort positions that don't compel low-leverage busywork that doesn't help me assess the position above those that do.
Sure, they might mean to exclude me, but I'm skeptical.
Re: Becoming a dungeon master for an interview
#26In interviewing I try to avoid approaches that in any form or shape resemble riddles, so ostensibly open problems but with predetermined acceptable answers.
I've found that it's both frustrating for the candidate and doesn't give me much insight.
Such a back and forth to me is too close for comfort, even though I used to be into role-playing games back in the day.
Currently I try to use the little time I have to determine whether the person in front of me is a charlatan, so only questions that are easy to answer for someone actually having the skills advertised in their CV.
Re: Becoming a dungeon master for an interview
#27Earlier quoted context omitted.
> was willing to submit to it for the approval of this company I abstain, myself. I have too much real work that I'd like to push forward to be able justify spending weeks of free time on fake work.
Great! Isn’t that the point? That some people who really don’t want the job won’t invest a bit of their time and people who do really want the job will?
[flagged]
Re: Becoming a dungeon master for an interview
#28I was expecting different dungeon master: https://thefinalrumble.miraheze.org/wiki/Van_Darkholme
Took me a moment or two to realize this is about DnD.
After all, interviews tend to be a stressful and intense process...
Re: Becoming a dungeon master for an interview
#29> Interviews should be as close as possible to the work that the candidate would do if they join. Interviews should give information to both parties about what it would be like if the person joined. Simulating a typical work task, as this article describes, might give you some of that. Though important to remember that's far from all that's relevant to either party. A recently fashionable Leetcode hazing, on the othe…
making a react component in a 45 minute interview (something I recently did) is better than leetcode, but still a poor signal. on the job I'll never do a time trial where I'm being watched and gaslit about "just wanting to see how I think" as opposed to "do it perfectly from memory in this collaborative coding session faster than this guy escaping a dystopia in Asia, and trying not to be deported back"
find a way to simulate that I will do it some time over the next two weeks because the product manager reduced everyone's story points in half for this sprint in the grooming session, and the fact that I even did that gets me praised because nobody else on the team finished their tasks
Re: Becoming a dungeon master for an interview
#30> Interviews should be as close as possible to the work that the candidate would do if they join. Interviews should give information to both parties about what it would be like if the person joined. Simulating a typical work task, as this article describes, might give you some of that. Though important to remember that's far from all that's relevant to either party. A recently fashionable Leetcode hazing, on the othe…
[deleted]