Reason #75: It's a Vocation Wearing a Profession's Suit

You took the same calculus sequence as the pre-med students. You took the same physics as the future physicists. You survived thermodynamics, fluid mechanics, machine design, heat transfer, and a senior capstone that asked you to deliver a working prototype on a semester's budget. Four, five, or six, years of professional-grade training, See Reason #2, and at the end of it you entered a labor market where your salary was set before you opened your mouth, your employer chose your city, and your title carried no legal weight in most of the work you actually did. You did the coursework of a profession. You got the career structure of a trade. Strangers still think you are the former. Everyone inside the field knows you are the latter. See Reason #3.

Sociologists have a framework for this. A profession, in the classical sense, controls its own entry, protects its title, enables independent practice, and sets its own price floor. Medicine does all four. Law does all four. You do none. See Reason #13. Your PE is optional, and in most mechanical roles it changes neither your pay nor your autonomy. See Reason #17. Your title is protected on paper in some states, but in practice anyone sitting in the right chair at the right company gets called a mechanical engineer regardless of credentials. You cannot open a firm, stamp drawings, and bill clients the way a civil engineer can. See Reason #58. And you have no guild, no union, and no professional body that negotiates a floor on what your labor is worth. Those are not four separate failures. They are one diagnosis.

The honest version of this argument requires a concession. Engineering as a whole is a weak profession. Academic sociologists like Andrew Abbott and Eliot Freidson have documented this for decades. Engineers work inside organizations, not for clients. They are subordinated to managerial authority over budgets, timelines, and scope. They do not control the terms of their own practice the way doctors and lawyers do (Abbott, 1988; Freidson, 2001). When civil engineering's own professional society tried to move the discipline closer to true professional status through ASCE's "Raise the Bar" initiative, the effort itself was an admission that even the strongest engineering branch had not arrived yet (Russell, 2011). All engineering sits on the weak side of the profession line. But mechanical engineering is not just weak. It is the branch where every weakness converges with no compensating strength.

Civil engineers have the PE, the stamp, and a regulatory architecture that creates a retail market for their work. Roughly 50 to 60 percent of all licensed professional engineers in the United States are civil or structural, because licensure is structurally embedded in how civil work gets permitted and built. Computer science has no guild at all, but it has around 1.5 million jobs, a telework rate near two thirds, a median salary above $130,000, and multiple independent paths from freelancing to SaaS. Electrical and chemical engineers share most of mechanical's structural weaknesses, but they have higher pay ceilings and much smaller graduating classes, which means less oversupply pressure and more room to negotiate. Mechanical engineering has the largest graduating class in engineering, the lowest median pay among the major branches, and the flattest salary curve. See Reason #18. It has the most geographic captivity. See Reason #74. And it has virtually no viable independent practice pathway. Civil found a guild niche. Computer science found market leverage. Electrical and chemical found higher pay and tighter pipelines. Mechanical found nothing.

That is what a vocation looks like when you dress it in professional clothing. You do professional-difficulty work, you carry a professional-grade student debt load, you build a professional self-image, and then you enter a market that treats you the way it treats any other interchangeable labor input: your salary is compressed. See Reason #27. Your leverage is negligible. Your location is dictated. Your career is a series of lateral moves inside organizations that owe you nothing. The plumber standing next to you on the job site has a protected trade, a portable license, and the ability to hang a shingle tomorrow. See Reason #56 and See Reason #64. The difference between you and a graphic designer is that the graphic designer knows. You spent five years and a hundred thousand dollars believing you were entering something else. See Reason #67.

You were not.

References:

Abbott, A. (1988). The system of professions: An essay on the division of expert labor. University of Chicago Press.

Freidson, E. (2001). Professionalism: The third logic. University of Chicago Press.

Russell, J. S. (2011). The sociology of professions: Application to the civil engineering "Raise the Bar" initiative. Journal of Professional Issues in Engineering Education and Practice, 137(2), 98–107. https://doi.org/10.1061/(ASCE)EI.1943-5541.0000043

Reason #74: Outside the Clusters, You Don't Exist

You type your city into a job board and filter for mechanical engineering. Three results come back. One is HVAC service. One is a six-month contract an hour and a half away. One was posted nine weeks ago and the listing has not been updated since. You refine the search. You widen the radius. You check a second board. The results do not improve. You are not in a bad market. You are in no market at all.

