Jobs · Management · Oregon

Physical Plant Manager, Construction and Facility Maintenance Manager 2 (Pendleton)

Oregon Department of Corrections · Pendleton, OR · 1 mo ago
ManagementFull-time
We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove sections like "About The Department", "About The Process – What To Expect", "Requirements For Employment", "Equity, Diversity, Inclusion, and Belonging", etc unless they contain substantive info relevant to sections? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove EEO statements, etc. But we need to keep substantive info like responsibilities, qualifications, benefits, pay, schedule, etc. We need to parse the posting. Key info: - Position Title: Physical Plant Manager, Construction and Facility Maintenance Manager 2 (Pendleton) (but we don't repeat as heading) - Agency: Department of Corrections - Initial Posting Date 09/25/2026 Application Deadline 10/06/2026 (metadata, can be folded into short p or drop) - Salary Range $7,537 - $11,657 - Position Type Employee - Job Description: includes "About The Job – Your Role" paragraph. - Responsibilities: list of duties. - Minimum Qualifications: experience and education. - Enterprise Competencies: list. - Benefits: description. - Working Conditions: description. - About The Department: maybe not needed. - About The Process – What To Expect: maybe not needed (application instructions). Remove. - Requirements For Employment: includes CJIS background check etc. Might be considered requirements? Could be part of Requirements section. - Equity, Diversity, Inclusion, etc: remove as EEO boilerplate. - Additional info: Veterans preference etc maybe not needed. - Working Conditions: includes details. - Benefits: includes salary range note about PERS. We need to decide which sections to include: About the role (summary), Responsibilities, Requirements (maybe combine minimum qualifications and enterprise competencies?), Qualifications (maybe same as Requirements?), Skills (maybe enterprise competencies?), Benefits, Pay, Schedule. We must not create sections with filler like "commensurate with experience". Pay section: we have salary range, so we can include Pay section with that range. Schedule: we have work schedule info: "Work schedule is driven by institutional need... may involve long hours... Employee is subject to recall 24 hours per day... Occasional in-state and out-of-state overnight travel is required." That's schedule info. So we can include Schedule section. Benefits: we have description. Now we need to ensure we don't repeat content unnecessarily. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits, and

    for prose. We must not include markdown fences. We must output only HTML fragment. Let's extract substantive content. About the role: The paragraph after "About The Job – Your Role": "The Physical Plant Manager is part of the EOCI Management Team and oversees all operations of the institution’s physical plant. This role manages major facility projects, leads physical plant staff, ensures maintenance and repair activities are completed properly, and maintains compliance with safety, OSHA, and DOC standards. The manager directs personnel functions including hiring, training, evaluations, discipline, and supervision of staff and AIC work crews, while ensuring strict adherence to DOC rules for custody, tool/key control, and contraband. The position coordinates capital projects with DOC Facilities, oversees contractor activities, and manages building systems, utilities, and security maintenance. Responsibilities include monitoring section and vehicle budgets, auditing utility costs, and ensuring fiscal compliance. The manager oversees the assigned state vehicle fleet and supports institutional operations as Officer of the Day, assists in emergencies, completes investigations, and leads special projects. This role promotes positive communication, community engagement, and supports DOC values through inclusive leadership and fostering a respectful, culturally competent workplace. This position is management services and may be eligible for Police & Fire (P&F) benefits through Public Employees Retirement System (PERS), as defined by statute." We can keep that as prose in About the role. Responsibilities: The posting already has a list of duties within that paragraph; but we could also extract a bullet list. However the instruction: Use

    • for any list of duties/requirements/benefits. The responsibilities are embedded in prose; we could convert to list for clarity but must preserve all substantive information; we can either keep as prose or list. Safer to keep as prose? But they said use
      • for any list of duties/requirements/benefits. If we don't have an explicit list, we can keep prose. However we could create a list from the responsibilities mentioned. That would be summarizing but not inventing; we would be rephrasing but preserving detail. Might be okay. But to be safe, we can keep responsibilities as prose within the About the role section, and not create a separate Responsibilities section unless there is a distinct list. The posting does not have a separate "Responsibilities" heading; it's integrated. So we may not create a Responsibilities section. However the instruction says to include a section ONLY when the posting has real, specific content for it. Since there is no explicit Responsibilities section, we could omit it. But we might still include Responsibilities if we extract the duties into a list. That would be creating a section with content derived from the posting, which is allowed as long as we preserve all substantive info and not invent. I think it's acceptable to create a Responsibilities section with bullet list of duties extracted. Similarly Requirements: we have Minimum Qualifications (experience and education) and Enterprise Competencies. Could be Requirements section. Qualifications: maybe same as Requirements; but we could separate: Requirements = minimum qualifications, Qualifications = enterprise competencies? Or combine. Skills: maybe enterprise competencies. We need to avoid thin sections. Prefer few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But the instruction lists possible headings; we can choose to include only those with real content. We could include About the role, Responsibilities, Requirements (including minimum qualifications and enterprise competencies), Benefits, Pay, Schedule. We should not include Skills if we already covered enterprise competencies under Requirements. Let's decide: - About the role: prose summary. - Responsibilities: bullet list of duties. - Requirements: bullet list of minimum qualifications (experience/education) and enterprise competencies (maybe as sub-bullets). Could be two lists. - Benefits: bullet list of benefits. - Pay: salary range. - Schedule: prose about work schedule, recall, travel. We must not include fluff like "commensurate with experience". Not present. Now extract details. Responsibilities list: from the paragraph we can break into bullet points: - Oversees all operations of the institution’s physical plant. - Manages major facility projects. - Leads physical plant staff. - Ensures maintenance and repair activities are completed properly. - Maintains compliance with safety, OSHA, and DOC standards. - Directs personnel functions including hiring, training, evaluations, discipline, and supervision of staff and AIC work crews. - Ensures strict adherence to DOC rules for custody, tool/key control, and contraband. - Coordinates capital projects with DOC Facilities. - Oversees contractor activities. - Manages building systems, utilities, and security maintenance. - Monitors section and vehicle budgets. - Audits utility costs. - Ensures fiscal compliance. - Oversees the assigned state vehicle fleet. - Supports institutional operations as Officer of the Day. - Assists in emergencies. - Completes investigations. - Leads special projects. - Promotes positive communication, community engagement. - Supports DOC values through inclusive leadership and fostering a respectful, culturally competent workplace. - May be eligible for Police & Fire (P&F) benefits through PERS (maybe belongs to benefits but we can keep). But note that the last sentence about P&F benefits is more about benefits; we could keep in Benefits section. Now Minimum Qualifications: The text: "Manager 2 Six years of lead work, foreman work, or supervision related to the class concept; OR four years of experience related to the class concept AND completion of an accredited vocational-training or construction-training program related to the class concept; OR three years of related experience and a bachelor’s degree in a related field; OR an equivalent combination of education, training, and experience." We can format as bullet list with OR statements. Enterprise Competencies list: Communication, Innovation, Intentional Engagement, Mentoring and Developing People, Stewardship, Business Acumen. We could list them. Now Benefits: The paragraph: "The salary range listed above is for non-PERS qualifying applicants. PERS qualifying applicants may be eligible for an adjusted range to reflect an additional 6.95%. The State of Oregon provides a generous benefit package, which includes: Family health, vision, and dental insurance Vacation, sick leave, and 11 paid holidays 21 days paid military leave for national guard and reserve components Optional short and long-term disability Term life insurance Fully paid retirement program Oregon Saving Growth Plan Flexible spending accounts for health and childcare And more" We need to turn into bullet list. Pay: Salary range $7,537 - $11,657 (presumably monthly?). We'll just output that. Schedule: From Working Conditions and other parts: "Work schedule is driven by institutional need in providing appropriate supervision of direct reports and completing other duties as assigned. There may be high priority administrative assignments, which may involve long hours within the confines of the institution. Employee is subject to recall 24 hours per day in the event of an emergency or work stoppage and is subjected to assignment in any area of the institution. Occasional in-state and out-of-state overnight travel is required." Also earlier: "Work is performed in a prison housing maximum, close, medium, and minimum-security AICs. The AICs have the potential for becoming angry, hostile, abusive, and aggressive increasing the risk for employees Of physical injury, death and/or being taken hostage. There is an inherent responsibility to provide assistance through recall and/or reassignment during AIC unrest and other emergency situations occurring at the institution. The institution is located in Eastern Oregon and is exposed to temperature extremes and inclement weather. The incumbent may be required to perform duties outside in the inclement weather and temperature extremes. Eastern Oregon Correctional Institution buildings are air-conditioned in most areas, climate controlled in other areas. Walking long distances to get to the workstation or to perform work will be required. Most AIC housing units are four requiring the use of stairs to reach the different level. All employees are required to use a computer for E-Mail, word processing and related AIC information systems in the regular performance of their duties." That's more about working conditions, not strictly schedule. But schedule section can include work schedule, recall, travel, maybe also mention environmental conditions? The instruction says Schedule section only if posting actually states them. The posting does state work schedule details, recall, travel. So we can include those. The other working condition details could be omitted or maybe we could include under Schedule? Might be considered working conditions not schedule. Safer to include only schedule-related info: work schedule driven by institutional need, may involve long hours, employee subject to recall 24/7, occasional in-state/out-of-state overnight travel. We'll keep that. Now we need to ensure we don't include boilerplate like EEO, etc. We'll omit those paragraphs. Now produce HTML. Structure:

        About the role

        ... prose ...

        Responsibilities

        • ...
        • ...

        Requirements

        Minimum qualifications:

        • Six years of lead work, foreman work, or supervision related

Similar jobs