Soft Skills Engineering · Jamison Dance and Dave Smith

Episode 462: Supporting laid-off employee and how to rebuild culture after layoffs

·29 min·2 clips
Jameson and Dave compare layoffs to torture, revealing why managers can't make it a positive experience.
This episode of Soft Skills Engineering addresses two listener questions about layoffs in software engineering. Hosts Jameson Dance and Dave Smith, both experienced engineers, offer practical advice on navigating these difficult workplace situations. The first question comes from a manager who must lay off an employee and wants to know how to provide meaningful support. Dave shares his personal experience of being laid off, where his manager's offer of vague help felt unhelpful. Jameson recounts witnessing a firing where a manager promised a follow-up discussion that never happened. They reference a scene from the movie *Moneyball* where Brad Pitt's character advocates for delivering bad news directly and quickly. Both hosts agree the most concrete help a manager can offer is connecting the employee to specific job opportunities they know about. A key insight is that the laid-off person is often in a state of shock, making it a poor time to absorb logistical details. They emphasize the critical step of getting the employee's personal contact information before their work email is deactivated. The hosts suggest that offering to give resume feedback or be a reference can be appropriate, but warn against making promises you cannot keep. They analogize the manager's role to trying to reduce pain in an unavoidably terrible situation. The tone is conversational and darkly humorous, with the hosts using metaphors involving torture and referencing 9/11 in a comedic aside. Their style blends personal anecdotes with direct, pragmatic advice, acknowledging the emotional difficulty for all parties. The second question is from an engineer at a company that has conducted three rounds of layoffs, damaging morale and culture. The hosts apply a principle that companies with a history of layoffs are more likely to conduct more. They suggest that leadership is responsible for rebuilding culture by providing transparency, such as sharing business metrics like runway or burn rate. For an individual contributor, they recommend having a frank conversation with one's manager to understand how to become "layoff-proof." If deciding to leave, they acknowledge it's hard to job search while remaining fully engaged. They propose that if an employee typically works beyond 40 hours, it's fair to redirect that extra energy into a job search. A strategic move is to identify which teams or projects are most critical to the company's revenue and try to join them. The advice throughout is realistic, focusing on damage control and strategic positioning rather than easy solutions. This episode would resonate with engineering managers facing layoffs or individual contributors in unstable companies. Listeners seeking purely technical content or optimistic career guidance might find the subject matter too bleak.

As heard by us

Practical layoff-era advice, after a slow opening.

The episode starts with banter and patron shout-outs before settling into a listener question about three rounds of layoffs, low morale, and the choice to stay or leave.

Read the full review in PlayNext →

Why you'd press play

Three layoffs in, the question is less about slogans and more about what you do next.

Read the full recommendation in PlayNext →
Listen to the show on