Director of Strategic Communications and Community Engagement
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat job title as heading (already shown)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Identify the Content Type:**
- The user provided text that seems to be a "Qualifications" section and a "GENERAL FUNCTIONS" section from a job posting.
- It includes qualifications, requirements, and general functions/responsibilities.
- I need to parse this into the specified HTML structure.
3. **Analyze the Provided Text:**
Let's break down the text:
"Qualifications Bachelor's degree in communications, public relations, journalism, marketing, community engagement, education, or a related field preferred.Demonstrated professional experience in strategic communications, public relations, journalism, community engagement, or a related field.Exceptional written, verbal, interpersonal, and visual communication skills.Demonstrated ability to translate complex information into clear, accessible, audience-centered communication.Experience developing and implementing comprehensive internal and external communication strategies.Strong skills in storytelling across multiple platforms, including digital media, photography, videography, social media, web, print, and emerging communication tools.Demonstrated ability to build trusting relationships with diverse stakeholders and facilitate meaningful community engagement.Ability to exercise sound judgment, discretion, responsiveness, and professionalism in complex or sensitive situations.Experience in public education, public agencies, or community-based organizations preferred.Public Records Officer training (or must be obtained within 90 days of hire).Valid Washington State driver's license."
Then: "GENERAL FUNCTIONS: Provides strategic leadership for districtwide communications, storytelling, engagement, public relations, and community outreach; ensures that the District's communication efforts are aligned with the Strategic Plan and helps students, staff, families, and community members see themselves as part of #OneOakHarbor; leads proactive and responsive communication; elevates student and staff voices; strengthens family and community engagement; builds partnerships; supports schools and departments in telling their stories; manages the District's communication platforms and brand; supports crisis and emergency communication; and helps the District listen to and learn from the community it serves."
Wait, the user's prompt actually starts with "Qualifications..." and then "GENERAL FUNCTIONS: ...". But the user's instruction says: "Reformat a job posting into clean, well-structured semantic HTML." And they gave me this text. I need to figure out what sections this belongs to.
Looking at the text, it has:
- A "Qualifications" block (list of requirements)
- A "GENERAL FUNCTIONS" block (description of role/responsibilities)
The user's rules mention using `
` for section headings like: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I need to map the content to these headings appropriately, but only include sections that have real content.
Let's identify what's present:
- "Qualifications" section: Yes, there's a long list of qualifications.
- "GENERAL FUNCTIONS" which seems like "About the role" or "Responsibilities". The text starts with "GENERAL FUNCTIONS:" and then describes the role. This maps to "Responsibilities" or "About the role". I'll use "Responsibilities" or keep it as "About the role"? The rules say use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I should pick the most appropriate. Since the text says "GENERAL FUNCTIONS:", I'll map it to "Responsibilities" or "About the role". I think "Responsibilities" fits well, but I could also do "About the role". I'll check the exact wording: "GENERAL FUNCTIONS: Provides strategic leadership...". I'll use `Responsibilities
` or maybe `About the role
`. The rules list examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll use "Responsibilities" since it's general functions. Or maybe "About the role" is better. I'll decide based on content. The content is a description of what the role does. I'll use `Responsibilities
` as it's a direct match to the function description. Actually, looking at typical job postings, "General Functions" often maps to "Responsibilities". I'll use "Responsibilities". But wait, the rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I can choose either. I'll go with "Responsibilities" since the text is "GENERAL FUNCTIONS:". Alternatively, I could use "About the role". I think "Responsibilities" is fine.
- Qualifications: Yes, there's a qualifications list.
- Skills: The qualifications include skills like "Exceptional written, verbal, interpersonal, and visual communication skills", "Strong skills in storytelling across multiple platforms...". These could go under "Skills" or be part of "Qualifications". The rules have a separate "Skills" heading. I'll consider if I should split them. The instruction says: "Prefer a few substantive sections over many thin ones." So I should consolidate if needed. The qualifications already cover skills implicitly. But there's a distinct "Skills" heading in the examples. I need to decide. Looking at the text, many items are qualifications that also describe skills. I might put them under "Qualifications" only, or create a "Skills" section if there's distinct content. Let's see: The qualifications list includes both requirements and skills. I'll likely just have "Qualifications" and "Responsibilities". But the rules mention "Skills" as a possible heading. I'll evaluate if there's clear, separate skills content. The text: "Exceptional written, verbal, interpersonal, and visual communication skills." "Demonstrated ability to translate complex information..." "Experience developing..." "Strong skills in storytelling..." These are skills, but they're embedded in the qualifications section. I think it's better to not create a thin "Skills" section unless there's distinct content beyond qualifications. The rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if I create a "Skills" section, I need specific content that isn't already in qualifications. I'll probably just stick to "Qualifications" and "Responsibilities". But let's read carefully: The user provided text has "Qualifications" at the start, then "GENERAL FUNCTIONS:". The rules say use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should map the provided content to these. The text explicitly starts with "Qualifications", so that's a heading. The "GENERAL FUNCTIONS" maps to "Responsibilities" or "About the role".
Let's parse the qualifications text as a list. The rules say: "Use - for any list of duties/requirements/benefits". So I'll convert the qualifications into an unordered list. But the qualifications are given as a continuous paragraph-like text. I need to split them into list items. The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to extract each qualification as a list item, or keep them as paragraphs? The rule: "Use
- for any list of duties/requirements/benefits". Since these are requirements/qualifications, I should use `
- `. I'll break them into separate `
- ` items.
Let's list out the qualifications from the text:
1. Bachelor's degree in communications, public relations, journalism, marketing, community engagement, education, or a related field preferred.
2. Demonstrated professional experience in strategic communications, public relations, journalism, community engagement, or a related field.
3. Exceptional written, verbal, interpersonal, and visual communication skills.
4. Demonstrated ability to translate complex information into clear, accessible, audience-centered communication.
5. Experience developing and implementing comprehensive internal and external communication strategies.
6. Strong skills in storytelling across multiple platforms, including digital media, photography, videography, social media, web, print, and emerging communication tools.
7. Demonstrated ability to build trusting relationships with diverse stakeholders and facilitate meaningful community engagement.
8. Ability to exercise sound judgment, discretion, responsiveness, and professionalism in complex or sensitive situations.
9. Experience in public education, public agencies, or community-based organizations preferred.
10. Public Records Officer training (or must be obtained within 90 days of hire).
11. Valid Washington State driver's license.
Are all these valid? Yes. I'll make sure each is a separate `
- `. Some might be combined if they're very similar, but the rule says preserve all substantive information. I'll keep them as separate items, but maybe group slightly? I'll err on preserving detail, so separate `
- ` items.
Now the "GENERAL FUNCTIONS" part: "Provides strategic leadership for districtwide communications, storytelling, engagement, public relations, and community outreach; ensures that the District's communication efforts are aligned with the Strategic Plan and helps students, staff, families, and community members see themselves as part of #OneOakHarbor; leads proactive and responsive communication; elevates student and staff voices; strengthens family and community engagement; builds partnerships; supports schools and departments in telling their stories; manages the District's communication platforms and brand; supports crisis and emergency communication; and helps the District listen to and learn from the community it serves."
This is a description of responsibilities. I'll put it under a section. The heading options: "About the role" or "Responsibilities". I'll use `
Responsibilities
` since it's "GENERAL FUNCTIONS". But I could also use `About the role
`. I'll check the exact wording the user gave for headings: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll pick "Responsibilities" as it directly maps to "GENERAL FUNCTIONS". Alternatively, I could use "About the role" and put the general functions there. I think "Responsibilities" is fine.
Now, what about other sections? The posting might have "Requirements", "Skills", etc. But the user only provided "Qualifications" and "GENERAL FUNCTIONS". I should not invent sections. The rule: "include a section ONLY when the posting has real, specific content for it". So I'll
` for prose - Do NOT repeat job title as heading (already shown) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Identify the Content Type:** - The user provided text that seems to be a "Qualifications" section and a "GENERAL FUNCTIONS" section from a job posting. - It includes qualifications, requirements, and general functions/responsibilities. - I need to parse this into the specified HTML structure. 3. **Analyze the Provided Text:** Let's break down the text: "Qualifications Bachelor's degree in communications, public relations, journalism, marketing, community engagement, education, or a related field preferred.Demonstrated professional experience in strategic communications, public relations, journalism, community engagement, or a related field.Exceptional written, verbal, interpersonal, and visual communication skills.Demonstrated ability to translate complex information into clear, accessible, audience-centered communication.Experience developing and implementing comprehensive internal and external communication strategies.Strong skills in storytelling across multiple platforms, including digital media, photography, videography, social media, web, print, and emerging communication tools.Demonstrated ability to build trusting relationships with diverse stakeholders and facilitate meaningful community engagement.Ability to exercise sound judgment, discretion, responsiveness, and professionalism in complex or sensitive situations.Experience in public education, public agencies, or community-based organizations preferred.Public Records Officer training (or must be obtained within 90 days of hire).Valid Washington State driver's license." Then: "GENERAL FUNCTIONS: Provides strategic leadership for districtwide communications, storytelling, engagement, public relations, and community outreach; ensures that the District's communication efforts are aligned with the Strategic Plan and helps students, staff, families, and community members see themselves as part of #OneOakHarbor; leads proactive and responsive communication; elevates student and staff voices; strengthens family and community engagement; builds partnerships; supports schools and departments in telling their stories; manages the District's communication platforms and brand; supports crisis and emergency communication; and helps the District listen to and learn from the community it serves." Wait, the user's prompt actually starts with "Qualifications..." and then "GENERAL FUNCTIONS: ...". But the user's instruction says: "Reformat a job posting into clean, well-structured semantic HTML." And they gave me this text. I need to figure out what sections this belongs to. Looking at the text, it has: - A "Qualifications" block (list of requirements) - A "GENERAL FUNCTIONS" block (description of role/responsibilities) The user's rules mention using `
` for section headings like: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
I need to map the content to these headings appropriately, but only include sections that have real content.
Let's identify what's present:
- "Qualifications" section: Yes, there's a long list of qualifications.
- "GENERAL FUNCTIONS" which seems like "About the role" or "Responsibilities". The text starts with "GENERAL FUNCTIONS:" and then describes the role. This maps to "Responsibilities" or "About the role". I'll use "Responsibilities" or keep it as "About the role"? The rules say use `` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). I should pick the most appropriate. Since the text says "GENERAL FUNCTIONS:", I'll map it to "Responsibilities" or "About the role". I think "Responsibilities" fits well, but I could also do "About the role". I'll check the exact wording: "GENERAL FUNCTIONS: Provides strategic leadership...". I'll use `Responsibilities
` or maybe `About the role
`. The rules list examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll use "Responsibilities" since it's general functions. Or maybe "About the role" is better. I'll decide based on content. The content is a description of what the role does. I'll use `Responsibilities
` as it's a direct match to the function description. Actually, looking at typical job postings, "General Functions" often maps to "Responsibilities". I'll use "Responsibilities". But wait, the rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I can choose either. I'll go with "Responsibilities" since the text is "GENERAL FUNCTIONS:". Alternatively, I could use "About the role". I think "Responsibilities" is fine.
- Qualifications: Yes, there's a qualifications list.
- Skills: The qualifications include skills like "Exceptional written, verbal, interpersonal, and visual communication skills", "Strong skills in storytelling across multiple platforms...". These could go under "Skills" or be part of "Qualifications". The rules have a separate "Skills" heading. I'll consider if I should split them. The instruction says: "Prefer a few substantive sections over many thin ones." So I should consolidate if needed. The qualifications already cover skills implicitly. But there's a distinct "Skills" heading in the examples. I need to decide. Looking at the text, many items are qualifications that also describe skills. I might put them under "Qualifications" only, or create a "Skills" section if there's distinct content. Let's see: The qualifications list includes both requirements and skills. I'll likely just have "Qualifications" and "Responsibilities". But the rules mention "Skills" as a possible heading. I'll evaluate if there's clear, separate skills content. The text: "Exceptional written, verbal, interpersonal, and visual communication skills." "Demonstrated ability to translate complex information..." "Experience developing..." "Strong skills in storytelling..." These are skills, but they're embedded in the qualifications section. I think it's better to not create a thin "Skills" section unless there's distinct content beyond qualifications. The rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if I create a "Skills" section, I need specific content that isn't already in qualifications. I'll probably just stick to "Qualifications" and "Responsibilities". But let's read carefully: The user provided text has "Qualifications" at the start, then "GENERAL FUNCTIONS:". The rules say use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should map the provided content to these. The text explicitly starts with "Qualifications", so that's a heading. The "GENERAL FUNCTIONS" maps to "Responsibilities" or "About the role".
Let's parse the qualifications text as a list. The rules say: "Use - for any list of duties/requirements/benefits". So I'll convert the qualifications into an unordered list. But the qualifications are given as a continuous paragraph-like text. I need to split them into list items. The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to extract each qualification as a list item, or keep them as paragraphs? The rule: "Use
- for any list of duties/requirements/benefits". Since these are requirements/qualifications, I should use `
- `. I'll break them into separate `
- ` items.
Let's list out the qualifications from the text:
1. Bachelor's degree in communications, public relations, journalism, marketing, community engagement, education, or a related field preferred.
2. Demonstrated professional experience in strategic communications, public relations, journalism, community engagement, or a related field.
3. Exceptional written, verbal, interpersonal, and visual communication skills.
4. Demonstrated ability to translate complex information into clear, accessible, audience-centered communication.
5. Experience developing and implementing comprehensive internal and external communication strategies.
6. Strong skills in storytelling across multiple platforms, including digital media, photography, videography, social media, web, print, and emerging communication tools.
7. Demonstrated ability to build trusting relationships with diverse stakeholders and facilitate meaningful community engagement.
8. Ability to exercise sound judgment, discretion, responsiveness, and professionalism in complex or sensitive situations.
9. Experience in public education, public agencies, or community-based organizations preferred.
10. Public Records Officer training (or must be obtained within 90 days of hire).
11. Valid Washington State driver's license.
Are all these valid? Yes. I'll make sure each is a separate `
- `. Some might be combined if they're very similar, but the rule says preserve all substantive information. I'll keep them as separate items, but maybe group slightly? I'll err on preserving detail, so separate `
- ` items.
Now the "GENERAL FUNCTIONS" part: "Provides strategic leadership for districtwide communications, storytelling, engagement, public relations, and community outreach; ensures that the District's communication efforts are aligned with the Strategic Plan and helps students, staff, families, and community members see themselves as part of #OneOakHarbor; leads proactive and responsive communication; elevates student and staff voices; strengthens family and community engagement; builds partnerships; supports schools and departments in telling their stories; manages the District's communication platforms and brand; supports crisis and emergency communication; and helps the District listen to and learn from the community it serves."
This is a description of responsibilities. I'll put it under a section. The heading options: "About the role" or "Responsibilities". I'll use `
Responsibilities
` since it's "GENERAL FUNCTIONS". But I could also use `About the role
`. I'll check the exact wording the user gave for headings: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll pick "Responsibilities" as it directly maps to "GENERAL FUNCTIONS". Alternatively, I could use "About the role" and put the general functions there. I think "Responsibilities" is fine.
Now, what about other sections? The posting might have "Requirements", "Skills", etc. But the user only provided "Qualifications" and "GENERAL FUNCTIONS". I should not invent sections. The rule: "include a section ONLY when the posting has real, specific content for it". So I'll
Responsibilities
` or maybe `About the role
`. The rules list examples: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll use "Responsibilities" since it's general functions. Or maybe "About the role" is better. I'll decide based on content. The content is a description of what the role does. I'll use `Responsibilities
` as it's a direct match to the function description. Actually, looking at typical job postings, "General Functions" often maps to "Responsibilities". I'll use "Responsibilities". But wait, the rules say: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I can choose either. I'll go with "Responsibilities" since the text is "GENERAL FUNCTIONS:". Alternatively, I could use "About the role". I think "Responsibilities" is fine.
- Qualifications: Yes, there's a qualifications list.
- Skills: The qualifications include skills like "Exceptional written, verbal, interpersonal, and visual communication skills", "Strong skills in storytelling across multiple platforms...". These could go under "Skills" or be part of "Qualifications". The rules have a separate "Skills" heading. I'll consider if I should split them. The instruction says: "Prefer a few substantive sections over many thin ones." So I should consolidate if needed. The qualifications already cover skills implicitly. But there's a distinct "Skills" heading in the examples. I need to decide. Looking at the text, many items are qualifications that also describe skills. I might put them under "Qualifications" only, or create a "Skills" section if there's distinct content. Let's see: The qualifications list includes both requirements and skills. I'll likely just have "Qualifications" and "Responsibilities". But the rules mention "Skills" as a possible heading. I'll evaluate if there's clear, separate skills content. The text: "Exceptional written, verbal, interpersonal, and visual communication skills." "Demonstrated ability to translate complex information..." "Experience developing..." "Strong skills in storytelling..." These are skills, but they're embedded in the qualifications section. I think it's better to not create a thin "Skills" section unless there's distinct content beyond qualifications. The rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if I create a "Skills" section, I need specific content that isn't already in qualifications. I'll probably just stick to "Qualifications" and "Responsibilities". But let's read carefully: The user provided text has "Qualifications" at the start, then "GENERAL FUNCTIONS:". The rules say use headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I should map the provided content to these. The text explicitly starts with "Qualifications", so that's a heading. The "GENERAL FUNCTIONS" maps to "Responsibilities" or "About the role".
Let's parse the qualifications text as a list. The rules say: "Use - for any list of duties/requirements/benefits". So I'll convert the qualifications into an unordered list. But the qualifications are given as a continuous paragraph-like text. I need to split them into list items. The rules say "Preserve ALL substantive information; do NOT invent or summarize away detail." So I need to extract each qualification as a list item, or keep them as paragraphs? The rule: "Use
- for any list of duties/requirements/benefits". Since these are requirements/qualifications, I should use `
- `. I'll break them into separate `
- ` items.
Let's list out the qualifications from the text:
1. Bachelor's degree in communications, public relations, journalism, marketing, community engagement, education, or a related field preferred.
2. Demonstrated professional experience in strategic communications, public relations, journalism, community engagement, or a related field.
3. Exceptional written, verbal, interpersonal, and visual communication skills.
4. Demonstrated ability to translate complex information into clear, accessible, audience-centered communication.
5. Experience developing and implementing comprehensive internal and external communication strategies.
6. Strong skills in storytelling across multiple platforms, including digital media, photography, videography, social media, web, print, and emerging communication tools.
7. Demonstrated ability to build trusting relationships with diverse stakeholders and facilitate meaningful community engagement.
8. Ability to exercise sound judgment, discretion, responsiveness, and professionalism in complex or sensitive situations.
9. Experience in public education, public agencies, or community-based organizations preferred.
10. Public Records Officer training (or must be obtained within 90 days of hire).
11. Valid Washington State driver's license.
Are all these valid? Yes. I'll make sure each is a separate `
- `. Some might be combined if they're very similar, but the rule says preserve all substantive information. I'll keep them as separate items, but maybe group slightly? I'll err on preserving detail, so separate `
- ` items.
Now the "GENERAL FUNCTIONS" part: "Provides strategic leadership for districtwide communications, storytelling, engagement, public relations, and community outreach; ensures that the District's communication efforts are aligned with the Strategic Plan and helps students, staff, families, and community members see themselves as part of #OneOakHarbor; leads proactive and responsive communication; elevates student and staff voices; strengthens family and community engagement; builds partnerships; supports schools and departments in telling their stories; manages the District's communication platforms and brand; supports crisis and emergency communication; and helps the District listen to and learn from the community it serves."
This is a description of responsibilities. I'll put it under a section. The heading options: "About the role" or "Responsibilities". I'll use `
Responsibilities
` since it's "GENERAL FUNCTIONS". But I could also use `About the role
`. I'll check the exact wording the user gave for headings: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll pick "Responsibilities" as it directly maps to "GENERAL FUNCTIONS". Alternatively, I could use "About the role" and put the general functions there. I think "Responsibilities" is fine.
Now, what about other sections? The posting might have "Requirements", "Skills", etc. But the user only provided "Qualifications" and "GENERAL FUNCTIONS". I should not invent sections. The rule: "include a section ONLY when the posting has real, specific content for it". So I'll
- for any list of duties/requirements/benefits". Since these are requirements/qualifications, I should use `
- `. I'll break them into separate `
- ` items. Let's list out the qualifications from the text: 1. Bachelor's degree in communications, public relations, journalism, marketing, community engagement, education, or a related field preferred. 2. Demonstrated professional experience in strategic communications, public relations, journalism, community engagement, or a related field. 3. Exceptional written, verbal, interpersonal, and visual communication skills. 4. Demonstrated ability to translate complex information into clear, accessible, audience-centered communication. 5. Experience developing and implementing comprehensive internal and external communication strategies. 6. Strong skills in storytelling across multiple platforms, including digital media, photography, videography, social media, web, print, and emerging communication tools. 7. Demonstrated ability to build trusting relationships with diverse stakeholders and facilitate meaningful community engagement. 8. Ability to exercise sound judgment, discretion, responsiveness, and professionalism in complex or sensitive situations. 9. Experience in public education, public agencies, or community-based organizations preferred. 10. Public Records Officer training (or must be obtained within 90 days of hire). 11. Valid Washington State driver's license. Are all these valid? Yes. I'll make sure each is a separate `
- `. Some might be combined if they're very similar, but the rule says preserve all substantive information. I'll keep them as separate items, but maybe group slightly? I'll err on preserving detail, so separate `
- ` items.
Now the "GENERAL FUNCTIONS" part: "Provides strategic leadership for districtwide communications, storytelling, engagement, public relations, and community outreach; ensures that the District's communication efforts are aligned with the Strategic Plan and helps students, staff, families, and community members see themselves as part of #OneOakHarbor; leads proactive and responsive communication; elevates student and staff voices; strengthens family and community engagement; builds partnerships; supports schools and departments in telling their stories; manages the District's communication platforms and brand; supports crisis and emergency communication; and helps the District listen to and learn from the community it serves."
This is a description of responsibilities. I'll put it under a section. The heading options: "About the role" or "Responsibilities". I'll use `
Responsibilities
` since it's "GENERAL FUNCTIONS". But I could also use `About the role
`. I'll check the exact wording the user gave for headings: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I'll pick "Responsibilities" as it directly maps to "GENERAL FUNCTIONS". Alternatively, I could use "About the role" and put the general functions there. I think "Responsibilities" is fine. Now, what about other sections? The posting might have "Requirements", "Skills", etc. But the user only provided "Qualifications" and "GENERAL FUNCTIONS". I should not invent sections. The rule: "include a section ONLY when the posting has real, specific content for it". So I'll