Director of Information Technology Job Description Template

In plain language: States the official job title, FLSA exemption status, employment type (full-time, exempt), and the position this role reports to and supervises.

Common mistake: Listing an informal title that does not match the payroll system or org chart — mismatches create confusion in performance reviews and make compensation benchmarking unreliable.

In plain language: A 3–5 sentence overview of the role's purpose, the organizational unit it leads, and the strategic outcomes it owns.

Common mistake: Writing a position summary so broad it could apply to any technology role — failing to tie it to the organization's specific scale, industry, or strategic priorities reduces its usefulness for both recruiting and performance management.

In plain language: Enumerates the duties the role must perform, clearly distinguishing essential functions (ADA-relevant) from secondary tasks.

Common mistake: Conflating essential functions with preferred activities — courts and HR tribunals look at the essential-function list when evaluating reasonable accommodation requests; vague or inflated lists create legal exposure.

In plain language: Defines the role's forward-looking responsibilities — IT roadmap, technology investment decisions, digital transformation ownership, and board or executive reporting.

Common mistake: Omitting budget ownership from strategic duties — without a stated budget scope, the role's authority is ambiguous and compensation negotiations become harder to anchor.

In plain language: Assigns ownership of the company's information security program, risk management obligations, and applicable regulatory compliance frameworks.

Common mistake: Listing compliance frameworks without specifying who is accountable for which controls — ambiguity between IT, legal, and compliance leads to gaps and audit findings.

In plain language: States minimum non-negotiable education, years of experience, and credentials the candidate must hold before being considered.

Common mistake: Setting qualification thresholds that screen out protected classes without documented business necessity — degree requirements and years-of-experience floors that exceed genuine job needs expose the employer to disparate-impact claims.

In plain language: Lists certifications, tools, and experience that are desirable but not mandatory, helping candidates self-select and ranking criteria for hiring decisions.

Common mistake: Blending required and preferred qualifications into a single undifferentiated list — this makes screening inconsistent and creates legal risk if different standards are applied to different candidates.

In plain language: States the salary range, bonus eligibility, benefits summary, work location, and any physical or travel requirements.

Common mistake: Omitting a salary range in jurisdictions where pay transparency is legally mandated — Colorado, California, New York, and Washington all require ranges on job postings; violations carry fines.

In plain language: Defines measurable outcomes the role is expected to achieve, giving both parties a basis for performance reviews and merit decisions.

Common mistake: Leaving performance expectations entirely out of the job description — when expectations are absent from the hiring document, performance improvement plans and terminations become harder to defend.

In plain language: Affirms the employer's commitment to non-discriminatory hiring and invites candidates requiring accommodations to request them.

Common mistake: Copying a boilerplate EEO statement without updating the company name or contact information — an inaccurate or generic EEO clause signals a careless process to both candidates and regulators.

A Director of Information Technology leads the planning, implementation, and management of an organization's technology systems, infrastructure, and IT staff. Core responsibilities include developing the IT strategy and budget, overseeing network and cloud infrastructure, managing cybersecurity and compliance programs, negotiating vendor contracts, and reporting on technology performance to executive leadership. The role bridges hands-on technical oversight with organizational strategy.

Most organizations require a bachelor's degree in Computer Science, Information Technology, or a related field, plus 8 or more years of progressive IT experience including at least 3 years in a management or leadership role. Common preferred credentials include ITIL v4, CISSP, CISM, or a master's degree in Information Systems. Budget management experience — typically $500K or more annually — and demonstrated experience with cloud platforms (AWS, Azure, or GCP) are widely expected at the director level.

A Chief Information Officer (CIO) is a C-suite executive with company-wide technology authority, board reporting relationships, and typically ownership of digital strategy and IT governance at the enterprise level. A Director of IT usually reports to the CIO, COO, or CEO and focuses on operational execution — managing the IT team, infrastructure, vendor relationships, and day-to-day technology performance. In smaller companies without a CIO, the Director of IT often absorbs strategic responsibilities as well.

A job description is generally not intended to be a binding employment contract, but courts in several jurisdictions have found that specific compensation promises or termination language in a job description can create contractual obligations — particularly if the document was signed or incorporated by reference into an offer. To protect at-will status, keep contractual terms in the employment contract and limit the job description to duties, qualifications, and general expectations.

In an increasing number of US jurisdictions, yes. Colorado, California, New York, Washington, and several municipalities require employers to include a compensation range on job postings. Even where not legally required, including a range reduces time-to-hire, improves candidate quality, and supports internal pay equity. Review the pay transparency laws applicable to every location where the role will be posted.

A job description is the internal HR document defining the role's duties, qualifications, reporting structure, and performance expectations — used for hiring, performance reviews, and compensation benchmarking. A job posting is the candidate-facing version published on career sites, which typically includes marketing language about company culture and benefits alongside the core role details. Both documents should be consistent but serve different audiences and purposes.

At minimum, review and update the job description annually during the performance review cycle. Additionally, update it whenever the role's scope changes significantly — such as when a new compliance framework is adopted, the IT team size changes by 20% or more, or the reporting structure is reorganized. An outdated job description undermines performance management and creates misalignment between expectations and actual duties.

The relevant frameworks depend on your industry. Healthcare organizations should reference HIPAA; payment processors or retailers should list PCI-DSS; SaaS companies serving enterprise clients commonly require SOC 2 Type II oversight; organizations with EU customers or employees must address GDPR. Naming specific frameworks in the job description ensures you attract candidates with directly relevant compliance experience and establishes clear accountability for regulatory obligations from day one.

It is generally best practice to have the new hire acknowledge the job description in writing — either as a standalone signature or as an attachment to the employment contract. Signed acknowledgment confirms the employee reviewed and understood the role's essential functions and expectations, which supports performance management and, where applicable, ADA accommodation determinations. Consult employment counsel about the best approach for your jurisdiction.