Refactoring Back End Engineering Hiring at Slack

Re:Refactoring Back End Engineering Hiring at Slack by malvosenior on Thursday April 04, 2019 @02:41PM (#19575708)

When you start working with someone day to day you can very quickly find out if they are good or not. You don't have to fully get them up to speed and have them learn all of the domain knowledge of your company. Start small and evaluate quickly. Certainly you can learn more when they start working than you can in the interview process.

> when you expect your teams to satisfy multiple stakeholders or to grow beyond initial job requirements

This honestly sounds like bad management.

[ Parent | on HN ]

Re:Refactoring Back End Engineering Hiring at Slack by evrydayhustling on Thursday April 04, 2019 @04:24PM (#19576721)

Wat? Bad management to consider how your devs will interact with other roles (PMs, customer support, other dev teams)?

I can't figure out if your devs just don't do that, or if you think you can speak for everyone's standards after one conversation with a candidate.

[ Parent | on HN ]

Re:Refactoring Back End Engineering Hiring at Slack by malvosenior on Thursday April 04, 2019 @04:51PM (#19576971)

Those people should of course be part of the interview process if the developer will be interacting with them. I don't see how that makes a bad hire any more expensive though. Maybe I'm misunderstanding what you're trying to say.

[ Parent | on HN ]

Re:Refactoring Back End Engineering Hiring at Slack by evrydayhustling on Thursday April 04, 2019 @05:00PM (#19577064)

Nah, looks like I misunderstood your "hire based on conversation alone". I thought you meant conversation with just you. My bad.

[ Parent | on HN ]