3 ms·
The article contains some decent advice if you're hiring folks with 10-15 yoe. But if you're hiring someone with 5 yoe as a "Senior", then you'd better only hir
by throwawaygh 5y ago
The article contains some decent advice if you're hiring folks with 10-15 yoe. But if you're hiring someone with 5 yoe as a "Senior", then you'd better only hire them to work on what they have experience with. And the latter is more common than the former IME.
In other words, there's been significant title creep in the last decade and "Senior" no longer means what the author of this post seems to assume (experience with multiple frameworks, languages, orgs, etc).
- datameta 5y agoI think there is a difference between hiring someone with C# experience for a Java role, or someone with C++ experience for a Rust role, and hiring someone for a diametrically opposed software stack. There is nuance. Though I would say someone with at least intermediate abilities in half a dozen languages has a great track record for learning new things. Carpenters are not sifted for how much experience they have in soft woods, hard woods, or plywood.
- throwawaygh 5y agoYeah, totally fair. Nuance is king. Still. I can see hiring someone with 5 yoe C# to serve as the Senior on a Java project. However, I wonder about hiring someone with 5 yoe C# to serve as the Senior on a Java project. There would have to be some sort of additional major value add (e.g., domain expertise). At 15 yoe C# experience this starts to make a lot more sense.