A Tale of Two Job Specifications 👍👎
Recently I came across two job specifications for roles that were broadly related to data and information systems. On the surface they looked similar enough, both requiring analytical thinking, technical skills and the ability to support organisational objectives. However, once I started reading them closely, the difference in quality between the two documents became immediately obvious. One specification was so vague that I found myself writing comments all over it in red, while the other provided genuine insight into the role and the technologies involved. It was a perfect example of how a well-written job specification can help both employers and candidates.
The first job specification described the responsibilities of a Senior Analyst role. It contained plenty of corporate language about supporting stakeholders, analysing data, promoting service improvement and contributing to organisational objectives. While none of these requirements were unreasonable, they were written in such broad terms that almost anyone could claim to meet them. Phrases such as "strong ICT skills", "experience of using computer packages" and "knowledge of databases and reporting tools" tell a candidate very little about what they would actually be doing day to day. The document left me wondering what technologies the team used, what systems they maintained and what skills would genuinely help somebody succeed in the role.
By contrast, the Information Systems Specialist specification immediately stood out because it contained specific technical requirements. Rather than simply asking for experience with "computer systems", it listed technologies such as Microsoft Endpoint Configuration Manager (MECM), Intune, Windows Server, Active Directory, VMware, Azure Cloud Solutions, Microsoft 365, Azure Virtual Desktop, PowerShell and backup and recovery systems. This instantly gives applicants a much clearer picture of what the role involves and allows them to assess their own suitability more accurately.
The most valuable aspect of this level of detail is that it creates a roadmap for professional development. Even if a candidate does not currently possess all the required skills, they can identify the gaps and begin learning. For example, someone with a background in software development or data analysis can see that gaining experience with Azure, Active Directory or PowerShell would make them more competitive for future infrastructure and systems roles. The specification effectively becomes a learning guide as well as a recruitment document.
There is also a significant advantage for employers. Clear specifications attract better-targeted applications. When applicants understand exactly what technologies and responsibilities are involved, they are less likely to apply blindly and more likely to tailor their applications appropriately. This saves time for hiring managers and increases the likelihood of finding candidates who genuinely fit the role. Vague specifications may cast a wider net, but they often generate large numbers of applications from people who are simply guessing whether they are suitable.
Ultimately, the Information Systems Specialist job specification demonstrates what good recruitment documentation should look like. It explains the purpose of the role, identifies the systems involved and provides enough technical detail for candidates to understand both the job and the skills required to perform it successfully. The Senior Analyst specification may have described the outcomes expected from the role, but the Information Systems Specialist specification explained how those outcomes would be achieved. As somebody actively trying to build a career in technology, I found the second document far more useful because it showed me exactly what I need to learn if I want to do that job in the future.
Comments