Technology

59374 readers

3794 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 1 year ago

MODERATORS

[email protected]

244

Tech Job Interviews Are Out of Control (www.wired.com)

submitted 8 months ago by [email protected] to c/[email protected]

37 comments fedilink hide all child comments

Tech Job Interviews Are Out of Control::Tech companies are famous for coddling their workers but after mass layoffs the industry's culture has shifted. Engineers say that getting hired can require days of work on unpaid assignments.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 37 points 8 months ago (4 children)

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.

[–] [email protected] 10 points 8 months ago (2 children)

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.

[–] [email protected] 6 points 8 months ago (1 children)

I don't want them to see my hobby code, it's far worse than my professional code.

[–] [email protected] 1 points 8 months ago

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).

load more comments (1 replies)