4 ms·
> but in my opinion, every new developer should find some way to stand out. This doesn't really accomplish anything worthwhile. Now you're hiring and you recei
by thaumasiotes 5y ago
> but in my opinion, every new developer should find some way to stand out.
This doesn't really accomplish anything worthwhile. Now you're hiring and you receive 50 applications each with their own unique way of standing out, so you're supposedly considering which of 50 points in a 50-dimensional space you like the best.
Obviously the only thing you can do is map each point onto a one-dimensional space and choose the highest value. To do this you need to know exactly how much you care about any given resume item.
It's more effective for you, and easier for everyone involved, if you just decide what you want and do an assessment based on that.
- mooreds 5y ago> > but in my opinion, every new developer should find some way to stand out. > Now you're hiring and you receive 50 applications each with their own unique way of standing out, so you're supposedly considering which of 50 points in a 50-dimensional space you like the best. Just because people should do something doesn't mean they will. > It's more effective for you, and easier for everyone involved, if you just decide what you want and do an assessment based on that. This is a great approach and can pair nicely with the effort based filter I outline. I don't know about you, but when I hired a new developer a few years ago for a remote position, no experience required, for a company that isn't nationally known, I got ~100 resumes in not very long. I also wanted to pay people for their time (at least a nominal sum!) if they did an assessment for us. That meant I had to have some way to distinguish folks. Of course, I did the quick 'nope' pass, but still had a lot of folks to weed through. All I'm saying is that as a candidate, putting in effort will help you land a job, precisely because effort is expensive and most folks won't do it.
- thaumasiotes 5y ago> All I'm saying is that as a candidate, putting in effort will help you land a job, precisely because effort is expensive and most folks won't do it. This can be true, but it doesn't support the idea that high-value signaling is expensive. Putting in effort is expensive. But putting in effort is not necessarily a high-value signal. Filtering your job applications based on effort put into the application can easily lower the quality of the candidate you select, because the metric you're focusing has so little to do with performance.