Come on man, junior or mid level engineers are suposed to do well defined tasks, or projects. It is part of the Team Lead, Lead/Staff engineers to reduce the b

Come on man, junior or mid level engineers are suposed to do well defined tasks, or projects. It is part of the Team Lead, Lead/Staff engineers to reduce the business requirements to a relatively well defined project. That's how most mid level, and large companies work. You are not hiring an engineer with 2yoe to 'coordinate business values', unless you work at some scrappy startup. The original article has a good point: Young engineers are so used to google for everything, that they often don't understand the code, or framework they are working with. Back in the day (prior to StackOverflow), we called them "Framework, Glue and Paste Engineers". Basically people that used frameworks without understanding what they did. It was fine for basic stuff, until the point you crash servers because you have no clue what did Hibernate do under the hood with those queries. Anyway.... the article is clearly aimed at more junior hires.