
Episode 436: Paralyzed by checkboxes and I'm on a "must keep happy" list
About this episode
In this episode, Dave and Jamison answer these questions:
-
Marcus Zackerberg asks,
I work at a megacorp whose recent focus has been on reliability. The company already has mature SLO coverage outage response standards, but my org has taken it to the extreme this year. For example…
There is now a dashboard of “service health” that is reviewed by engineering leadership. In it, services are marked “unhealthy” permanently upon a failing check (think HTTP /health). To return to a “healthy” state, one must manually explain the failure with an entry in a spreadsheet, which must be reviewed and signed off.
Increasingly I feel this has the opposite effect, discouraging nuanced work to improve reliability and instead becoming “checkbox driven development”, as well as impacting our ability to ship on our existing roadmap items. Additionally, our tech lead is fairly junior and frequently fails to communicate the org’s expectations to the team, leading to us being under the gun of the reliability dashboard often.
Any advice on how to make the best of this situation?
-
Hi Guys! I’m a senior engineer at a mid sized software company. The company has had a couple of high level departures recently, and during that process I’ve come into the knowledge that my name is one of a handful on a list of “engineers to keep happy”. I feel like this information should be of use to me, but I’m unsure on how I should leverage it.
On one hand it’s nice to know I’m valued, but I think I’d rather be explicitly told that or better yet, receive dollars in lieu of praise. I’m also at the point in my career where I’m looking for staff roles, and the topic of promotion has come up several times with my manager. He supports me (and I believe him), but we agree that it would be difficult to make the case to the business.
What do I do with this new knowledge, and is there a way to benefit from it without accidentally triggering a preemptive search for my own replacement?
Get every episode summarized
Each time Soft Skills Engineering publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from Soft Skills Engineering

Episode 529: Zoom calls on my open floor plan and laconic staff engineer
Soft Skills Engineering

Episode 528: Sleepy family software business and leaving after an acquisition
Soft Skills Engineering

Episode 527: I lost my job after 10 years and am I too old to switch to a securi...
Soft Skills Engineering

Episode 526: Why can't I get promoted so quickly after my last promotion and I g...
Soft Skills Engineering