News for hackers. Stuff that matters.
Re:Why talent agents for engineers don’t exist by nickff on Friday October 31, 2014 @02:05PM (#8540168)
Many engineering projects (especially outside of software) can last many years, making engineer (knowledge and understanding) retention quite valuable, and the engineers involved wish to see it through. In addition, we should keep the nature of the firm in mind, and remember that keeping a team together has the potential to greatly reduce transaction and switching costs.[1]

[1] http://en.wikipedia.org/wiki/The_Nature_of_the_Firm

Re:Why talent agents for engineers don’t exist by chatmasta on Friday October 31, 2014 @02:08PM (#8540187)
I'm familiar with that essay (did you also just watch Aaron Levie's stanford talk?), and that's a good point.

How greatly are transaction/switching costs affected when segmenting projects in 6-12 month intervals? I would guess, that when you're throwing senior engineers at projects, the switching costs are non-trivial, but low. It's probably an acceptable tradeoff to pay when developing specialized projects you don't expect to carry over to future ones.

There's also the argument of developing a labor force to compete with other enterprises. However, if the best engineers are in sufficiently high demand, it may be more economically rational for them to move between projects every 6-12 months, gradually increasing their pay-rate and improving their portfolio after completing each one. If this is the case, then companies would be forced to hire top engineers on a contractual basis (or pay them a significant markup annually), purely to compete in the labor market for top talent.

Re:Why talent agents for engineers don’t exist by Swizec on Friday October 31, 2014 @02:27PM (#8540287)
It was my impression that most top engineers already do this by either being freelancers or through poaching.

Or even, at the very least, by switching projects internally.