There are roughly 281,000 mechanical engineering jobs in the United States (Bureau of Labor Statistics [BLS], 2024a). See Reason #34. More than half of them are in ten states. Michigan alone holds over 32,000. The Detroit metro area employs more than 20,000 mechanical engineers, one for every hundred workers in the region. Washington, D.C., the capital of the country, employs roughly 500 (BLS, 2024b). New York City, the largest labor market in the nation, has a mechanical engineering location quotient of 0.29 (BLS, 2024a). That means for every mechanical engineer you would expect to find based on national averages, New York has fewer than one in three. You are not scarce there. You are a rounding error.

Source: Bureau of Labor Statistics, OEWS May 2023. Mechanical Engineers (17-2141).

The numbers behind the map are worse than the colors suggest. Five states account for over 40 percent of every mechanical engineering job in the country. Michigan leads with a location quotient of 4.05, meaning it has four times the national average concentration of MEs. California, the largest state economy, has a location quotient below 1.0. It is actually underrepresented in mechanical engineering jobs relative to its size.

Table 1. ME Employment by Top States (May 2023 OEWS)

State	ME Jobs	Location Quotient	% of U.S. ME Total
Michigan	32,580	4.05	11.6%
California	27,420	0.82	9.8%
Texas	19,630	0.78	7.0%
Pennsylvania	19,060	1.73	6.8%
Ohio	15,160	1.50	5.4%
Top 5 subtotal	113,850		40.5%
Remaining 45 states + D.C.	~167,000		~59.5%
U.S. total (ME)	~281,000		100%

Source: Bureau of Labor Statistics, OEWS May 2023. SOC 17-2141. Location quotient measures local concentration relative to the national average (1.0 = average). Five states hold over 40 percent of all ME jobs.

The map gets worse when you compare it to other fields. California employs 27,420 mechanical engineers. It also employs 304,390 software developers (BLS, 2024c). That is an 11-to-1 ratio in a single state. Nationally, there are nearly six software developers for every mechanical engineer. Software and computer occupations have telework rates near 65 percent (BLS, 2023a). Mechanical engineers sit closer to 26 percent (BLS, 2023b). See Reason #30. A software developer in Boise or Raleigh or Omaha can work for a company in San Francisco without moving. You cannot test a casting from your living room. You cannot run a DV plan from a home office in a city that has no test lab, no prototype shop, and no OEM within two hundred miles. Your work is physical, your employers are clustered, and the gap between those two facts is your career.

Table 2. ME vs. Software Developer Employment, Top States (May 2023 OEWS)

State	ME Jobs	Software Dev Jobs	Ratio (SW : ME)
California	27,420	304,390	11.1 : 1
Texas	19,630	138,510	7.1 : 1
Washington	—	89,110
Virginia	—	86,680
New York	—	105,460
U.S. total	~281,000	1,656,880	5.9 : 1

Source: Bureau of Labor Statistics, OEWS May 2023. ME = SOC 17-2141. Software developers = SOC 15-1252. — = state not in top 5 for ME employment; full state data available in BLS downloadable files. Washington, Virginia, and New York each employ more software developers than the top ME state (Michigan) employs mechanical engineers. California alone employs 304,390 software developers. The entire U.S. mechanical engineering workforce is roughly 281,000.

If you zoom in further, the concentration gets more extreme. The metro areas with the highest ME location quotients are not coastal cities or tech hubs. They are manufacturing corridors. Columbus, Indiana, a city built around one company, has a location quotient of 26.54. That means it has over 26 times the national average concentration of mechanical engineers. Three of the top five metros are in Michigan. These are the places where your career lives. If you are not in one of them, you are reading job boards with three results.

Table 3. Top Metro Areas for ME Concentration (May 2023 OEWS)

Metro Area	ME Jobs	Location Quotient	Mean Wage
Columbus, IN	1,340	26.54	$117,070
California-Lexington Park, MD	680	14.48	$110,700
Waterloo-Cedar Falls, IA	1,010	11.68	$108,150
Saginaw, MI	870	10.99	$93,530
Detroit-Warren-Dearborn, MI	20,390	10.73	$102,870
Huntsville, AL	2,260	8.99	$111,780
Ann Arbor, MI	1,910	8.85	$108,980
New Bern, NC	350	7.79	$88,280
Fond du Lac, WI	300	6.69	$101,100
Bremerton-Silverdale, WA	600	6.49	$102,710

