The Uncensored Truth About an IT Career: Why You Should Still Pursue It — And What Nobody Tells You
In 2014, a senior engineer at Amazon died at his desk. He was 30. His colleagues didn’t notice for hours because everyone assumed he was just working late. The coroner listed the cause of death as natural causes. The tech industry listed it as business as usual.
Every blog post about IT careers reads the same way. “Great salary! Exciting challenges! Unlimited growth! Fast-paced environment!” They read like recruitment brochures because that’s exactly what they are — written by HR departments, career coaches selling courses, and coding bootcamps that need your $15,000 tuition.
Here’s what those posts don’t tell you: working in IT can be one of the most intellectually rewarding, financially liberating, and personally destructive career paths you can choose. All three at the same time. And if you’re going to make this decision — a decision that will shape the next 10 to 40 years of your life — you deserve the full picture. Not the brochure.
This article is the version no recruiter will write. The uncensored, unfiltered truth about what an IT career actually looks like — the money, the burnout, the politics, the layoffs, the addiction, the brilliance, and the existential questions that hit you at 3 AM when you’re debugging a production outage and wondering why you chose this over becoming a carpenter.
And after all of that — after the full, honest accounting — I’ll explain why you should probably pursue it anyway.
The Money: It’s Real, But It’s Not What You Think
The Numbers Don’t Lie — But They Do Mislead
Let’s start with what draws most people in: the salary.
The U.S. Bureau of Labor Statistics (BLS, May 2024 data) reports the following median annual wages for IT occupations:
These are real numbers. They’re significantly higher than the national median salary of $48,060. And for senior roles at top-tier companies — FAANG (Facebook/Meta, Apple, Amazon, Netflix, Google) and comparable firms — total compensation (salary + stock + bonuses) can reach $300,000–$700,000+ for senior engineers, and over $1 million for staff-level and principal engineers.
But here’s what the salary numbers don’t tell you:
1. The distribution is bimodal, not normal. IT salaries don’t follow a bell curve. They follow a power law. A relatively small number of engineers at elite companies earn extraordinary compensation. A much larger number of IT workers — helpdesk technicians, junior sysadmins, entry-level support staff, developers at small companies — earn $40,000–$70,000, work brutal hours, and don’t have stock options or free lunches.
Dr. Hal Varian, chief economist at Google and professor at UC Berkeley, has noted that tech compensation exhibits classic Extremistan dynamics (Nassim Taleb’s term): the median is misleading because the distribution is heavily skewed by the top end. When a recruiter says “the average software engineer earns $130K,” they’re averaging in the Google senior engineers making $500K with the WordPress developers making $55K. Both exist in the same “industry.” They inhabit different economic universes.
2. Cost of living eats the salary. The highest-paying IT jobs are concentrated in the most expensive cities on Earth. San Francisco, New York, Seattle, London, Zurich. A $180,000 salary in San Francisco — after federal taxes, California state taxes, $3,500/month rent for a one-bedroom apartment, and the general cost of living — provides a lifestyle roughly equivalent to $85,000 in Austin, Texas.
The Economist’s Big Mac Index and Numbeo’s cost-of-living data consistently show that real purchasing power for tech workers in major hubs is 30–50% lower than their nominal salaries suggest. You’re rich on paper. You’re middle class at the grocery store.
3. The golden handcuffs are real. Stock-based compensation at large tech companies typically vests over four years. Leave before year four and you forfeit unvested stock — which can represent 30–60% of your total compensation. This creates what insiders call “golden handcuffs”: you want to leave, you can’t afford to leave, so you stay. And every year you stay, a new grant starts vesting, resetting the clock.
Laszlo Bock, former SVP of People Operations at Google and author of Work Rules!, acknowledged this dynamic openly: vesting schedules are designed to retain talent. They’re also designed to make leaving feel like losing money — even when staying costs you something harder to measure: time, health, passion.
The Burnout: The Industry’s Open Secret
The Numbers Are Catastrophic
In 2022, Yerbo — a burnout analytics platform — surveyed over 36,000 tech professionals across 33 countries. The findings:
- 42% were at high risk of burnout
- 62% reported feeling physically and emotionally drained
- 56% were unable to relax when they got home
- 52% reported feeling dissatisfied with their work achievements
Blind — an anonymous workplace social network verified by corporate email — regularly surveys tech employees. Their 2023 data showed that 73% of tech workers reported burnout, with the highest rates at Amazon (81%), Meta (77%), and Google (74%).
These are not anecdotal complaints. These are systemic, measurable, epidemiological-level mental health crises in one of the highest-paid industries on Earth.
Why IT Burns People Out
The burnout isn’t accidental. It’s structural.
Dr. Christina Maslach at UC Berkeley — the psychologist who literally invented the Maslach Burnout Inventory (MBI), the standard diagnostic tool used worldwide — identified six organizational factors that drive burnout:
That last one — values mismatch — deserves special attention.
The Ethical Weight Nobody Warns You About
In 2018, thousands of Google employees signed a petition and dozens resigned over Project Maven — a Pentagon contract to use AI for drone strike targeting. In 2019, employees at Palantir, Microsoft, Amazon, and Salesforce staged walkouts over contracts with ICE (Immigration and Customs Enforcement). In 2021, Frances Haugen, a Facebook product manager, testified before the U.S. Senate that the company’s own internal research showed Instagram was damaging teenage mental health — and the company suppressed the findings.
Here’s the reality nobody puts in the “Top 10 Reasons to Work in IT” listicle: your code has consequences. The recommendation algorithm you optimize might be feeding conspiracy theories to teenagers. The A/B test you run might be engineering addiction. The surveillance system you build might be used by an authoritarian government to track dissidents. The “user engagement” metric you’re rewarded for increasing might be indistinguishable from “time stolen from a human being’s finite life.”
Dr. Safiya Umoja Noble, professor at UCLA and author of Algorithms of Oppression (2018), has documented how search algorithms encode racial and gender biases. Cathy O’Neil, mathematician and author of Weapons of Math Destruction (2016), demonstrated how opaque algorithmic systems in hiring, policing, and lending perpetuate inequality while hiding behind the veneer of mathematical objectivity.
This doesn’t mean all IT work is ethically compromised. Much of it is genuinely beneficial — healthcare IT, accessibility engineering, open-source infrastructure, educational technology. But the high-paying, high-prestige jobs at the companies most aggressively recruiting you are, disproportionately, the ones most likely to present ethical dilemmas.
You should know that going in.
The Layoffs: Nobody Is Safe
The 2022–2024 Tech Bloodbath
Between November 2022 and March 2024, the technology industry laid off approximately 430,000 workers globally (data from Layoffs.fyi, the most comprehensive tracker of tech layoffs):
These weren’t struggling companies. Meta posted $39.1 billion in revenue the same quarter it laid off 11,000 people. Google’s parent company Alphabet reported $307 billion in revenue for 2023 while cutting 12,000 jobs. The layoffs weren’t survival moves. They were margin optimization — cutting costs to satisfy shareholders and signal “discipline” to Wall Street.
Steven Greenhouse, veteran labor reporter and author of Beaten Down, Worked Up, observed: “These layoffs are less about financial necessity and more about a shift in corporate psychology — from growth-at-all-costs to efficiency theater.”
The lesson: no salary, no stock package, and no employer loyalty protects you from a spreadsheet decision made by someone who doesn’t know your name. The IT industry will pay you extremely well right up until the moment it decides it doesn’t need you — and that moment can arrive with no warning, no fault of your own, and no connection to your performance.
The Myth of “Job Security Through Skill”
The industry narrative is: “Stay relevant. Keep learning. Upskill constantly, and you’ll always be employable.”
This is partially true and profoundly misleading.
Yes, skills matter. A strong engineer with current skills will generally find new work faster than a weak one. But the 2022–2024 layoffs revealed something the industry doesn’t like to admit: many of the people laid off were excellent. Staff engineers with 15 years of experience. Team leads with spotless performance reviews. People who had “upskilled” exactly as told.
They were laid off anyway — because the decision wasn’t about individuals. It was about headcount. It was about margins. It was about a CEO’s letter to shareholders.
Dr. Peter Cappelli at the Wharton School, who has studied employment trends for decades, puts it bluntly: “The notion that employees can protect themselves from layoffs through skill alone is a convenient fiction that shifts responsibility from employers to workers.”
Skills help. But skills are necessary, not sufficient. Financial resilience — savings, multiple income streams, low debt, a network outside your current employer — is the real safety net. Not your AWS certification.
The Intellectual Honesty: What’s Genuinely Great
Now. After all of that — the inflated salary narratives, the burnout epidemic, the ethical minefields, the mass layoffs — here’s the part that matters: why you should probably do it anyway.
Because when you strip away the corporate propaganda and the disillusionment, what remains is something genuinely remarkable.
1. The Problem-Solving Is Unmatched
There is no intellectual experience quite like debugging a system that nobody understands, finding the root cause, and fixing it. Programming is applied philosophy — you are constructing logical systems from pure abstraction, testing them against reality, and iterating until they work.
Edsger Dijkstra — Turing Award winner, one of the founding giants of computer science — wrote: “The art of programming is the art of organizing complexity.” That art is deeply satisfying in a way that few other professions offer.
When you write code that works — code that solves a problem that previously required hours of human labor, or code that enables something that was previously impossible — the satisfaction is not metaphorical. It is visceral. You built something from nothing. From thought to function. From abstraction to impact.
Mihaly Csikszentmihalyi (the psychologist who discovered flow state) found that programmers report some of the highest rates of flow experiences among all professions — those periods of deep, absorbed concentration where hours pass like minutes and the quality of work is at its peak. IT, at its best, is a flow state machine.
2. The Leverage Is Extraordinary
A carpenter can build one house at a time. A doctor can see one patient at a time. A teacher can teach one class at a time.
A software engineer can write code that runs on a billion devices simultaneously.
This is not an exaggeration. A single commit to a widely-used open-source library — Linux, React, OpenSSL, Python — can affect billions of users. Linus Torvalds, working alone in 1991, wrote the first version of the Linux kernel. Today, Linux runs on 96.3% of the top one million web servers (W3Techs, 2024), all Android phones, most embedded systems, the International Space Station, and virtually every supercomputer on Earth.
Get Mimic 💚’s stories in your inbox
Join Medium for free to get updates from this writer.
One person. One codebase. Billions of devices.
No other profession offers this ratio of individual effort to global impact. A single engineer, with a laptop and an internet connection, can build something that reaches every continent on Earth within weeks. The leverage is absurd — and it’s the fundamental reason tech compensation is so high. You’re not being paid for your time. You’re being paid for your leverage.
3. The Meritocracy Is Imperfect But Real
Let’s be honest: the tech industry has serious diversity and equity problems. The Kapor Center and other research organizations have documented systemic bias in hiring, promotion, and workplace culture — particularly affecting women, Black, Latino, and Indigenous professionals.
But compared to industries like law, finance, medicine, and academia — where credentials from elite institutions, family connections, and demographic background play enormous roles in career trajectory — IT has a relatively more permeable entry barrier.
No other high-paying industry accepts self-taught practitioners to the degree that IT does. You don’t need a degree from Stanford to get hired at Google (Google’s own data shows that roughly 15% of their engineers have no college degree). You don’t need to come from money. You don’t need to know someone. You need to be able to demonstrate competence — through projects, contributions, interviews, and measurable output.
This is imperfect meritocracy. There are biases. There are gatekeepers. But the barriers are lower than almost anywhere else — and for people from non-traditional backgrounds, that matters enormously.
Stack Overflow’s annual Developer Survey (2024) consistently shows that over 40% of professional developers describe themselves as at least partially self-taught. In what other industry paying six figures can nearly half the workforce say that?
4. The Optionality Is Unmatched
IT skills are fungible across industries. A software engineer can work in healthcare, finance, defense, education, entertainment, agriculture, logistics, government, or pure research — without starting over. The core skills transfer.
This gives IT professionals something rare: career optionality. If you burn out on fintech, you can move to healthtech. If you tire of enterprise software, you can freelance. If you want to leave the country, your skills travel — tech hiring is globally portable in a way that most professions are not.
Dr. Herminia Ibarra at London Business School, who studies career transitions, has found that the most successful career changers are those with transferable, high-demand skills and broad professional networks. IT checks both boxes structurally.
5. Remote Work Changed Everything
Before 2020, remote work in tech was a perk offered by some companies. After COVID-19, it became an industry standard. Scoop Technologies data (2024) shows that 67% of tech companies offer fully remote or hybrid work arrangements — the highest rate of any industry.
This fundamentally changed the economics of an IT career:
- You can earn a San Francisco salary while living in Bali, Portugal, Mexico City, or rural Tennessee
- You can structure your work around your life rather than your life around your work
- Geographic arbitrage — earning in a high-cost economy while spending in a low-cost one — is available to IT workers in a way it isn’t to nurses, electricians, or lawyers
Prithwiraj Choudhury at Harvard Business School has studied remote work extensively and found that geographic flexibility is the single most valued non-monetary benefit among knowledge workers — ranked higher than salary increases, titles, or promotion speed.
6. You’re Building the Future — For Better or Worse
Every major transformation of the next 50 years — artificial intelligence, quantum computing, biotechnology, clean energy, space exploration, autonomous systems — runs on software. There is no future that doesn’t pass through code.
This means IT professionals aren’t observers of the future. They’re architects of it. And that comes with a responsibility that most career guides don’t mention but that is, arguably, the most important reason to enter the field: the future needs people who give a damn.
If the only people building AI systems are those chasing stock options, the systems will optimize for profit. If some of the people building them are those who care about fairness, accessibility, privacy, and human flourishing — the systems might optimize for something better.
Stuart Russell, professor of computer science at UC Berkeley and author of Human Compatible (2019), argues that the single most important factor in whether AI benefits or harms humanity is who builds it and what values they bring. The technology is not inherently good or evil. The people are the variable.
The Honest Roadmap: What Actually Works
If you’ve read this far and still want in — good. Here’s the advice that career coaches charge thousands for, distilled into what actually matters:
1. Don’t Optimize for First Job. Optimize for Learning Rate.
Your first IT job will pay less than you want. It won’t be at Google. It might be helpdesk. It might be a small company nobody has heard of. It doesn’t matter.
What matters is your learning rate — how quickly you’re acquiring real, transferable skills. A junior role at a small company where you touch the entire stack, deploy to production, debug real outages, and work directly with customers will teach you more in one year than two years at a large corporation where you write unit tests for a microservice you don’t fully understand.
Cal Newport (Georgetown University), author of So Good They Can’t Ignore You, studied career trajectories across industries and found that early-career skill acquisition — what he calls “career capital” — is the single strongest predictor of long-term career satisfaction. Not passion. Not salary. Skill.
2. Build in Public. Ship Things.
The IT industry has a unique feature: your work can be visible to the entire world for free. Open-source contributions, personal projects, blog posts, GitHub repositories — these are your portfolio, your resume, and your network-building tool all in one.
John Resig built jQuery as a side project. Evan You built Vue.js as a side project. Mitchell Hashimoto built Vagrant as a side project — and it became the foundation of HashiCorp, valued at over $5 billion at IPO. Side projects are not hobbies. They’re career accelerators.
You don’t need to build the next jQuery. You need to build anything — and show it to people. A working project demonstrates more than any certification, any degree, and any whiteboard interview.
3. Invest in Systems Thinking, Not Just Syntax
Programming languages change. Frameworks change. Cloud platforms change. What doesn’t change: the ability to understand complex systems, reason about tradeoffs, communicate technical ideas clearly, and debug problems methodically.
Gerald Weinberg — one of the earliest writers on the human side of computing, author of The Psychology of Computer Programming (1971) — argued that the most valuable skill in software engineering is not programming. It’s thinking about programming. The ability to model a problem, decompose it, identify edge cases, and reason about failure modes is worth more than fluency in any specific language.
Learn the fundamentals deeply: data structures, algorithms, networking, operating systems, databases, security basics. These don’t expire. React might be gone in five years. TCP/IP will be here in fifty.
4. Guard Your Health Like Your Career Depends on It — Because It Does
The IT industry normalizes sedentary behavior, poor sleep, caffeine dependency, screen addiction, and chronic stress. The consequences are measurable:
- Dr. James Levine at the Mayo Clinic coined the phrase “sitting is the new smoking” — extended sedentary behavior is associated with a 40% increase in all-cause mortality (Biswas et al., 2015, Annals of Internal Medicine)
- Matthew Walker (UC Berkeley), author of Why We Sleep, has shown that sleeping less than 7 hours regularly impairs cognitive function, immune response, emotional regulation, and — critically for IT workers — problem-solving ability and creative thinking
- Chronic stress — the kind that comes from on-call rotations, production outages, and performance reviews — elevates cortisol, impairs hippocampal function (memory), and is associated with increased risk of cardiovascular disease, depression, and anxiety
Your body is not a platform you can scale horizontally. It doesn’t have redundancy. There’s no failover. If it goes down, everything goes down. Exercise, sleep, nutrition, and stress management are not self-care luxuries. They are career infrastructure.
5. Build Financial Resilience Early
The highest-risk moment in an IT career is not the learning curve. It’s the moment you become dependent on a single employer’s compensation — especially when that compensation includes deferred stock.
Ramit Sethi, author of I Will Teach You to Be Rich, and Morgan Housel, author of The Psychology of Money, both emphasize the same principle: your savings rate matters more than your salary. An engineer earning $200,000 who spends $195,000 is more financially fragile than a sysadmin earning $80,000 who saves $25,000.
Build an emergency fund. Keep lifestyle inflation below income growth. Diversify income sources when possible. The goal is optionality — the ability to walk away from a bad job, survive a layoff, or take a risk on something you care about — without financial catastrophe.
6. Find Your People
IT can be isolating — especially remote IT. The loneliness problem is not trivial.
Dr. Vivek Murthy, the U.S. Surgeon General, issued an advisory in 2023 declaring loneliness and social isolation a public health epidemic, with health impacts comparable to smoking 15 cigarettes per day.
Tech communities — open-source projects, local meetups, online forums, hackathons, mentorship programs — are not optional social accessories. They’re survival infrastructure. The people who sustain long, fulfilling IT careers almost always have a community — a group of peers who understand the work, share the challenges, and provide perspective when the industry’s dysfunction becomes overwhelming.
The Bottom Line
Here is the uncensored truth about an IT career:
The money is real — but it’s distributed unevenly, eaten by cost of living, and attached to golden handcuffs that make leaving feel like financial suicide.
The burnout is real — structural, measurable, and normalized by an industry that treats human beings as “resources” to be “allocated” and “scaled.”
The layoffs are real — and they can hit anyone, at any performance level, at any time, for reasons that have nothing to do with you.
The ethical compromises are real — and they accumulate quietly until one day you realize you’ve spent five years optimizing engagement metrics for an app that makes teenagers miserable.
And the work is genuinely, profoundly, unreplaceably extraordinary. The intellectual challenge. The creative satisfaction. The leverage. The optionality. The ability to build something from nothing that runs on a billion devices. The chance to shape the infrastructure of the future.
Both things are true. The brilliance and the brutality. The opportunity and the exploitation. The freedom and the golden cage.
The people who thrive in IT are not the ones who ignored the dark side. They’re the ones who saw it clearly, prepared for it deliberately, and chose the career anyway — with open eyes, strong boundaries, financial resilience, and a clear sense of what they’re willing to trade and what they’re not.
Don’t pursue an IT career because a blog post told you it’s exciting and the salary is great.
Pursue it because you’ve seen the full picture — the magnificent and the brutal — and you’ve decided that what you can build is worth what it costs.
Just make sure you know the price before you pay it.
Tags: #ITCareer #TechIndustry #SoftwareEngineering #Burnout #CareerAdvice #Psychology #Technology #Layoffs #RemoteWork #UncensoredTruth
If this gave you a more honest view of tech than any recruiter ever will — hit 👏 and share it with someone who’s about to enroll in a $15,000 coding bootcamp without knowing the full story.
