Senior Civil Engineer/Project Manager - Mining

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Key info: - At MacKay, we believe great people... (intro). Could be "About the role" or maybe "About MacKay"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" containing description of role and company. - Responsibilities: list of key responsibilities bullet points. - Requirements: Minimum Qualifications maybe. - Qualifications: Preferred Qualifications maybe. - Skills: maybe combine some skills? Could be separate but we can include if content. - Benefits: list of benefits. - Pay: US Pay Range. - Schedule: traveling 20% of the time, hybrid role based out of Albuquerque or Phoenix. We must not create sections with filler like "commensurate with experience". We have actual pay range and schedule info. We must not include duplicated lines, cookie/navigation/legal/EEO etc. Remove lines about background check, E-Verify, EEO, etc. Also remove "Open until filled." etc. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all substantive content from the posting, but we can reformat. We need to ensure we don't lose any substantive info: e.g., "At MacKay, we believe great people are the foundation..." etc. That's substantive but maybe belongs in About the role. We need to include details like: "full-time “seller-doer” Civil Project Manager to join our Mining team. Project win and delivery experience in mine reclamation, site remediation, and closure is preferred. This role offers the opportunity to grow our mining practice in the Southwestern United States. This Project Manager position involves traveling 20% of the time. This hybrid role can be based out of our Albuquerque or Phoenix branch offices." Also responsibilities list. Minimum qualifications list. Preferred qualifications. Why Join MacKay section includes culture etc. That could be part of About the role or maybe separate but we can include as part of About the role. We need to avoid duplication: there is repeated paragraphs about MacKay being infrastructure etc. We need to keep substantive but not duplicate identical lines. We'll need to deduplicate. Let's extract substantive paragraphs: Intro: "At MacKay, we believe great people are the foundation of our growth and success. We are in an exciting phase of expansion, creating new opportunities for our employees to take on meaningful work, collaborate across disciplines, and build long-term careers. Whether your role is technical or part of our support services team, you play an important role in delivering high-quality work and helping our projects succeed. We are seeking a full-time “seller-doer” Civil Project Manager to join our Mining team. Project win and delivery experience in mine reclamation, site remediation, and closure is preferred. This role offers the opportunity to grow our mining practice in the Southwestern United States. This Project Manager position involves traveling 20% of the time. This hybrid role can be based out of our Albuquerque or Phoenix branch offices." Then "Key Responsibilities" list (multiple bullet points). We'll capture each. Then "Minimum Qualifications" list. Then "Preferred Qualifications" list. Then "Why Join MacKay?" with subpoints: A people-first culture, Meaningful work and real impact, Growth and opportunity, A strong and trusted foundation, Opportunities to share in success, Our Values (list of values), Who We Are (some description). This is substantive but could be part of About the role or maybe separate sections like "About MacKay". However instruction only lists certain headings; we can still include other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Probably we should stick to those headings only. So we need to map content to those headings. We can put company culture etc under "About the role". Or maybe we can create a separate "About MacKay" but not in list; risk of being considered not following instruction. Safer to put under "About the role". Skills: we could extract skills from qualifications: Strong project management, leadership, client relationship skills, Excellent written and verbal communication skills, Excellent analytical, organizational, and problem-solving skills, Proficiency in civil engineering design software and methodologies. Could be a Skills section. Benefits: list of benefits. Pay: US Pay Range. Schedule: traveling 20% of the time, hybrid location. We must not create sections with filler like "not specified". We have actual content. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce something like:

About the role

At MacKay, we believe great people are the foundation of our growth and success. We are in an exciting phase of expansion, creating new opportunities for our employees to take on meaningful work, collaborate across disciplines, and build long-term careers. Whether your role is technical or part of our support services team, you play an important role in delivering high-quality work and helping our projects succeed. We are seeking a full-time “seller-doer” Civil Project Manager to join our Mining team. Project win and delivery experience in mine reclamation, site remediation, and closure is preferred. This role offers the opportunity to grow our mining practice in the Southwestern United States. This Project Manager position involves traveling 20% of the time. This hybrid role can be based out of our Albuquerque or Phoenix branch offices.

Responsibilities

• Act as lead engineer for civil and geotechnical components of mining infrastructure projects, with full accountability for technical quality, safety, and regulatory compliance
• Plan, provide design guidance, and manage a variety of active and closure mining projects.
• Prepare and manage project scope, budget, schedule, and meet deliverables.
• Participate in detailed design and permitting processes
• Prepare and review engineering calculations, models, and methods.
• Communicate with clients about current projects, identify and position the firm to win future work, and ensure the firm’s success.
• Effectively supervise technical staff to deliver projects.
• Directing field activities, including investigation, monitoring, and testing services on a construction project
• Write and review technical reports
• Assist with business development efforts to cultivate strong client relationships.