Source: Bureau of Labor Statistics, OEWS May 2023. SOC 17-2141. Sorted by location quotient. Columbus, IN (Cummins headquarters) has over 26 times the national average concentration of MEs. Outside of Detroit, the highest-concentration metros employ fewer than 2,300 mechanical engineers each. These are not cities you dream of moving to. They are cities where one employer decides whether your career exists.

Outside the top ten states, the remaining 120,000 or so mechanical engineering jobs are scattered across forty states, territories, and the District of Columbia. In many of those states, the entire ME workforce is measured in the low hundreds. In some states, the entire mechanical engineering workforce is smaller than the accounting department at a mid-size company. If you live in one of those states and want to stay, your options are not limited. They are functionally zero. The job that exists is the job you take, on the terms it offers, because there is no second offer coming from across town.

This is why the advice to "just relocate" misses the point. You can relocate. Many do. But you are not relocating to a city. You are relocating to a plant, or a cluster of plants, in a region you did not choose, for a program that may not outlive your mortgage. See Reason #20. Look at Table 3 again. Outside of Detroit, the highest-concentration metros each employ fewer than 2,300 MEs. Saginaw has 870. Fond du Lac has 300. You are not moving to a labor market. You are moving to a plant. And when that program ends, you do not get to search locally. You search the map again, the same short list of metros with the same short list of employers, and you ask your family to move again.

The map has always looked like this. Nobody shows it to you before you declare the major.

References:

Bureau of Labor Statistics. (2023a, December 19). About 1 in 3 workers in management, professional, and related occupations teleworked in November 2023. The Economics Daily. https://www.bls.gov/opub/ted/2023/about-1-in-3-workers-in-management-professional-and-related-occupations-teleworked-november-2023.htm

Bureau of Labor Statistics. (2023b). Occupational requirements survey: Mechanical engineers. https://www.bls.gov/ors/factsheet/mechanical-engineers.htm

Bureau of Labor Statistics. (2024a). Occupational employment and wage statistics, May 2023: Mechanical engineers (17-2141). https://www.bls.gov/oes/2023/may/oes172141.htm

Bureau of Labor Statistics. (2024b). Occupational employment and wage statistics, May 2023: District of Columbia. https://www.bls.gov/oes/2023/may/oes_dc.htm

Bureau of Labor Statistics. (2024c). Occupational employment and wage statistics, May 2023: Software developers (15-1252). https://www.bls.gov/oes/2023/may/oes151252.htm

Reason #73: You're the Last to Know When the Program Dies

You submitted the ECO on Friday. Revision D of the intake manifold bracket, with the updated tolerance stack and the supplier's adjusted tool path. You had been working that change for three weeks through routing, review, and two rounds of comments from quality. On Monday you badge in and the program is dead.

Nobody called you over the weekend. The email went out at 4:47 PM Friday from a VP two levels above your director, addressed to a distribution list you are not on. By the time you sit down, your coworkers already know. Someone saw it on Teams. Someone heard it from a supply chain manager who heard it from purchasing. You are the last to find out because you were doing the work. You were a line item on someone else's cost sheet. See Reason #23.

The DV test plan you spent two months writing will never run. See Reason #36. The fixtures you speced are in a quote cycle that purchasing will cancel before lunch. The PPAP package you assembled documents a part that will never be produced. The supplier you spent six months qualifying will move on to someone else's program or close the file entirely. None of this was failing. All of it was on schedule. The program was killed for reasons that had nothing to do with engineering. See Reason #72. Portfolio rebalancing. A revised market forecast. A bet on a different platform that someone in strategy liked better. The decision was made in a room full of people who do not know what a tolerance stack is and do not need to.

This is not rare. In automotive, programs get killed mid-cycle regularly. In defense, contract phases are descoped or shelved after years of preliminary design review. In consumer products, a product line gets cut because retail shelf commitments shifted. In industrial equipment, a next-generation platform gets frozen indefinitely because the installed base is "good enough." In this line of work, you do not control whether anything you build leaves the building. The common thread is that engineers find out last and absorb the cost first. You were the most invested person in the building. You were also the least informed.

What happens next depends on how your employer accounts for the loss. You get reassigned to a program that is already staffed and does not need you. You sit on sustaining work and minor ECOs while management figures out where to bill your hours. Or the cancellation becomes a restructuring and you are part of the reduction. In every scenario, the months or years you poured into the dead program collapse into a single resume line about a product nobody outside your old building has heard of, on a platform that no longer exists, for a market someone in another time zone decided not to enter.

