Comment by kelnos
9 hours ago
> Leaders will own much more, with as many as 15+ direct reports. [...] Every leader at Coinbase must also be a strong and active individual contributor. Managers should be like player-coaches, getting their hands dirty alongside their teams.
Oof. So not only are they giving their remaining managers more reports, but those managers will be expected to do lots of other, non-management work.
Sure, nothing can go wrong there... Even if they didn't have non-managerial work to do, 15+ direct reports is just too many. They're not going to get to spend enough time meeting each report's needs, not a chance.
I think as layoffs emails go, it's a pretty good one (as the current top comment points out[0]), but boy, I would not want to be working at a company like what Coinbase is turning into. Non-technical teams shipping code to prod? No thanks. "AI-native pods"? No thanks. I do like the idea of one-person teams; I was at my most productive when I was in that kind of role (though I'm not sure my experience generalizes). I get that companies are still struggling to figure out how to adapt to LLMs, but... damn.
Pretty solid severance package for the folks being laid off, though.
Or maybe we should go back to what it was before Google and big $$$ tech decided that if you were a "manager" you shouldn't contribute technically. Being a manager now means a bunch of busy work talking to other managers and weekly 1:1s. There is a ton that has been written about the managerial class. Producing nothing, but for sure making themselves look self-important.
Before that the manager was essentially the best engineer in the team (or the one that wanted to get promoted). Being a manger meant you were respected directly for your skills and you were expected to still be a full time contributor. Directors meant you were one of the best ICs out there. Now, being a manager or a director means you sometimes did an MBA in an unrelated field. This brought a ton of politics, nonsense meetings (because the most visible output for managers is more meetings where they can posture).
Let's go back to what it used to be. We don't need weekly 1:1s to check on feelings. We don't need a full layer of managers syncing with each others and taking political decisions that will mainly advance them. We don't need another layer of gatekeepers.
I'm not saying all managers are bad, but this charade has been pushed a bit too far.
> We don't need weekly 1:1s to check on feelings.
As a manager that does weekly 1:1s, I agree with that statement. But I do need 1:1s to check on progress, uncover blockers that people haven’t surfaced on their own, make continuous small decisions, offer support, assess performance, collect status information for my manager, and last but not least give employees the opportunity to share feelings frequently. They do, and it’s not very often, but it’s important to have a dedicated place for it otherwise devs often don’t share until damage is being done.
I’ve also watched devs who didn’t have weekly check-ins go pretty far off the rails. One dev I remember would go off by himself for weeks designing clever code and over-engineering things that weren’t needed. I thought to myself that someone should be checking in with him, and then months later I got stuck doing overtime before a delivery deadline with dozens of other devs on a weekend chasing an intermittent release-only runtime crash that turns out he caused by trying to get tricky with copy constructors. A quick 1:1 could have prevented this bug that ended up costing tens or hundreds of thousands before it ever happened.
BTW, the best managers I’ve ever had were technical contributors, and they tended to be more relaxed about check-ins than the non-technical managers, in part because they had a better sense of where things sat. Personally I also feel like a better manager when I’m contributing technically to a project, and devs seem to respect that more.
It is possible to move most of that discussion to required but intentional async communication.
1 reply →
The best manager I had in my career was a guy with zero software dev experience. Technical skills and leadership are simply different fields. Converting a best engineer into a mediocre manager doesn't sound like a solution for anything.
They're not completely different fields. Staff engineer and above is unobtainable without some of the leadership skills a manager needs. There's a lot of soft skill overlap between high impact ICs and management.
I like to think of it as a manager isn't required to have technical expertise, it can help, I can hurt, but they have to be a leader. Junior and mid career are required to have technical expertise, but not required to have leadership, though it would certainly help them be high impact and thought leaders in their space.
The more senior I get, the more like a manager I am. Less hands on, more coaching, guiding, teaching and setting direction. Meetings and docs become my tools less than code. When I'm writing code I'm only increasing the output of one person, me. Everything else is force multiplication. I just don't have to do the bullshit performance management.
1 reply →
The best manager role I ever worked with wasn't incredibly technical, although he was loosely working on getting some IT certifications at the time. He wasn't even the person I really reported to, he was just a project manager that was really on the ball. I knew if I needed something, I could go ask him real quick and he'd make it happen. If I didn't have the full specs, he'd go chase down the other teams and get them sorted leaving me to stay busy with the technical work. I knew if he threw a meeting my way we'd have a good agenda with real issues to work through, and I knew I'd get minutes sent out after the meeting to keep track of what was decided.
I haven't had many excellent experiences with project managers, but dang was he good at keeping me unblocked.
As a data point, I work at a US company that ended up in this place and the same thing is happening.
In my BU there were directors with 2 direct reports. Even at the next level up, the number of non-IC directs is only high single digits. There are many managers who were already engaging technically with the product (not PRs but playing an active role in planning work) and they have no idea what directors are actually doing...aside from attending meetings with other directors.
Almost all decision-making capacity has been moved outside of teams which has resulted in almost no actual work (because everything needs to be cleared by someone with no engagement with product) and people leaving (because promo decisions are made by people who have no idea what anyone is contributing, the worst ICs are the only ones they can retain ofc).
It is a terrible environment to work in.
I don't necessarily think the manager should be best IC but definitely someone who is genuinely talented with sufficient scope and responsibility to make good decisions/add value for ICs. There are way too many passengers today.
Also, this is true of higher-level ICs. At my work, they have no real engagement with product so have influence through ambiguous statements about the general direction that get passed around like the word of God. None of these decisions, so far, have been helpful or relevant.
As one of those supposedly higher level ICs, I agree entirely with the assessment.
A decade or so ago, the high level ICs I interacted with were much more technical.
They were the kind who would perhaps not invent truly novel things--but plenty did in the right companies--but they had mastered their domains and genuinely solved thorny problems that others struggled with.
Nowadays, they are more political and less involved. I have met many that do not code or barely code. I've been in months of meetings to decide to do something fairly obvious just to ensure "alignment" even though no parties actually disagreed, just wanted to nitpick minor details that could just be a comment on a PR.
> Before that the manager was essentially the best engineer in the team
I'm not sure that's ever been true.
A majority of the big corporations I've worked at this was the typical developer track.
- entry level dev
- senior dev (start being groomed for management)
- senior dev/leader (take on 25% management duties)
- manager - management track.
Once you're on a management track, you essentially are taken off of any dev work and then depending on how well you've networked determines how fast you move up the management chain. Some companies like Target, they groom and move anybody up relatively fast who they see any potential in.
The only exceptions I've seen in my career are either startups or medium sized companies where there is no management track. You're a developer from the day you're hired until you either get fired, laid off or leave the company.
When I was an entry level dev, I left three companies because they wanted to start grooming me to move up into management. I was way more into being a developer and writing code then managing people.
You people (as in this HN community) have your conception of middle management taken from memes, comics and to some extent a lack of experience. Managing even 5-10 people means juggling projects, personnel management, being held accountable for all actions of your people, having to be sandwiched between the pie-in-the-sky class and the myopic individual, translator in between. It means jumping on outage calls, doing architecture reviews, and getting slammed with meetings.
Please tell me where these 'managers make a lot of money and do nothing but approve timesheets' companies are, I'd kill to work for one!
I was a technical team lead/line manager and I watched my team casually ask about what I did all day and then 10 minutes later call me up to spend an hour debugging their code for them. And then the next one called me up to work on theirs... :-)
On the other hand I've had managers just the same - cannot understand why anything is difficult and certainly wouldn't waste their time trying to help you.
It's just people, they're sympathetic or not. Determined or not. They care about the outcome for more than themselves or not.
You're describing frontline management, not middle management. My 2 cents is that frontline management is the worst job in engineering, for the reasons you describe and more.
> We don't need weekly 1:1s to check on feelings
Hard agree. One-on-ones are one of the silliest fads in our industry lately. Why would you wait until a weekly scheduled meeting to bring something up? Your manager's job is to be available to you when you need something, not just once a week. And if they want to know how you're feeling.. they should ask, putting it on an agenda feels very disingenuous.
Me and my direct manager (a C-level) tried weekly 1:1s for a full year and ended up giving up on it because it was clearly unproductive cargo-culting.
I make it a point to have 5-10 minute ad-hoc conversations with my directs 1-2 times a week, feels a lot more natural than a scheduled 1-on-1. Twice a year we have a company-sanctioned formal sit-down about perf.
As a result, people pop in my office regularly to start these conversations, which I prefer because it leads me to believe I am approachable, which is by far one of the most important things a manager should be.
>> Producing nothing, but for sure making themselves look self-important.
A good manager is worth their worth in gold even if they produce zero technical output. I've had managers that were absolutely instrumental in my career as a programmer, and they did close to zero IC work.
>>Before that the manager was essentially the best engineer in the tea
Yes, and it was absolutely awful. Keep the best engineer in the team as the best engineer on the team. Call them experts, distinguished, senior++, whatever, don't make them managers.
>>Let's go back to what it used to be
God, please don't.
>>We don't need weekly 1:1s to check on feelings.
Speak for yourself please. I find weekly 1:1 extremely important for the entire team, especially in fully remote roles.
You can both be right. It depends on company culture, which depends on the experience, maturity, and attitude of senior management.
The two extremes of company culture are status cultures and service cultures.
In a status culture the product is the internal status hierarchy. External products are largely incidental goals, and customers and markets are only valued to the extent they create metrics that can be exploited by status seekers. Likewise employees.
In a service culture the goal is customer service through high quality output and employee development.
US corps lean far more to status culture than service culture. This is excellent for short termism, but the culture often becomes dysfunctional, if not outright abusive, and sooner or later it implodes, because status cultures aren't good at accepting reality, or at accurately reading it when they do accept it.
And status cultures tend to cargo cult management, where the C-suite is comparing its status to other C-suites, and copying apparent status-raising actions without thinking them through.
In good times a status culture will overhire, because hiring more employees looks like growth. In bad times status cultures will overfire because "cutting the slack" is lowest common denominator status management.
AI is the same on steroids. You get the promise of more growth with fewer employees, and that's hard to resist, even though it's entirely speculative and could easily be catastrophic. (Company results, and especially lasting company results, are orthogonal to whether some employees get good results with AI, because what actually affects results is how predictable the improvements are, whether there are likely downsides, and whether they're structurally in the right places.)
Whether managers should also be ICs is a side issue.
I do think that if LLMs are the equivalent of more employees, then you'd expect people to do more managerial work and less individual contribution. Certainly, that's what I see in my day-to-day.
When your job becomes managing a fleet of agents, with all the design, planning, coordination, supervision and evaluation that requires, is that "individual contribution" or "managerial work"?
I was a manager of 12 for several months and that was really difficult. I got a severe burnout, even though I had no IC responsibilities. I cannot imagine how could I dedicate enough time to my team if I did.
This jumped out at me right away too. What happened to the days when a dedicated manager would manage 8 reports? What now? AI is going to double the communication bandwidth with these reports and further double the free time they have?
I do think the most efficient form of team is a "cell" of three people. One is a little unstable.
> What happened to the days when a dedicated manager would manage 8 reports?
Cheap money went away which caused companies to start asking hard questions about productivity and how much those dedicated managers were contributing.
Then there's the convenient answer of "AI made me do it", to which investors are somehow really empathetic... feels like every company CEO is operating on the mindset of "its gonna hit the fan any moment now", except they're the ones holding the fan.
Just curious if there's a reason you mentioned 8 or if that's an arbitrary number? Was 8 an industry norm/upper limit at one point?
Perhaps related to https://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus...
Flattening is a management fad right now. Loser leaders want to be like Elon or whatever.
It is pretty stupid and pathetic tbh, but easier than making an effective organization.
A 30 min 1-1 per week per report would be a full working day. Never mind that if you're an IC then you'll also be expected to support other people using your code, as well as analysing and approving decisions for your reports.
It might be better to have 45 minutes every 2 weeks with reports, which is 1.5 days every 2 weeks. Then probably another 2 days every two weeks for sideways and upwards meetings, 2 days for ad hoc planning and design work, and 4 days for coding and reviewing.
Hope they're well paid!
Also, why use the analogy of player-coaches? How many successful player-coaches are there in the big leagues? There's a reason it's very uncommon ...
Its because when something is illogical, these "brains" retort to using some kind of a streched out metaphor which dumbs it down and makes it make sense, to them at least. So they invent the stupidities like treating a team as a Navy-SEAL unit or a sports team or... coming up with something like "player-coach"...
This ain't about sports.
In most sports you've retired by the age of 40 and most coaches are older than that. I would say that's the reason it's common in sports, but that's the exception not the rule
lol I read "as many as 15+ direct reports" and thought it was hilariously low. My manager at google had like 50+ directs in 2010. And he was the best boss I've ever had.
Popular conception of what a manager is is wildly unambitious.
Weekly 1:1 is performative and useless. It's not what makes a good manager. What makes a good manager is:
... etc ...
If a manager is doing these things well I don't need a standing meeting at all. Or we can meet quarterly to check in.
Email is a thing.
Interesting. I'd define all of those tasks as the job of a team/tech lead, rather than a manager. I've worked at places where the same person did both roles, and it was not always a great mix.
If you think hiring, prioritizing, planning, and cross-team negotiation are all tasks of a tech lead and not a manager, then what is the job of an engineering manager in your opinion?
This is stupid and irrational. It's like seeing someone eat 100 cakes, and then assuming everyone can do it. And then getting diabetes afterwards.
It seems quite counterproductive to assume such a system would scale to everyone else, or that everyone else could possibly implement this. This is cowboy levels of human resource management, not careful engineering.
I mean I have 7 reports right now and we're a startup. And fully remote. And I'm still contributing as an IC too.
A manager who is also contributing code is almost an entirely different role than a manager who is not contributing code. Typically the former should not exist in a smaller org and in a larger org it makes sense to shift to the latter because there's enough non-code work to do that you might as well dedicate whole people to the task.
Different roles though.
> They're not going to get to spend enough time meeting each report's needs, not a chance.
What needs? If you squeeze people hard enough there are no needs anymore, only responsibilities and urgent+important backlogs that have no bottom.
Welcome to 2026.
If everything is high prio nothing is and if the backlog is always full it's not a problem if it fills up even more. If I am at the assembly line, I am doing my darnedest not to make it run faster. One can only sprint so long.
It is not a problem if you are an assembly line robot making motions. People, however, are not robots. They get held accountable by their higher-ups for delivering on these (often nonsensical) priorities, they risk getting fired when expectations are not met, and high uncertainty of faulty planning systems like that is extremely stressful in itself.
2 replies →