5 ms·
I don't think anyone is trying to cover that up. Many teams are responsible for boring and low-impact work, so they need to hire people who are easy to manage o
by SpicyLemonZest 6y ago
I don't think anyone is trying to cover that up. Many teams are responsible for boring and low-impact work, so they need to hire people who are easy to manage or the work won't get done.
- throwaway_pdp09 6y agoWhat is that work? Why can't it be automated?
- bargle0 6y agoProbably because it’s still cheaper to throw people at it.
- anewdirection 6y agoSome things need a human touch. Interacting with other humans is one of those things. See any automated customer service bot ever to see how absolutely terrible an idea that would be.
- adrianN 6y agoGood luck automating fixing bugs and implementing weird customer requests in an old legacy application.
- joejerryronnie 6y agoProbably because these are not rote tasks being performed but rather new dev projects driven by new demands, priorities, and business requirements. You can’t automate that type of work.
- ViViDboarder 6y agoRuling out skilled folks for their skills Kate a poor way of being for those teams. Motivation is something entirely different than aptitude. I hire engineers to work on internal tools. It’s far from the most “glamorous” roles in the SWE world and a lot of great engineers would not want to be working with Salesforce or Oracle. However, it’s very important and strategic to our business. I don’t reduce the qualifications when hiring though. I actually add another. They must be motivated by this type of work. I find people who care about efficiency of teams and are motivated by having a revenue impact more than being able to point to a widget on the main site and say “I did this”. I’ve been quite successful at it for the last 7 or so years with slightly lower turnover than the rest of the org or industry averages.