Engineering Designer

for prose. Do NOT repeat job title as heading. 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. We need to parse the posting. Content: - Title: Engineering Designer - Entry-Level Civil Engineer All Groups All Office Locations $65,000 - $80,000 base salary Regular Full-Time - Company: Robert Peccia & Associates (RPA) - Opening paragraph: welcomes applications from recent graduates and early-career engineers interested in building their careers with our employee-owned civil engineering firm. This posting will remain open as we look for talented entry-level engineers for opportunities across our offices and technical groups. Hiring needs vary over time, and applications will be considered as positions become available. - As an Engineering Designer at RPA, you will work alongside experienced engineers, project managers, designers, and technical staff on a variety of infrastructure projects serving communities throughout Montana and the region. Depending on your interests, experience, office preference, and RPA's staffing needs, opportunities may be available in transportation, water and wastewater, site civil, airports, structures, or other civil engineering disciplines. Engineering Designers gain hands-on experience throughout the planning, design, and construction phases of projects while developing the technical and professional skills needed to advance within the engineering profession. - Typical responsibilities may include: list of bullet points (Engineering Design, Technical Analysis, Reports and Documentation, Project Coordination, Field Work, Construction Support, Professional Development). Each bullet includes description. - Requirements: We are primarily interested in recent graduates and early-career professionals who want to learn, grow, and become long-term contributors to RPA. Desired qualifications include: list of bullet points (Bachelor's degree in Civil Engineering, Civil Engineering Technology, or a related engineering field; Engineering Intern (EI) certification, or the ability to obtain certification within six months of employment; 0-4 years of engineering, design, construction, internship, or related experience; Fundamental understanding of engineering principles and design and construction practices; Strong interpersonal, organizational, and communication skills; Attention to detail and a willingness to learn new technical skills; Ability to work effectively both independently and as part of a project team; Willingness to travel and perform field work when required by project assignments; A positive attitude and commitment to being an active participant in RPA's employee-owned culture and alignment with our Core Values) - Applicants are encouraged to identify their preferred RPA office location(s) and areas of technical interest as part of the application process. Placement will depend on the candidate's interests and qualifications as well as current opportunities and staffing needs within RPA. - Benefits: heading "Benefits About RPA"? Actually there is a line: "Benefits About RPA". Then a paragraph about RPA being employee-owned etc. Then "Company Culture And Benefits" heading, then list of benefits: Generous Retirement Plan, 100% Employee Owned, Competitive Salary and Bonuses, Flexible Work Environment, Professional Growth. Additional details about our benefits can be found on our RPA Advantage Page. - Pay: The posting includes "$65,000 - $80,000 base salary". So we have pay info. - Schedule: "Regular Full-Time". So schedule info. We need to decide sections: We have About the role (intro paragraph), Responsibilities (list), Requirements (list), Benefits (list), Pay (maybe a short paragraph), Schedule (maybe short paragraph). Also maybe Qualifications? The posting lumps qualifications under Requirements. Could also have Skills? Not separate. We must not create sections with filler. So we need to include sections only if we have real content. We have: - About the role: we have introductory paragraph(s). Could combine the first paragraph about welcoming applications and the description of role. That is substantive. - Responsibilities: list of duties. - Requirements: list of qualifications. - Benefits: list of benefits. - Pay: we have salary range. - Schedule: we have "Regular Full-Time". We need to output HTML fragment only, no /, no markdown fences. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. So we won't put a heading for the title. We must not put Job ID/requisition numbers as headings — none present. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the substance but not necessarily verbatim; but we should not lose detail. We'll try to keep the content. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit EEO etc. There's "Applicants are encouraged to identify their preferred RPA office location(s) and areas of technical interest as part of the application process." That's application instruction? Might be considered application instruction; but it's also substantive about placement. The instruction says to remove application instructions. However, the line about identifying preferred office location and areas of technical interest is more about candidate preferences; but it's still part of application process. The instruction says remove application instructions. Should we remove that sentence? It says "Applicants are encouraged to identify their preferred RPA office location(s) and areas of technical interest as part of the application process. Placement will depend on the candidate's interests and qualifications as well as current opportunities and staffing needs within RPA." The first sentence is an instruction; the second is about placement. Might be considered application instruction. Safer to remove the first sentence, keep the second? But the second also mentions placement depends on candidate's interests and qualifications as well as current opportunities and staffing needs. That's substantive about how placement works. Might keep that as prose. We also have "Additional details about our benefits can be found on our RPA Advantage Page." That's a reference to external page; could be considered application instruction? It's a pointer for more details; maybe we keep it as part of benefits section? It's not a list item; it's a sentence. Could keep as prose. We need to avoid duplication: there may be duplicated lines; I don't see duplicates. Now decide sections: - About the role: combine the introductory paragraphs: "Robert Peccia & Associates (RPA) welcomes applications from recent graduates and early-career engineers interested in building their careers with our employee-owned civil engineering firm. This posting will remain open as we look for talented entry-level engineers for opportunities across our offices and technical groups. Hiring needs vary over time, and applications will be considered as positions become available. As an Engineering Designer at RPA, you will work alongside experienced engineers, project managers, designers, and technical staff on a variety of infrastructure projects serving communities throughout Montana and the region. Depending on your interests, experience, office preference, and RPA's staffing needs, opportunities may be available in transportation, water and wastewater, site civil, airports, structures, or other civil engineering disciplines. Engineering Designers gain hands-on experience throughout the planning, design, and construction phases of projects while developing the technical and professional skills needed to advance within the engineering profession." We could also include the sentence about placement? Might be better under About the role or separate? It's about placement based on interests; could be part of About the role. But we also have "Applicants are encouraged to identify their preferred RPA office location(s) and areas of technical interest as part of the application process." We'll remove that as application instruction. Keep "Placement will depend on the candidate's interests and qualifications as well as current opportunities and staffing needs within RPA." That's substantive. Thus About the role paragraph could end with that sentence. Now Responsibilities: list: - Engineering Design: Assist with the development of engineering designs, construction plans, specifications, quantities, and cost estimates - Technical Analysis: Perform engineering calculations, evaluate alternatives, analyze data, and assist with preparation of technical recommendations - Reports and Documentation: Assist with planning documents, engineering reports, technical memoranda, design documentation, and project correspondence - Project Coordination: Work collaboratively with project managers, engineers, designers, clients, agencies, and other members of multidisciplinary project teams - Field Work: Participate in data collection, site visits, construction observation, inspections, and other field activities as appropriate for the project and technical group - Construction Support: Assist with construction documentation, contract administration, record drawings, and project closeout activities - Professional Development: Develop technical expertise through hands-on project experience, mentoring, training, and involvement in professional and community organizations We need to output as

  • each. Now Requirements: list: - Bachelor's degree in Civil Engineering, Civil Engineering Technology, or a related engineering field - Engineering Intern (EI) certification, or the ability to obtain certification within six months of employment - 0-4 years of engineering, design, construction, internship, or related experience - Fundamental understanding of engineering principles and design and construction practices - Strong interpersonal, organizational, and communication skills - Attention to detail and a willingness to learn new technical skills - Ability to work effectively both independently and as part of a project team - Willingness to travel and perform field work when required by project assignments - A positive attitude and commitment to being an active participant in RPA's employee-owned culture and alignment with our Core Values Now Benefits: list: - Generous Retirement Plan: RPA contributes to your retirement future, with no match required, starting on day one - 100% Employee Owned: Our Employee Stock Ownership Program (ESOP) provides you with direct ownership in the company, aligning your success with ours - Competitive Salary and Bonuses: Enjoy a rewarding compensation structure including competitive base salary and company-wide bonus program - Flexible Work Environment: We support work-life balance with excellent leave policies, flexible schedules, and paid time over 40 hours per week - Professional Growth: We support and encourage professional development and involvement in civic/professional organizations and provide ample opportunity for career growth within RPA Also we have "Additional details about our benefits can be found on our RPA Advantage Page." Could be a

    after the list. Now Pay: we have "$65,000 - $80,000 base salary". Also maybe mention "Regular Full-Time" is schedule. So Pay section:

    $65,000 - $80,000 base salary

    Schedule:

    Regular Full-Time

    We need to ensure we don't create sections with filler. All have content. Now order: Typically About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Could also include Qualifications but we have Requirements covering qualifications. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have Requirements; we could also have Qualifications but that would duplicate. Better to keep Requirements only. We must not create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary and schedule, so okay. Now produce HTML fragment. We need to wrap each section in

    heading then content. For lists:

    • ...