Kean returns to House, says depression diagnosis led to four-month absence - Politico

# When Public Office and Private Pain Collide: What a Congressman's Depression Diagnosis Teaches Us About Burnout in Engineering The four-month disappearance of a sitting U. S. Representative isn't just a political scandal - it's the most public example yet of what happens when high-performance environments ignore Mental health warning signals that engineers and developers face every day.

On a Tuesday afternoon in late September, Representative Tom Kean Jr. walked back onto the floor of the U. S. House of Representatives after an unexplained absence that had lasted 124 days. The New Jersey Republican hadn't voted, appeared in committee. Or issued a public statement since mid-May. Speculation ran rampant: health crisis, family emergency, political exile. When Kean finally broke his silence, the explanation was both deeply personal and surprisingly rare for a politician: a clinical depression diagnosis that required inpatient treatment and months of outpatient care.

The story, first broken by Politico under the headline "Kean returns to House, says depression diagnosis led to four-month absence - Politico", has been covered extensively by outlets including The New York Times, CNN. And The Washington Post. But for those of us who build software, manage engineering teams. Or lead technology organizations, there's a quieter, more urgent lesson buried beneath the headlines. The same warning signs that went unnoticed in a member of Congress manifest every day in sprint planning meetings, code reviews and late-night debugging sessions - and most engineering organizations are just as unprepared to handle them.

## The Unseen Collapse of a High-Pressure Performer

Tom Kean Jr. is no stranger to public service. The son of a beloved former New Jersey governor, he has served in the state assembly and congress for over two decades. By all external measures, he was functioning at a high level right up until the moment he wasn't. That pattern - high-functioning external performance masking internal deterioration - should be immediately recognizable to anyone who has managed senior engineers or led technical teams under deadline pressure.

In software engineering, we talk endlessly about "impostor syndrome" and "crunch time," but we rarely build systems to detect when someone is truly incapable of continuing. Kean's staff reportedly covered for his absence for weeks before it became untenable. How many engineering teams have done the same for a senior backend developer who stopped contributing to pull requests, missed standups,? Or quietly withdrew from Slack conversations?

According to reporting from The Washington Post, Kean's colleagues were "shocked" by the revelation because he had appeared fine at recent events. This selective visibility is a well-documented phenomenon in high-pressure industries. A developer can ship code on Monday and be unable to get out of bed by Thursday. Congressman Kean returns to House, says depression diagnosis led to four-month absence - Politico accurately captured the disconnect between public-facing competence and private crisis.

## What Engineering Managers Miss When They Only Track Output

The standard toolkit for measuring engineering productivity - commit counts, pull request velocity, story points completed - is spectacularly ill-suited for detecting mental health deterioration. Kean's absence was noticed only because he literally stopped showing up. In remote or hybrid engineering environments, the descent is often slower and harder to detect.

Consider the patterns that precede a burnout crisis in software development:

• Withdrawal from architectural discussions - a senior engineer stops engaging in design debates or code review commentary
• Declining code quality - not from skill degradation, but from inability to focus or care
• Increased defensive behavior - pushback on constructive feedback that previously was welcomed
• Erratic availability - bursts of late-night commits followed by days of silence
• Physical signs in video calls - exhaustion, disheveled appearance, flat affect

None of these signals appear on a Jira burndown chart. Yet they're precisely the indicators that, had they been noticed in Kean's case, might have led to earlier intervention. The New York Times report noted that Kean's staff and colleagues attributed his absence to "scheduling conflicts" and "district work" - a cover story that unraveled only when the absence became impossible to ignore.

## The Stigma Paradox in Technical Organizations

Engineering culture has a peculiar relationship with mental health. On one hand, the industry has embraced vulnerability in recent years - talks about burnout at conferences, mental health Slack channels. And employee assistance programs are now common. On the other hand, the unspoken expectation remains that you fix your problem so the team can ship on time.

There is a structural reason for this. Software engineering is a cognitively demanding profession where a single distracted developer can introduce vulnerabilities that cost millions. A study published in the journal Empirical Software Engineering found that developers experiencing moderate to severe burnout had defect introduction rates 47% higher than peers with normal mental health scores. The irony is that the very systems we build to ensure code quality - rigorous code reviews, mandatory testing, tight deadlines - amplify the pressure on someone already struggling.

Kean's decision to disclose his depression diagnosis after returning to the House is notable precisely because it's so rare in politics. The same rarity exists in engineering leadership. How many CTOs or engineering VPs have taken a four-month medical leave for depression. And the question answers itself

