> It’s not like we have a term like “individual contributor” or anything in the industry.
Perhaps I'm missing something here.
To me "individual contributor" means anyone who is NOT: A (technical) "Lead", "Chief", "Architect", or (possibly) "Staff" anything, and has no management or team-leader responsibilities.
I'm not saying there can't be very clear counter examples, I guess the overall sense though is that "being a team player' is generally considered an attractive quality in any employee. If A is a team player and B isn't, and they're otherwise equivalent, you're probably going to take/keep A.
It's not like (most) hiring managers put "not a team player" in the pro column.
Alas, I’ve learned that while everyone wants to hire them to fix their hideously fucked systems, they really don’t enjoy being told that their systems are, in fact, hideously fucked. They’d much prefer you quietly put out fires while biting your tongue about how they aren’t actually fixing any root causes.
The problem is that people are being cut for not being perceived as a team player, because they don't exactly fit the narrow perspective avoided by the dominant social culture. That doesn't mean they aren't team players.
For example: someone not always looking into your eyes while talking can be perceived as "rude". Same for wearing noise-canceling headphones in a talk-heavy environment. Oh, you don't drink alcohol during the "optional" Friday-afternoon company mixer? That's just weird. Want to have a day off for Eid rather than Christmas? Wellll, you did ask for it six months in advance and we did approve it already, buuuuut Dave planned a last-minute meeting which conflicts with the mandatory team meeting, so we moved the mandatory team meeting onto your day off... We'll just pay the hours you spent doing first-line support during Christmas in cash, okay?
It’s not like we have a term like “individual contributor” or anything in the industry.
I’ve worked with several excellent “just leave me alone” sysadmin types.
> It’s not like we have a term like “individual contributor” or anything in the industry.
Perhaps I'm missing something here.
To me "individual contributor" means anyone who is NOT: A (technical) "Lead", "Chief", "Architect", or (possibly) "Staff" anything, and has no management or team-leader responsibilities.
Yeah, it doesn't mean a 1-person-team, it means your job doesn't include supervising someone else.
I'm not saying there can't be very clear counter examples, I guess the overall sense though is that "being a team player' is generally considered an attractive quality in any employee. If A is a team player and B isn't, and they're otherwise equivalent, you're probably going to take/keep A.
It's not like (most) hiring managers put "not a team player" in the pro column.
Alas, I’ve learned that while everyone wants to hire them to fix their hideously fucked systems, they really don’t enjoy being told that their systems are, in fact, hideously fucked. They’d much prefer you quietly put out fires while biting your tongue about how they aren’t actually fixing any root causes.
The problem is that people are being cut for not being perceived as a team player, because they don't exactly fit the narrow perspective avoided by the dominant social culture. That doesn't mean they aren't team players.
For example: someone not always looking into your eyes while talking can be perceived as "rude". Same for wearing noise-canceling headphones in a talk-heavy environment. Oh, you don't drink alcohol during the "optional" Friday-afternoon company mixer? That's just weird. Want to have a day off for Eid rather than Christmas? Wellll, you did ask for it six months in advance and we did approve it already, buuuuut Dave planned a last-minute meeting which conflicts with the mandatory team meeting, so we moved the mandatory team meeting onto your day off... We'll just pay the hours you spent doing first-line support during Christmas in cash, okay?