A Field Guide to Tech Company Stereotypes
Description
An infographic comic titled 'So, you want to work for a tech company?' by Mart Virkus for Toggl. The top half is a detailed isometric illustration of a chaotic tech office, featuring a 'FOUNTAIN OF GROWTH' filled with skulls labeled 'Qualified lead,' a kitchen with 'free snacks!,' and a 'NERF GUN WAR ZONE.' Various employees are depicted in their stereotypical roles. The bottom half, under the heading 'THE CAST:', provides humorous descriptions for eleven roles. For example, 'FRONT-END DEVS' are 'A.K.A. "not actual engineers" in backend vocab,' the 'BACKEND ENGINEER' is a 'watchful protector and a silent knight,' and the 'SERVERS' are 'The only ones working 24/7.' The comic satirizes the culture and archetypal roles within a typical startup, from the 'black wizard' SEO leadgen to the chained 'in-house designer,' offering a cynical but relatable overview for anyone in the industry
Comments
7Comment deleted
This chart is missing the most critical role: the Senior Engineer who's the sole owner of a legacy monolith, kept happy with a mechanical keyboard and a promise to one day rewrite it all in Rust
Notice how the servers are the only cast members working 24/7 - just like the senior engineer’s cronjob that’s kept the monolith alive since 2012 while the rest of the org fires Nerf darts and tweets GIFs about ‘shipping fast.’
The best part about being a senior engineer is explaining to the CEO why their "surprise product launch" idea needs more than the QA team we don't have to test the microservices we haven't finished migrating from the monolith we swore we'd deprecate three years ago
This comic perfectly captures the unspoken org chart: interns generate the traffic, customer support masters the art of diplomatic rejection, the CFO pretends fiscal responsibility is a team sport, and the CEO communicates exclusively in reaction GIFs. Meanwhile, backend engineers insist they're 'not actual engineers' (despite architecting distributed systems), DevOps operates in the shadows like Office Ninjas (because nobody notices infrastructure until it breaks), and frontend devs perpetually brace for design overhauls mid-sprint. The real MVPs? The sysadmins keeping everything running and the servers that never sleep - because in tech, the only constant is that production issues don't respect work-life balance
Conway’s Law in one poster: the kitchen is shared mutable state, the Nerf zone provides eventual consistency, and the only component with an SLA is the server closet
Founder's COBOL monolith: the ultimate unrefactorable service that's been 'temporarily' critical since the Eisenhower administration
Accurate org diagram: the only node with a real SLO is “servers,” while everyone else optimizes OKRs for Nerf accuracy and the CTO spends the error budget keeping the Fountain of Growth from DDoSing the monolith