CorporateCulture
Post #6519 · source on Telegram
When managers demand: 'So, what would you say you actually do?'
Description
The image shows a drab, gray-walled cubicle farm straight out of the 1990s. Two people with blurred faces sit side-by-side at a conference table: on the left, a younger person in a light-gray hoodie clutching a pen and notepad; on the right, an older, suit-and-tie manager with folded hands. Fluorescent office lights and endless cubicles stretch out behind them. Bold white subtitle text at the bottom reads, "What would you say you do here?" The scene parodies a performance-review interview - famously from the movie Office Space - capturing the corporate ritual where management asks engineers to justify intangible work like refactoring, code reviews, or keeping the build green, a situation every seasoned developer can relate to
More like this
More like this in CorporateCulture →
Use J and K for navigation
Comments
9Comment deleted
I turn Sales’ vaporware into a cloud-native Rube Goldberg machine that keeps the 40-year-old COBOL alive behind a GraphQL façade and only pages me during executive off-sites - so basically “nothing.”
After 20 years in tech, I've realized the hardest distributed systems problem isn't CAP theorem or consensus algorithms - it's achieving consensus on what anyone's job title actually means when 'Staff Engineer' at one company debugs CSS and at another designs planetary-scale infrastructure
Every senior engineer has faced this question at least once - usually right after spending three months refactoring a critical system that now 'just works' so well that nobody notices it anymore. The irony is that the best engineering work is often invisible: the incident that never happened, the outage that was prevented, the technical debt that was quietly eliminated. Try explaining to non-technical stakeholders that you spent Q3 reducing deployment time from 4 hours to 12 minutes while improving reliability from three-nines to five-nines - they'll still ask 'but what features did you ship?' The most valuable contributions are often the hardest to articulate in a performance review, which is why experienced engineers learn to keep a 'brag document' of their architectural decisions, system improvements, and the fires they prevented before anyone knew there was smoke
I balance CAP theorem impossibilities while herding microservices through zero-downtime deploys - coffee-fueled
I run the alignment microservice: convert executive OKRs into Jira epics and quarterly slide decks with strong eventual consistency and zero impact on p99
What do I do here? I’m the API between Product and Git: validate “can we just” payloads, rate-limit them with ADRs, and return “it depends” with a 429
Who? Comment deleted
Musk's Teen Titans Comment deleted
I would say they do something related to AI because the hands look like they were poorly made 😁 Comment deleted