Chapter 15: The Loneliest Job in the Startup
Let everything happen to you Beauty and terror Just keep going No feeling is final
The Book of Hours (trans. Joanna Macy & Anita Barrows)
A CTO identified only as Lawrence, in a case study published by CTO Craft, describes the experience that most CTO burnout accounts circle around but few articulate this precisely: "I just remember feeling like I never wanted to code or work with code again. In fact, I didn’t want to even work with people who worked with code. The very idea of getting involved in that kind of thing made my blood run cold."[1]
Lawrence had been a self-employed CTO for several years. The burnout came gradually — not as a dramatic collapse but as an oscillation between withdrawal and combativeness. "I’d gone from giving my all, to becoming so withdrawn on some days that everything was a challenge — I had no energy or mental capacity to do anything. On other days, the simplest things would annoy me and even basic requests from colleagues had me feeling combative."[1] When the burnout was finally undeniable, Lawrence did not seek help. "Being self-employed, I lacked the support and assistance I needed. But if I’m honest, I never actively asked for help either. I didn’t know where to start and it felt like yet another insurmountable task when at that point, I couldn’t even manage to write a line of code without exhausting myself."[1]
Lawrence’s story is not unusual. It is the norm. The LeadDev Engineering Leadership Report 2025, surveying 617 engineering leaders and developers, found that 22% were at critical burnout levels and 46% were at moderate-to-critical levels — using the Maslach Burnout Inventory, the standard psychometric instrument for measuring occupational burnout.[2] Michael Freeman, a psychiatrist and researcher at UC Berkeley and UCSF, found that 49% of entrepreneurs report at least one lifetime mental health condition, with depression at 30% — roughly three to four times the rate in the general population. Seventy-two percent of entrepreneurs were directly or indirectly affected by mental health issues.[3]
This chapter argues that CTO burnout is not a personal failing. It is a structural feature of the role — predictable, preventable, and compounded by the financial vulnerability that most startup CTOs either do not understand or do not address. Emotional survival and financial survival are the same conversation, because the CTO who is burning out while being underpaid is experiencing two crises simultaneously, each making the other worse.
The Isolation Is Structural
The CTO role is isolating in ways that other executive roles are not. A CTO Craft survey of 100 tech leaders found that 97% had felt lonely as a leader, with 63% feeling lonely in their current role "sometimes" and 19% feeling lonely "all of the time."[4] This exceeds the broader C-suite benchmark: RHR International found that 50% of CEOs report loneliness, with 61% saying it hinders their performance.[5]
The CTO’s isolation has specific structural causes. Stephan Schmidt, who has coached more than 80 CTOs, describes the dynamic: "You can’t share your real problems. Tell your team you’re worried about the architecture? Now they’re worried too. Tell the CEO you’re not sure you can deliver? That’s a career conversation. Tell your spouse about the production incident at 2am? Their eyes glaze over. The problems you carry are yours alone."[6]
Schmidt provides a personal example that illustrates the weight. His predecessor had woven a third-party technology throughout the system. One day, a salesperson from that vendor informed him that the licensing costs would increase from $80,000 to $800,000 per year — threatening the existence of a company with hundreds of employees. "I never felt so lonely," Schmidt writes.[6] The CTO is often the only person in the company who understands both the technical reality and the business consequence of a technical problem. That understanding is the job. The loneliness of carrying it without anyone to share it with is the price.
The role sits at a junction that produces isolation from every direction. Schmidt’s formulation: "Every executive faces some isolation. But CTOs carry extra weight. You speak a different language. Half your job is translation. Explaining technical reality to people who don’t want to hear it. Explaining business constraints to engineers who think product is the enemy. You’re the bridge. Bridges are lonely places."[6]
A 2024 Harvard Business Review study of more than 100 CEOs found that executive loneliness stems from "responsibility and decision authority rather than social isolation."[7] The CTO is not lonely because they lack colleagues. They are lonely because the decisions they carry — about architecture, about technical debt, about team composition, about what is possible and what is not — are decisions that no one else in the company is qualified to share. Twenty-five percent of the CEOs in that study reported frequent loneliness, and more than half described significant episodic loneliness — yet most minimised it because they felt pressure to appear composed.[7]
Jerry Colonna, a former venture capitalist who became an executive coach after experiencing his own crisis, built Reboot.io around the premise that this isolation is the central challenge of startup leadership. His signature question — "How have I been complicit in creating the conditions I say I don’t want?" — is designed to surface the patterns that leaders cannot see from inside the isolation.[8] The CTO who never steps back to ask why the role feels unsustainable will continue to sustain the conditions that are causing it.
The isolation is also self-reinforcing. The CTO who feels that they cannot share concerns about system fragility begins to carry the knowledge alone. The weight of that knowledge produces stress. The stress produces withdrawal. The withdrawal deepens the isolation. Kacper Brzozowski, CTO of ResumeLab, describes the specific moment he recognised the pattern: "My first signs of burnout appeared on the horizon when I started to feel apathy toward my work. Specifically, I caught myself feeling depersonalization and cynicism for my day-to-day duties as a CTO."[9] The apathy was not a character flaw. It was the second dimension of the Maslach Burnout Inventory — depersonalisation — manifesting as the predictable consequence of chronic isolation under pressure.
|
AUTHOR: Your experience of isolation at CorralData — the specific form it takes. Is it the "bridge" dynamic Schmidt describes? Is there a specific technical concern you carry that you cannot fully share with the team or the CEO? The reader needs to see isolation named in a specific, current context. |
What Burnout Actually Is
The World Health Organization, in its 2019 International Classification of Diseases, defined burnout as "a syndrome conceptualized as resulting from chronic workplace stress that has not been successfully managed," characterised by three dimensions: energy depletion or exhaustion, increased mental distance from one’s job (cynicism or negativism), and reduced professional efficacy.[10] The WHO is explicit: burnout is not a medical condition. It is an occupational phenomenon — the result of a mismatch between the person and the job, not a pathology of the person.
Christina Maslach, who developed the Maslach Burnout Inventory in 1981 and has spent four decades studying burnout, identifies six areas of work life where mismatches drive the syndrome: workload, control, reward, community, fairness, and values.[11] The CTO role is remarkable in that it produces mismatches across all six simultaneously. The workload is infinite — technology never stops evolving, the backlog never shrinks, the team always needs more. Control is ambiguous — the CTO is responsible for technical outcomes but often lacks authority over the business decisions that constrain those outcomes. Reward is delayed — equity is probabilistic and illiquid, salary is below market, and the most important contributions (architectural judgment, risk prevention, team development) are invisible to the people who determine compensation. Community is thin — as the isolation section described. Fairness is uneven — the CTO who prevents a crisis gets no credit, while the CTO who fixes one publicly gets a round of applause. And values are frequently in tension — the CTO who cares about code quality and engineering culture is working inside a system that rewards shipping speed and revenue growth.
Joel Gascoigne, co-founder and CEO of Buffer, provides the most detailed firsthand account of what these mismatches produce. "This is how I’d describe my experience of burnout: I lost motivation. I just didn’t care. I knew I cared deeply, but I had nothing left. I couldn’t get up in the morning. I felt very sensitive and emotional. It was like anything could set me off."[12] Gascoigne identifies a mechanism that is specific to founders and founding CTOs: adrenaline masking. "While I was exercising and keeping myself in good shape, as well as feeling optimistic about the future of Buffer, it was adrenaline that was carrying me forward. By the spring of 2017, the company felt much more stable. As soon as the adrenaline subsided my body, and mind, suddenly realized everything I’d gone through."[12]
The implication for the startup CTO: burnout often arrives not during the crisis but after it. The sprint to launch, the firefighting phase, the fundraise — these sustain the CTO through adrenaline. When the company stabilises, the CTO’s body catches up. The burnout that was accumulating under the surface becomes undeniable precisely when the external pressure eases.
A 2021 meta-analysis of 17 studies, comparing 730 burnout patients to 649 controls, found that burnout impairs the specific cognitive functions the CTO role depends on. Executive function — the ability to plan, prioritise, and make complex decisions — showed a moderate deficit. Attention and processing speed were similarly affected. Most alarmingly, the researchers found that "cognitive difficulties can persist several years after treatment despite clinical improvement."[13] The CTO who pushes through burnout is not just suffering emotionally. They are degrading the decision-making capability that justifies their role.
Rand Fishkin, founder of Moz and SparkToro, describes the moment when isolation and burnout converged at a CEO summit organised by Brad Feld: "Near the start of the session, Brad asked all the CEOs in the room to raise their hand if they had experienced severe anxiety, depression, or other emotional or mental disorders during their tenure as CEO. Every hand in the room went up, save two. At that moment, a sense of relief washed over me, so powerful I almost cried in my chair. I thought I was alone."[14]
Fishkin’s hand-raising moment — the room full of CEOs who had all experienced severe anxiety or depression — is the emotional proof of the statistical reality. But the nature of that anxiety shifts with the market, and the CTO who does not recognise which kind of burnout they are experiencing will apply the wrong remedy.
Boom conditions produce burnout through overwork and impossible expectations. The team is hiring faster than it can absorb, every quarter the targets increase, and the CTO is expected to scale the engineering organisation while shipping product at the same pace — a contradiction that Ben Horowitz’s "peacetime CEO" framework identifies as the burden of abundance. The peacetime leader "must maximise and broaden the current opportunity," but the broadening never stops, and the CTO’s sense of accomplishment recedes with each expanded scope.[15] Bust conditions produce a different devastation — not overwork but dread and moral injury. The CTO who hired aggressively during the boom now conducts layoffs, cuts projects they championed, and watches their equity become worthless while maintaining morale for the survivors. Andy Dunn, writing in Fortune during the 2023–2024 downturn, captures the impossible performance: "Some days I publicly project hope, usually when I am genuinely feeling optimistic. Other days I privately suffer the reality of things going nowhere, and then attempt to share just the right amount of the difficulty with the team."[16] The Sifted 2025 founder survey confirms the scale: 54% of founders experienced burnout in the preceding twelve months, with 75% reporting anxiety.[17] And uncertainty — the 2025–2026 mode of tariffs, geopolitical fragmentation, and AI disruption — produces burnout through decision fatigue. Every choice feels high-stakes because the ground is shifting, and the information needed to make good decisions remains unavailable. Kelly Vaughn, a senior engineering manager at Zapier, describes the organisational consequence: managers "feel like they’re juggling too many people and too many fires," and because "people don’t raise red flags — the flags get buried," the CTO operates in an information vacuum while making constant high-stakes calls.[18]
Jerry Colonna names the mechanism that connects all three: "Founders think burnout comes from working too hard. It doesn’t. It comes from tying your identity to your company’s success."[8] During a boom, that identity fusion means the CTO can never feel they have done enough, because the targets keep rising. During a bust, it means the company’s decline is experienced as personal failure. During uncertainty, it means the CTO cannot rest because every decision feels existential. The intervention differs by market condition — boom burnout responds to boundary-setting and scope discipline; bust burnout requires processing grief and moral injury; uncertainty burnout demands decision-load reduction — but the underlying vulnerability is the same. The CTO who has fused their identity with the company’s trajectory will burn out in any market. The question is only which flavour of burnout arrives first.
|
AUTHOR: Which market condition has CorralData operated in during your tenure — and which burnout pattern, if any, have you felt? The reader at a healthcare startup in 2026 is likely experiencing uncertainty burnout (AI disruption, regulatory shifts, funding market instability) and needs to see it named. |
Building Support Before You Need It
Kellan Elliott-McCrea, former CTO of Etsy, published a survival guide for senior tech managers that remains the most practical document on the subject. His framework has three components: a therapist or coach, a peer group, and the self-awareness to use both before crisis forces the issue.[19]
On the need for a therapist or coach, Elliott-McCrea is direct: "Management brings shit up. It’s a psychological job. Your relationship with your parents is unfortunately relevant. Knowing what triggers you, and why, and having someone you trust to talk through it is the only way to do the job well."[19] This is not self-help rhetoric. Executive coaching shows robust return on investment across multiple studies: the International Coaching Federation and PwC’s 2024 global study found that 87% of coaching clients reported positive ROI, with meta-analyses across the industry consistently finding three to seven times return on investment.[20]
On the peer group, Elliott-McCrea provides the specific format: "Find some folks in your industry, with similar job scope. Get together regularly. Talk shop. But the real shop. The stuff you don’t talk about when the people you work for or the people who work for you are around. This should be off the record. This isn’t a meet up. Start with a small group. Intimacy is the name of the game."[19] His description of what the peer group reveals is the passage that most CTOs cite when they discover it: "What you’ll find out is everything is fucked up everywhere. And you feel better about your own job. Your problems suck, but boy are you super glad you don’t have their problems. Perspective is the thin line between a challenging but manageable problem, and chittering balled up in the corner."[19]
The peer infrastructure now exists at scale. CTO Craft, founded by Andy Skipper in 2017 after he observed "a lot of burnout, a lot of anxiety, a lot of isolation, a lot of loneliness in CTOs," has grown to more than 18,000 members, with a curated Slack community of 8,000 and structured Mentoring Circles — groups of up to eight tech leaders meeting monthly for 90 minutes, led by an experienced CTO coach.[21] The Rands Leadership Slack, created by Michael Lopp (who led engineering at Apple, Slack, and Palantir), has more than 35,000 members — all people leaders supporting each other across the industry.[22] Jerry Colonna’s Reboot.io runs intensive leadership bootcamps — five-day retreats for cohorts of 15 leaders — built on a model that combines practical leadership skills with what Colonna calls "radical self-inquiry."[8]
Schmidt, who advocates the same peer-group approach, adds the warning about what does not work: "Pretending everything’s fine. Working harder. Drinking. Isolation as coping strategy. I’ve tried most of these. None of them helped."[6]
The common thread across every source in the research is timing. The support infrastructure must be built before the CTO needs it. Elliott-McCrea’s framing: "Put your own oxygen mask on first."[19] The CTO who waits until they are in crisis to find a coach, build a peer group, or join a community will discover that the executive function impairment caused by burnout makes it harder to do exactly the things that would help. The time to build the support system is when the CTO does not think they need it.
The format matters. Schmidt, who has seen dozens of peer groups work and fail, identifies the characteristics of the ones that work: "Peer groups work. Other CTOs going through the same thing. No need to explain the context. No risk to your reputation. Just people who get it. The CTO groups I’ve seen work best are small — five to eight people — regular, meeting monthly, and confidential."[6] The confidentiality is not a detail. It is the foundation. The CTO who cannot speak freely about the real problems — the failing system, the underperforming engineer, the CEO who does not understand the technical constraints — will get nothing from the group except another obligation on their calendar.
The coaching component serves a different function from the peer group. The peer group provides perspective — the reassurance that everything is broken everywhere, and that the CTO’s problems, while serious, are not uniquely unsolvable. The coach provides reflection — the ability to see patterns in one’s own behaviour that are invisible from the inside. Elliott-McCrea is candid about why the psychological dimension matters: "Your relationship with your parents is unfortunately relevant."[19] The CTO who reacts to criticism from the CEO with defensive withdrawal, or who responds to an engineer’s mistake with disproportionate anger, is bringing patterns from outside the role into the role. A coach can surface those patterns. A peer group cannot — and should not try.
|
AUTHOR: Your support infrastructure — do you have a peer group, a coach, a community? If so, how did you find them and what do they provide? If not, what has prevented you from building one? The reader at your stage needs to see the support infrastructure being used (or its absence being felt) by a working CTO. |
The Financial Dimension
The emotional weight of the CTO role is compounded by a financial vulnerability that most startup CTOs neither understand nor address. The throughline is simple: the CTO who is burning out while being underpaid is experiencing two crises simultaneously, and each one makes the other worse.
Kruze Consulting, analysing anonymised payroll data from more than 250 venture-backed startups, found that founding CTOs earn an average of $139,000 — compared to $213,000 for non-founding CTOs hired into the same role. The gap is $57,000 at the seed stage and widens to $116,000 at Series A.[23] The founding CTO accepts below-market compensation on the understanding that equity will make up the difference. But equity is probabilistic, illiquid, and subject to dilution that most CTOs do not fully understand until it is too late.
The dilution arithmetic is straightforward and brutal. Carta data from more than 1,200 priced rounds shows that each funding round dilutes existing shareholders by roughly 15 to 20%. A CTO who starts with 10% at the seed stage will typically retain roughly 7.5% after the seed round, 6% after Series A, and 4% after Series B.[24] The percentage that felt substantial at founding shrinks with each round — and 60% of venture-backed companies return less than the original investment, according to Cambridge Associates data spanning 1990 to 2010.[25] The CTO’s below-market salary is, as investor Jason Cohen frames it, "a cash investment they’re making in your company" — one that fails more often than it succeeds.[26]
Fred Wilson, co-founder of Union Square Ventures, describes the equity comprehension gap: "You can’t pay your rent or take a vacation with your options. They might be worthless if the company fails. You have to pay taxes when you exercise and if you can’t sell the underlying stock that can be painful. For all of these reasons, many employees don’t really value the equity and they often don’t understand it either."[27] Carta’s own data confirms this: only 32.8% of vested, in-the-money options were exercised in late 2024 — meaning more than two-thirds of the equity that employees had earned and could have claimed went unexercised.[28]
The CTO who does not understand their compensation — who does not know their market rate, does not understand dilution mechanics, does not have a plan for option exercise, and does not know when to renegotiate — is making the burnout problem worse. The financial stress of being underpaid compounds the emotional exhaustion of the role. The sense that the sacrifice is not being recognised — because the CTO has never articulated it in financial terms — feeds the cynicism that Maslach identifies as the second dimension of burnout.
The self-sacrifice dynamic is cultural as well as financial. CTO Academy describes the pattern: "Within this environment, there is often pressure to work for below market salary on the basis it’s an exciting place to work. Staff salaries always take priority which means the senior team take any hit when it comes to the level and regularity of remuneration."[29] The CTO who accepts this framing — who takes the below-market salary without quantifying the gap, without understanding the probability-weighted value of their equity, and without a timeline for renegotiation — is not being generous. They are being uninformed. And the uninformed sacrifice compounds over years: a $74,000 annual gap over four years of vesting is $296,000 in forgone salary, bet on equity that has a better-than-even chance of returning nothing.
The tax dimension adds a layer that catches many CTOs by surprise. The 83(b) election — a one-page IRS form that must be filed within 30 days of receiving restricted stock — can mean the difference between a manageable tax bill and a catastrophic one. Stripe Atlas warns that the failure to file "has bankrupted very smart, honest taxpayers whose only mistakes were working for a company that got valuable and neglecting to send in a one-page piece of paper by a deadline."[30] The 409A valuation determines the strike price of options, and exercising at the wrong time can trigger taxes on unrealised gains that the CTO cannot actually access.[31] These are not edge cases. They are the standard financial terrain of the startup CTO, and the CTO who does not understand them is carrying financial risk they have never quantified.
The practical actions are specific. First, know your market rate. Kruze Consulting publishes annual salary data by stage and role. Carta publishes equity benchmarks. Index Ventures provides an option plan calculator based on data from more than 20,000 grants across 1,650 startups. The CTO who has not consulted these sources is negotiating blind. Second, understand your equity. The Holloway Guide to Equity Compensation is the most comprehensive public resource — it covers option types, vesting schedules, exercise windows, and the tax traps described above.[25] Third, renegotiate before you are forced to. Fred Wilson warns that "When founders get diluted below double-digit ownership, they begin to see themselves as employees, not owners, and that is bad for the company, the team, and the investors."[27] The CTO who waits for the board to raise the subject of compensation will wait forever. The board is not thinking about CTO pay. The CTO must raise it themselves — using the business acumen language from Chapter 10 to present their compensation case as a business decision, not a personal request.
|
AUTHOR: CorralData’s compensation structure — what you can share about the founding CTO’s financial reality at a B2B SaaS company scaling toward $6MM ARR. Has the founding-vs-hired gap been visible in your experience? Has equity dilution played out as the research describes? The reader needs to see the financial dimension grounded in a real company, not just in aggregate data. |
The Early-Warning System
The CTO who recognises burnout early has options. The CTO who recognises it late has a crisis. The Maslach framework provides the diagnostic: emotional exhaustion (do you feel depleted before the day begins?), depersonalisation (have you become cynical about your work or your colleagues?), and reduced personal accomplishment (do you feel that your contributions do not matter?).[11]
Andy Skipper, founder of CTO Craft, identifies warning signs specific to the CTO role: the perpetual call-and-response dynamic of technology leadership, where the infinite potential of software creates infinite requests. "Because, when the potential of something is infinite, so become the requests; it is this specific stressor to find something new, something better, and fast, that we believe makes burnout at senior level increasingly likely."[32] The CTO-specific warning signs include: avoiding code or technical discussions that previously engaged you (Lawrence’s experience), dreading one-on-ones with direct reports, making decisions by default rather than by deliberation, and the feeling that every problem is someone else’s failure rather than a shared challenge.
Gascoigne’s recovery provides the counterpoint. "About three to four weeks into my break, I felt much better. I felt lighter. I got my energy and motivation and excitement for Buffer back again." His key insight: "A key turning point in my burnout recovery was rediscovering the hobbies that I enjoyed doing before Buffer."[12] Lawrence’s recovery followed a different path: "Slowly but surely, I began to feel like I could cope and when an opportunity arose to found a startup in the creative industry, I jumped at the chance. And despite spending most of my time not actually using a computer, I rediscovered a passion for what I did."[1]
The research on recovery converges on a principle that sounds simple and is remarkably hard to execute: the CTO must create structural separation between their identity and the role. Chapter 13 addressed the identity transition from maker to multiplier. This chapter argues that the transition is not complete until the CTO has sources of identity, accomplishment, and community that exist outside the company. The peer group is one. The hobbies are another. The financial security to walk away — which requires the compensation literacy described above — is the third.
Matt Munson, a founder coach who experienced burnout himself, took a 12-week sabbatical that included a seven-day silent meditation retreat. His conclusion was more nuanced than "take time off": "Not necessary for every founder experiencing burnout to get out of the role to find relief. Many founders find relief by redesigning their roles or adjusting their workload."[33] The redesign — not the escape — is the sustainable response. The CTO who can identify which parts of the role are energising and which are depleting, and then restructure their responsibilities accordingly (by hiring a VPE, as Chapter 11 described, or by delegating specific functions), addresses the structural mismatch without abandoning the role.
The Maslach model offers one additional insight that connects burnout prevention to the community dimension of the CTO role. "A lively, attentive, responsive community is incompatible with burnout."[11] The CTO who builds the team culture described in Chapter 11 — generative, blameless, trusting — is not just creating a better engineering organisation. They are creating an environment that protects their own wellbeing. The CTO who builds a pathological or bureaucratic culture is constructing the conditions for their own burnout.
|
AUTHOR: Your early-warning system — how do you monitor your own state? Do you have practices (exercise, hobbies, time away from screens) that serve as burnout buffers? The reader who is approaching burnout needs to see the system, not just the diagnosis. |
The loneliest job in the startup is not lonely because the CTO lacks people around them. It is lonely because the specific weight of the role — the technical judgment, the business translation, the people management, the constant pressure to ship more, faster, with fewer resources — cannot be fully shared with anyone inside the company. The CEO does not understand the technical dimension. The engineers do not see the business dimension. The board does not see either.
The CTO who survives this role builds the infrastructure that the role does not provide: a peer group who understands the weight, a coach who helps them carry it, and the financial literacy to ensure that the sacrifice has a price they have consciously chosen to pay. The alternative — the CTO who carries the weight alone, who does not understand their compensation, who does not seek help until the burnout is undeniable — is the CTO who ends up like Lawrence: unable to write a line of code, unable to ask for help, and wondering how it came to this.
Chapter 16 addresses the question that follows: when the CTO has done everything this chapter recommends and still decides it is time to leave — how to make that transition a strength rather than a failure.