Executive Support Specialist 2 (ESS2) - CNO Executive Assistant
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse posting. Key info: - Position Title: Executive Support Specialist 2 (ESS2) - CNO Executive Assistant (but we do NOT repeat job title as heading). - Agency: Oregon Health Authority - Salary Range: $4,312 - $5,988 (non-PERS qualifying range; if qualifies for PERS, increase by 6.95%). So we have salary info. - Shift: Monday – Friday 8:00am – 5:00pm Days off: Sat/Sun. This position is 100% on site. - Responsibilities: described in "What you will do!" paragraph: provide confidential executive and administrative support to CNO and Nursing Division leaders; functions with integrity and confidentiality; preparing reports, managing assigned projects, scheduling and calendar management; supporting leadership strategic objectives; participates in all CNO related meetings; conducts research assignments; collects data and information for Nursing leadership; supports Nursing meetings including staff and committee meetings, with scheduling and record keeping; provides administrative support with requirements for hospital licensure, regulatory standards, compliance, supporting operational communication, and tracking of data for the Nursing division; applies and interprets ORSs, OARs, nurse contract language (SEIU and AFSCME), staffing policies and procedures, and hospital and department policies and protocols; discretion handling highly sensitive matters; coordinating projects on behalf of the CNO; supporting Nursing Services strategic initiatives and regulatory compliance. - Minimum Qualifications: One year of experience performing administrative duties in support of agency projects or programs. Qualifying experience would involve data collection and analysis; project evaluation and/or analysis; interpretation and application of laws, rules, and regulations; or similar experience. - Desired Attributes: list of attributes: exceptional customer service and ability to communicate complex information clearly and professionally, both verbally and in writing, to a wide range of internal and external partners; advanced proficiency in Microsoft Word, Excel, PowerPoint, Outlook, Teams, Skype and Zoom; proficient in AdobePro, Visio, SharePoint, Intranet Web Page Editing; experience working effectively with individuals and groups with diverse perspectives, interests, and cultural backgrounds, demonstrating strong cultural competence and a commitment to inclusive practices; knowledge of governmental relations and public policy pertaining to mental health issues and challenges; experience with project management tools and concepts; experience in budget and finance operations and principles; experience in managing sensitive issues and confidential information with discretion and professionalism. - Benefits: listed under "About The Team & Benefits Of Joining": Excellent, low-cost medical, vision, and dental coverage for you and your family; optional benefits like life insurance, disability coverage, deferred compensation, and FSA options for health and childcare; generous paid time off: 11 holidays, 3 personal days, monthly sick leave, and vacation accrual starting at 8 hours/month; potential eligibility for the Public Service Loan Forgiveness Program; retirement security through Public Employees Retirement System (PERS)/Oregon Public Service Retirement Plan (OPSRP); training and development opportunities to grow your career with the State of Oregon. - Pay: salary range given. - Schedule: shift Monday-Friday 8am-5pm, days off Sat/Sun, 100% on site. - Additional details: location Salem, OR; full-time; may fill future vacancies; contingent upon criminal records check; salary listed is non-PERS qualifying range; if qualifies for PERS, salary range will increase by 6.95%; etc. But we should not repeat boilerplate like EEO etc. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "How To Apply", "Application Guidance", "After You Apply", "Reminders", "Contact Information", "Helpful Links & Resources", etc. Also remove "Initial Posting Date", "Application Deadline", "Agency", "Position Type", maybe we can include them as metadata in a short
or drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph with agency, location, maybe date? But we should preserve all substantive information. The dates (Initial Posting Date, Application Deadline) are metadata but maybe not substantive for the role? They are not essential to job description; but we could include them in a short paragraph. However instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine metadata into a short
at top. We need to output only HTML fragment, no /, no markdown. Thus produce something like:
Agency: Oregon Health Authority. Location: Salem, OR. Schedule: Monday–Friday 8:00 am–5:00 pm (Sat/Sun off), 100% on‑site. Salary range: $4,312–$5,988 (non‑PERS qualifying; +6.95 % if PERS‑eligible).
Then sections:About the role
maybe a paragraph summarizing purpose: provide confidential executive and administrative support to CNO and Nursing Division leaders... But we must not repeat job title as heading. "About the role" is okay. ThenResponsibilities
with- items for each duty.
Then
Minimum Qualifications
with- .
Then
Desired Attributes
with- (or could be Skills). But we have Skills section maybe separate: we could put desired attributes under Skills. However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications (maybe Minimum Qualifications) and Skills (desired attributes). We'll decide.
We have Pay and Schedule sections: we already included salary and schedule in metadata paragraph, but we could also create separate Pay and Schedule sections if they have specific content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we keep Pay and Schedule as separate sections only if they have real specific content. We have salary range and shift details. Could create
Pay
with paragraph about salary range and PERS note. AndSchedule
with paragraph about shift and on-site. But we already included them in metadata; but we can still create sections. However we must not repeat info. Better to create sections for Pay and Schedule and maybe combine agency/location in a short intro paragraph. Thus: Intro paragraph: Agency, Location. ThenAbout the role
paragraph. ThenResponsibilities
- ...
Then
Qualifications
- ... (minimum qualifications)
Then
Skills
- ... (desired attributes)
Then
Benefits
- ...
Then
Pay
paragraph. ThenSchedule
paragraph. We must not include sections with filler like "commensurate with experience". We have real content. Now we need to ensure we preserve all substantive information. Let's extract details. From posting: - Agency: Oregon Health Authority - Location: Salem, OR (mentioned: "This announcement will be used to fill full-time positions located in Salem, OR," and "This position is 100% in person..."). - Position type: Employee (but not needed). - About the role: The purpose of this position is to provide confidential executive and administrative support to the Chief Nursing Officer and Nursing Division leaders who oversee daily hospital operations and patient care delivery for the Oregon State Hospital. The incumbent functions with integrity and confidentiality in compliance with HIPAA and dealing with sensitive information. We can paraphrase but must preserve all substantive information; we can keep sentences. - Responsibilities list: - preparing reports - managing assigned projects - scheduling and calendar management - supporting leadership strategic objectives and goals - participating in all CNO related meetings - conducting research assignments as assigned - collecting data and information for Nursing leadership - supporting Nursing meetings including staff and committee meetings, with scheduling and record keeping - providing administrative support with requirements for hospital licensure, regulatory standards, compliance, supporting operational communication, and tracking of data for the Nursing division - applying and interpreting ORSs, OARs, nurse contract language (SEIU and AFSCME), staffing policies and procedures, and hospital and department policies and protocols to effectively carry out its duties - handling highly sensitive matters and information with discretion - coordinating projects on behalf of the CNO - supporting Nursing Services strategic initiatives and regulatory compliance We need to ensure we capture all. - Minimum Qualifications: - One year of experience performing administrative duties in support of agency projects or programs. - Qualifying experience would involve data collection and analysis; project evaluation and/or analysis; interpretation and application of laws, rules, and regulations; or similar experience. - Desired Attributes (Skills): - Exceptional customer service and the ability to communicate complex information clearly and professionally, both verbally and in writing, to a wide range of internal and external partners. - Advanced proficiency in Microsoft Word, Excel, PowerPoint, Outlook, Teams, Skype and Zoom. - Proficient in AdobePro, Visio, SharePoint, Intranet Web Page Editing. - Experience working effectively with individuals and groups with diverse perspectives, interests, and cultural backgrounds, demonstrating strong cultural competence and a commitment to inclusive practices. - Knowledge of governmental relations and public policy pertaining to mental health issues and challenges. - Experience with project management tools and concepts. - Experience in budget and finance operations and principles. - Experience in managing sensitive issues and confidential information with discretion and professionalism. - Benefits: - Excellent, low-cost medical, vision, and dental coverage for you and your family. - Optional benefits like life insurance, disability coverage, deferred compensation, and FSA options for health and childcare. - Generous paid time off: 11 holidays, 3 personal days, monthly sick leave, and vacation accrual starting at 8 hours/month. - Potential eligibility for the Public Service Loan Forgiveness Program. - Retirement security through Public Employees Retirement System (PERS)/Oregon Public Service Retirement Plan (OPSRP). - Training and development opportunities to grow your career with the State of Oregon. - Pay: - Salary Range $4,312 - $5,988 (non-PERS qualifying range). If the successful candidate qualifies for PERS, the salary range will increase by 6.95%. - Schedule: - Shift: Monday – Friday 8:00am – 5:00pm - Days off: Sat/Sun - This position is 100% on site We also have other details: "Employment is contingent upon a criminal records check that meets OHA criteria at the time of hire and throughout employment." That's substantive; maybe we could include in a section like "Additional Details" but not required headings. Could add a paragraph after schedule maybe under "Additional Information". But we only have prescribed headings; we could add aafter schedule for extra info. The instruction: "Prefer a few substantive sections over many thin ones." So we could add a short paragraph for "Additional Details" without heading? But they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should stick to those. Additional info like criminal records check could be placed in
- (or could be Skills). But we have Skills section maybe separate: we could put desired attributes under Skills. However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications (maybe Minimum Qualifications) and Skills (desired attributes). We'll decide.
We have Pay and Schedule sections: we already included salary and schedule in metadata paragraph, but we could also create separate Pay and Schedule sections if they have specific content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we keep Pay and Schedule as separate sections only if they have real specific content. We have salary range and shift details. Could create
- .
Then