this post was submitted on 23 Feb 2024
244 points (98.0% liked)
Technology
60058 readers
3901 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Paywall.
Archive link
Six hour-long segments is pretty far from abnormal.
Homework - especially anything before the rest of the process - is absolute bullshit. If you're not also investing any time in the interview, you can compensate me. My time is not less valuable than yours.
I did once spend an hour or two putting together a presentation for one prospective employer - it was attended by several engineers and managers over the course of a half hour, so there was still reciprocation - but I declined to perform the at-home coding exercise at the end of the process.
They still extended an offer.
Presentations and homework for interviews, wtf? I've been at my job for about 7 years now, and I don't remember any prospective employers asking for this type of shit. Is this really becoming common? If so, I've been thinking about how vocational jobs don't seem so bad these days in terms of pay...
Multiple hour-long interviews I'm actually fine with. It's not ideal, but in that case at least the company is also spending resources on the process.
Homework / pre-interview projects that take more than a hour is unreasonable, to me. I have public repositories / commits I can share with you if you want to see how I write code.
I don't want them to see my hobby code, it's far worse than my professional code.
I recommend having a public portfolio. You needn't have all your hobby code be public, but I think having source you've written available is an advantage.
When I was doing interviews, I definitely looked at GitHub (etc.) profiles of they were listed on the resume. I even found at least one indirectly -- either from their email or LinkedIn.
I like to point people at my accepted patched to open source software (Git and a Haskell library).
Reader mode on firefox shows the whole thing
Paywall.
Paywall.
Nope.
Seems like you failed to notice that my comment prompted someone to post a non-paywalled link, helping everyone.