Associate Dean (Media and Information Technology Department) SAC - req14203
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Fold minor metadata into short
or drop it
- Preserve ALL substantive information
- Remove boilerplate (EEO, cookie, navigation, legal, scam warnings, duplicated lines, application instructions)
- Include section ONLY when posting has real, specific content for it
- Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment, no /, no markdown code fences
Now, let's parse the content:
The posting includes:
- Title: Associate Dean (but we don't repeat as heading)
- Some metadata: TRS/ORP retiree note, posting closes date, hours per week, hourly/salaried, annual salary, funding source, number of openings, benefits eligible, location, outside working hours.
- Job Summary and Description: detailed paragraph.
- Qualifications: Minimum Education and Experience, Preferred Education and Experience, Licenses and Certifications.
- EEO Statement (boilerplate, remove)
We need to decide sections. The user suggests headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we only include if there's real content.
From the posting:
- Job Summary and Description: this is about the role and responsibilities. Could be "About the role" or "Responsibilities". The description includes both summary and duties. I'll use "About the role" for the summary and maybe "Responsibilities" for the duties? But the description is a single paragraph that includes both. Could split? The rule: use
for section headings. I think we can have "About the role" with the summary paragraph, and "Responsibilities" if there are specific duties listed. The description is prose, not a list. It says "This role translates College and District academic strategy into day-to-day department delivery by executing approved curriculum, coordinating faculty and staff, managing course scheduling and staffing, supporting student progression and completion, stewarding resources and operational readiness, and ensuring quality, assessment, and applicable compliance across assigned departments and their instructional offerings." That's a list of duties in prose. Could convert to a list? The rule: use - for any list of duties/requirements/benefits. The description is a sentence with a series of gerunds. Could break into list items. But the rule says "for any list of duties". It's not explicitly a list but we can parse as list. However, the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the prose as is, but if it's a list-like structure, we can make a list. I think it's better to keep as prose paragraph under "About the role" or "Job Summary". The user example headings include "About the role" and "Responsibilities". I'll create "About the role" with the summary paragraph, and maybe "Responsibilities" with a list of the duties extracted. But the posting doesn't have a separate responsibilities section; it's all in Job Summary and Description. I'll treat the whole description as "About the role" and include the duties as a list? Let's see: The description is one paragraph. I'll keep it as a paragraph under "About the role". Then Qualifications section with subsections: Minimum Education and Experience, Preferred Education and Experience, Licenses and Certifications. Those are lists. Use
- for each bullet.
Metadata: salary, hours, location, schedule, benefits eligible. The posting states: Annual Salary: $124,141.00, Hours per Week: 40, Hourly or Salaried: Salary, Benefits Eligible: Yes, Location: ..., Outside working hours: Some Evening or weekend hours may be required. These are specific details. Should we create sections for Pay, Schedule, Benefits? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary, hours, schedule, benefits eligible. So we can include them. But the user says "Prefer a few substantive sections over many thin ones." We could fold metadata into a short
at the top or bottom. However, the rule: "fold minor metadata into a short
or drop it." But salary, schedule, benefits are not minor? They are specific. The user says "include a section ONLY when the posting has real, specific content for it". The posting has specific content for Pay (salary), Schedule (hours, outside hours), Benefits (eligible). But they are single lines. Could create sections with a single paragraph each. That might be thin. Better to combine into a "Position Details" section? But the allowed headings are predefined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Benefits, Pay, Schedule if they have content. The posting says "Benefits Eligible: Yes" - that's minimal. Could just mention in a paragraph. Similarly Pay: annual salary. Schedule: hours per week and outside hours. I think we can create a "Position Details" section? Not in the allowed list. The allowed headings are examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So we can use those. I'll create sections for Pay, Schedule, Benefits if they have substantive content. But "Benefits Eligible: Yes" is not substantive; no details about benefits. So maybe omit Benefits section. Pay: specific salary. Schedule: specific hours and note about evenings/weekends. Could include Schedule section. Pay section with salary. But the rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them. However, they are thin. The user says "Prefer a few substantive sections over many thin ones." So maybe fold into a single "Position Details" paragraph under a heading? But the allowed headings don't include that. Could use "Schedule" and "Pay" as headings with a paragraph each. That's acceptable.
Also, there is a note about TRS/ORP retiree and posting closes date. That's minor metadata, can fold into a paragraph or drop. The posting closes date is not needed for the job description? Might be considered application instruction. The rule: remove application instructions. So drop posting closes date. The TRS/ORP note is a clarification for retirees, maybe keep as a note? Could be a paragraph.
Location: could be included in Schedule or a separate "Location" heading? Not in allowed list. Could fold into Schedule or a paragraph.
Let's structure:
1. About the role: with the job summary paragraph.
2. Responsibilities: maybe extract the duties as a list? The description includes a list of duties. I'll create a Responsibilities section with a list of the duties mentioned.
3. Qualifications: with subsections for Minimum Education and Experience, Preferred Education and Experience, Licenses and Certifications. Each as a list.
4. Pay: with salary.
5. Schedule: with hours per week, salaried, outside hours.
6. Benefits: maybe just "Benefits Eligible: Yes" but that's thin. Could omit.
Also, there is "Funding source: Hard Money" and "Number of opening: 1". Minor metadata, drop.
Now, write HTML.
We need to output only HTML fragment. No markdown.
Let's draft:
About the role
The Associate Dean serves as the College's operational leader for assigned departments. This role translates College and District academic strategy into day-to-day department delivery by executing approved curriculum, coordinating faculty and staff, managing course scheduling and staffing, supporting student progression and completion, stewarding resources and operational readiness, and ensuring quality, assessment, and applicable compliance across assigned departments and their instructional offerings. The Associate Dean operates within frameworks set by the College and District and provides clear administrative authority for faculty evaluation, resource stewardship, and operational decision-making. Depending on assignment, the role may support Transfer discipline, Workforce / CTE programs, or a combination of department portfolios, with additional responsibilities as described in this job description. Reports to the appropriate Dean, as assigned.
Responsibilities
- Execute approved curriculum
- Coordinate faculty and staff
- Manage course scheduling and staffing
- Support student progression and completion
- Steward resources and operational readiness
- Ensure quality, assessment, and applicable compliance across assigned departments and their instructional offerings
- Provide administrative authority for faculty evaluation, resource stewardship, and operational decision-making
- Support Transfer discipline, Workforce / CTE programs, or a combination of department portfolios
But note: the description says "This role translates ... by executing approved curriculum, coordinating faculty and staff, managing course scheduling and staffing, supporting student progression and completion, stewarding resources and operational readiness, and ensuring quality, assessment, and applicable compliance..." That's a list. Also "The Associate Dean operates within frameworks ... and provides clear administrative authority for faculty evaluation, resource stewardship, and operational decision-making." And "Depending on assignment, the role may support Transfer discipline, Workforce / CTE programs, or a combination of department portfolios, with additional responsibilities as described in this job description." So I'll include those as list items.
Now Qualifications:
Qualifications
Minimum Education and Experience
- Level of educational completion as required for faculty status
- Experience in college teaching, instructional administration and program planning and development with a record of increasingly broad responsibilities
Preferred Education and Experience
- Advanced degree in relevant field of study
- Five years of experience leading academic departments in a higher education institution
- Seven or more years of experience as a faculty member at a higher education institution
Licenses and Certifications
- Licenses or certifications may be required depending on programs managed (e.g., Registered Nursing license)
Note: The posting says "To view a complete job description, click here." That's a link, but we don't have URL. Probably ignore.
Now Pay:
Pay
Annual salary: $124,141.00 (salaried position).
Schedule:
Schedule
Full-time, 40 hours per week. Standard hours Monday–Friday, 8:00 a.m. to 5:00 p.m.; some evening or weekend hours may be required.
Benefits: The posting says "Benefits Eligible: Yes". Could include a Benefits section with that, but it's thin. The rule: never create Benefits section unless posting actually states them. It states "Benefits Eligible: Yes". That's a statement. But no details. Could include a short paragraph. However, the user says "never emit a heading followed by filler/placeholder text".
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Fold minor metadata into short
or drop it - Preserve ALL substantive information - Remove boilerplate (EEO, cookie, navigation, legal, scam warnings, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Now, let's parse the content: The posting includes: - Title: Associate Dean (but we don't repeat as heading) - Some metadata: TRS/ORP retiree note, posting closes date, hours per week, hourly/salaried, annual salary, funding source, number of openings, benefits eligible, location, outside working hours. - Job Summary and Description: detailed paragraph. - Qualifications: Minimum Education and Experience, Preferred Education and Experience, Licenses and Certifications. - EEO Statement (boilerplate, remove) We need to decide sections. The user suggests headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we only include if there's real content. From the posting: - Job Summary and Description: this is about the role and responsibilities. Could be "About the role" or "Responsibilities". The description includes both summary and duties. I'll use "About the role" for the summary and maybe "Responsibilities" for the duties? But the description is a single paragraph that includes both. Could split? The rule: use
for section headings. I think we can have "About the role" with the summary paragraph, and "Responsibilities" if there are specific duties listed. The description is prose, not a list. It says "This role translates College and District academic strategy into day-to-day department delivery by executing approved curriculum, coordinating faculty and staff, managing course scheduling and staffing, supporting student progression and completion, stewarding resources and operational readiness, and ensuring quality, assessment, and applicable compliance across assigned departments and their instructional offerings." That's a list of duties in prose. Could convert to a list? The rule: use - for any list of duties/requirements/benefits. The description is a sentence with a series of gerunds. Could break into list items. But the rule says "for any list of duties". It's not explicitly a list but we can parse as list. However, the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the prose as is, but if it's a list-like structure, we can make a list. I think it's better to keep as prose paragraph under "About the role" or "Job Summary". The user example headings include "About the role" and "Responsibilities". I'll create "About the role" with the summary paragraph, and maybe "Responsibilities" with a list of the duties extracted. But the posting doesn't have a separate responsibilities section; it's all in Job Summary and Description. I'll treat the whole description as "About the role" and include the duties as a list? Let's see: The description is one paragraph. I'll keep it as a paragraph under "About the role". Then Qualifications section with subsections: Minimum Education and Experience, Preferred Education and Experience, Licenses and Certifications. Those are lists. Use
- for each bullet.
Metadata: salary, hours, location, schedule, benefits eligible. The posting states: Annual Salary: $124,141.00, Hours per Week: 40, Hourly or Salaried: Salary, Benefits Eligible: Yes, Location: ..., Outside working hours: Some Evening or weekend hours may be required. These are specific details. Should we create sections for Pay, Schedule, Benefits? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary, hours, schedule, benefits eligible. So we can include them. But the user says "Prefer a few substantive sections over many thin ones." We could fold metadata into a short
at the top or bottom. However, the rule: "fold minor metadata into a short
or drop it." But salary, schedule, benefits are not minor? They are specific. The user says "include a section ONLY when the posting has real, specific content for it". The posting has specific content for Pay (salary), Schedule (hours, outside hours), Benefits (eligible). But they are single lines. Could create sections with a single paragraph each. That might be thin. Better to combine into a "Position Details" section? But the allowed headings are predefined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Benefits, Pay, Schedule if they have content. The posting says "Benefits Eligible: Yes" - that's minimal. Could just mention in a paragraph. Similarly Pay: annual salary. Schedule: hours per week and outside hours. I think we can create a "Position Details" section? Not in the allowed list. The allowed headings are examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So we can use those. I'll create sections for Pay, Schedule, Benefits if they have substantive content. But "Benefits Eligible: Yes" is not substantive; no details about benefits. So maybe omit Benefits section. Pay: specific salary. Schedule: specific hours and note about evenings/weekends. Could include Schedule section. Pay section with salary. But the rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them. However, they are thin. The user says "Prefer a few substantive sections over many thin ones." So maybe fold into a single "Position Details" paragraph under a heading? But the allowed headings don't include that. Could use "Schedule" and "Pay" as headings with a paragraph each. That's acceptable.
Also, there is a note about TRS/ORP retiree and posting closes date. That's minor metadata, can fold into a paragraph or drop. The posting closes date is not needed for the job description? Might be considered application instruction. The rule: remove application instructions. So drop posting closes date. The TRS/ORP note is a clarification for retirees, maybe keep as a note? Could be a paragraph.
Location: could be included in Schedule or a separate "Location" heading? Not in allowed list. Could fold into Schedule or a paragraph.
Let's structure:
1. About the role: with the job summary paragraph.
2. Responsibilities: maybe extract the duties as a list? The description includes a list of duties. I'll create a Responsibilities section with a list of the duties mentioned.
3. Qualifications: with subsections for Minimum Education and Experience, Preferred Education and Experience, Licenses and Certifications. Each as a list.
4. Pay: with salary.
5. Schedule: with hours per week, salaried, outside hours.
6. Benefits: maybe just "Benefits Eligible: Yes" but that's thin. Could omit.
Also, there is "Funding source: Hard Money" and "Number of opening: 1". Minor metadata, drop.
Now, write HTML.
We need to output only HTML fragment. No markdown.
Let's draft:
About the role
The Associate Dean serves as the College's operational leader for assigned departments. This role translates College and District academic strategy into day-to-day department delivery by executing approved curriculum, coordinating faculty and staff, managing course scheduling and staffing, supporting student progression and completion, stewarding resources and operational readiness, and ensuring quality, assessment, and applicable compliance across assigned departments and their instructional offerings. The Associate Dean operates within frameworks set by the College and District and provides clear administrative authority for faculty evaluation, resource stewardship, and operational decision-making. Depending on assignment, the role may support Transfer discipline, Workforce / CTE programs, or a combination of department portfolios, with additional responsibilities as described in this job description. Reports to the appropriate Dean, as assigned.
Responsibilities
- Execute approved curriculum
- Coordinate faculty and staff
- Manage course scheduling and staffing
- Support student progression and completion
- Steward resources and operational readiness
- Ensure quality, assessment, and applicable compliance across assigned departments and their instructional offerings
- Provide administrative authority for faculty evaluation, resource stewardship, and operational decision-making
- Support Transfer discipline, Workforce / CTE programs, or a combination of department portfolios
But note: the description says "This role translates ... by executing approved curriculum, coordinating faculty and staff, managing course scheduling and staffing, supporting student progression and completion, stewarding resources and operational readiness, and ensuring quality, assessment, and applicable compliance..." That's a list. Also "The Associate Dean operates within frameworks ... and provides clear administrative authority for faculty evaluation, resource stewardship, and operational decision-making." And "Depending on assignment, the role may support Transfer discipline, Workforce / CTE programs, or a combination of department portfolios, with additional responsibilities as described in this job description." So I'll include those as list items.
Now Qualifications:
Qualifications
Minimum Education and Experience
- Level of educational completion as required for faculty status
- Experience in college teaching, instructional administration and program planning and development with a record of increasingly broad responsibilities
Preferred Education and Experience
- Advanced degree in relevant field of study
- Five years of experience leading academic departments in a higher education institution
- Seven or more years of experience as a faculty member at a higher education institution
Licenses and Certifications
- Licenses or certifications may be required depending on programs managed (e.g., Registered Nursing license)
Note: The posting says "To view a complete job description, click here." That's a link, but we don't have URL. Probably ignore.
Now Pay:
Pay
Annual salary: $124,141.00 (salaried position).
Schedule:
Schedule
Full-time, 40 hours per week. Standard hours Monday–Friday, 8:00 a.m. to 5:00 p.m.; some evening or weekend hours may be required.
Benefits: The posting says "Benefits Eligible: Yes". Could include a Benefits section with that, but it's thin. The rule: never create Benefits section unless posting actually states them. It states "Benefits Eligible: Yes". That's a statement. But no details. Could include a short paragraph. However, the user says "never emit a heading followed by filler/placeholder text".
- for each bullet.
Metadata: salary, hours, location, schedule, benefits eligible. The posting states: Annual Salary: $124,141.00, Hours per Week: 40, Hourly or Salaried: Salary, Benefits Eligible: Yes, Location: ..., Outside working hours: Some Evening or weekend hours may be required. These are specific details. Should we create sections for Pay, Schedule, Benefits? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does state salary, hours, schedule, benefits eligible. So we can include them. But the user says "Prefer a few substantive sections over many thin ones." We could fold metadata into a short
at the top or bottom. However, the rule: "fold minor metadata into a short
or drop it." But salary, schedule, benefits are not minor? They are specific. The user says "include a section ONLY when the posting has real, specific content for it". The posting has specific content for Pay (salary), Schedule (hours, outside hours), Benefits (eligible). But they are single lines. Could create sections with a single paragraph each. That might be thin. Better to combine into a "Position Details" section? But the allowed headings are predefined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Benefits, Pay, Schedule if they have content. The posting says "Benefits Eligible: Yes" - that's minimal. Could just mention in a paragraph. Similarly Pay: annual salary. Schedule: hours per week and outside hours. I think we can create a "Position Details" section? Not in the allowed list. The allowed headings are examples: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So we can use those. I'll create sections for Pay, Schedule, Benefits if they have substantive content. But "Benefits Eligible: Yes" is not substantive; no details about benefits. So maybe omit Benefits section. Pay: specific salary. Schedule: specific hours and note about evenings/weekends. Could include Schedule section. Pay section with salary. But the rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them. However, they are thin. The user says "Prefer a few substantive sections over many thin ones." So maybe fold into a single "Position Details" paragraph under a heading? But the allowed headings don't include that. Could use "Schedule" and "Pay" as headings with a paragraph each. That's acceptable. Also, there is a note about TRS/ORP retiree and posting closes date. That's minor metadata, can fold into a paragraph or drop. The posting closes date is not needed for the job description? Might be considered application instruction. The rule: remove application instructions. So drop posting closes date. The TRS/ORP note is a clarification for retirees, maybe keep as a note? Could be a paragraph. Location: could be included in Schedule or a separate "Location" heading? Not in allowed list. Could fold into Schedule or a paragraph. Let's structure: 1. About the role: with the job summary paragraph. 2. Responsibilities: maybe extract the duties as a list? The description includes a list of duties. I'll create a Responsibilities section with a list of the duties mentioned. 3. Qualifications: with subsections for Minimum Education and Experience, Preferred Education and Experience, Licenses and Certifications. Each as a list. 4. Pay: with salary. 5. Schedule: with hours per week, salaried, outside hours. 6. Benefits: maybe just "Benefits Eligible: Yes" but that's thin. Could omit. Also, there is "Funding source: Hard Money" and "Number of opening: 1". Minor metadata, drop. Now, write HTML. We need to output only HTML fragment. No markdown. Let's draft:
About the role
The Associate Dean serves as the College's operational leader for assigned departments. This role translates College and District academic strategy into day-to-day department delivery by executing approved curriculum, coordinating faculty and staff, managing course scheduling and staffing, supporting student progression and completion, stewarding resources and operational readiness, and ensuring quality, assessment, and applicable compliance across assigned departments and their instructional offerings. The Associate Dean operates within frameworks set by the College and District and provides clear administrative authority for faculty evaluation, resource stewardship, and operational decision-making. Depending on assignment, the role may support Transfer discipline, Workforce / CTE programs, or a combination of department portfolios, with additional responsibilities as described in this job description. Reports to the appropriate Dean, as assigned.
Responsibilities
- Execute approved curriculum
- Coordinate faculty and staff
- Manage course scheduling and staffing
- Support student progression and completion
- Steward resources and operational readiness
- Ensure quality, assessment, and applicable compliance across assigned departments and their instructional offerings
- Provide administrative authority for faculty evaluation, resource stewardship, and operational decision-making
- Support Transfer discipline, Workforce / CTE programs, or a combination of department portfolios
Qualifications
Minimum Education and Experience
- Level of educational completion as required for faculty status
- Experience in college teaching, instructional administration and program planning and development with a record of increasingly broad responsibilities
Preferred Education and Experience
- Advanced degree in relevant field of study
- Five years of experience leading academic departments in a higher education institution
- Seven or more years of experience as a faculty member at a higher education institution
Licenses and Certifications
- Licenses or certifications may be required depending on programs managed (e.g., Registered Nursing license)
Pay
Annual salary: $124,141.00 (salaried position).
Schedule:Schedule
Full-time, 40 hours per week. Standard hours Monday–Friday, 8:00 a.m. to 5:00 p.m.; some evening or weekend hours may be required.
Benefits: The posting says "Benefits Eligible: Yes". Could include a Benefits section with that, but it's thin. The rule: never create Benefits section unless posting actually states them. It states "Benefits Eligible: Yes". That's a statement. But no details. Could include a short paragraph. However, the user says "never emit a heading followed by filler/placeholder text".