Some nuggets of wisdom from the article when managing an engineering org:
- “if the only reason an engineer wants to work for you is because of your tech stack, that may be a warning sign. Culture Amp therefore avoids hiring engineers who are purely technology-focused. As a product company, we seek to hire people who are mostly excited about our product and its mission, and who are happy to learn new things when necessary to progress that. When someone tells us in an interview they’re excited about working here because they like functional programming (say), we count that as an indication they might not be a good fit.”
- “Perhaps the greatest challenge for engineers as they reach more senior levels in their career is to make decisions that balance the moment-to-moment joy (or frustration) that a given tool affords them, and the costs (or benefits) that same tool might create for their team, company or client over time and at scale”
Because if there was something more concrete to offer that isn't done better, either from them or from the firm they represent, they'd go with that instead.
At least those that talk publicly about company culture. It feels performative and inauthentic, but maybe that's necessary to compete? They are selling culture surveillance technology of some sort.
Reminds me of mandates to get more on the engineering blog: makes an organic, authentic good into something performative.
Culture Amp is a performance review system that lets you give/receive feedback to/from peers and/or their managers. Please view their post with that in-mind.
Maybe it’s just because I’m also based in Melbourne, but I’ve worked for two or three places that use cultureamp, it’s a pretty solid service to help manage personal development goals and employee surveys etc. I even used to work for a competitor of theirs, and I’d rate their stuff much better, I wouldn’t write them off just because you’re not familiar with them.
> if the only reason an engineer wants to work for you is because of your tech stack, that may be a warning sign. Culture Amp therefore avoids hiring engineers who are purely technology-focused.
For the case of senior engineers conflict with this:
> Perhaps the greatest challenge for engineers as they reach more senior levels in their career is to make decisions that balance the moment-to-moment joy (or frustration) that a given tool affords them
- “if the only reason an engineer wants to work for you is because of your tech stack, that may be a warning sign. Culture Amp therefore avoids hiring engineers who are purely technology-focused. As a product company, we seek to hire people who are mostly excited about our product and its mission, and who are happy to learn new things when necessary to progress that. When someone tells us in an interview they’re excited about working here because they like functional programming (say), we count that as an indication they might not be a good fit.”
- “Perhaps the greatest challenge for engineers as they reach more senior levels in their career is to make decisions that balance the moment-to-moment joy (or frustration) that a given tool affords them, and the costs (or benefits) that same tool might create for their team, company or client over time and at scale”