The subsea project engineer is the one who turns a client's brief into an executable method: they define how the work will be done, calculate the auxiliary equipment needed, write the procedures and answer the offshore team's questions. They don't run the dive, but almost everything the diver does underwater has already been written down by someone in this role.
When a diver opens the job pack and finds a procedure with its sequence of steps, its sketches, its tool list and its acceptance criteria, there's someone behind that document. Usually it's a subsea project engineer, a role that's barely visible from deck yet determines a great deal of what will happen below.
It's a role that exists on both the contractor's side, where they design how to carry out what's been contracted, and the client's side, where they define what's being asked for and review what the contractor proposes. In both cases the output is the same: method, calculation and documentation.
What they do in practice
Turning scope into method
A client asks for a result: replace a component, inspect a structure, connect two lengths of pipe. The engineer translates that into a concrete sequence of operations that can be carried out with the resources available, in an order that makes sense and with checkpoints along the way. That translation is the essence of the role, and it's where experience shows.
Translating it well means having thought the job through from the point of view of whoever will do it: what visibility, what current, what access and what dexterity it's reasonable to expect. A procedure written by someone who has never seen an underwater job tends to be flawless on paper and unworkable in the water, and the team spots it on the first dive.
Engineering the auxiliary equipment
A large part of the technical work isn't in the final component, but in everything needed to place it. Lifting frames, guide tools, weights and floats, purpose-built tools, positioning jigs. All of that has to be designed, calculated and built, and it's the project engineering's responsibility.
This is where calculations that leave no room for guesswork come in: lifting loads with their dynamic coefficients from vessel motion, the stability of the piece during descent, buoyancy and trim, loads at the lifting points. The lifting and rigging arrangement that the diver finds on site comes from these calculations.
Write procedures
The procedure is the central deliverable. A good document describes the sequence step by step, identifies the critical points and what to do if something doesn't go to plan, defines the acceptance criteria and lists what's needed to carry it out. And it's written to be read in a control room by someone who's tired, not to show off: short sentences, clear sketches and no ambiguity on anything that matters.
That document also goes through client review and is usually integrated with the operation's risk assessment. Keeping the two consistent is the engineer's responsibility: a procedure that contradicts the risk assessment creates exactly the kind of confusion it was meant to prevent.
Data, measurement and as-built
Many interventions depend on measuring accurately before anything is manufactured. Determining the exact geometry between two points on the seabed so a piece can be fabricated to fit first time is a classic problem, and underwater metrology is the discipline that solves it. The engineer defines what's measured, with what method and to what tolerance, and then validates the data that comes back.
At the end of the job the mirror-image task happens: capturing what was actually carried out, with its deviations from what was designed, and leaving it documented for whoever maintains that installation ten years from now. It's the least glamorous part of the role and one of the most valuable.
What they don't do
They don't run the diving operation. Responsibility for how and when the water is entered belongs to the diving supervisor, and it doesn't transfer just because the engineer wrote the procedure. If conditions on site don't allow the plan to be carried out, it's the supervisor who decides to stop, and the engineer's role is to propose an alternative, not to push for the plan to be followed regardless.
Nor are they the client's representative, even though they sometimes work for one. These are different functions: one is technical and the other contractual, and on large projects they're held by different people precisely so the incentives don't get mixed up.
Where the people in this role come from
There are two pathways and both work. The first is the academic one: a degree in mechanical, naval, civil or structural engineering, followed by specialisation in the sector. It brings a solid grounding in calculation and standards, and it's the majority route at large companies.
The second is the trade route: divers and supervisors with years of campaign experience who train up on the technical side and move into engineering or planning. They bring something that can't be taught, which is knowing what is and isn't achievable underwater, and they tend to write the most workable procedures in the sector. It's one of the natural paths for anyone looking for career continuity without the physical exposure of campaign work.
What good teams usually do is mix both profiles. A flawless calculation that ignores operational reality and operational intuition with no calculation behind it fail in different ways, and together they correct each other.
What the job is like
There's also a dimension of accountability worth understanding before aiming for this role. The documents a project engineer signs have consequences: if a lifting calculation is wrong, someone can get hurt, and if a procedure omits a critical step, the error will surface at the worst possible moment. That accountability isn't shared with the team carrying out the work, it's taken on with the signature, which is why cross-checks between engineers aren't bureaucracy but a necessary safeguard.
It's mainly an office-based role, with trips to site at key moments: mobilisation, critical operations and close-out. That mix is exactly its appeal for a lot of people coming from a background at sea, because it keeps the link to real work without the long rotations.
The pace, though, is demanding during the preparation phases, when engineering has to be closed out against a mobilisation date that doesn't move. And during execution there are support on-call rotations, because when something doesn't fit a thousand kilometres away and fifty metres down, the call reaches engineering at any hour.
There are four skills that make the difference: fluent calculation and technical drawing, knowledge of the applicable standards and codes, the ability to write clearly, and technical English, because both the sector's documentation and its communication are mostly handled in that language.
The moment a campaign's success is decided
If you ask experienced people when an underwater campaign is won or lost, the answer is usually the same: in the preparation phase, weeks before anyone goes in the water. That's when it's decided whether the method is right, whether the auxiliary equipment is properly sized, and whether reasonable contingencies have been planned for.
That upfront work has an unglamorous side: imagining what could go wrong and preparing the response. What to do if the piece doesn't fit by a few millimetres, if the current exceeds what was expected, if a tool fails halfway through the operation, or if visibility rules out the final check. A procedure with alternatives already thought through avoids improvised decisions at the worst moment.
The other part is making sure the interfaces are closed off: with the vessel, with the diving crew, with the manufacturer of the piece, with the client. A large share of on-site problems aren't technical, they're coordination issues between parties who assumed different things. Catching those diverging assumptions before mobilisation is one of the least visible functions of the role and one of the most worthwhile.
And there's a third, which is knowing how much detail is useful. An overly long-winded procedure doesn't get read and ends up being worked around; one that's too sparse leaves important decisions to the moment's judgement. Finding that middle ground is a craft in itself, and it's learned by watching how the documents you write get used on site, which is one more reason to get on the boat now and then and listen to the team that executes them. The engineers the crew turns to when there's a problem are usually the same ones who showed up on deck when there wasn't one, and that reputation is built slowly and lost fast.
Why it's worth a diver understanding this role
For two practical reasons. The first is immediate: a diver who understands where the procedure comes from can offer concrete improvements before the campaign, and that input is welcome when it arrives in time. Feedback from deck is what separates a procedure that's followed from one that gets worked around on the fly.
The second is about career. It's one of the possible destinations when looking for continuity beyond work in the water, alongside supervision, inspection and client representation. It's worth knowing about early, because preparing for it takes years and is best done while still working. In the community of the sector it's easy to find people who have made that move, and in empleo you can see what profiles are being sought.
Frequently asked questions
Does a subsea project engineer have to be a diver?
It's not a requirement, and many come from an engineering degree without ever having dived. That said, operational experience shows a lot in the quality of procedures, and quite a few of the best professionals in the role come from the trade itself.
How is it different from the diving supervisor?
The engineer defines how the work will be done and documents it before the campaign. The supervisor runs the operation in real time and takes responsibility for the dive. A procedure neither replaces nor limits the supervisor's authority to stop an operation.
What training is usually required?
The most common route is a degree in mechanical, naval, civil or structural engineering, backed up with experience in the sector. There's also the route up from the trade, with added technical training, which is particularly valued for writing procedures.
Is it an office job or a field job?
Mainly office-based, with site visits at key moments of the project and remote support during execution. That mix makes it an appealing path for professionals who want to cut down on campaign time without leaving the sector.
Which part of the job is most underrated?
The final documentation. Capturing what was actually carried out with its deviations, and leaving it usable for whoever maintains the installation years later, isn't glamorous but it determines the project's long-term value.
Published 6 September 2026 · By Arthur More, professional saturation diver
Photo: Ken Lund · CC BY-SA via Openverse