Hacker News new | ask | show | jobs
by bjornedstrom 2108 days ago
Just to offer a different perspective: An employer having too clear of an idea of a role can also be a red flag.

The past 10 years I've often been the first employee - or one of the first - joining or building up the company's security organization. The combination of (1) having a specialist skill and (2) being around very few other people with the same skill, naturally leads to a situation where too much clarity can be a bad thing. If a non-specialist define a security role, they will probably screw it up. And that's okay.

If you've worked in startups long enough you eventually get a lot of experience in how to hire people whose expertise you do not understand. As an employer and employee I enjoy the collaborative process of defining the role around the candidates strengths and weaknesses.

1 comments

This is a huge factor in early hiring success: can you effectively hire people whose roles you don't fully understand? Can you develop trust with the person you've hired and delegate effectively?