Career HR
Post #5535 · source on Telegram
The Senior Developer's Existential Dread: Becoming a Manager
Description
A meme capturing the moment a developer realizes their career is shifting towards management. The top text reads, 'When you are spending more time in meetings, Excel & JIRA and very less time doing coding..'. Below this is an image of the weary, long-haired anime character Alucard from the Castlevania series, looking down with a pained expression. The bottom caption articulates his inner monologue: '“Oh god. I’m turning into Manager”'. The humor stems from the relatable horror many senior engineers feel as their responsibilities transition from hands-on coding to administrative tasks. The progression into management is framed not as a promotion, but as an unfortunate transformation, a loss of the core identity of being a builder
More like this
More like this in Career HR →
Use J and K for navigation
Comments
7Comment deleted
The final stage of developer evolution is realizing your primary language is no longer Python, but Jira Query Language, and your most-used hotkey is 'Mute'
My IDE just started auto-completing “Let’s take this offline” - pretty sure I’ve been silently rebased onto the management branch
The scariest part isn't becoming a manager, it's realizing your code reviews now consist of "looks good to me" because you haven't touched the codebase in three sprints and you're just trusting the CI pipeline like it's your last connection to engineering
The classic IC-to-manager pipeline: first they take your terminal, then they give you a calendar. Before you know it, you're optimizing sprint velocity instead of Big O complexity, and your most complex algorithm is finding a meeting slot that works for six people across three timezones. The real tragedy? Your GitHub contribution graph goes from a beautiful green forest to a barren wasteland, while your Outlook calendar becomes a Tetris game you're losing
You know you’ve crossed to management when the only hot path you optimize is the meeting agenda - queuing theory still applies, but the orchestrator is Outlook and the merge conflicts live in JIRA, not Git
The moment you realize you’re management: your hot path is JIRA, your persistence layer is Excel, and your deployable is a slide deck
The ultimate context switch: from kernel panics to stakeholder syncs, with JIRA as the inescapable ISR