Marine Standards & Class Rules Engineer

Every merchant ship is built to a set of technical rules, and someone has to write and update them. This role does that. A rules engineer at a classification society (the organisations that set and check technical standards for ships, such as Lloyd's Register, DNV, ABS, Bureau Veritas, ClassNK and others) takes what the industry has learned about how ships fail and turns it into requirements that every designer and yard working under that society must follow. Called the same thing in most places, though titles such as rules developer, principal engineer (rules) or technical standards engineer are common.

This is a different job from the two it sits between. A naval architect designs a ship to the rules, and a marine surveyor checks that a particular ship meets them. The rules engineer works on the rules themselves: running calculations and tests to see whether a requirement is too weak or too strict, drafting new text, answering comments from industry, and explaining the reasoning in a technical background document so others can apply it consistently. Some societies also send engineers to international bodies such as the International Maritime Organization (IMO) and the International Association of Classification Societies (IACS), where the aim is shared requirements across many societies. The Common Structural Rules for oil tankers and bulk carriers are one result: several societies agreed one set of structural requirements instead of each keeping their own.

The effect of one change is large. A rule revised in an office in one city ends up in the design of every new ship of that type built under it, wherever it is built. That reach is why the work is slow and careful, and why a draft goes through consultation before it takes effect.

Most of the job is wording and persuasion, not calculation. Two engineers can agree on the physics and still spend weeks on whether a sentence says "shall" or "should," because the difference decides who is liable and what a surveyor can insist on. People who like exact language and patient negotiation do well. People who want to see a finished product from their work will find it frustrating, since a rule can take years from first idea to entry into force.

You will rarely be credited. Rules are published under a society's name, and good ones go unnoticed because nothing goes wrong. The role also pulls you towards compromise: the final text is usually the version every party could accept, which is not always the version you would have written alone. Pay is typically in line with senior engineering roles at the society, though specific figures vary widely by country and employer and are not reliably published.

The pressure comes in waves. New fuels such as methanol, ammonia and hydrogen, and new automation, mean rules have to be written for ship types with little operating history. Rules engineers are working in that gap now, which makes the work more interesting and less settled than it was a generation ago.

The usual route is a degree in naval architecture, ocean, marine, mechanical or structural engineering, followed by several years of design appraisal, surveying, shipyard or ship design work. Society job listings for principal engineers in rule development commonly ask for a relevant engineering degree, proficiency in engineering software and finite element analysis, and experience that lets you defend a technical position to other experts [happening now; ABS and Lloyd's Register recruitment listings, 2026]. Few people start in rules work directly; it is more often a move made after some years in design or survey. The route is similar in Europe, North America and East Asia, where the large societies have their rules departments, though language and local accreditation differ. Writing well matters as much as engineering depth, so technical report and standards writing is worth practising early.