University IT job descriptions are, with remarkable consistency, bad. Not because the people writing them do not care — but because the process that produces them is designed for compliance, not recruiting. HR classification systems, committee review, legal sign-off, and grade-band consistency produce a document that satisfies every institutional requirement and repels qualified candidates.
The result shows up in your applicant pool: shallow, underqualified, or misaligned candidates who applied because no one else did. Then the search committee concludes the role is hard to fill and the search extends another 60 days. The actual problem is not the market — it is the job description. This post provides before-and-after rewrites for four high-demand higher education IT staffing roles, along with the principles behind them.
The first thing a candidate sees in most university IT postings is a requirements list: 10 bullet points of technical credentials, certifications, and experience years. This is backwards. Qualified candidates who are passively exploring — the ones you actually want — skim the opening and decide in 15 seconds whether to keep reading. If the opening communicates "here is what you must prove to be considered," the candidate who has three competing offers puts you last.
The opening should answer the question the candidate is actually asking: "Why would I want this job?" Lead with impact, mission, and the interesting work — not the credential checklist.
Work-life balance. Tuition remission for dependents. Pension contributions. Stable employment with genuine job security. Proximity to research and academic expertise. These are real advantages that many IT professionals — particularly those with families, academic backgrounds, or long-term career stability goals — value significantly. They are consistently buried in paragraph eight of the job description, after the 15-item requirement list.
Candidates who are weighing a university role against a private-sector offer need to see the full value proposition early. If they reach your compensation section and the salary is 25 percent lower than competing offers, they will close the tab unless they already understand what they are getting in return.
Salary transparency is now a legal requirement in Massachusetts, New York, Connecticut, Rhode Island, and several other states. Beyond compliance, hiding the compensation range wastes everyone's time — candidates who apply without knowing the salary discover the gap after three interviews and withdraw. The market has moved: candidates now view salary range omission as either a red flag or an indication that the range is indefensible.
Post the range. If the range is genuinely uncompetitive, address it directly in the description with the offsetting value: "The salary range for this role is $72,000 to $88,000. We recognize this is below market for some comparable roles and are transparent about what we offer in return." That honesty earns more candidate trust than a hidden range.
Before: "Minimum 5 years of experience in information security. CISSP or Security+ required. Experience with SIEM platforms, vulnerability scanning tools, and incident response. Must be able to pass background check. Salary: commensurate with experience."
After: "Help protect the data, research, and educational infrastructure of 18,000 students and faculty. As a Cybersecurity Analyst at [University], you will own threat detection and incident response for a campus environment unlike any corporate SOC — open networks, 200+ SaaS integrations, and research data from ITAR-controlled projects to student wellness records. You will work alongside a team that takes security seriously, with access to emerging research in cybersecurity directly from faculty partners. We offer a $78,000–$95,000 salary, generous pension contribution, tuition remission for dependents, and a hybrid schedule. 3+ years of security operations experience required; SIEM familiarity preferred."
Before: "Extensive knowledge of Workday Student module required. Experience with SIS configuration, testing, and data validation. Ability to work with cross-functional teams. Bachelor's degree in Computer Science or related field."
After: "Join the team running one of the most complex Workday Student implementations in the Northeast. We are mid-migration from PeopleSoft Campus Solutions and looking for a Functional Analyst who has been through this before — someone who knows what a clean Student record import looks like and can translate Workday configuration options into decisions faculty governance can understand. This is a two-year contract engagement with a conversion track. $95–$115/hour. Higher education ERP experience required; Workday Student preferred."
Before: "5+ years of experience in data engineering. Proficiency in SQL, Python, and ETL tools. Experience with data warehouse design. Knowledge of FERPA preferred."
After: "Build the data infrastructure that tells us which students are succeeding and which are falling behind — before it is too late to help. As a Data Engineer at [University], you will design and maintain the institutional data warehouse integrating Banner SIS, Canvas LMS, Salesforce CRM, and our financial aid system into a coherent platform for enrollment analytics, student success modeling, and institutional effectiveness reporting. You will work directly with the VP of Enrollment and the Provost's office — your work has visible, measurable impact on the students we serve. $105,000–$125,000, full benefits, tuition remission. FERPA data governance experience is a plus; we will train the right candidate."
Before: "Experience with AWS, Azure, or GCP required. Knowledge of cloud security frameworks. Scripting experience preferred. Must have demonstrated experience in infrastructure management."
After: "Architect and manage the cloud infrastructure that powers research computing, student services, and administrative operations for a leading research university. You will own our AWS and Azure environments — including migration from on-premise legacy systems, research computing cluster management, and the hybrid identity infrastructure connecting cloud and campus systems. The work is technically interesting, the team is collaborative, and the stakes are real. $98,000–$118,000, hybrid schedule, tuition remission. 4+ years of cloud infrastructure experience required."
Each rewrite follows the same logic: open with the interesting work and the impact, include the compensation and benefits early, set realistic requirements that do not exclude qualified candidates, and close with the institutional advantages that make a university role genuinely worth choosing.
Writing job descriptions this way requires pushing back against the institutional process that produces the committee-drafted compliance document. That is a political challenge, not just a writing challenge. A higher education IT staffing partner can support this process by advising on how peer institutions are positioning roles and what the market is responding to. Overture Partners regularly provides job description consulting to university HR and TA teams as part of our IT staffing in the Boston area practice.
Still not getting qualified applicants? Let Overture handle the sourcing and deliver candidates who fit. Our higher education IT staffing team is ready to help.