You did everything right. The program did not care.

Reason #72: The System Works Exactly as Designed (Just Not for You)

You have been reading this blog and thinking something is broken. The oversupply, the pay compression, the credential treadmill, the churn. It looks like a system failing its people. It is not failing. It is working. Every piece is doing exactly what it was built to do. The problem is that none of it was built for you. See Reason #60.

Start with the universities. They do not cap enrollment because enrollment is revenue. Mechanical engineering is the most popular engineering major in the country, which means it is the most profitable pipeline to keep open. See Reason #4. Every undecided freshman who defaults into ME is a tuition-paying seat for five or six years. See Reason #1. The department does not ask whether the market can absorb the graduates. The department asks whether the lecture hall is full. It is. The department is working as designed.

ABET accredits the programs. It does not limit them. It audits syllabi and faculty credentials and capstone rubrics. It does not restrict the number of seats, does not lobby for title protection, does not enforce scope of practice, and does not intervene when the graduate-to-opening ratio reaches two and a half to one. See Reason #13 and See Reason #34. Its job is to certify quality, not to manage supply. It certifies. The pipeline fills. ABET is working as designed.

Employers benefit next. A permanent buyer's market means they can post "entry-level" with three years of required experience and still fill the seat. They can run six-month temp-to-perm auditions and call it due diligence. See Reason #45. They can hold raises to 3% because ten qualified replacements will accept the same number tomorrow. They can classify you as overhead and budget you accordingly. See Reason #23. The surplus is not a problem for them. It is a procurement advantage. Hiring is working as designed.

Staffing firms sit in the middle and profit from the churn. Every contract placement, every temp extension, every conversion fee is a transaction that only exists because the pipeline keeps refilling and companies keep hedging. The more volatile the hiring cycle, the more valuable the middleman. Staffing is working as designed.

The professional societies collect dues, host conferences, and publish journals. They do not negotiate pay floors, restrict entry, or enforce title protection the way the AMA or the ABA do. ASME will sell you a membership and a networking lunch. It will not stand between you and the employer who just cut your team by 40%. See Reason #13. The society is working as designed. It was designed to be a trade association, not a guild.

The party line holds it together. See Reason #39. Recruiting pages publish reassurance. Outreach organizations push the pipeline forward. When enough doubt accumulates, someone writes a "debunking myths" article to steady the next cohort. See Reason #59. The messaging is working as designed. Its job is not to inform you. Its job is to keep you walking forward.

Now step back and look at the whole machine. Universities profit from your tuition. ABET profits from accreditation fees. Employers profit from your replaceability. Staffing firms profit from your churn. Societies profit from your dues. The outreach apparatus profits from your optimism. At every stage, a stakeholder extracts value from the surplus, and at no stage does any stakeholder have an incentive to reduce it. The oversupply is not a market failure. It is the market. You are not a participant in this system. You are the input.

This is why so many reasons on this blog can all be true at the same time without anyone fixing any of them. The people who could intervene, the universities, the accreditors, the professional bodies, are the same people who benefit from the status quo. The employers who complain about "talent shortages" are the same employers who offshore junior work, refuse to train, and post fifteen-year experience requirements for roles they gutted a decade ago. See Reason #25 and See Reason #55. Nobody is confused. Everybody is comfortable. The only person absorbing the cost is you.

You thought the system was supposed to serve you. It serves itself. You are the subsidy it runs on.

Reason #71: Their Engineering Experience Compounds, Yours Expires at the Door

Every other traditional engineering branch has a direction it compounds into. Electrical engineers can pivot from power systems into embedded, FPGA design, signal processing, controls, or chip verification without abandoning their foundation. Each move deepens the resume. Chemical engineers slide from refining into pharma, biotech, polymers, or process safety, carrying their unit ops fluency with them. Computer engineers walk into software, data infrastructure, ML pipelines, or hardware architecture. Civil engineers get a PE, open a firm, stamp drawings, and build a practice with their own name on the door. See Reason #38. Each of these fields has internal momentum. You start somewhere, you build, and the building carries you upward or outward into something that still recognizes what you were.

Mechanical engineering does not work this way. See Reason #8. You spend two years on vibration analysis for rotating equipment in oil and gas, and the next job posting wants thermal management for consumer electronics in a different CAD package. Your experience does not transfer. It resets. The broadness that was supposed to be your advantage is the reason nothing compounds, because there is no spine that connects your last role to your next one. Every move sideways feels like starting over. Every move up means leaving ME entirely. See Reason #28.

