Meme mocking stereotypical executive personas across engineering, sales, design, product
Description
The image contains the caption text: "Head of Engineering | Head of Sales Head of Design | Head of Product" centered above a 2×2 photo grid. Top-left (Head of Engineering): a casually-dressed person in a dark hoodie slouches in an ornate, gold-trimmed office, embodying the hoodie-wearing coder stereotype. Top-right (Head of Sales): a person in an open-collar white dress shirt sprawls confidently across a tan leather sofa with one arm over the backrest, a smartphone nearby, projecting slick sales bravado. Bottom-left (Head of Design): a person in a minimalist black turtleneck and blazer sits upright at a lavish table, channeling the Steve-Jobs-inspired design archetype. Bottom-right (Head of Product): a person in rolled-up sleeves leans forward, hand covering their face in visible frustration or exhaustion, hinting at product-management stress. The meme humorously contrasts wardrobe, posture, and mood to poke fun at how different leadership disciplines are perceived inside tech companies, resonating with developers familiar with cross-department stereotypes
Comments
7Comment deleted
QBR in one jpg: hoodie wants to rewrite it in Rust, open-collar just promised the enterprise tier next week, turtleneck insists on another 0.5 px of whitespace, and rolled-sleeves is face-palming because the roadmap now violates causality
The Head of Engineering explaining why the 6-month rewrite will take 18 months, while Sales already sold features from the 2025 roadmap, Design is protecting pixel-perfect mockups that ignore API constraints, and Product just realized they've been A/B testing on the same 5% of users for three quarters
Four VP titles, one payroll entry - the only org chart that's also a single point of failure
This perfectly captures the eternal truth: while Sales reclines on their quota-crushing throne and Product contemplates their next pivot, the Head of Engineering is simultaneously firefighting production incidents, explaining why 'just add AI' isn't a two-day sprint, defending architectural decisions to stakeholders who think microservices means 'small and therefore cheap,' and wondering why their team's burnout rate correlates suspiciously with the number of 'quick wins' promised by other departments. The real kicker? Engineering's the only role where 'everything working perfectly' is considered baseline expectations rather than remarkable achievement
Head of Product facepalms when Eng quotes O(n log n) delivery but Sales demands O(1) closes - classic CAP theorem for stakeholder consensus
Pre-seed org chart: all four “Head of” boxes are symlinks to the same PID - context-switching between Slack, CRM, Figma, and Jira is the whole scheduler
Seed-stage org chart: Engineering‑me is paging myself for a 2 a.m. rollback, Sales‑me just promised enterprise SSO, Design‑me wants a full rebrand, and Product‑me updated the roadmap to “yes.”