From Cabling Engineer to Project Manager: How to Make the Move in ICT Infrastructure
Most ICT project managers did not start their careers managing projects. They started on site. Running cable, learning installation sequences, developing an instinct for what can go wrong and when. That background is not just useful in a project management role. In most cases, it is what makes the role work.
The challenge is that the move itself is not automatic. Technical competence on site does not translate directly into project management capability. The transition requires something deliberate.
What the project manager role actually involves in ICT
On an ICT infrastructure project, the PM role covers scope management, programme management, resource coordination, subcontractor management, client communication, and risk tracking. In practice, this means being the person who knows what every other person on the project is doing, where the dependencies are, and what needs to happen to keep delivery on track.
The technical background matters because it allows a PM to have real conversations with engineers, identify when a problem is being underestimated, and catch issues in drawings or programmes before they become delays. A PM without that foundation has to rely entirely on what other people tell them.
What makes the transition successful
Engineers who make the move effectively tend to share a few characteristics.
They are already doing informal coordination on site. Keeping track of what other trades are doing. Communicating scope changes. Flagging problems before they become visible. This is the same underlying pattern of thinking as project management.
They understand documentation. Testing records, as-built drawings, handover packs. Not just completing them, but understanding why they matter and what downstream problems poor documentation creates.
They are comfortable with uncertainty. Technical delivery is often about solving a known problem. Project management is often about managing a situation where the full picture is not yet clear.
What tends to hold engineers back
The most common reason experienced engineers do not make the move is that they have not been given the opportunity to manage a scope, even a small one. Without that first project management experience, the CV looks like a pure technical delivery background regardless of capability.
The second reason is hesitation around commercial awareness. Budget management, programme reporting, and client-facing communication all feel unfamiliar at first. They become less intimidating with exposure. The way to get that exposure is to ask for it on a project where a senior PM can provide oversight.
Certifications and qualifications
APM Project Management Qualification and PRINCE2 Practitioner carry the most weight in the UK infrastructure market. PMP is also recognised, particularly on internationally delivered projects.
Certifications are secondary to demonstrated experience. A PM who has delivered a complex project without a formal qualification is consistently preferred over someone with a qualification and no delivery track record. Certifications are useful when they support an existing experience base, not as a substitute for one.
Planning the move
The most effective path is a role that involves both technical delivery and an element of site coordination or scope management. Once that experience is documented and visible on a CV, the move into a formally recognised PM role becomes straightforward.
The move into project management does not require starting again. It requires building on what site experience has already developed and making that development visible.
If you are at a stage where project management looks like the right direction, our consultants can help identify roles that support that transition rather than delaying it.