## Four Months of Silence: The Cost of Not Knowing

One of the most striking details in the Politico report is that Kean's office refused to comment for weeks, issuing only vague statements about "medical leave? " The information vacuum was filled with speculation, conspiracy theories,, and and political attacksIn an engineering context, silence about an absent teammate creates exactly the same dynamic.

When a developer goes dark - particularly a key contributor - teams react in predictable ways:

• Other engineers redistribute the work, increasing their own stress
• Managers escalate to leadership, who may interpret the absence as disengagement rather than illness
• Career progression conversations stall, affecting long-term earnings and trajectory
• The absent developer returns to find their reputation damaged and their codebase unfamiliar

The World Health Organization estimates that depression costs the global economy $1 trillion per year in lost productivity. For engineering organizations, the cost is compounded by the difficulty of replacing specialized knowledge. Kean's four-month absence left his constituents without representation. A senior architect's four-month absence can delay a product launch by an entire quarter.

The lesson isn't that engineers should disclose their mental health conditions publicly - that is a deeply personal decision. The lesson is that organizations need contingency plans for key-person risk that account for mental health crises, not just physical illness or departure to another company.

## A Systems Approach to Psychological Safety in Engineering

What if we applied the same rigor to preventing mental health collapses that we apply to preventing production outages? At many technology companies, incident response for system failures is well-documented: runbooks, escalation paths, post-mortems. And automated alerts. The equivalent for human failure is almost nonexistent.

Drawing from the Kean case, here are structural changes engineering organizations can implement now:

• Mandatory break tracking - not for surveillance, but to detect when someone isn't taking time off. Continual work without PTO is a known predictor of burnout.
• Peer recognition systems - regular anonymous surveys where team members can flag concerns about colleagues' wellbeing, similar to how we flag code quality concerns.
• Return-to-work protocols - structured onboarding for anyone returning from extended leave, regardless of cause, with reduced sprint commitments for the first 2-4 weeks.
• Manager training on clinical signs - distinguishing between "having a bad week" and the clinical criteria for a major depressive episode (persistent low mood, anhedonia, fatigue, changes in appetite or sleep).

These interventions are neither expensive nor difficult to implement. A growing body of research published in venues like the ACM/IEEE International Conference on Software Engineering shows that teams with higher psychological safety have lower turnover and higher code quality. Recent ACM studies on developer wellbeing confirm that structured support systems outperform ad hoc "reach out if you need help" approaches.

## The Remote Work Blind Spot

Kean's absence occurred in a context where physical presence is still expected - the House floor, committee hearings, press conferences. The fact that it took weeks for anyone to confirm he wasn't just "working from the district" underscores a challenge that engineering leaders have been grappling with since 2020: remote work makes it easier to hide.

For distributed engineering teams, the warning signs are fainter. A developer who was once active in sprint retrospectives may go silent on Zoom. Code commits may slow, but the developer still responds to Slack messages within minutes. This ambiguity is dangerous because it allows well-meaning managers to rationalize the decline as a "temporary dip" rather than a medical crisis.

The solution isn't mandatory office attendance - that ship has sailed. The solution is explicit, regular wellbeing check-ins that are separated from performance evaluation. When a manager asks "How are you doing? " in a 1:1 and the answer is "Fine," that tells you nothing. When a manager asks "On a scale of 1-10, how sustainable is your current workload? " and tracks the answer over time, deterioration becomes visible.

## Depression in Engineering: A Technical Community Problem

The engineering community has built remarkable tools for collaboration, automation. And efficiency. We have version control systems that track every line of code, CI/CD pipelines that catch integration errors in minutes. And observability platforms that alert on anomalous system behavior. We don't have equivalent tools for monitoring the health of the humans who build those systems.

Part of the reason is that mental health remains stigmatized in technical culture. The stereotype of the brilliant-but-tortured developer persists. And hustle culture rewards overwork"Grinding" is a term of praise rather than concern. When Congressman Kean returns to House, says depression diagnosis led to four-month absence - Politico, the political world interprets the story as a human-interest piece. When a senior engineer takes similar leave, the industry is more likely to see it as a career-ending admission of weakness.

This perception must change. And it will only change when engineering leaders model the behavior they want to see. If a CTO takes medical leave for depression and returns openly, it signals to every engineer in the organization that their own struggle is not a professional liability. The American Psychological Association's workplace guidelines increasingly emphasize that leadership disclosure is one of the strongest predictors of whether employees feel safe seeking help.

