The Engineering Manager's role is under attack (again)

(manager.dev)

43 points | by fagnerbrack 8 hours ago ago

82 comments

  • scott_w 7 hours ago ago

    Reading Meta wants a 1:50 ratio is wild. Let’s put some simple numbers down.

    I like a 30 minute 1-on-1 per engineer per week. At 1:50, 25 hours out of my 40 are now 1-on-1s.

    Assume a usual team is 5 engineers, so I’m covering 10 teams, effectively.

    So I have 15 hours to keep context of 10 teams. Am I expected to contribute as an IC, too? Usually when I’m directly leading a team, putting code into prod is how I feel the pain.

    Finally: am I getting 10x the salary for doing the job of 10 EMs?

    I’m all for cutting bureaucracy but is AI really this magical?

    • paperpunk 7 hours ago ago

      Not that I'm defending that ratio, but I can't imagine if they have a 1:50 ratio, they're expecting to do 1:1s every week. Maybe do it every 2 weeks. Now you've got half your time back.

      For better or worse AI also enables unprecedented levels of surveillance of your team. You can churn through what every single one of those 50 people is doing every day, what they're actually delivering, what their working habits are, what conflicts they're having with people, etc.

      • jaynetics 7 hours ago ago

        You can churn through all that, but I'm not sure you'll understand the people in a relevant way. At this ratio it's more like a warden or evangelist role or so, rather than actual people management.

        • throwup238 7 hours ago ago

          > it's more like a warden

          We are in a prison drama and this is the fucking Shawshank Redemption, right? But with more tunnelling through shit and no fucking redemption.

      • scott_w 3 hours ago ago

        > if they have a 1:50 ratio, they're expecting to do 1:1s every week

        > AI also enables unprecedented levels of surveillance of your team

        If 1-on-1 = status update in your mind, then no wonder 1:50 looks feasible.

    • ramblerman 6 hours ago ago

      It's so wild to me how locked people are in their little rituals.

      This 1to1 culture is something everyone started copying from each other to add a few levers of control and make their calendars look full. It's by no means an optimum of how to run a company or improve communication.

      But you are so stuck in the local (non)optimum you can only judge this through that little viewpoint.

      • scott_w 2 hours ago ago

        I'm really not sure what your objection is. Have you had a string of poor managers and are now jaded on the whole experience? Is it just 1-on-1s that you object to? What is it that you object to? What system, process, etc. have you found that's superior? What does it give you that's missing from 1-on-1s?

        I accept that it's totally possible to get all the benefits of regular communication, building trust, discussing career growth, identifying problems, etc. without 1-on-1s. I just find that the managers who don't do 1-on-1s also don't do those other things, either.

        • ramblerman 2 hours ago ago

          I'm saying that with the wave of change that is about to hit us as we try to adapt our organizations to agentic coding, I'm doubtful EMs remain a thing.

          It's a strange side manager role, that isn't about the product or bottom line.

          • scott_w 2 hours ago ago

            What evidence do you have? So far you’ve just said words without any real depth from experience or research.

            • ramblerman an hour ago ago

              It's my opinion about the future, history and the lindy effect corroborate somewhat.

              • scott_w 31 minutes ago ago

                So this nonsense about local optima, people stuck in rituals was just a sad attempt to sound profound then you fall back on "it's just like, my opinion, man!" I had a distant hope you'd bring something actually interesting. Sad.

      • menaerus 5 hours ago ago

        I mean obviously true because what else such management roles would be doing if not micromanaging their teams to death?

        Their deliverable is a report to the stakeholder so of course they are heavily incentivized to find ways how to collect sufficiently sized data for it. They could opt in to proactively scrape the necessary content from slack/teams, ticketing systems, PRs, and then creating a report, submitting it to the team for a review but no - that would make them look very replaceable, and out of enough work for a 40-hour week.

        I always hated these "ceremonies" with passion - pure waste of time for most engineering teams. Micromgmt in disguise.

        • scott_w 2 hours ago ago

          > I mean obviously true because what else such management roles would be doing if not micromanaging their teams to death?

          Building trust? Helping their career growth? Finding opportunities for them to develop their skills in a way they can sell up to their own manager to get that promotion? Spotting that a team member is unhappy and trying to help resolve it. Or supporting them leaving in a way that minimises disruption for the business and keeps a good relationship with that person.

          Look, these are all possible without 1-on-1s, I just see that managers who don't do 1-on-1s don't do any of these things anyway, so it's hard to separate out.

    • matwood 7 hours ago ago

      > Reading Meta wants a 1:50 ratio is wild.

      This could be on purpose to remove any of the human element out of managing. At that ratio you’re not dealing with pets, but cattle. My personal management style wouldn’t fit that type of ratio, but I also have never worked at a big tech company.

      • lrem 6 hours ago ago

        I'm in another big tech company. Ratios fluctuate, but there is an eternal "we need more managers, we're looking for the good ones as fast as we can". I guess the ratios will inch down now, with what's happening in the market?

    • onion2k 7 hours ago ago

      I like a 30 minute 1-on-1 per engineer per week.

      Assuming you're not doing project status updates and you're actually talking about them rather than the work, that seems like quite a lot of dedicated time. I do half that with my reports.

      • rpdillon 23 minutes ago ago

        You schedule it, sometimes you end early. Often there's plenty to talk about.

      • scott_w 3 hours ago ago

        Yes, it's a mix. Obviously not everyone needs 30 minutes every week but you still need the time there for when they do need that time. Don't forget the pre-and-post time you spend preparing and following up. It's usually more than the calendar slot.

      • dysfunctionalok 7 hours ago ago

        Interesting data point: median time between 1-on-1s with my boss is measured in months. One time I went for a year without talking directly. We’re a small company, but I still find it interesting we function (somewhat). It definitely is possible to keep the ship going with minimal oversight.

        • scott_w 3 hours ago ago

          It's possible but it does mean that, if you become unhappy with work for any reason, the baseline of trust that can only be built on regular communication just isn't there.

          I'm not saying it can't work but, having worked both in small (10 people) and medium/large (2000 people) organisations, regular conversations with my team is probably the thing in my week that has had more impact than anything else. For them, myself and the organisation.

          • dysfunctionalok 2 hours ago ago

            I think I came across as claiming it was healthy and I genuinely think it is enormously stupid. Major problems are swept under the rug, communication in general even with colleagues is subpar. The business as whole could probably 10x its revenue or more if we would be able talk properly to each other.

            I fully agree it is healthy for both the individuals involved and the business at large.

            Still, it keeps surprising me how resilient groups of people can be. Perhaps being on the spectrum helps here, I am not sure.

            • scott_w 2 hours ago ago

              Oh, absolutely! I’ve said for a long time that it’s possible to succeed in spite of bad practices (not just in management!) but it helps to have good practices.

    • vasco 7 hours ago ago

      Well on the other hand only these megacorps will need managers because for 99% of other software companies, 10 people will be enough.

      • scott_w 7 hours ago ago

        I don’t necessarily disagree on the ratios but I think that’s because we’ll see more software companies overall rather than because companies will engage mass layoffs.

    • N_Lens 7 hours ago ago

      They’re delusional (and will soon pay the price for their hubris), just like Microsoft

      • scott_w 7 hours ago ago

        Obviously, they did let Zuckerberg get away with the Metaverse idea for 10 years ;-)

    • sudohalt 7 hours ago ago

      You must deal with incompetent engineers if you're meeting with them for 30min a week. 1-1 should be once a month (maybe bi weekly)

      • scott_w 3 hours ago ago

        Why would I spend my time on incompetent engineers? I fire those engineers. In my experience, I find 30 minutes is nowhere near enough time for my best engineers.

        • stvltvs 2 hours ago ago

          What do you talk about if it's not a work status update?

          As an IC, a weekly cadence feels too frequent. I struggle to find anything relevant to discuss because things don't change that much every week.

          • scott_w 2 hours ago ago

            Career growth, how they’re getting on in general, what issues they see (technical, personal, professional). Sometimes we just chat. Not everyone uses the full 30 minutes every week but we need it there so we can use it when it is needed.

            I can get a status update from the standup, so I’m more interested in the person.

  • arnvald 8 hours ago ago

    I used to work in an organization where a senior director had 2 direct reports, one of them being a director who had 2-3 direct reports (senior managers), and these senior managers had maybe 3-4 managers each.

    Getting anything done was a nightmare because everyone up to the senior director level wanted to have an impact on the decision, so the approval process took ages.

    When done right, the flattening is good (and I say it as a middle manager) - it should remove layers that don’t add value, and empower people at lower levels. In this case removing the senior director or director wouldn’t hurt the organization.

    Unfortunately what I often see is that an organization will reduce number of people in one layer from 3 to 2, increasing the number of direct reports, but keeping the same number of layers leading to no improvements (besides cutting costs)

    • ErrantX 7 hours ago ago

      I think generally the approval problem is more a cultural one than a structural (the main reference work ok this is Turn the Ship Around by David Marquet).

    • drivebyhooting 7 hours ago ago

      I’ve seen a director with no reports.

      • nomorewords 7 hours ago ago

        This is meta, but recently I'm seeing more and more comment like this which just provide a soundbite and don't expand, it starts feeling reddit-like. OK, so you saw a director with no reports, but what's the context? What were they doing? Are you saying this as a bad thing or a good thing? I don't understand the purpose of this comment when it hasn't expanded on the point it's trying to make (and I'm not even sure what that is)

        • glimshe 6 hours ago ago

          I've seen that too, so let me give you the context.

          This was FAANG. The person was hired for a cross-cutting role that could one day have a team. Let's say, Globalization support for a large household name product.

          They went to a bunch of meetings and created documents that others, under other "team directors" had to read and use to affect their plans. So in theory they had a big goal that they had to deliver through influence. As a director, they participated in the right meetings and affected promotions of high ranking employees.

          I didn't work directly with them so I don't know if it worked. I remember seeing them gone from the org chart one day.

          Don't some financial companies have VPs without reports? I remember someone who was an entry level hire from Duke University leaving the company I worked for and in 3 years being a VP at some big name company, perhaps Goldman Sachs? A friend told me that particular role had no team, but this was a long time ago so I'm not sure about the one.

      • vrosas 6 hours ago ago

        I saw that once, because their entire team (3 senior engineers) quit in protest of how much they hated him. To my shock the director was allowed to stay and rebuild their team. What an eye-opening situation that was.

      • AndyPa32 6 hours ago ago

        There's a german word for that (of course): "Frühstücksdirektor" - translates to director of breakfast.

      • matwood 7 hours ago ago

        This can happen with external facing positions. The director in question needs to have the perception they speak for the company.

  • praptak 7 hours ago ago

    From my experience as a software engineer there is not enough management being done.

    I'm talking situations like broken processes that everyone complains about but nobody has the power to change. Planning cycles that stack delays. Unclear ownership where anyone can block your request but no one can approve it.

    I'm not saying this simply translates to "more managers". There obviously can be too many cooks. But I think currently we have too little and 50:1 is crazy, simply because 50 people cannot work as a single homogeneous group and you end up with TLs pretending they are not managers.

  • okaleniuk 4 hours ago ago

    Maybe it should be under attack. I've been promoted to engineering management position two years ago and, as soon as I got rid of all the bullshit activities, the role itself dissolved.

    Now I spend about two hours a week on regular syncs, an maybe another hour on average putting fires down. The rest of the time I do engineering along with my teammates. Needless to say, we are super productive in this setup.

  • austin-cheney 7 hours ago ago

    At the last job I was managing 14 people (about 40% of the project), baby sitting the dysfunctional project manager, developing, and providing QA support for after hours deployments. I don’t miss it. I had too many bosses each with too many diverging goals.

    My number one goal when looking for the next job is to identify immaturity early. The result is I am still unemployed.

  • dcminter 7 hours ago ago

    The article makes a case that EMs do useful work but fails to make the case for why EMs can't be replaced by AI.

    • hasyimibhar 7 hours ago ago

      Personally I feel like it's insane to think that EM can be replaced by AI. EM are meant to solve people problems. The best thing that has ever happened in my career was having a good EM that stood up for me when I made expensive mistakes when he could have easily fired me. No way an AI could have done that.

      • roncesvalles 7 hours ago ago

        A sufficiently good prompt can encode such generosity.

        I honestly think AI is perfect for people management because it has complete visibility into everything you do. It has perfect metrics about its reports' productivity, when they come in, when they leave, the transcripts of every single meeting. And the objective is not to make a dystopian slavemaster that fires you if you slack off for a minute, or starts a PIP because you couldn't work well the week after your mother died. Human-like empathy and subjectivity would be part of its programming.

        And in many ways, it's better than a human manager because there are no personal grudges, prejudices, all the ick that comes with firing someone that you're close with. Promotions, bonuses, firings are all fair and data-supported. Everybody is subject to the same rubric.

        • hasyimibhar 6 hours ago ago

          I'm sorry, but this is AI psychosis.

          • FearNotDaniel 3 hours ago ago

            Unfortunately the current “wisdom” on HN is that everything has to be either/or. Either the human input of our jobs is so irreplaceable that we have to carry on doing everything by hand, or absolutely everything a human does can be replaced overnight by sufficiently advanced LLM technology. That’s not even the vision that Anthropic are selling. Knowing when to put a human in the loop is key, and building the automations around giving that human everything they need to make that call as efficiently as possible.

        • kaffekaka 6 hours ago ago

          > And the objective is not to make a dystopian slavemaster that fires you if you slack off for a minute ...

          But that is what it would become.

        • rpdillon 19 minutes ago ago

          So you want your boss to be AI. Interesting choice.

    • vasco 7 hours ago ago

      Most will because you will simply not need to hire as much people. I used to run a tribe of 4 teams to do something I'm today doing with me and another guy. These are real projects that have better outcomes and get done faster with 2 people vs 4 teams (20 people) because this way we also have no coordination or communication problems. And I believe I'm a better manager than I am an engineer, so this isn't even bragging about anything, its just what it is.

  • Animats 7 hours ago ago

    "One of the things managers repeatedly ask me about in workshops is: “How do I keep the team together when they prefer to talk to AI rather than talk to each other?”

    Now that's a new problem. Usually articles like this re-hash classic problems.

    (I recently had to chat with customer support for a retailer. The other end was human, and one of the better AIs would have been far more useful.)

    • FearNotDaniel 7 hours ago ago

      In my experience this tends to be because the team has never learned what healthy communication looks like in the first place. If communication between team members is already perceived as a burden, then obviously people are going to isolate themselves even more when they get faster answers from an LLM without the drama of people being offended because they are being asked to communicate. The impact of agentic tools on team dynamics is similar to their impact on documentation and system architecture - if you were already doing it right in the first place then the bots help you make it better; if you are not but you know it, and ask the bots how to transform to a more structured approach they can help with that too; if you neglect it completely then the bots will help you make it worse than before.

  • fullstackwife 8 hours ago ago

    The article is from Sep 1, so still before Opus 5.5 release date, and I guess the mindset of authors was formulated long time before Opus 5 release, which I consider the turning point of software engineering industry. Things changed a lot since then, and it was a point of no return.

    • Synthetic7346 7 hours ago ago

      Good as it is, I don't see opus 5.5 replacing managers

      • fullstackwife 7 hours ago ago

        The business model changed since then, you no longer need a small army of devs to solve problems, we no longer need to play LARP of Prussian army to work in the industry. Article says someone is attacking the role, but the brutal truth is different: the demand for such service is decreasing rapidly.

    • PufPufPuf 6 hours ago ago

      Can you be more specific on what changed with Opus 5.5? What turning point? What point of no return?

    • jayd16 7 hours ago ago

      What does that have to do with the article?

      In fact, what are you trying to say? Seems like a generic response you could try to post in every submission.

      • anon7725 7 hours ago ago

        Haven’t you noticed that after the Opus 5.5 release, colours are more vibrant, interactions more pleasant and turds more pungent?

        • kaffekaka 6 hours ago ago

          ROFL

          On a serious note, actively disengaging from AI psychosis and impending burnout has made my life better, so timeline wise, yes the latest AI drops have been correlated with those things you mention.

      • jurgenburgen 7 hours ago ago

        Anthropic astroturfing? That marketing budget has to be spent somewhere.

    • nyanmatt 7 hours ago ago

      Pretty typical for a manager; out of date and irrelevant. Probably had to wait 2 months for approval from the hierarchy of bureaucracy. When the team can be agile on its own, the management process gets left in the dust.

      Sorry, managers, for being unnecessarily harsh.

      • mawadev 7 hours ago ago

        I'm most certainly working for a less happy company where managers insist on a lot of reporting where already understaffed teams spend their time filling and updating jira instead of doing the work to get a project done. Not sure if it has anything to do with managers, but no matter the amount between, there finally has to be more trust again. Whenever I have to speak to a manager, I'm met with disinterest in what has to be done, how and how much it costs. Seems like its best to do nothing and produce no costs except a wage. There is always some sort of haggling and personal things going on as well that should be far away from building a working system.

        At this point I believe that even if we had AGI/ASI, we'd still hit our head on the decision making processes, since it seems to be an interpersonal people problem instead of simply providing solutions to very real problems people pay for.

        Even former engineers who move to such management roles change their frame of mind with enough exposure to the upper layers and they forget what it all is about.

        • kaffekaka 6 hours ago ago

          > At this point I believe that even if we had AGI/ASI, we'd still hit our head on the decision making processes, since it seems to be an interpersonal people problem instead of simply providing solutions to very real problems people pay for.

          Yes absolutely! People problems are at the core of everything.

    • wavemode 7 hours ago ago

      I can't tell if this comment is satire.

  • matsemann 7 hours ago ago

    I've never worked a place where I've liked the implementation of engineering managers. Often it feels like the EM is both the tech lead / architect and your manager, which conflates things too much. Also they're often too busy to do either part good enough.

    I've much preferred when the managerial role is outside my team, or at least a different person. Makes it easier to discuss things with them.

    I'm not saying I don't value their work. Just that I don't like the way of putting multiple responsibilities onto one person.

    • roncesvalles 7 hours ago ago

      I like the American big tech approach where there is a parallel track for IC and management, so that the most senior engineer on the team would not be the manager.

      European and Asian companies in comparison have the approach where an IC gets promoted to a manager, who is both the most experienced and the highest paid person on the team (and often the oldest). This is of course flawed because being a good manager and being a good software engineer require mostly different skills.

    • ErrantX 7 hours ago ago

      As a leader of leaders I've long thought the same. In my experience, the EM role is too generalist and so you tend to have a bunch of average performance from an otherwise above average group.

      Had much better success shaping specific roles, especially splitting people leader and delivery lead.

    • ancheril 7 hours ago ago

      Last job they expected that of me. It was my first time as EM. One month in, I told the boss I couldn't do both well simultaneously and requested to do people lead only, the boss agreed. I kept overseeing the tech side (support on design, doing code reviews etc) but not calling the shots (except when warranted). It worked well.

  • maxipavlovic 4 hours ago ago

    It's the best time to be alive as an EM today. You at least have a chance to lead a team and do cool engineering without a complete burnout.

    The ones who are attacked are most probably the enterprise-like comfort layers that uses Copilot instead of Claude Code (replace with a good tool that you like). And if I am wrong and our job is forced to do engineering again, I don't see that as a loss, sincerely.

  • undefined 6 hours ago ago
    [deleted]
  • t43562 8 hours ago ago

    Developers do sometimes think they can do without managers until, as the article mentions, there's anything that needs deciding or a "people problem". It does make me laugh a bit that at each level there is a non-understanding about the adjacent levels such that destructive changes seem good at first glance.

    IMO it is valuable for people to occasionally do things out of their own area to generate that understanding but what business would ever allow that?

    • throw9398922 7 hours ago ago

      Perhaps developers can decide on their own? In my experience most managers are major bottle neck, and just "diversity hires". They are not capable of comprehending the problem, let alone deciding.

      I so much prefer to just exchange markdown folders with other developers and their agents. After a few rounds we get decisions and can move on. No weeks and weeks of meetings needed!

      • jeffreygoesto 7 hours ago ago

        This is taking past the parent comment and shows that parts of the divide are on the engineering side. Your point is valid and definitively weighs much, but I don't understand how engineers don't reflect what their contribution in this is and I am sad for all who haven't worked with good people managers. Those really elevate an organization to a next level. Seen both cases (good and bad managers). Similar for product managers. Engineers think they need to build. Period. But the sentence continues with "for customers" and they can't understand customers and their problems at all.

        • throw9398922 7 hours ago ago

          > Engineers think they need to build. Period. But the sentence continues with "for customers" and they can't understand customers and their problems at all.

          And managers are working for customers? In my experience they only focus on revenue, and squeezing out more out of customers. The MBA/management culture is cancer that is eating industry. With AI developers can simply bypass it!

          As engineer I got in troubles for adding minor features or improvements, customers asked for. That was outside plan, without managers approval, and very simple to do (compilation flag, extra text field...). It was planned as next "major" release/contract for tons of momey.

          • kaffekaka 6 hours ago ago

            With the benefits of AI I feel that it is the only path forward. I refuse to let PMs gatekeep an inefficient process. If they feel threatened (likely), they need to adapt on their side.

          • t43562 6 hours ago ago

            Well, I'm sorry you got into trouble....but what one always tends to forget is that the software belongs to the company not the people writing it.

        • kaffekaka 6 hours ago ago

          > Engineers think they need to build. Period. But the sentence continues with "for customers" and they can't understand customers and their problems at all.

          So if I can understand customers, I am not really an engineer?

          • t43562 5 hours ago ago

            Anyone who is removed from the customer tends to have their own conception of what the customer wants/needs and it's not always that close because of their own assumptions. I think it's excellent if developers can talk to customers but some companies obviously seem to think this is risky for some reason - possibly legal.

            I've seen it when working with internal customers - we thought they were idiots and they thought we were idiots till we flew over to meet them and saw the kind of problems they had. After that work went much better - the proposed solutions were more generally right.

            • kaffekaka 3 hours ago ago

              Ok. Where I work all customers are internal and there is really no legal or other risk involved in having developers and customers meeting directly.

              My experience is that middlemen cause misunderstandings.

          • jeffreygoesto 6 hours ago ago

            You are. But also the exception.

            We pivoted to three roles (that oversee a bigger number of engineers to limit the overhead): tech, people and business. Our experience is good, we managed to build triplets that can focus on each area and trust each other. Probability of finding one person doing all three well is just too low.

      • t43562 6 hours ago ago

        What happens when 2 developers disagree violently? Someone has to break the deadlock.

        I was a team lead, now I'm a developer again. I have to say that putting yourself in other people's shoes does give you sympathy for them and it's extremely easy to rubbish everyone's problems other than one's own.

      • secretsatan 6 hours ago ago

        You don’t know diversity hires till you meet the traditional management hire, where qualification is married guy with kids.

        • t43562 6 hours ago ago

          People with kids and a mortgage want stability and moving around is much more difficult for them - hence a company can have more control over them.