Programming Coordinator
Patricia Reser Center for the Arts · Beaverton, OR · 1 mo ago
Hybrid$50k–$55k/yrFull-time
We need to output HTML fragment with sections: About the role (maybe "About the job"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We have content: About the job (description). That's about the role. So we can have
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We have content: About the job (description). That's about the role. So we can have About the role
with paragraph(s). Then responsibilities: list of duties. Then requirements/qualifications/skills: we have "SKILLS AND EXPERIENCE NEEDED" and "PREFERRED QUALIFICATIONS". Could combine into Requirements and Qualifications? The instruction: use headings for those categories. We can have Requirements
for required skills/experience, and Preferred Qualifications
maybe but they said only those example headings; but we can still use Qualifications heading. They said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications heading. Skills could be separate but we have skills list; we could put under Skills heading. But we have both skills and experience needed. Could combine into Skills heading. However we also have "PREFERRED QUALIFICATIONS". Could put under Qualifications heading. Let's decide: Use headings: About the role, Responsibilities, Skills, Qualifications, Benefits, Pay. Pay we have salary range. Benefits we have list. Schedule not provided, so omit. Also we have Working Environment - Essential Physical Abilities; that's not in list but could be part of Requirements? Might be omitted as not matching headings; but we could include under Qualifications? But instruction: only include sections when posting has real specific content for it; we can include a section for Working Environment if we want but not in example list; but they said use those headings as examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings; but we could also add other headings if needed? Safer to stick to those. So we need to map content to those headings.
We have:
- About the role: paragraph describing role.
- Responsibilities: bullet list of duties.
- Skills: list of skills and experience needed (the bullet list under SKILLS AND EXPERIENCE NEEDED). Could be under Skills heading.
- Qualifications: maybe combine required and preferred? Could have Qualifications heading for both required and preferred qualifications. But we have also "PREFERRED QUALIFICATIONS". Could put under Qualifications.
- Benefits: list.
- Pay: salary range.
We should not repeat job title as heading. No Job ID etc.
We must preserve all substantive information; do not invent or summarize away detail. Must not include boilerplate like EEO etc. There's none.
We must remove application instructions (HOW TO APPLY). So omit that section.
We must not include cookie/navigation/legal etc. None.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits, so include.
Schedule not stated, so omit.
We must not emit heading followed by filler/placeholder text. Ensure we have content.
Now produce HTML fragment.
Structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings; but we could also add other headings if needed? Safer to stick to those. So we need to map content to those headings.
We have:
- About the role: paragraph describing role.
- Responsibilities: bullet list of duties.
- Skills: list of skills and experience needed (the bullet list under SKILLS AND EXPERIENCE NEEDED). Could be under Skills heading.
- Qualifications: maybe combine required and preferred? Could have Qualifications heading for both required and preferred qualifications. But we have also "PREFERRED QUALIFICATIONS". Could put under Qualifications.
- Benefits: list.
- Pay: salary range.
We should not repeat job title as heading. No Job ID etc.
We must preserve all substantive information; do not invent or summarize away detail. Must not include boilerplate like EEO etc. There's none.
We must remove application instructions (HOW TO APPLY). So omit that section.
We must not include cookie/navigation/legal etc. None.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay and Benefits, so include.
Schedule not stated, so omit.
We must not emit heading followed by filler/placeholder text. Ensure we have content.
Now produce HTML fragment.
Structure:
About the role
... paragraph(s) ...
Responsibilities
- ... each bullet ... ...
Skills
- ... each skill/experience needed ... ...
Qualifications
- ... preferred qualifications ... ...
Requirements
and include both skills/experience needed and physical abilities. But then we would have duplicate content if we also have Skills heading. Better to use Requirements heading for required skills/experience and physical abilities, and Skills heading for maybe not needed? But we have a list of skills and experience needed; that is essentially requirements. So we can put that under Requirements. Then we could have Qualifications heading for preferred qualifications. Then we could have Benefits and Pay. Thus:About the role
...
Responsibilities
- ...
Requirements
- ... skills and experience needed ...
... physical abilities ...
maybe separate paragraph. But we need to keep list format for duties/requirements/benefits. For physical abilities, it's a list of abilities; could be- as well.
Thus:
- A strong sense of urgency with respect to deadlines, contractual obligations, and effective internal communications ...
- Desire and ability to engage in equity and inclusion initiatives and discussions in the workplace, and to apply equity principles in practice
- Ability to represent the Mission and values of The Reser to staff, community partners, and the public
- Candidates may be required to transport visiting artists to events, and accordingly must possess a valid driver's license and have a clean driving record