4 ms·
>> The problem with signalling is that high value signalling is expensive. > That's the point! Neither of these is correct. High-value signaling is difficult
by thaumasiotes 5y ago
>> The problem with signalling is that high value signalling is expensive.
> That's the point!
Neither of these is correct. High-value signaling is difficult to fake. If what you want to signal is wealth, then signaling is expensive. But if you're looking for a job, you probably aren't trying to signal wealth. Signaling competence doesn't have to be expensive.
- ebiester 5y agoI believe the expense, in this case, is talking about cost in time, not money.
- thaumasiotes 5y agoThat is not a necessary part of signaling competence. It's a part of the method lordnacho wishes to recommend.
- mooreds 5y agoSorry if I was imprecise in my verbiage. I was talking about expense in the general sense (time, effort, focus) not just money. For example, it takes more work to research a company, find the hiring manager, see what meetups the team members might attend, determine part of their tech stack, build an app in that tech stack using their product, volunteer to give a talk on that app, let the manager and team know about your talk and then ask about open positions, than it does to shoot a resume off. But if I was at a company where a candidate did the former set of activities, it would knock my socks off and they'd definitely move to the front of the interview line. Note, not everyone has time for this particular way to stand out (we all have different obligations), but in my opinion, every new developer should find some way to stand out.
- 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.
- yCombLinks 5y agoHe doesn't mean expensive in terms of money.
- thaumasiotes 5y agoIf you read my responses to the other two comments that came before you, you probably noticed that that isn't relevant to my point. I don't mean expensive in terms of money either. What were you trying to say?
- yCombLinks 5y agoNo, I didn't read them, they weren't there when I loaded the page. You're unnecessarily aggressive in your response. Your previous reply was all about wealth, and how signaling outside of wealth was not expensive. Hard not to frame that as viewing it in terms of money.