Soft Skills Engineering · Jamison Dance and Dave Smith

Episode 457: How do I get off the on-call rotation and "big tech" == "big leagues"?

·27 min·2 clips
A senior engineer reveals how on-call caused explosive diarrhea and 24 energy drinks in five days.
This episode of Soft Skills Engineering features hosts Dave Smith and Jameson Dance answering listener questions about software development careers. They address a senior engineer's brutal on-call experience and a developer's curiosity about talent at big tech firms. An anonymous senior engineer at a big tech company describes a seven-day on-call shift requiring 12 hours of manual dashboard monitoring daily, aligned with Pacific Time despite being in the EU. The listener reports consuming 24 energy drinks, suffering from sleep deprivation and health issues, and straining their family life during this rotation. Dave and Jameson note a staff engineer on the team avoids the rotation, suggesting one escape is becoming "too essential" for on-call duty. They propose discussing shorter rotation cycles or schedule adjustments with a manager as potential solutions. The hosts recommend the engineer rally teammates to advocate for technical improvements to the "fuzzy" alerting system. Jameson speculates the engineer's remote status might make them hesitant to complain, fearing it could jeopardize their position. Dave points out that such an intense on-call schedule likely leads to human error, providing a business case for change. The second question, from "Bebop," asks if the average developer at a big tech company is more skilled than one at a large non-technology firm. Jameson believes, based on gut feeling and hiring perceptions, that big tech developers are generally better on average. Dave agrees but emphasizes there is high variance at all companies, and great engineers exist everywhere. The hosts discuss how big tech offers exposure to solved, large-scale problems, while startups provide broader ownership and unsolved challenges. They conclude that a career can benefit from experiences in both environments. The tone is conversational, humorous, and empathetic, blending practical advice with lighthearted banter. This episode would appeal to software engineers seeking career advice or commiseration about difficult workplace practices. Listeners looking for highly technical deep dives or those averse to casual, anecdotal discussions might find it less engaging.
Listen to the show on