Compare this to the civil path. A civil engineer takes the FE, works four years under a PE, passes the PE exam, and can open a practice. The licensure is the ramp. The stamp is the product. The independence is built into the profession's structure. In ME, the PE rarely changes your day, your title, or your pay. See Reason #17. There is no guild protecting scope of practice, no licensing body that limits who can do the work, no mechanism that turns your years of experience into a credential that opens a door only you can walk through. See Reason #13. You accumulate seniority inside institutions. Outside them, you are almost invisible. See Reason #56.

The tools reinforce the trap. Your CAD proficiency resets with every job change because the next company runs a different platform. See Reason #62. Your process knowledge is locked inside the ERP, the PLM, the supplier network, and the quality system of whoever employed you last. A software engineer carries a GitHub portfolio. An EE carries board designs and proven schematics. You carry NDAs and expired logins. When you try to go independent, the stamp problem, the liability problem, and the systems-you-do-not-own problem converge into a wall. See Reason #58.

So the internal trajectory dead-ends and the external pivots are expensive. By mid-career you have invested a decade into a field that does not let you climb inside it and does not let you leave cleanly. See Reason #46. The innovation frontier moved to software, batteries, controls, and computation years ago. See Reason #7 and See Reason #35. The curriculum never added a new pillar to match. The market still has two and a half of you for every opening. See Reason #34. And the exit options all require you to explain, from scratch, why a mechanical engineer belongs in a room that was not built for one.

Other branches have escape velocity. They have internal ladders that lead somewhere, external pivots that recognize what you built, and independent paths that do not require a decade of institutional apprenticeship before you are allowed to charge for your judgment. ME has none of these. It has lateral resets, upward departures, and a "broadness" that dissolves the moment you try to point it in a single direction.

You were told it was an intersection. It is a cul-de-sac with a view of other people's highways.

Reason #70: The Community Polices Itself

You would think that a professional community facing a documented oversupply problem would want to talk about it. You would think that engineers, people trained to read data and draw conclusions, would at least engage with the numbers before dismissing the person who posted them. That is not what happens. Post a sourced, detailed comment about mechanical engineering's structural problems on a mechanical engineering forum and the most likely outcome is not a counterargument. It is a removal (See Reason #39).

