The other day, I saw this meme in one of the Slack channels I’m in:

I went from chuckle to “Oh, shit, is this me?” in a fraction of a second—a scene better described with the :lolsob: emoji:

The meme was funny, and it also got me reflecting about the Engineering Manager’s expectations during the ZIRP era and how those expectations shifted almost overnight.
I became an Engineering Manager at the beginning of the pandemic, and I still remember very vividly how everything—from the courses to the conversations—was 100% focused on people management. I was being implicitly trained to become a coach. My performance was measured by the output of the team I was leading, and although staying technical was encouraged, it was rarely brought up during performance reviews—at least in my case. It was one of the main reasons I’ve heard why many ICs didn’t even consider the management path—it was a people management role, and they didn’t want to stop coding. This setup helped me to become a decent people manager. It also gave me the space to explore and improve complementary skills in product management and business strategy.
Fast forward to today, the post-ZIRP era. An era marked by constant layoffs and the great flattening. Swoosh! That’s the sound of the pendulum swinging all the way to the opposite extreme of EM expectations—the speed of the swing is probably a testament to how high the pendulum was during ZIRP. Now managers are expected to lead bigger teams and stay hands-on, almost like another IC on the team—judged by what you ship, not just how you lead. Coaching is nearly a pejorative term. And ICs don’t want to become managers for a different reason: it feels like too much.
I look forward to the day when the pendulum settles and we find balance—the kind that values both code and coaching, velocity and vision. People-first leadership made me a better manager, and it also shaped how I approach product, strategy, and teamwork. We’re building faster teams—but are we building better ones?


