I like to ask folks what they do for fun, gives me a better general idea of who they are
Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
6) No US Politics.
Please don't post about current US Politics. If you need to do this, try [email protected] or [email protected]
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
Other pros:
- You might filter out people who want to Create The Nexus of Torment from Hit Sci-Fi Novel Don't Create The Nexus of Torment
Cons
- they'll get hired by Microsoft instead
Other Cons:
- Keep in mind a lot of people don't read much, if at all which is sad. Meanwhile, you still need to hire people.
- We're all motivated by money. Like you said you don't work for free. Neither would I. A job is a job and for most people it means sacrificing very precious hours of their time (time they will never get back, no matter how well they get paid) in exchange for that money. It's nothing but a contract which can be summarized as this: you give me money, I give you my expertise/willingness to sweat on my part of that contract. End of the contract. We're not family, we're not (yet) friends (and we never be), as an employer you have no say in what I do outside of work (no matter how it's becoming the norm to think the opposite), and what I like to read is none your business as my employer. Obviously, we may both be willing to talk about it but that's a personal choice. I just re-read P.K. Dick's Ubik, have you read it?
I mostly read manga. But for sci-fi books the freshest one in my memory is Dune.
Would you hold that against me?
No
I interviewed someone today whose hobby was poetry of the African diasporia, for a position relative to logistics.
While I know very little about that specific poetic oeuvre, hearing them talk about their passion gave me an insight into their personality.
Perhaps ask questions about what they're into rather than if they're into thing.
Perhaps ask questions about what they're into rather than if they're into thing.
This is great advice! Asking about something specific is off-putting and could lose a great candidate.
Asking an open ended question about their hobbies can get the same positive result, and will catch candidates who wouldn't have anything to say about science fiction.
I grew up coding but don’t read sci-fi. You need to expand your idea on what a good motived coder looks like. It sounds like you’re in a bubble.
You're right, it's exclusive when it shouldn't be.
I would expand the question. "Sci-fi had always inspired me, what clicks for you and why?"
I like this question. I think this works great. I'm too low on the pyramid to interview much anymore, but might ask this in my next interview!
When dating people, I often ask "name a book that's not Harry Potter". Doesn't even have to be one you've read. Pick any book at all (other than Harry Potter) and tell me why you thought of it.
I'm not gatekeeping people who do or don't read books, and i don't care if it's sci fi, fantasy, fanfic, nonfic, whatever. what i do care about is that you are aware of at least one book and care enough to remember what it's about. That's a low bar, but not as low as you might think.
The "no Harry Potter" clause isn't specifically due to jkr being a terf (although that too), but because it's such an overused answer. Yeah, I do remember the books that were so popular that they had their own brand of jelly beans. I have run out of things to say about them. Pick literally anything else.
I imagine being in a date and my mind panicking and coming up with the Kamasutra first.
This doesn't correlate with good developers at all in my experience. If I was to ask one question it would be "tell me about your passion project" or "What's the last thing you nerded out on?"
No. What? No.
Unless you publish sci-fi novels as a business, I suppose. Then maybe. But no.
I don't have anything against "culture fit", but that means that if you think someone will make your life miserable by sharing a space for eight hours it's okay to go with someone else. It's not a blank check to audit people's Spotify histories. Job interviews aren't dates.
The fact that you even weighed the pros and cons of your proposal puts you light years ahead of most hiring managers.
Haha I'm afraid every time I interview someone. I know that I personally hate being asked whiteboard algorithm questions, and I don't think they're very useful either. When I interview people I ask them two main questions:
- What is your hottest take on coding? It can be controversial or not, it just has to be a strongly held opinion. For example, if you despise Windows, tell me why. If you are a zealot for Vim/Emacs, rant at me. If you think that dynamically typed languages are the worst thing ever, prove it.
I don't actually care about what their opinion is (though I think it's good to hire people with a lot of intellectual diversity), I just want to see if they can extemporaneously rant about coding for 10-15mins
- What is a technology (an API, a cloud service, a programming language, a new kind of algorithm, etc.) that you are excited about and that you want to be able to use at work some day
Again, the actual tech doesn't matter too much to me, but this indicates that they read up on the latest goings-ons of the industry they're in. I also think that it's a good character trait to be someone who desperately searches for problems to apply a novel solution to. I don't think it's always a good idea to ACTUALLY create a solution looking for a problem, but I think it's a good intellectual trait to have
Those are both great questions.
Agreed. Hiring manager green flags for sure.
Interesting, I posted a top level comment to you but you're already doing some similar things to what I posted.
This seems terrible.
- Weeds out a lot of people since half of Americans don’t read books at all.
Is that always a good thing? What about people who don't read much but listen to audiobooks and go to the theatre a lot?
- Theoretically filters out people who love this kind of tech subculture from people who are just in it for the money
One of the best programmers I ever worked with was 'in it for the money'. He was what Goldman Sachs used to call 'long term greedy' though which meant he had an eye on the success of the project above and beyond his own responsibilities and his own code. That's why he was one of the best programmers.
listen to audiobooks
Listening to an audiobook is reading unless you're really fucking pedantic. (and in that case, you shouldn't be taken seriously)
The content of an audiobook of, idk, name a story you enjoy, is exactly the same as the content of the paperback or ebook.
Maybe just ask them if they have read anything interesting lately ?
I would try to leave it more open-ended when asking what their hobbies are outside of work, and then ask whatever follow-up questions you can think of that would let them express what they're passionate about.
As a tension softener, I tend to open interviews with: What's the best movie ever and why should I love it too?
It helps me tell how good they are convincing someone else of something while also it helps them relax a bit, as a softball before we start pitching curved ones.
I prefer doing this rather than asking for hobbies as the interviewees tend to gave prepared corporate-grade answers.
I tend to finish asking to give us a song recommendation, which sets a better mood (hopefully) to end it.
I just hope there's nobody out there still trying to figure out if they gave us the wrong recommendations.
Oh that's so stressful. I actually hate sharing my song and movie recommendations because I usually like weird indie shit that nobody else enjoys (as pretentious as that makes me sound). I get extremely self conscious about my taste in stuff and would 100% worry that I gave the wrong recommendation.
Oh god just thinking about this is giving me anxiety.
I want someone that's pleasant to work with and can pull their weight, but that's just my preference.
Echoing this. Even as someone who does read sci-fi, I think leaving it open ended is better. Hobbies is a good angle; it could also be "What show, book, or film did you enjoy recently?" then follow it up with "Why?" and work from there.
What this shows:
- They live a balanced-enough life that they have time to do relaxing stuff, aren't money-focused tryhards like OP is trying to weed out.
- Allows them to demonstrate explaining a topic unfamiliar to the interviewer.
- Shows how they respond to unexpected questions outside the normal, practiced interview set.
- Follow up questions can still weed out people who are viewing it "just because", they heard it was popular, or whatever.
I never got super into sci-fi; it just wasn't my cuppa. I was always on the fantasy side of things with regard to fiction, being heavily into D&D and many of the novels around the various settings and characters. Edit: I've been a developer since the mid aughts and alternately worked in tech and other jobs before that. I wrote my first programs in basic around 9 or 10 when dad gave me something to do to keep out of his hair.
"Any sufficiently advanced technology is indistinguishable from magic" -Arthur C. Clarke
Always loved this one as a sci-fi and fantasy kid. When you love dragons and teleportation and talking animals, it kinda doesn't matter how they are delivered to your brain.
I like to say that Star Wars is to fantasy what Discworld is to sci-fi. Star wars is swords and sorcery in space, and Discworld is ethics and robotics in middle earth.
Discworld is ethics and robotics in middle earth.
You just blew my mind, a little. Dang. That's Apt.
clacks header
GNU Terry Pratchett.
A buddy of mine was interviewing for a job and got it in part because he was a player in one of my games. They knew they could get along with him.
My dad designed jet engines and nobody made him design a jet engine on the whiteboard. So you are starting from the right place.
We are here where we are today because we spent too much time thinking that acting like the right kind of nerd meant you were a good programmer. There's nothing wrong with going to a job, working hard, and then doing something else. I know very productive engineers who don't have a favorite science fiction book who were great to work with.
Given things lately, I think it's healthy that a lot of people have had to take a step back and realize that their employer would totally harvest their organs for profit if they could get away with it. Providing people the right "tech subculture" cues has resulted in a lot of people working themselves to death and never seeing any income windfalls.
I actively hate a bunch of my old science fiction books from when I was a kid because they were written with what is, to my adult mind, a not-very-subtle fascist bent. There's, obviously, some great novels out there that expand your mind ... but at the same time, there's a lot of the science fiction canon where I'd probably hate working with people who took those books seriously.
And, likewise, there's a lot of people who simply don't have time because they are smart people actually trying to get into the lucrative field of computer science and a good scifi novel reading session is a luxury they just don't have.
"Tell me about your favorite science fiction book" is pretty much a textbook case for how to have good intentions but conduct an interview that's, when you step back and think about it some more, biased. It's checking for subculture-fit in ways that have nothing to do with how they are at work.
On the other hand, whiteboard tests are also useless.
If you want to make a better interview, I'd suggest you have an interview guide. Not a manager? Just write your own for your interviews and keep to it. This protects you from unconsciously giving the person who looks the part easy questions.
If you want to check for culture fit, talk about things at work that matter. Are you worried someone is going to talk down to a junior engineer? Make them talk about a time they had to mentor a junior engineer. Did they succeed? What did they do? Ask them about the best project manager or doc writer they worked with. Are you worried that they aren't serious enough about getting shit done at work? Talk about the worst incident they ever were part of, but not the technical parts, just how they made sure it got fixed. Are you worried that they aren't a good team player? Ask about their best collaborations. Or how they organized work on a large project. Or the time that they took one for the team. If you think through how the last crop of yuppies pissed you off for a while and break it down into questions that they'd not have a good answer to, you should be able to make a nice set of behavioral screening questions and a set of attributes that you want the person to display in their answers.
I speak casually but my aim is just to find out if they have the technical skills necessary for the role. I find little social things come up by happenstance.
I see what you're getting at, but maybe broaden it to just their favorite book. I also certainly wouldn't disqualify based on not having read books (sci-fi or otherwise), because maybe they read short stories online, or maybe comics or something similar.
If you have the authority to try to make a good company culture; hell yes you should. Even if they don't often read novels, or they read something other than sci-fi, it'll help you understand their personality and weed out people who suck. If someone says they prefer reading sci-fi manga or playing fantasy ttrpgs or any other possible nerdy thing they are probably leagues better than a ladder climbing type.There are plenty of places for a soulless corpo to go work for, if you can keep them away from you and yours you'll have a much better and healthier company and (more importantly) life in the long run.
@[email protected] looks like you want to promote a mono culture? a lot of brilliant people I work with don't read scifi, or anything like that. It is still a pleasure to work with them.
Also, working for money is exactly what we all do, it is great to do what you want but some people just care abour their paycheck and that is fine.
Finally, IANAL, but I suspect it could be a discriminatory practice to select people who like things that you like.
I think you could get the same info from opinions on movies.
Interest in coding doesn't necessarily imply an interest in science fiction either.
The ladder climbing type are easy to route out, just ask them if/how they engage in synergy outside of work.
I interviewed for a gig that explicitly stated "Must have a strong preference for Marvel over D.C." Got the job, been on it going on 14 years now.
Do you have a strong preference for Marvel over D.C. or did you you lie lol
I dodged. "All I'm going to say on that is I met Stan Lee at San Diego Comic Con in 1995 and got his autograph."
When I've interviewed candidates for software engineering positions, I have never asked any questions about them outside of work. I don't personally feel that it has a lot of impact on how they perform at work.