When competitors offer huge packages and devs feign disgust while asking directions
Description
White-background meme with two parts. Top text in black reads: "Manager: One of our competitor company is trying to pull all programmers from us with huge package..." followed by a line break and bold "Me:". Below, a cropped sitcom screenshot shows three people in a boutique; their faces are blurred for anonymity. The man in the center, wearing a light-blue T-shirt that says "Long Beach RACING COLLECTIBLES," looks intrigued while a blonde woman stands beside him. Large white subtitle at the bottom states, "Oh my god! That's disgusting. Where?" The humor plays on developers pretending to be appalled yet eagerly wanting the location of the generous salary package, a familiar scenario of talent poaching and retention battles in tech companies
Comments
6Comment deleted
Manager: The competitor’s dangling 2× salary to poach our devs. Me: “Morally outrageous… also, do they support blue-green resignations or is it a big-bang two-weeks cutover?”
The best retention strategy isn't a ping pong table or free snacks - it's realizing your senior engineers have already automated their LinkedIn response to recruiters with 'Current TC + 40% and we can talk.'
The classic developer response to hearing about competitor offers: expressing moral outrage while simultaneously opening LinkedIn in an incognito tab. It's the tech industry's version of 'I would never leave... but hypothetically, what's the TC breakdown, equity vesting schedule, and do they have unlimited PTO?' Every senior engineer knows the dance - you're not actively looking, but you're definitely passively listening, especially when 'huge package' could mean finally affording that San Francisco studio apartment or paying off those student loans from your CS degree that the bootcamp grads somehow avoided
Competitor wants to “git pull” us with a huge package; I’ll switch remotes for equity, not for an 800MB npm tarball with 1k transitive deps and a surprise crypto miner
If comp is a package, ours is a transitive dependency pinned to 2019 with known CVEs; theirs is a signed zero‑cliff LTS build - of course the branch will fast‑forward
PMs hype the rival's 'huge package' as innovation; we know it's just another gigabyte node_modules disaster waiting to vendor-lock your build