CHIEF INFORMATION OFFICER
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc as headings; can fold minor metadata into short
or drop it. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info. Let's parse the posting: - Requisition ID: 24677 (metadata) - Work Location: OFFICE OF THE CHIEF INFORMATION OFFICER - City: FT. LAUDERDALE - POSITION GOAL: description about CIO responsibilities. - Essential Performance Responsibilities: includes a link to website and job code. The actual responsibilities are described in the POSITION GOAL? Actually the POSITION GOAL is a description. Then "Essential Performance Responsibilities" says to review the complete job description via link. So we have no explicit list of responsibilities besides the POSITION GOAL. We can treat POSITION GOAL as About the role? Or maybe we need sections: About the role (POSITION GOAL), Responsibilities (maybe we can extract from POSITION GOAL? But we need to not invent. The posting says "Essential Performance Responsibilities To review the complete job description, access the following website...". So there is no explicit list given; we should not create a Responsibilities section with placeholder. So we should omit Responsibilities if no specific content. - Minimum Qualifications & Experience: list of qualifications. That's Requirements/Qualifications. - Preferred Qualifications & Experience: same as minimum? Actually repeats same link. No additional content. - SIGNIFICANT CONTACTS-frequency, contact, purpose: description of contacts. - Physical Requirements: Light work description. - TERMS OF EMPLOYMENT: Salary and benefits shall be paid consistent with District's approved compensation plan. Length of work year and hours of employment shall be those established by the School Board. - Link To Job Description: repeated. - Advertisement Window: 09/15/2026 - Open Until Filled - Work Calendar: 244 Day Cal - Classification: Exempt - Compensation: Educational Support Management Association of Broward, INC. (ESMAB) PAY BAND S - $123,485.00 - $224,395.00 Thus we have specific content for: - About the role: POSITION GOAL paragraph. - Requirements/Qualifications: Minimum Qualifications & Experience (list). Could split into Requirements (minimum) and Qualifications (preferred) but preferred is same as minimum? Actually preferred qualifications section repeats same link but no extra detail. So we could combine into Qualifications section. - Skills: Proven skills in written and verbal communication, vendor and contract negotiation, budget preparation and monitoring, planning, and organizing, and interpersonal relationship building. Also successful implementation of one or more ERP systems. That's skills. - Benefits: Not explicitly stated besides "Salary and benefits shall be paid consistent with the District's approved compensation plan." No specifics. So we should not create Benefits section because no specific benefits listed. - Pay: Compensation band with salary range. So we can have Pay section. - Schedule: Work Calendar: 244 Day Cal. Also maybe Length of work year and hours of employment shall be those established by the School Board (but not specific). So we have specific: Work Calendar: 244 Day Cal. So we can have Schedule section with that. - Also we have Physical Requirements: Light work description. Could be under Requirements? But we could create a separate section? Not in allowed headings list. Could fold into Requirements or maybe into a generic section? The allowed headings are limited; we could put physical requirements under Requirements as a list item. - Significant Contacts: could be under Responsibilities? Not exactly. Could be under About the role? Might be better to include as a separate section? Not allowed headings. Could fold into Responsibilities? But we don't have Responsibilities section because lacking specifics. However we could create Responsibilities section with the significant contacts as duties? Might be okay if we treat them as responsibilities. But we need to avoid filler. The significant contacts is substantive: "Work collaboratively with Senior Management, the School Board, District and school staff at all levels, business, community, private and public education leaders, to apply the most relevant, cost-effective technology that supports the District's goals and strategy." That's a responsibility. So we can include Responsibilities section with that as a bullet. - Also the POSITION GOAL could be About the role. Thus sections:
About the role
POSITION GOAL text.
Responsibilities
- Work collaboratively with Senior Management, the School Board, District and school staff at all levels, business, community, private and public education leaders, to apply the most relevant, cost-effective technology that supports the District's goals and strategy.
Requirements
- Minimum qualifications: earned bachelor’s degree from an accredited institution in computer science, information systems, engineering, business administration, educational technology, or related field.
- A minimum of ten (10) years within the last fifteen (15) years of increasingly responsible executive experience including eight (8) years or more of successful direct management of a major Information Technology (IT) operation.
- Strong leadership traits and ability to effectively interact at the Superintendent’s Cabinet and School Board level.
- Experience leading and managing functions and departments interfacing with IT clients, IT processes, and systems.
- Customer focus and establishment and management of service level agreements in a complex environment involving multiple platforms, applications, communication systems, and vendors.
- Knowledge of business principles, business process analysis and redesign, techniques of administration, organization, and management, strategic and operational planning, human resources, change management, and financial cost analysis, equipment and software features of various computer systems and a sound understanding of integration capabilities, including but not limited to ecommerce, web applications, data warehouses, and enterprise systems, systems design, development and implementation process, including requirements analysis, feasibility studies, software design, programming, pilot testing, installation, evaluation, quality assurance and operational management.
- Proven skills in written and verbal communication, vendor and contract negotiation, budget preparation and monitoring, planning, and organizing, and interpersonal relationship building.
- Successful implementation of one or more ERP systems.
- Physical requirements: Light work – exerting up to 20 pounds of force occasionally, and/or up to 10 pounds of force frequently as needed to move objects.
Skills
maybe we already included skills in requirements; but we could separate skills: proven skills in written and verbal communication, vendor and contract negotiation, budget preparation and monitoring, planning, and organizing, and interpersonal relationship building; successful implementation of one or more ERP systems. However we already listed those in requirements. To avoid duplication, we could keep them under Requirements and not have Skills section. But the instruction: Prefer a few substantive sections over many thin ones. So we could combine skills into Requirements. However we have a separate Skills heading allowed; we could create Skills section with those skills. But then we would duplicate content. Better to not duplicate; we can put skills under Requirements as part of qualifications. That's fine.Pay
Compensation: Educational Support Management Association of Broward, INC. (ESMAB) PAY BAND S - $123,485.00 - $224,395.00
Schedule
Work Calendar: 244 Day Cal
We also have Classification: Exempt. Could be under Schedule or maybe a separate section? Not in allowed headings. Could fold into Schedule paragraph. We also have Advertisement Window: 09/15/2026 - Open Until Filled. Could be minor metadata; we could drop or put in a short p under maybe a generic section? Not needed. We must not include boilerplate like "To review the complete job description, access the following website..." etc. So we removed those lines. We must not repeat job title as heading. We didn't. We must not put Job ID/requisition numbers as headings; we can drop them. We must preserve all substantive information. Did we miss any? Let's check: - POSITION GOAL: captured. - Essential Performance Responsibilities: we captured as Responsibilities bullet. - Minimum Qualifications & Experience: captured as list items. - Preferred Qualifications & Experience: no extra. - SIGNIFICANT CONTACTS: captured as Responsibilities bullet (maybe we could also add as separate bullet but we already have one bullet; we could add another bullet for contacts? Actually we used that bullet for contacts. Good. - Physical Requirements: captured as list item. - TERMS OF EMPLOYMENT: we captured salary and benefits statement in Pay section; length of work year and hours of employment: we didn't capture explicitly. That's substantive: "Length of the work year and hours of employment shall be those established by the School Board." That's not specific but it's a statement. Should we include? It's not specific numbers; but it's still substantive. However we already have Schedule section with Work Calendar: 244 Day Cal. That gives length of work year. The hours of employment statement is generic; we could add to Schedule paragraph: "Length of the work year and hours of employment shall be those established by the School Board." That adds info. - Link To Job Description: boilerplate, drop. - Advertisement Window: 09/15/2026 - Open Until Filled: could be minor metadata; we could drop or include as a short p maybe under a generic section? Not required. - Work Calendar: 244 Day Cal captured. - Classification: Exempt: we could add to Schedule paragraph. - Compensation: captured. Thus final HTML:About the role
The Chief Information Officer (CIO) position has primary responsibility and commensurate authority for providing executive level leadership for improving the planning, procurement, implementation, operation, support, and maintenance of IT systems that support and enhance education and business operations as well as improve cost effectiveness and efficiency. This position is strategically placed to work with both academic and administrative leaders to facilitate institutional change and create a positive organizational culture for information technology services that supports the District’s goals and objectives.
Responsibilities
- Work collaboratively with Senior Management, the School Board, District and school staff at all levels, business, community, private and public education leaders, to apply the most relevant, cost-effective technology that supports the District's goals and strategy.
Requirements
- Earned bachelor’s degree from an accredited institution in computer science, information systems, engineering, business administration, educational technology, or related field.
- A minimum of ten (10) years within the last fifteen (15) years of increasingly responsible executive experience including eight (8) years or more of successful direct management of a major Information Technology (IT) operation.
- Strong leadership traits and the ability to effectively interact at the Superintendent’s Cabinet and School Board level.
- Experience leading and managing functions and departments interfacing with IT clients, information technology processes, and systems.
- Customer focus and the establishment and management of service level agreements in a complex environment involving multiple platforms, applications, communication systems, and vendors.
- Knowledge of business principles, business process analysis and redesign, and techniques of administration, organization, and management, strategic and operational planning, human resources, change management, and financial cost analysis, equipment and software features of various computer systems and a sound understanding of integration capabilities, including but not