The pattern is predictable enough that you can set a clock by it. You write a substantive reply explaining that the field graduates far more engineers than the labor market absorbs (See Reason #1), that the Bureau of Labor Statistics projects flat or declining demand (See Reason #50), that one in five ME graduates ends up in a job that does not require the degree at all (See Reason #63). You cite the source. You link the federal data. Someone replies "sounds like you just had a bad employer." Someone else says "maybe engineering isn't for everyone." Then a gatekeeper removes the comment. Not because it violated a rule. Because it made the room uncomfortable and one of the rules was close enough to justify the click. No link was posted. No product was sold. The content was removed because of what it said, and the person who said it was permanently banned from two forums by the same gatekeeper on the same day.

Some of you reading this right now are learning for the first time that ME has the highest underemployment rate among the major engineering disciplines. You are learning it here because you were never going to learn it there. The forums where you would naturally ask "is this degree worth it" are the same forums where the answer gets deleted. The spaces where a first-year student posts "should I switch to EE" are the same spaces where the person with thirty years of experience and a sourced reply gets banned for self-promotion he did not commit. The pipeline does not just fail to warn you. It actively prevents other people from warning you (See Reason #25).

This is not an institutional policy. It is a community reflex. People who chose mechanical engineering and built careers around it have a stake in the narrative. They sat through the same thermodynamics sequence you did. They fought through the same job search. Admitting that the market is structurally oversaturated means admitting that the difficulty of the degree did not buy what they were told it would buy (See Reason #60). That is a hard thing to sit with. It is easier to call the messenger bitter and move on.

The suppression happens at every level. Online, forum gatekeepers remove posts and ban users whose only infraction was being specific. In departments, professors steer conversations away from labor market data and toward innovation narratives. At professional society events, the panel on "the future of mechanical engineering" never includes a slide showing that the field produces roughly two and a half graduates for every projected opening (See Reason #34). The New York Fed publishes it. The BLS publishes it. Nobody on the podium mentions it. And if someone in the audience brings it up, the panel chair moves to the next question (See Reason #59).

What makes this specific to mechanical engineering, and not just a general observation about groupthink, is the size of the gap between the field's self-image and its market position. Electrical engineering forums do not need to police criticism because their graduates are not underwater. Computer science forums do not need to delete comments about pay compression because pay compression is not their problem. The intensity of the suppression is proportional to the size of the thing being suppressed. ME has the largest graduating class, the flattest pay curve relative to difficulty, and the worst underemployment numbers in the engineering column. That combination produces a community that cannot afford to let the conversation happen.

A profession that was confident in its value would engage its critics. A profession that was honest about its challenges would surface the data and let prospective students decide for themselves. What you get instead is a profession that treats factual criticism the way a company treats a quality escape: contain it, document the containment, and make sure it does not reach the customer. You are the customer. And if you are reading this blog, it is probably because nobody in the places you looked first would let you see it.

Reason #69: The Seniors Who Trained You Won't Be Replaced

You learn mechanical engineering from someone who already knows it. Not from a textbook. Not from an SOP. From the person sitting ten feet away who tells you that the tolerance on that bore is tighter than the drawing says, because the last three builds chattered and nobody updated the print. That person is retiring in four years. Nobody is training a replacement.

This is how the pipeline dies. Not all at once. Quietly, over a hiring cycle or two. A company outsources the junior design work because it is "routine" and the offshore rate is a third of the loaded cost. The senior engineers keep their seats because they are the ones who check the outsourced output, catch the errors, and know which rules are real and which ones are artifacts of a drawing that has not been revised since 2009. Management looks at the org chart and sees savings. What they do not see is a missing generation (see Reason #25).

Junior work is not junior because it is easy. It is junior because it is where you learn what the senior people already know. You learn stack-ups by blowing one. You learn supplier tolerances by chasing a casting that came in hot. You learn test lab scheduling by watching your timeline collapse when the shaker is booked through Q3. You learn DFMEA not from the template but from the field return that nobody predicted. All of that requires being in the room, on the floor, next to someone who has already made the mistake you are about to make. The company will not teach you this. Your onboarding is a slideshow and a safety quiz (see Reason #54). The plant is the real classroom (see Reason #52). When you offshore that work, you do not just lose a task. You lose the classroom.

The senior engineers notice first. They spend more hours reviewing than creating. Their redlines multiply. The offshore team follows the procedure but misses the intent, so the senior rewrites the section, adds a note, and moves on. Then they rewrite another section. Then another. They become full-time editors of work they used to do themselves in half the time. They are needed, which in this field means they are being used until the cost of keeping them exceeds the cost of the errors they catch (see Reason #55). Nobody is learning from the corrections because the corrections go into an email thread that crosses nine time zones and ends with "noted, will update" (see Reason #12).

Five years in, the senior retires. The company posts the role. The job listing asks for fifteen years of experience in a niche that the company itself stopped teaching a decade ago. Nobody internal qualifies because nobody internal was developed. Nobody external qualifies at the salary offered because the people with that experience know what it is worth, and the company has spent a decade proving it will not pay accordingly (see Reason #27). The role stays open for eight months, gets downgraded to a "lead" title, and eventually gets filled by someone who checks the boxes on paper but has never touched the product. The field produces two and a half candidates for every opening (see Reason #34). None of them have fifteen years in a niche the company stopped cultivating a decade ago. The institutional knowledge is gone. It did not get outsourced. It got extinguished.

This is not a temporary gap. It is a permanent one. You cannot rebuild a ten-year development ladder by posting a req. You cannot buy judgment from a staffing agency. You cannot extract tribal knowledge from a retired engineer's email archive. The company burned the bridge while standing on it. The seniors who might have stayed were told the only way up was out of engineering entirely (see Reason #28), and now the procedures run without anyone who understands what they were written to protect.

You will enter this field and be told there is a shortage of experienced engineers. There is. The companies created it themselves.

Reason #68: AI Won't Replace Mechanical Engineers, It Will Replace What They Became

You will hear this at every conference and in every LinkedIn thread for the next decade: AI cannot replace real mechanical engineering. It cannot feel a tolerance stack go wrong. It cannot walk the floor and notice a fixture is drifting. It cannot sit across from a supplier and read the pause before the lie. All of that is true. None of it matters. Because the job you actually do every week is not that. See Reason #40.

You already read what the job became. You route ECOs through approval chains. You fill out DFMEA templates one failure mode at a time. You build DV/PV matrices in spreadsheets and track them in portals. You write test reports that exist to prove something passed, not to explain why it works. You chase RoHS and REACH certificates from suppliers who do not answer emails. You update BOMs in ERP systems that fight you. You reformat PDFs because a customer portal rejects embedded fonts. You paste screenshots into PowerPoint decks that a manager will skim for one bullet before asking for a risk line. See Reason #33 and See Reason #9.

That is the job. Not the brochure version. The calendar version. The version you live Monday through Friday, and often Saturdays as well. And every single item on that list is text-in, text-out work. It is structured, repetitive, and traceable, which is exactly the profile that large language models and workflow automation were built to eat. The question was never whether AI could replace a mechanical engineer who sizes a pressure vessel from first principles. The question is whether AI can fill out the paperwork that surrounds the pressure vessel after someone else already sized it. The answer is yes. It already can.

The compliance layer accelerates this. You spend increasing fractions of your week not designing but proving, assembling cert packs, mapping test evidence to requirements, building traceability matrices, and writing justification memos so an auditor can check a box. See Reason #51. That work expanded until it became the job. And it expanded into the exact shape of a task that automation handles well: collect inputs, apply rules, generate output, route for signature. You did not need to be replaced. You needed to be transcribed. See Reason #65.

The people who say "AI can't do what I do" are thinking of the 20% that still feels like engineering. The thermal intuition. The fixture hack that saved a build. The moment you overrode the model because you remembered a field return from 2016. That part is real, and no model replicates it today. But that 20% does not justify the headcount. The headcount was justified by the other 80%, the administrative throughput that kept gates moving, reports filed, and portals green. See Reason #42 and See Reason #26. When that 80% gets cheaper to automate than to staff, the headcount shrinks. You keep the title. You lose the seat.

This is not speculation. It is the same pattern that played out when admin work moved offshore, except faster and without the time zone lag. See Reason #40 already told you the rule: if the work can be written down, the work can be moved. Now it does not even need to move. It just needs a prompt.

The field will not vanish. Someone will still walk the floor. Someone will still argue with a casting vendor about why the draft angle cannot drop another half degree. But there will be fewer someones, and the ones who remain will be expected to carry the 20% that matters on a fraction of the old headcount, while a dashboard handles the rest. That is not survival. It is compression. And in a market that already has two and a half candidates for every opening, compression does not create opportunity. It removes it.

You were told your judgment makes you irreplaceable. It does. The job just stopped being about judgment a long time ago.

Reason #67: It Has the Worst Return on Investment in Engineering

You picked mechanical engineering because it sounded safe. Broad. The one that keeps your options open. You heard that from an adviser, a parent, or a rankings page that listed median salaries without telling you where ME actually sits relative to the other branches. See Reason #63 already showed you part of the picture. This is the rest.

The Federal Reserve Bank of New York tracks wages, unemployment, and underemployment for recent college graduates by major, using American Community Survey data refreshed each year. The dataset now spans six consecutive releases, from roughly 2018 through 2024. Mechanical engineering appears in every one. It does not appear well.

In the most recent data, ME early-career median pay is $80,000. That ranks sixth out of seven named engineering branches. Computer engineering pays $90,000. Chemical and aerospace both pay $85,000. Industrial pays $83,000. Electrical pays $82,000. Only civil engineering, at $75,000, sits below you. At mid-career the order reshuffles slightly but the position does not improve. Chemical leads at $135,000. Computer follows at $131,000. Aerospace reaches $130,000. Electrical hits $123,000. Mechanical sits at $120,000, still second from the bottom (Federal Reserve Bank of New York, 2020-2026).

This is not a single unlucky snapshot. Average those six years and the pattern holds. ME's early-career average is roughly $71,000, again sixth of seven. Its mid-career average is about $109,000, fifth of seven. The ranking barely moves because the gap is structural, not cyclical. You already saw the plateau in Reason #27. The Fed data confirm it is not a feeling. It is a position on a chart that does not budge.

Now add underemployment. In the 2024 ACS release, 20.1% of recent ME graduates are working jobs that typically do not require a college degree. One in five. Computer engineering underemployment is 15.8%. Civil is 15.6%. Aerospace is 14.7%. Chemical is 17.9%. ME sits in the bottom half of that list too, outperformed by branches that pay more and place better (Federal Reserve Bank of New York, 2020-2026).

Then add the cost of the degree itself. Mechanical engineering is the discipline most likely to stretch past four years. Rigid prerequisite chains, annual-only course offerings, and a math and physics gauntlet that starts before core ME even begins all conspire to push the median closer to five or six years. See Reason #2. That extra year is not free. At an in-state public university it costs another $25,000 to $40,000 in tuition and fees. It also costs a year of earnings you did not collect. At ME's own early-career median, that is roughly $80,000 in forgone salary. The total opportunity cost of one extra year is north of $100,000 before you account for the compounding you missed in a retirement account. You paid more to enter at the bottom.

Grad school does not fix it. A master's does not reliably move you up the wage ladder in ME because employers price experience over letters, and the market already has two and a half candidates for every seat. See Reason #19 and Reason #34. The Fed's own data show ME's share with a graduate degree hovering around 39%, lower than chemical, electrical, aerospace, and miscellaneous engineering. Even the people who do chase more school are not rewarded with a proportionally steeper curve. The plateau is the plateau. More tuition does not tilt it.

So here is the arithmetic you were never shown on the brochure. You chose the engineering major that takes the longest to complete, pays near the bottom at every career stage, underemploys one in five of its graduates, and offers a mid-career ceiling that chemical, computer, and aerospace engineers pass on their way to somewhere higher. You did this because someone told you it was broad. Broad, in this context, meant cheap. Not for you. For them.

The data did not need to be this clear. But it is. Six years of Federal Reserve numbers, exposed by a single spreadsheet, quietly ranking you last among equals in a profession that already underpays its own. You earned the hardest degree on the menu and got the smallest check at the table.

References:

Federal Reserve Bank of New York. (2020-2026). The labor market for recent college graduates. https://www.newyorkfed.org/research/college-labor-market

Reason #66: Your Personal Life Is an Employer Subsidy

You move for the job. You leave behind a person, a city, a proximity to family that you will not get back on this timeline. You do it because mechanical engineering is a physical discipline and the openings are where the plant is, not where your life is. See Reason #20. You tell yourself it is temporary. It is not temporary. The next role is in another plant town chosen by rail access and tax abatements, and the one after that is wherever your sub-specialty still has funding. See Reason #11.

Other engineering branches do not extract this. A software engineer negotiates remote before accepting the offer. An EE in chip design can work from a dozen metros with active semiconductor clusters, most of them places people actually want to live. A CS grad picks a coast and stays on it. You pick the job and the job picks your zip code, your commute, your weekend radius, and by extension, the pool of people you will meet, date, befriend, and rely on for the next several years.

The entry ramp makes it worse. The internships that qualify you for entry-level are in the same plant towns, on the same shift schedules, demanding the same uprooting. See Reason #57. You vanish for a summer, then vanish again for the first job. The people you left behind adjust to your absence. Some wait. Many do not. You learn this when the distance stops being a logistics problem and starts being a verdict.

Once you are there, the schedule finishes what the geography started. ME is remote-proof. See Reason #30. The test lab, the build floor, the shaker queue, the supplier visit, the 2 a.m. line-down call. Your availability is not flexible because the hardware is not flexible. Date nights get canceled for thermal soaks. Weekends get eaten by qualification runs that could not get chamber time during the week. You are not lazy. You are tethered. And the tether is shorter than your friends in other fields will ever understand, because their jobs do not live in a building that smells like coolant.

The social cost compounds quietly. You work in rooms that skew 8:1 male. See Reason #43. Your peer network is small, homogeneous, and geographically scattered across plant towns that do not overlap. The informal connections that other professionals build through mixed workplaces, urban density, and overlapping social circles do not form as easily when your office is a manufacturing campus thirty minutes from the nearest downtown. You make friends at work because work is where you are. Then you change jobs and the friends reset because the zip code resets.

None of this shows up on a pay stub. That is the point. It is an uncompensated extraction. The company gets your proximity, your flexibility, your weekends, and your willingness to relocate. You get a salary that already trails your engineering peers. See Reason #20. The gap between what you are paid and what the job actually costs you is filled by your relationships, your geography, your time, and your health. In economics that gap has a name. It is a subsidy. You are the one paying it.

The younger version of you does not see this. The offer letter looks like a beginning, not a trade. You are twenty-two or twenty-five and the move feels like ambition. You pack the car, sign the lease, and promise everyone it is temporary. Two and a half years later the company outsources the entire engineering department, and you are standing in a town you did not choose, missing a person you did not intend to lose, holding a resume that qualifies you to do it all over again somewhere else. See Reason #46.

The brochure calls it opportunity. Your twenties call it back and get voicemail.