The maritime and industrial engineering world has long operated on a sacred hierarchy. The Chief Engineer is the apex of technical authority aboard a vessel, inside a power plant, or at the helm of any heavy industrial operation. Years of sea time, endorsements, class certifications, and hard-earned experience are supposed to guarantee a certain floor of competence.

They do not.

What rank guarantees is authority — and authority, unchecked by genuine competence, is one of the most quietly catastrophic forces in any engineering environment.

This article is not an attack on Chief Engineers. Some of the most technically brilliant engineers alive hold that rank, and they wear it with the humility that true expertise tends to produce. This article is about the other kind — the ones who climbed the ladder through tenure, politics, or sheer attrition, and who now wield their four-ring authority like a weapon against anyone who dares question their judgment.

These are the dangerous ones. And in high-stakes engineering environments, they harm people.

Engineering is a discipline that punishes arrogance eventually. The laws of thermodynamics do not care about your rank. A crankshaft does not respect seniority. Seawater does not negotiate.

But inside a hierarchical organization — a ship, a refinery, a power generation facility — the reckoning can be delayed, sometimes long enough that the incompetent senior engineer retires before the consequences arrive. In that delay, something deeply dangerous takes root: the normalization of rank as a proxy for technical truth.

It works like this. A Second Engineer raises a concern about an anomalous vibration reading from the port main engine. He has pulled the trend data, cross-referenced it with the manufacturer’s manual, and believes the issue is early-stage crankshaft deflection that could escalate into bearing failure. He is almost certainly right.

The Chief Engineer, who has not personally run a deflection check in eleven years and does not particularly want to hear about a problem that would complicate his schedule, dismisses it. “I’ve been doing this for thirty years. That’s normal for this engine at this RPM.”

End of discussion. Two weeks later, the engine throws a bearing at sea in heavy weather.

This exact sequence — with minor variations in machinery type and geography — has repeated itself across the global engineering industry more times than any of us want to count.

Aviation fixed this — or at least significantly addressed it — through a framework called Crew Resource Management (CRM). After a string of catastrophic accidents in the 1970s and 1980s where junior officers had the correct information and said nothing, the aviation industry fundamentally restructured how authority and technical input interact in cockpits.

The result was a cultural revolution: a First Officer is not only permitted to challenge a Captain’s technical judgment — they are required to. The hierarchy remains intact for decision-making, but technical input is actively solicited across all ranks, and dissent is protected.

The maritime and heavy engineering industries have made gestures in this direction — ISM Code requirements, SMS documentation frameworks, toolbox talks, and safety meetings. But the culture in too many engine rooms remains stubbornly anchored in rank-based authority, where a Chief Engineer’s technical opinion is treated as fact, not input.

The danger is structural. The solution must be cultural.

Not every technically weak Chief Engineer is aware of their limitations. Either way, the behavioral signatures are remarkably consistent.

It would be convenient if the only consequence of a rank-first, competence-second engineering culture was broken machinery. Machinery can be repaired. The real costs are harder to quantify and harder to recover from.

The best Chief Engineers share a counterintuitive quality: they are visibly uncertain about the right things.

They will tell you exactly what a particular piece of machinery should sound like at a particular load, with the confidence of someone who has listened to it for years. But ask them about a diagnostic they haven’t performed recently, or a system change implemented after their core training, and they will say: “Let me check that before I answer.” They will pull the manual. They will call the maker. They will ask the Second Engineer who has been working with the new control system daily.

This is not weakness. This is the epistemological discipline that keeps people alive in high-stakes environments.

They also create psychologically safe technical environments. Junior engineers bring them problems early, because bringing problems early is rewarded. Anomalies get documented and discussed, not buried. Disagreements about diagnosis get worked through with data, not resolved by rank.

And they stay current. They attend technical seminars. They read class society publications. They engage with new technology rather than dismissing it. Their value is not locked in the certification they obtained a decade ago but in the quality of their current thinking.

It is unfair to place the entire burden of this problem on individual Chief Engineers. The organizations that appoint, deploy, and retain them bear significant responsibility. Shipping companies and industrial operators that promote engineers based primarily on sea time rather than demonstrated technical judgment are creating the conditions for rank-over-competence cultures.

Organizations serious about engineering culture need to:

The engineering profession has traditionally not celebrated uncertainty. The expectation is competence, authority, precision — an engineer is supposed to know the answer. There is a cultural discomfort with the admission of not knowing that runs deep, and it runs deepest in the ranks where admitting uncertainty feels most threatening to status.

But consider this: in complex, high-energy, high-consequence systems, the most dangerous thing an engineer can do is be confidently wrong. The second most dangerous thing is to create an environment where being confidently wrong goes unchallenged.

The Chief Engineer who says “I want the Second’s diagnostic on this before we decide” is not showing weakness. They are demonstrating exactly the judgment that makes someone safe to put in charge of a multi-million dollar, life-safety-critical engineering plant.

This is a conversation the engineering industry needs to have more openly, more persistently, and with less deference to rank in the having of it.

If you are a junior engineer who has seen this dynamic play out — who has been in that control room when the technically wrong Chief ended the discussion with authority rather than argument — you are not imagining it, and you are not alone. Document what you observe. Raise concerns through formal channels. Find the mentors and organizations that reward your competence rather than your compliance.

If you are a Chief Engineer reading this: the fact that you are reading it — that you sought out serious professional content, that you are willing to engage with uncomfortable questions about your profession — already puts you in a different category from the engineers this article is warning about. Stay curious. Stay humble. The engineers beneath you are watching how you handle what you don’t know just as closely as how you handle what you do.

And if you are in a position of organizational authority: the culture in those engine rooms is your responsibility. The silent Second Engineer who didn’t push back hard enough — he learned that silence from somewhere.