Principal Engineer

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must include only sections with real specific content. Let's parse the posting. Content: - About The Role: paragraph describing role, etc. That's about the role. So we can have

About the role

with

content. - Responsibilities: The "What You'll Do" section lists duties. So we can have

Responsibilities

with

• each duty. - Requirements: Minimum Qualifications (Bachelor's degree, years experience, supervisory experience, or equivalent). Also Required Licenses & Certifications (PE license, driver's license). Those are requirements. Could combine into Requirements section. - Qualifications: Desired (but Not Required) Attributes list. Could be Qualifications or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide where each piece goes. We have: - Minimum Qualifications (required) -> could be Requirements. - Required Licenses & Certifications -> also Requirements. - Desired (but Not Required) Attributes -> could be Qualifications or Skills. Since they are desired attributes, maybe Qualifications. - Skills: maybe we could extract from Ideal Candidate section: collaborative leader, communication, stakeholder engagement, negotiation, leadership, etc. That could be Skills. - Benefits: The posting mentions Benefits: "The City of Bend offers an excellent competitive benefits package for Employees and Dependents for health and dental coverage, retirement benefits, and a robust paid leave program. Details are available on the benefits tab of the job posting." That's specific enough to create Benefits section. - Pay: Starting compensation description: "Starting compensation is determined based on a pay equity analysis considering the candidate’s education, applicable work experience, and internal equity." That's not a specific number or range, but it's still content about pay. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state something about starting compensation, albeit vague. It's still stating something about pay. So we can include Pay section with that sentence. - Schedule: No mention of schedule (full-time is mentioned earlier: regular, full-time). That's schedule info: "regular, full-time". That is schedule. So we could include Schedule section with that. But we need to avoid filler like "commensurate with experience", "not specified", etc. The pay description is not filler; it's a statement about how compensation determined. It's okay. Schedule: "regular, full-time" is specific. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We must remove application instructions (like deadline, attachments, etc.) and EEO statement. Also remove "What To Know Before Applying" etc. Also remove "Veterans' Preference", "Equity Statement", "Diversity & Equal Opportunity Employer Statement". Also remove "Classification Framework: Principal Engineer". Also remove "Please review the entire job posting, including the application requirements at the end." etc. We must preserve all substantive information: role description, duties, minimum qualifications, required licenses, desired attributes, ideal candidate traits, benefits, pay, schedule. We must not invent or summarize away detail. So we need to keep the exact sentences? We can keep them but can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can keep them as is. We can copy the text. We need to format as HTML: headings

  , paragraphs

  , lists

  • . Use only those tags. We must not include or . Just fragment. We need to decide ordering: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Let's extract each. About the role: The first paragraph after "About The Role". It includes multiple sentences. Let's copy that block: "The City of Bend is accepting applications for one (1) regular, full-time Principal Engineer in the Engineering Department. This is a salaried, exempt, non-represented position. The City may use this recruitment to establish an eligibility list for current or future vacancies. Please review the entire job posting, including the application requirements at the end. The City of Bend is seeking an experienced and collaborative Principal Engineer to lead the Engineering Department's Water and Stormwater Team and help deliver critical infrastructure projects that support one of Oregon's fastest-growing communities. In this role, you will provide technical leadership and strategic oversight for the planning, design, and delivery of water and stormwater capital improvement projects, including treatment, storage, transmission, distribution, and related infrastructure improvements. You will work closely with Water Services staff, operations personnel, consultants, contractors, regulators, and community stakeholders to ensure projects are delivered safely, efficiently, and with long-term community value. This is an exciting opportunity to assume leadership of an established engineering team and influence major investments in Bend's water and stormwater infrastructure. The successful candidate will oversee a diverse portfolio of capital projects, guide engineering staff, manage consultant partnerships, and help shape infrastructure strategies that support system reliability, regulatory compliance, operational resilience, and future growth. The position offers meaningful opportunities to solve complex technical challenges while contributing to the City's long-range planning efforts. The Principal Engineer plays an important role in connecting engineering solutions with community priorities. Candidates who are energized by public service, enjoy mentoring staff, and are motivated by delivering high-impact infrastructure projects will find significant opportunities to make a lasting contribution to the City of Bend and its residents." But note we need to remove application instructions like "Please review the entire job posting, including the application requirements at the end." That's part of application instructions; we should remove that sentence. Also "The City may use this recruitment to establish an eligibility list for current or future vacancies." That's maybe not application instruction but still about recruitment; it's substantive? Might be okay. However it's not about role specifics. Might be considered boilerplate? It's about the recruitment process. The instruction says remove application instructions. That sentence is about eligibility list; maybe not essential. Safer to remove it? It's not about the role. I'd remove it. Also "The City of Bend is accepting applications for one (1) regular, full-time Principal Engineer in the Engineering Department." That's substantive about the position. Keep. "This is a salaried, exempt, non-represented position." Keep. Now the rest is role description. We'll combine into a paragraph. Now Responsibilities: The "What You'll Do" list. Let's extract each duty: - Lead the planning, design, and delivery of water and stormwater infrastructure capital improvement projects. - Manage a portfolio of projects from early concept development through construction completion. - Supervise, mentor, and support the professional growth of engineering staff and project team members. - Coordinate with Water Services staff, consultants, contractors, regulatory agencies, and community stakeholders. - Manage project budgets, schedules, scopes, risks, and performance outcomes. - Review engineering plans, technical reports, specifications, and contract documents. - Present project information, recommendations, and updates to City leadership, City Council, advisory groups, and the public. - Oversee consultant selection, contract administration, procurement activities, and construction administration. - Help establish infrastructure priorities and support long-range capital planning efforts. - Respond to public inquiries and assist in resolving project-related concerns. We'll put each as
  • . Now Requirements: Minimum Qualifications and Required Licenses & Certifications. Minimum Qualifications text: "Bachelor's degree in Civil Engineering or a closely related field; andSix (6) to eight (8) years of progressively responsible engineering experience; andTwo (2) to three (3) years of supervisory or people management experience; orAn equivalent combination of education, training, and experience sufficient to successfully perform the essential duties of the position." Note there are missing spaces after semicolons? The original: "Bachelor's degree in Civil Engineering or a closely related field; andSix (6) to eight (8) years of progressively responsible engineering experience; andTwo (2) to three (3) years of supervisory or people management experience; orAn equivalent combination of education, training, and experience sufficient to successfully perform the essential duties of the position." We need to preserve the information; we can keep as is but maybe add spaces for readability? Changing text might be considered altering? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Adding spaces is not changing meaning, but it's altering the exact string. Safer to keep exactly as given? However the missing spaces might be a typo; but we should not "correct" it? The instruction doesn't forbid fixing obvious typos, but better to keep as is. We'll keep the exact text. Now Required Licenses & Certifications: "Professional Engineer (PE) license in Oregon, or ability to obtain Oregon licensure within six (6) months of appointment.Valid driver's license meeting City of Bend driving standards." Again missing space after period. Keep as is. We can combine into a
    list? Or just

    . Since it's a list of requirements, we could use

    • each. But the instruction: Use
      • for any list of duties/requirements/benefits. So we should use list for requirements. Thus we can have two
      • items: one for Minimum Qualifications, one for Required Licenses & Certifications. Now Qualifications: Desired (but Not Required) Attributes list. Extract: - Experience managing municipal water and stormwater utility capital improvement projects. - Experience leading engineering teams in a public-sector environment. - Experience with water treatment, storage, transmission, and distribution systems. - Demonstrated success managing multiple large-scale capital projects simultaneously. - Oregon PE license at time of application. - Master's degree in Civil Engineering, Water Resources, Engineering Management, or a related field. - PMP certification or similar project management credential. - Experience presenting to elected officials, governing boards, or advisory committees. We'll put as
        • . Now Skills: Ideal Candidate section includes traits. Extract sentences: "We're looking for someone who is a collaborative and approachable leader, thrives in a team environment, and enjoys developing others. The ideal candidate can balance competing priorities, effectively communicate complex technical information to diverse audiences, and build trusted relationships with colleagues, consultants, regulators, and community members. They are adaptable, solutions-focused, and motivated by serving the public through meaningful infrastructure investments. Highly qualified candidates will bring advanced knowledge of civil and water utility engineering practices, capital project delivery, construction management, consultant and contract administration, budgeting, regulatory compliance, and public-sector project management. Candidates should also demonstrate strong communication, stakeholder engagement, negotiation, and leadership skills." We could treat this as Skills. Use
          • each skill? Might be many. Could also put as

            . But instruction: Use

            • for any list of duties/requirements/benefits. Skills is a list; we can make list. We need to extract individual skills: collaborative and approachable leader, thrives in a team environment, enjoys developing others, balance competing priorities, effectively communicate complex technical information to diverse audiences, build trusted relationships with colleagues, consultants, regulators, and community members, adaptable, solutions-focused, motivated by serving the public through meaningful infrastructure investments, advanced knowledge of civil and water utility engineering practices, capital project delivery, construction management, consultant and contract administration, budgeting, regulatory compliance, public-sector project management, strong communication, stakeholder engagement, negotiation, leadership skills. That's many; but we can keep as a paragraph maybe. However instruction says use
              • for any list of duties/requirements/benefits. Skills is a list; we could still use
                • . But we risk making huge list; still okay. Alternatively we could treat Skills as

                  because it's not a clear list but a description. The instruction says "Use

                  • for any list of duties