2026-03-13

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.


A wide tree stump with visible growth rings sits in a cleared field with no young trees growing around it.




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.


Rows of typists at desks in the Navy Department typing pool, Washington DC, circa 1918, doing structured document work that machines eventually replaced.



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



Ancient Babylonian clay tablet in a museum case, labeled "Complaint about delivery of the wrong grade of copper, about 1750 BC."

2026-03-12

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.

Rusted cars sit abandoned in desert scrubland beside a wooden post stacked with directional signs pointing to distant cities along Route 66.





Reason #65: Your Diligence Is the Blueprint for Your Replacement

They will ask you to write it all down. Not because they want to improve quality. Because they want to email it.

It starts with a reasonable request. Document your design process. Map your workflows. Write procedures for how you select bearings, size shafts, set tolerances, run thermal calcs, validate test fixtures. They call it ISO 9001. They call it quality management. They call it "institutional knowledge capture." You do it because it sounds responsible, and because your name goes on the document, and because you were raised to believe that good engineers leave clean records. See Reason #40.

Then the procedures leave the building. Not as training material for the new hire down the hall. As an attachment to a contract engineering firm in another time zone. Your step-by-step becomes their checklist. Your judgment calls become their dropdown menus. Your institutional knowledge, the kind that took you a decade to build and a week to type, becomes the onboarding packet for someone billing at a third of your rate (see Reason #24).

This is the trick. Nobody tells you during the documentation push that you are writing your own replacement manual. The language is always improvement. Standardization. Repeatability. Risk reduction. The moment the PDF is final and the revision block is signed, it belongs to the company. And the company has already decided what to do with it. You have no professional body that will intervene, no guild clause that limits how your work product is deployed (see Reason #13).

The problem is that a procedure is not understanding. You can write down that a stator vane needs a specific trailing-edge radius for a given pressure ratio. You cannot write down the twenty iterations that taught you why, or the field return that taught you what happens when someone rounds it. A checklist can be followed. A feedback loop cannot be shipped (see Reason #33). The offshore house follows step four because step four says so. You followed step four because you watched step three fail on a test stand in 2014. That gap does not show up until warranty claims start arriving, and by then the people who understood the gap have been let go or moved on.

Management knows this will happen. They have seen it before, at Boeing, at Enphase, at every aerospace OEM that hollowed out its engineering bench in the name of cost reduction. They do it anyway because the savings land this quarter and the warranty costs land three years from now, under someone else's budget, on someone else's watch (see Reason #23). When the quality collapses, the fix is not to bring the work back. The fix is to add more review layers on top of the outsourced work. More checklists to check the checklists. More of your time spent verifying someone else's output instead of producing your own.

You will be asked to document everything you know. You should understand why.


Classical Chinese painting of scholars writing at red desks under a tiled pavilion while officials observe from above, knowledge captured on paper for someone else's use.


Reason #64: Four Years of Calculus to Stand Next to a Plumber

Earlier this year Sander van't Noordende, global CEO of Randstad, the largest staffing company on earth, told Fortune that young people should stop chasing office careers and learn a trade instead. When he listed the roles in demand, he named "skilled trades, mechanical engineers, machine operators, maintenance engineers, forklift drivers, truck drivers" (Royle, 2026). One list. One breath. No comma separating you from the forklift driver.

That is how the world's biggest labor clearinghouse categorizes your profession. Not alongside software engineers or data scientists. Between skilled trades and machine operators. See Reason #16. The man whose company places half a million workers a week filed your degree in the same demand bucket as jobs that require a CDL or a two-year apprenticeship. His advice to young people was blunt: stop following your passions, learn a craft or a trade, make a living. He was not talking about your profession as separate from that advice. He was including it.

He is not wrong about the demand. He is revealing how employers see you. The engineering staffing segment alone is a $10.4 billion market, and the temporary and contract share of all U.S. recruitment revenue sits near 89% (PGC Group, 2024). ASME has noted that mechanical engineering is "particularly well suited to contract placements" because projects surge and recede (Puente, 2023). That is not how you describe a profession. That is how you describe a trade with seasonal swings. See Reason #45.

The physical reality matches the classification. Your work is plant-bound, shift-adjacent, and tied to production calendars, see Reason #20. The dedicated technician layer that once separated the engineer from the floor is thinning. Companies that used to keep a tech on the fixture and an engineer on the drawing now want one person doing both. You troubleshoot the rig, then write the deviation, then update the model, then argue about the torque table. The hands-on work that belonged to a two-year graduate is now folded into your job description, but your salary does not reflect a second role. It reflects a plateau, see Reason #27.

Meanwhile the trades are closing the gap from below. A master plumber in a mid-cost metro clears $85,000 with zero tuition debt and a two-year ramp. A journeyman electrician on a data center corridor pushes past $100,000 with overtime. You spent four years on thermodynamics and $120,000 in tuition to land in the same demand bracket, on the same style of contract, listed on the same staffing requisition next to the same set of trades.

Nobody held a meeting and voted to reclassify mechanical engineering. It happened one requisition at a time. Hourly postings where salary used to be. Contract terms where permanent used to be. Hands on the fixture where a tech used to be. The CEO of Randstad did not cause this. He just said it out loud.


References: 

PGC Group. (2024, December 3). US staffing industry 2023 in review & trends to watch in 2024. https://pgcgroup.com/blog/us-staffing-industry-2023-in-review-and-trends-to-watch-in-2024

Puente, J. (2023, December 21). Contract staffing is popular, but has its downsides. ASME. https://www.asme.org/topics-resources/content/contract-staffing-is-popular%2C-but-has-its-downsides

Royle, O. R. (2026, January 6). The college-to-office path is dead: CEO of the world's biggest recruiter says Gen Z grads need to consider trade and hospitality jobs that don't even require degrees. Fortune. https://fortune.com/2026/01/06/college-to-office-path-dead-ceo-randstad-recruiter-gen-z-millennial-grads-trade-jobs/


A 1930s sedan with brooms lashed to its front bumper as a makeshift street sweeper, a man watching and grinning.


2026-03-11

Reason #63: One in Five of You Will Work Without Using the Degree

You picked mechanical engineering because it sounded broad. Flexible. The one that keeps your options open. That reputation is the entire sales pitch, and it collapses the moment you compare ME to the other engineering disciplines on any measure that actually matters. See Reason #8.

The Federal Reserve Bank of New York tracks labor market outcomes for recent college graduates by major every year, drawing from the U.S. Census Bureau's American Community Survey. The data cover unemployment, underemployment, and median wages for graduates ages 22 to 27, broken out across more than seventy fields of study. Across six years of data, from roughly 2019 through 2024, a pattern holds without exception: among the named engineering disciplines, mechanical engineering pays less and places worse than nearly all of them. Table 1 lays it out. In 2024, ME's early-career median wage was $80,000. Computer engineering paid $90,000. Aerospace and chemical engineering both paid $85,000. Industrial paid $83,000. Electrical paid $82,000. Only civil engineering, at $75,000, paid less. By mid-career the gap widens. Chemical engineering hits $135,000. Computer engineering, $131,000. Aerospace, $130,000. ME sits at $120,000. Still second to last. A chemical engineer earns $15,000 more per year at the same career stage, doing work of comparable difficulty, with a comparable unemployment rate. Over a twenty-year mid-career window, that is $300,000 in lost earnings before you account for compounding.

Table 1. Median Wages by Engineering Major, 2024 (Ages 22-27 and 35-45)

Major Early Career Mid-Career ME Deficit (Mid)
Computer Engineering $90,000 $131,000 -$11,000
Chemical Engineering $85,000 $135,000 -$15,000
Aerospace Engineering $85,000 $130,000 -$10,000
Industrial Engineering $83,000 $100,000 +$20,000
Electrical Engineering $82,000 $123,000 -$3,000
Mechanical Engineering $80,000 $120,000
Civil Engineering $75,000 $115,000 +$5,000

Source: Federal Reserve Bank of New York, The Labor Market for Recent College Graduates, February 2026 (2024 ACS data).

The underemployment numbers are worse, and they do not move. Underemployment, in the New York Fed's definition, means working in a job that does not typically require a bachelor's degree. For ME, that rate has hovered between 15.8 and 21.3 percent across every year the Fed has published this data. One in five ME graduates, year after year, ends up in a job that did not need the degree. That is not a blip. It is structural. Table 2 ranks the engineering disciplines by underemployment. In 2024, ME's rate was 20.1 percent. Aerospace was 14.7. Civil was 15.6. Computer engineering was 15.8. Chemical was 17.9. ME was worse than all of them. The only engineering categories with consistently higher underemployment are the vague ones: general engineering, miscellaneous engineering, and engineering technologies. The categories that exist because someone could not or did not specialize.

Table 2. Underemployment Rate by Engineering Major, 2024

Major Underemployment Unemployment
Aerospace Engineering 14.7% 2.2%
Civil Engineering 15.6% 2.3%
Computer Engineering 15.8% 7.8%
Chemical Engineering 17.9% 4.7%
Mechanical Engineering 20.1% 4.4%
Electrical Engineering 21.1% 3.2%
General Engineering 31.1% 4.5%
Miscellaneous Engineering 26.4% 3.7%

Source: Federal Reserve Bank of New York, The Labor Market for Recent College Graduates, February 2026 (2024 ACS data). Underemployment = share working in jobs that typically do not require a bachelor's degree. Italicized rows are non-specific/catch-all categories.

That last point deserves a second look. The "Swiss Army knife" argument says ME's breadth is an asset. If that were true, you would expect ME graduates to land degree-required jobs at a higher rate than graduates in narrower fields. The data say the opposite. Aerospace engineers study a tighter curriculum and have lower underemployment. Chemical engineers cover fewer domains and get placed more often. The breadth does not help you land a job. It helps employers slot you into whatever opening they cannot fill with someone who actually specialized. You become the fallback candidate, not the first choice. And because this is not a one-year anomaly, Table 3 shows ME's numbers across six consecutive years of ACS data. The numbers shift slightly. The ranking does not.

Table 3. Mechanical Engineering Underemployment, 2019-2024

ACS Year Underemployment Unemployment Early Career Mid-Career
~2019 21.3% 3.7% $65,000 $100,000
2020 19.4% 4.4% $68,000 $104,000
2021 15.8% 5.3% $70,000 $105,000
2022 20.3% 1.5% $70,000 $111,000
2023 19.4% 1.5% $75,000 $115,000
2024 20.1% 4.4% $80,000 $120,000

Source: Federal Reserve Bank of New York, The Labor Market for Recent College Graduates, annual releases 2020-2026. Historical data recovered from Internet Archive (Wayback Machine) snapshots. One in five ME graduates works a job that does not require a bachelor's degree. This has not changed in six years.

The 2021 dip to 15.8 percent was a COVID-era labor shortage. Employers were hiring anyone with a pulse and a degree. It snapped back to 20.3 percent the following year and has stayed there. The wage growth from $65,000 to $80,000 over six years looks like progress until you measure it against inflation. The Consumer Price Index rose roughly 25 percent over the same window. In real terms, ME early-career pay is flat or declining.

Nobody who has this data in front of them picks ME over chemical, electrical, civil, computer, or aerospace engineering. The coursework is comparably difficult. The time to degree is the same. The difference is what happens after. You graduate into a market that pays you less, places you worse, and treats your "versatility" as a discount rather than a premium. The other engineers are not just happier (see Reason #38). They are better compensated for the same years of effort, by every measure the Federal Reserve tracks.


References:

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


A single bird perched on power lines against a gray sky, still while the wires stretch empty in every direction


2026-02-20

Reason #62: The Tools Aren't Yours Either

You spend two years getting fast in SolidWorks. You learn the shortcuts, the assembly mates, the way the BOM export talks to your company's ERP. You build templates. You know where the configurations break and how to fake a sheet metal flat pattern when the algorithm chokes. Then you switch jobs and the new shop runs Creo. Everything resets. See Reason #56.

This is not like switching from Python to Java, where the logic carries and the syntax is a weekend. CAD platforms are ecosystems. The sketcher behaves differently. The constraint logic is different. The surfacing tools assume different workflows. The PDM vault has its own rules, its own check-in behavior, its own way of making your life difficult when a reference breaks. Your fluency was never in "mechanical design." It was in one company's licensed installation of one vendor's software on one IT department's image. You take none of it with you.

And the industry is fractured enough to make this hurt every time you move. Aerospace lives in CATIA and NX. Automotive splits across NX, CATIA, and Creo. Consumer products leans SolidWorks. Heavy equipment has pockets of Inventor. Some shops still run legacy seats they cannot afford to migrate. No standard won, so your resume becomes a list of platform allegiances that hiring managers scan like passports. The wrong stamp and you do not get past the filter. See Reason #1. When there are two and a half candidates for every seat, the one who already knows the tool gets the call. See Reason #34.

Software engineers pick up new frameworks because the abstractions transfer. A frontend developer moving from React to Vue is productive in a week. A controls engineer switching PLC vendors at least carries a logic structure that maps. Your move from SolidWorks to NX is not an abstraction shift. It is a muscle-memory rebuild, and it happens on the clock, under pressure, while the project schedule pretends you are already competent. See Reason #54.

The simulation side is the same story. You learn ANSYS at one company, then the next shop runs Abaqus, or Nastran, or a proprietary solver wrapped in a workflow you have never seen. Your FEA theory is identical. Your button knowledge is worthless. And button knowledge is what gets the model out the door by Thursday.

Nobody advertises this cost. The degree teaches you "engineering principles," and the career teaches you that principles do not matter until they are inside a specific tool on a specific seat that a specific employer is willing to pay for. Your competence is rented, not owned. The moment you walk out, the license stays behind, and so does most of what made you efficient. See Reason #8.

You will learn the new platform. You always do. It will take months, and during those months you will feel like an intern with a decade of experience and nothing to show for it.


Worn stone floor with a rectangular outline and parallel groove marks, traces of something removed and nothing left behind.


2026-01-30

Reason #61: It's Business Administration, With Consequences

You remember how engineering students talk about business majors. The jokes are a team sport. “Group projects.” “PowerPoints.” “Networking.” You say it with the smug relief of someone who survived thermo and earned the right to look down.

Then you graduate and your week becomes their week. See Reason #9. You are not designing a machine. You are herding a schedule. You are aligning stakeholders, routing approvals, updating trackers, and polishing a deck that exists to make yesterday’s decision look inevitable. The work that moves is the paperwork, and the paperwork is what you ship. See Reason #33

Mechanical just adds a special penalty: the moment something gets real, you inherit the mess. A test pops. A fitting weeps. A bracket sings at one speed only. The install “doesn’t match the drawing” because the drawing never met the install. Purchasing picked the vendor. Sales picked the date. Manufacturing picked the shortcut. Management picked the headcount. But when the hardware fails, it becomes “an engineering problem,” which means it becomes your problem. You spend the morning writing the story and the afternoon cleaning up the consequences, with your fingernails paying rent either way.

This is what a mature field does to you. The exciting choices are upstream and already locked. You inherit integration, tolerance, compliance, cost, and risk, repeated on platforms that are “proven” right up until they are not. You become a custodian of other people’s decisions. See Reason #14 The day-to-day is mind-numbing because it is designed to be auditable, not satisfying. See Reason #26 The center of the discipline barely moves, but the bureaucracy around it grows like mold. See Reason #35

And if you actually wanted to be close to the hardware, hands on, solving the real problems, you probably should have gone MET. In most plants, that is where the practical troubleshooting lives, where you get credit for the fix, and where your skill set compounds into the kind of competence that travels well to other sites and becomes very hard to replace at your own. Meanwhile the ME title often buys you the privilege of being the paperwork wrapper around the people doing the physical work. See Reason #16. You can call that “engineering leadership” if you need to sleep.

The final insult is that once your job becomes packets, portals, checklists, and closeouts, it becomes portable. Then it becomes outsourced or it becomes scripted. See Reason #40. You mocked business majors, then you did their job, and you still ended up in the corner of the plant wiping somebody else’s decision off a failing assembly.


Monkey in suit with hat and cane



2026-01-29

Reason #60: No Matter What They Tell You, There Are Winners, and You Aren’t One

Economist Steven E. Landsburg once put it bluntly: “in the economy, there is no such thing as a zero-sum game.”, you always end up with winners and losers. Mechanical engineering just teaches you what it feels like to be the loser while the profession insists the pipeline is healthy. See Reason #39. When the establishment starts publishing “debunking” pages, see Reason #59, it is not because everything is fine. It is because it needs you to keep walking forward anyway.

So who wins? The buyer wins. See Reason #23 and Reason #45. The people who get cheap, disposable educated labor and call it “opportunity.” In a crowded market, wages do not rise to meet difficulty. They sink to meet desperation, see Reason #18, and the pipeline keeps refilling. See Reason #1. The taxpayer pays for the pipeline through public universities, loan systems, tax policy, and contracts, and the buyer gets to shop the output at a discount.

That is why the biggest ME employers look the way they do. Engineering services firms sell your hours to someone else’s program. Manufacturers keep you around to absorb the physical remainder that software cannot wave away. Government and primes turn appropriations into schedules, and you turn schedules into signoffs. The iron triangle gets fed, and you get told to be grateful for “stability.”

The day-to-day mechanics make the arrangement obvious. You do the integration pain. You chase a supplier cert, discover the RoHS paperwork lapsed, wait for the vibration rig, renegotiate a casting tolerance shift that just broke your stackup, and rebook the thermal soak because the chamber is full. Then you compress that mess into a slide that reads “risk mitigated.” See Reason #26 and Reason #9. Your real training is pressure and slide decks, not instruction. See Reason #54. In ME, the report becomes the product because the report is what survives the institution. See Reason #33.

Engineering management wins in a smaller, uglier way. The VP wants dates. The director wants a clean narrative. The department head wants someone to “own” the action items. They are the interface, the capos that translate power into tasks. If you absorb the chaos quietly, they look effective. If you refuse to promise miracles, you look like the blocker. Being needed turns into being used, right up until you are used as the explanation. See Reason #55.

You could tell yourself the escape hatch is independence, but ME keeps that door narrow. Your credibility is rented from the institution, along with its tools, accounts, test evidence, and liability shield. See Reason #56. Even the “hang your own shingle” fantasy usually collapses into more gates, more permission, more dependence. See Reason #58.

There are winners, yes. They are just not the ones still up at night rewriting the DV plan.


Tall wooden totem with painted mask, standing in fallen leaves, layers piled like a hierarchy.


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 a...