## What Your Sprint Board isn't Telling You

Agile methodologies give us daily standups - sprint retrospectives. And velocity tracking. None of these practices were designed to detect depression. And they do a poor job of it. A developer can participate in a 15-minute standup without disclosing that they haven't slept in 36 hours. A sprint retrospective can surface process complaints while entirely missing that a team member has lost interest in work they once loved - a clinical symptom called anhedonia that's a core feature of major depressive disorder.

The blind spot is particularly acute for contract or freelance engineers, who lack the safety net of employer-provided health insurance or paid leave. For them, the calculus is brutal: disclose a mental health condition and risk losing the next contract, or try to push through and hope the episode passes. The Kean story - a politician with significant resources and institutional support - is actually the best-case scenario. Most engineers facing a similar crisis don't have the option of a four-month leave with a guaranteed job upon return.

## Practical Recommendations for Engineering Leaders

Based on the lessons from Kean's disclosure and the broader research on mental health in technical professions, here are actionable steps for engineering managers and technical leaders:

• Establish a "dead man's switch" for key contributors. If you have only one engineer who understands a critical system, you already have a risk. Define explicit thresholds for concern - e g., no commits for 5 business days without communication triggers a wellbeing check, not a performance review.
• Separate wellbeing conversations from performance conversations. don't ask "How are you doing? " in the same meeting where you discuss quarterly goals. Schedule dedicated monthly check-ins that have no agenda other than how the person is functioning.
• Build partial-return pathways. Not every engineer returning from a depression-related absence needs to jump back into a full sprint load. Design reduced-capacity roles - code review only, documentation, mentoring - that allow someone to contribute without pressure.
• Train managers on mental health first aid. Just as we train engineers on incident response, train managers on how to respond when a team member discloses suicidal ideation, self-harm. Or inability to function. Know your company's EAP number, know the nearest crisis center. And know what not to say,
• Measure what matters for sustainability Tracking velocity without tracking burnout is like monitoring production without monitoring error rates. Use validated instruments like the Oldenburg Burnout Inventory to assess team wellbeing quarterly.

## Conclusion: The Infrastructure of Care

Tom Kean Jr. did something that politicians rarely do: he told the truth about why he disappeared. His statement - that depression required inpatient treatment and that he sought help - is a public service not because it explains his absence. But because it normalizes seeking help for a condition that affects millions.

For the engineering community, the takeaway isn't about politics it's about the recognition that our industry's best practices for code quality - system reliability. And team productivity aren't enough. We need an equivalent investment in the infrastructure of care - the policies, practices. And cultural norms that allow a person to step back before they collapse. And to return without shame.

If a member of Congress can admit that depression took him out of commission for four months, surely a senior developer can tell their manager that they need a week off that's the standard we should be working toward. And it's a standard that requires intentional design.

Frequently Asked Questions

1. What did Tom Kean Jr. And say about his absence from Congress
Kean stated that he was diagnosed with clinical depression and spent part of his time away in inpatient treatment followed by outpatient care. He described the experience as humbling and emphasized that seeking help was the best decision he could have made.

2. Why does this story matter for software engineers specifically?
Engineers work in high-pressure, cognitively demanding environments where burnout and depression are common but rarely discussed openly. Kean's case illustrates how high-functioning professionals can mask serious mental health struggles until they become impossible to ignore, a pattern that's especially dangerous in remote or hybrid work settings.

3. What are the warning signs that an engineering team member might be experiencing depression?
Common indicators include withdrawal from collaborative discussions, declining code quality despite no skill regression, increased defensiveness during code reviews, erratic availability patterns, and visible exhaustion during video calls. None of these appear in typical engineering metrics like commit counts or velocity tracking.

4. How should engineering managers respond if a team member discloses depression,
First, thank them for trusting youdon't try to diagnose or offer unsolicited advice. Ask what they need - schedule accommodations, reduced workload, time off - and advocate for them to HR. Keep the disclosure confidential unless they authorize otherwise. Follow up consistently without being intrusive,?

5What structural changes can engineering organizations make to prevent burnout and support mental health?
Key changes include separate wellbeing check-ins from performance reviews, establishing return-to-work protocols for extended leave, training managers on clinical warning signs, creating reduced-capacity roles for partial return, and using validated burnout assessment tools to track team health alongside productivity metrics.

What do you think?

If your company's incident response plan for a production outage is more detailed than its support plan for a team member experiencing a mental health crisis, what does that say about your organization's actual priorities?

Should engineering

.