This may work well for small/medium sized companies, where they really care about who is being hired. Most big companies don't care, they just attract people to work under their predetermined conditions.
This may work well for small/medium sized companies, where they really care about who is being hired. Most big companies don't care, they just attract people to work under their predetermined conditions.
GR: "Hey, you seem perfect for a position I have in mind. Want to chat?"
Me: "Sure. What's the position?"
GR: "Well, what do you want to work on?"
If you assume that:
a) people are most productive doing something they're passionate about; and
b) the set of Google employees is smart and creative enough that what they want to work on is probably the right thing to work on;
then this is probably the optimum method of allocating developer resources.
You're encouraged to move on to another project every 18 months or so, but I'm pretty sure that doesn't happen too often, either.
Thanks for the clarification. The ad hoc manner in which many projects roll out at google, it almost seems as though they're still following the previous method; but I suppose that it could also be a function of management deciding to jump when a 20% project bears fruit.