Job boards for ICT consulting roles are full of it: "ITIL certified preferred," "PMP or Prince2 required," "Cisco certification advantageous." Scan enough of these listings and a clear picture forms in your head - there is a specific credential, maybe two, that unlocks the door. Get the cert, get the job. The problem is that the picture is built from recruiter shorthand, not from what the role genuinely demands once you're inside it.
Where the assumption comes from
Certifications are easy to screen for. A hiring manager sorting through 200 applications can filter on "ITIL v4" in thirty seconds; assessing whether someone can actually analyse a client's ICT architecture takes considerably longer. The assumption calcifies because certifications function as proxies, and proxies get repeated until they sound like requirements. Add to that the fact that training providers have a commercial interest in positioning their certificates as essential, and the myth becomes self-reinforcing.
What the role actually requires
The ESCO data for ICT Consultant lists twenty essential skills and knowledge areas. A specific certification is not among them. What is there tells a more nuanced story.
Several essentials are squarely analytical: analysing ICT systems, analysing software specifications, and verifying formal ICT specifications all sit on the required list. These are not things you absorb by passing a multiple-choice exam. They require sustained practice with real systems, real documentation, and real clients who give you incomplete information and expect coherent answers.
Project work is also core, not peripheral. Creating project specifications, managing ICT projects, and managing changes in ICT systems are all essential. So is managing contracts. A consultant who cannot navigate the commercial and administrative layer of a project is only doing half the job, regardless of what badges they hold.
Then there is the client-facing dimension. Identifying customer requirements and providing ICT consulting advice are both on the essentials list, which points to something the certification narrative tends to obscure: this role requires you to translate between technical reality and business need, not relying solely on the technical side. ICT sales methodologies appears as essential knowledge, which will surprise people who think of consulting as purely advisory. Understanding how solutions get sold and positioned is built into the role's core.
Legal requirements of ICT products is also essential knowledge. Compliance, licensing, data governance - these matter in practice and they do not come from a vendor certification.
What people miss
The three essentials that genuinely catch people off guard are the specification-related ones: analysing software specifications, creating project specifications, and verifying formal ICT specifications.
Most people picturing an ICT consultant imagine someone presenting recommendations in a boardroom, or running a discovery workshop, or writing a strategy document. The specification work sits underneath all of that and rarely makes it into the job ad headline. Being able to read, write, and verify formal technical specifications is a craft skill built over time through exposure to real projects. It is also the kind of skill that separates consultants who give advice that actually gets implemented from those whose recommendations gather dust.
Monitoring system performance and managing standard enterprise resource planning systems are also on the essentials list. These push the role closer to hands-on technical engagement than the "trusted advisor" framing of most consulting job ads suggests. An ICT Business Analyst and an ICT consultant share some of this territory, but the consultant's essentials list has a broader operational reach.
Visual presentation techniques appears as essential knowledge too, which is easy to dismiss as a soft-skills filler. It is not. A consultant who cannot make a complex system analysis legible to a non-technical stakeholder will struggle to get recommendations approved, regardless of how technically sound those recommendations are.
The verdict
The assumption is not completely wrong and it is not completely right. Specific certifications can signal relevant knowledge in particular domains, and some clients or employers will ask for them. But the ESCO essentials list for this role contains nothing that maps to a single required credential. What it contains instead is a demanding combination of analytical rigour, project management capability, client communication, commercial awareness, and legal literacy. That combination takes time and varied experience to build. A certification might accelerate one part of it. It will not substitute for the whole.
If you have been holding off on pursuing ICT consulting because you assumed you needed a particular certificate first, the full requirements breakdown at Proskiro's ICT consultant profile is worth reading before you make that call.