Requirements

• Bachelor’s degree in Civil Engineering, Geotechnical Engineering, or related field.
• Licensed Professional Engineer (PE) in NM or AZ, or the ability to obtain one within a year of employment
• 10+ years of progressive experience in civil and geotechnical engineering, primarily in the mining sector
• Extensive experience with earthworks, foundations, mine waste, tailings, heap leach pads, and water management systems
• Strong project management, leadership, and client relationship skills
• Excellent written and verbal communication skills
• Excellent analytical, organizational, and problem-solving skills
• Proficiency in civil engineering design software and methodologies

Qualifications

• M.S. in Civil, Geotechnical Engineering, or related field.
• Professional Consulting Services experience within the Mining sector

Skills

• Strong project management, leadership, and client relationship skills
• Excellent written and verbal communication skills
• Excellent analytical, organizational, and problem-solving skills
• Proficiency in civil engineering design software and methodologies

But note that skills duplicate some from requirements; but we must preserve all substantive info, not remove duplicates? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicates are okay if they appear in original; but we might be duplicating content that already appears elsewhere. However we might be repeating same bullet points; that's okay as long as we don't lose info. However we might want to avoid redundancy but it's not prohibited. However we could combine skills into a separate section but we already have them in Requirements. Might be redundant but still preserving. Might be okay. But we could also decide not to have a separate Skills section if it's redundant; but we need to include only when posting has real specific content for it. The posting does mention skills explicitly in Minimum Qualifications (strong project management..., excellent written..., excellent analytical..., proficiency...). So we could put those under Skills section, but they'd be duplicated if also in Requirements. To avoid duplication, we could move those skill bullets to Skills and keep Requirements focused on education, licensure, experience, specific technical experience. Let's parse Minimum Qualifications bullet list: - Bachelor’s degree in Civil Engineering, Geotechnical Engineering, or related field. - Licensed Professional Engineer (PE) in NM or AZ, or the ability to obtain one within a year of employment - 10+ years of progressive experience in civil and geotechnical engineering, primarily in the mining sector - Extensive experience with earthworks, foundations, mine waste, tailings, heap leach pads, and water management systems - Strong project management, leadership, and client relationship skills - Excellent written and verbal communication skills - Excellent analytical, organizational, and problem-solving skills - Proficiency in civil engineering design software and methodologies We could split: Requirements: education, licensure, experience, specific technical experience. Skills: the soft skills and software proficiency. Thus Requirements bullets: first four items. Skills bullets: last four. Preferred Qualifications: M.S., Professional Consulting Services experience within Mining sector. Now Benefits: we need to capture all benefits described: "Full-time employees receive a well-rounded benefit package including access to our company-sponsored Medical (including an HSA High Deductible option), Dental, Vision, FSA, and Supplemental Life Insurance plans. We also offer 100% company-paid Life Insurance, Short-Term Disability, and Long-Term Disability coverage. Employees are eligible to participate in our company's 401(k) plan with up to a 4% match. Additionally, employees receive paid vacation and sick time, 11 paid holidays, and are able to participate in employee ownership options. MacKay pays for expenses associated with licensure as well as annual performance bonuses." We should not include boilerplate like background check, E-Verify, EEO, etc. Pay: "US Pay Range: $135,000 USD - $185,000 USD" Schedule: traveling 20% of the time, hybrid role based out of Albuquerque or Phoenix. Now About the role: we need to include the intro paragraph plus maybe the Why Join MacKay and Who Are sections? But we might incorporate some of that into About the role to avoid extra sections. However we must not create sections with filler. If we put all that under About the role, it's fine. Let's craft About the role paragraph(s) that include: - At MacKay, we believe great people are the foundation... (intro) - We are seeking a full-time “seller-doer” Civil Project Manager... - Project win and delivery experience... - This role offers opportunity to grow mining practice in SW US. - This position involves traveling 20% of the time. Hybrid role based out of Albuquerque or Phoenix. - Why Join MacKay? (culture, meaningful work, growth, foundation, ownership, values) - Who We Are (description) We need to avoid duplication: The "Why Join MacKay?" and "Who We Are" sections contain some repetitive sentences already