Programming

17340 readers

314 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Coding interviews are effective (pcloadletter.dev)

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

21 comments fedilink hide all child comments

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

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

But how do you handle candidates who say something like "look, there's heaps of code that I'm proud of and would love to walk you through, but it's all work I've done for past companies and don't have access (or the legal right) to show you?"

It never once happened. They always knew in advance, so they could code something up if they felt like it.

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

Interesting, thanks. Do you give them any ideas or guidance as to what they should whip up? Or just leave it totally open-ended for them to figure out?

[–] [email protected] 2 points 7 months ago

I always left it open-ended and that seemed to work. Part of the interview was seeing what they'd come up with. I'm pretty sure people always brought things they'd already written.