Jobs · Engineering · Nevada

Geotechnical Engineer, Senior - Springer Mine/Mineral Processing Plant

Blue Moon Metals Inc. · Imlay, NV · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements (maybe Qualifications & Experience), Skills (Skills & Competencies), Benefits (if present), Pay (if present), Schedule (if present). We must only include sections that have real specific content. The posting includes: - About The Springer Site (but we should not repeat job title as heading; we can include About The Springer Site? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says use those headings; but we can also include other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those specific headings. The posting includes "About The Springer Site" and "About The Role". We could map "About The Role" to

About the role

. The "About The Springer Site" maybe not needed as a separate heading; could be part of About the role? But we need to preserve all substantive information. Could include a

describing the site under About the role or as a separate paragraph before the role heading. Since they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. They didn't forbid other headings like About the Springer Site, but they gave examples. Safer to follow examples: use headings for About the role, Responsibilities, Requirements (maybe Qualifications & Experience), Skills, Benefits, Pay, Schedule. We'll include only those that have content. Content: - About the role: we have "About The Role" paragraph plus maybe the Springer site description. We'll combine. - Responsibilities: "Key Responsibilities" with subheadings (Geotechnical Analysis, Field Investigation & Monitoring, Engineering & Construction Support, Risk & Safety Management, Technical Documentation, Stakeholder & Consultant Coordination). We'll output a

  • for each duty? Could list each bullet as
  • . The subheadings could be part of li text. - Requirements: Qualifications & Experience section. We'll output as
    • . - Skills: Skills & Competencies section. Output as
      • . - Benefits: The posting mentions "Receive competitive compensation and benefits while contributing to a safety-focused and collaborative team." That's vague; not specific benefits. No explicit benefits list. So we should NOT create Benefits section because no specific content. - Pay: "Pay Range And Compensation Package Compensation details will be discussed during the interview process." That's not specific; it's placeholder. So we should NOT create Pay section. - Schedule: "Working Conditions ... May require extended or rotational schedules based on project and operational needs." That's somewhat specific but not exact schedule. It's vague. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention schedule indirectly but not specific. Likely we should not create Schedule section because no concrete schedule like "Monday-Friday, 8am-5pm" etc. So omit. Thus we output sections: About the role, Responsibilities, Requirements, Skills. We need to preserve all substantive information. Ensure we don't lose any details. Let's extract content. About The Springer Site: "The Springer site is an underground mining operation located near Imlay, Nevada. As activities at the site continue to advance, geotechnical analysis and monitoring are essential to supporting safe design, construction, and site operations." About The Role: "The Senior Geotechnical Engineer provides technical expertise related to ground conditions, slope stability, excavation support, foundations, earthworks, and geotechnical risk at the Springer site. This role collects and interprets geotechnical information, monitors field conditions, and develops practical recommendations to support safe project execution and operations. Working closely with Engineering, Projects, Construction, Operations, Health and Safety, contractors, and consultants, the Geotechnical Engineer helps identify ground-related risks and ensures geotechnical requirements are incorporated into project planning and field activities." We can combine into a paragraph(s) under About the role. Responsibilities: list each duty. We'll produce
        • for each main duty, possibly with sub-bullets? But we can just include the description as li text. Key Responsibilities sections: - Geotechnical Analysis: "Analyze soil, rock, groundwater, and other geotechnical data to support engineering design and site activities. Evaluate ground conditions, slope stability, excavation requirements, foundations, and earthworks. Develop practical geotechnical recommendations, design criteria, and risk-control measures." - Field Investigation & Monitoring: "Plan and support geotechnical investigations, drilling programs, sampling, mapping, testing, and instrumentation activities. Inspect excavations, slopes, foundations, and other work areas to confirm actual ground conditions. Monitor geotechnical instrumentation and field performance and identify conditions requiring further assessment or action." - Engineering & Construction Support: "Review drawings, specifications, work plans, and contractor submissions for geotechnical considerations. Provide field support during excavation, earthworks, foundation construction, and other ground-related activities. Respond to technical questions and recommend solutions when actual site conditions differ from design assumptions." - Risk & Safety Management: "Identify, assess, document, and communicate geotechnical hazards and risks. Support the development of monitoring plans, trigger-action-response plans, and ground-control procedures. Participate in risk assessments, design reviews, incident investigations, and safety initiatives involving geotechnical conditions." - Technical Documentation: "Prepare technical reports, calculations, inspection records, monitoring summaries, and geotechnical recommendations. Maintain accurate records of investigations, test results, field observations, instrumentation data, and design decisions. Coordinate geotechnical information with engineering drawings, project records, and as-built documentation." - Stakeholder & Consultant Coordination: "Coordinate geotechnical activities with Engineering, Construction, Operations, Projects, contractors, laboratories, and specialist consultants. Review consultant deliverables and monitor field services for alignment with approved scopes and technical requirements. Communicate geotechnical findings, risks, and recommendations clearly to technical and non-technical stakeholders." We'll output each as
        • . Qualifications & Experience: - Bachelor’s degree in Geological Engineering, Geotechnical Engineering, Civil Engineering, or a related discipline. - Professional Engineer licensure in Nevada, or eligibility to obtain it, is preferred. - Minimum of 8 years of geotechnical engineering experience in mining, civil construction, heavy industry, or a related environment. - Experience with field investigations, geotechnical logging, slope-stability assessments, foundations, or earthworks. - Experience interpreting geotechnical data and preparing technical recommendations and reports. - Familiarity with geotechnical instrumentation, monitoring methods, and risk-management practices. - Valid driver’s license and ability to meet all site-access requirements. We'll output as
          • . Skills & Competencies: - Strong knowledge of soil and rock mechanics, geotechnical investigations, and engineering design principles. - Ability to analyze technical data and translate findings into practical field recommendations. - Ability to interpret geological information, drawings, specifications, and construction documentation. - Strong technical writing, communication, and problem-solving skills. - Proficiency with relevant geotechnical analysis, modelling, data-management, and Microsoft Office applications. - Ability to manage consultants, field programs, priorities, and technical deliverables. - Personal Attributes: Safety-focused and attentive to changing field conditions. Analytical, practical, and detail-oriented. Comfortable making evidence-based technical recommendations. Collaborative and able to communicate across engineering, construction, and operational teams. Proactive in identifying and escalating geotechnical risks. Comfortable working in active field and industrial environments. We could split personal attributes into separate li or keep as one. We'll keep as separate li for each attribute maybe. But we can keep as one li with sentences. Better to break into separate li for clarity. Thus: - Strong knowledge of soil and rock mechanics, geotechnical investigations, and engineering design principles. - Ability to analyze technical data and translate findings into practical field recommendations. - Ability to interpret geological information, drawings, specifications, and construction documentation. - Strong technical writing, communication, and problem-solving skills. - Proficiency with relevant geotechnical analysis, modelling, data-management, and Microsoft Office applications. - Ability to manage consultants, field programs, priorities, and technical deliverables. - Safety-focused and attentive to changing field conditions. - Analytical, practical, and detail-oriented. - Comfortable making evidence-based technical recommendations. - Collaborative and able to communicate across engineering, construction, and operational teams. - Proactive in identifying and escalating geotechnical risks. - Comfortable working in active field and industrial environments. Now Working Conditions: we might include as a paragraph under About the role? Not required heading. Could add a

            after About the role maybe. But we have no heading for Working Conditions. The instruction says use headings for those specific sections; we can still include paragraphs outside headings. We'll include a

            for Working Conditions after About the role maybe. But we must preserve all substantive information. Working Conditions includes: "This is a primarily site-based role at the Springer site in Imlay, Nevada. Work involves a combination of office analysis and regular field inspections. May require extended or rotational schedules based on project and operational needs. Requires walking over uneven terrain and accessing active construction or operational areas. The position may involve exposure to outdoor conditions, dust, noise, heavy equipment, elevations, and varying weather conditions." We'll add a

            after About the role. Also "Why Join" section: "Take on a key technical role where your recommendations will directly influence safe design, construction, and site operations. Work on varied geotechnical challenges involving field investigations, earthworks, foundations, slope stability, and risk management. Collaborate closely with Engineering, Construction, Projects, Operations, and specialist consultants. Help shape geotechnical standards, monitoring practices, and risk-management processes as the Springer site advances. Receive competitive compensation and benefits while contributing to a safety-focused and collaborative team." We could incorporate that into About the role or as a separate paragraph. Since we have no heading for Why Join, we can add a

            after Working Conditions maybe. Also "We are committed to diversity and inclusivity in our hiring practices and encourage applications from all qualified individuals." appears twice; we can include as a

            maybe at end. Also "This job posting is for an existing vacancy. Blue Moon Metals Inc. and its business entities do not currently utilize AI to screen, assess, or select applicants." That's metadata; we can fold into a short

            or drop. Probably drop as minor metadata. We must not include boilerplate like EEO etc. But the diversity statement is not boilerplate? It's a statement; could be considered boilerplate but it's substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the Equal Opportunity Statement lines. So we will not include them. Thus final HTML:

            About the role

            ... combined About Springer Site and About The Role paragraphs ...

            Working Conditions: ...

            Why Join: ...

            Responsibilities

            • ...
            • ...

            Requirements

            • ...
            • ...

            Skills

            • ...
            • ...
            No Pay/Benefits/Schedule. Make sure to not include any extra text outside HTML. Let's craft the About the role paragraph: "The Springer site is an underground mining operation located near Imlay, Nevada. As activities at the site continue to advance, geotechnical analysis and monitoring are essential to supporting safe design, construction, and site operations. The Senior Geotechnical Engineer provides technical expertise related to ground conditions, slope stability, excavation support, foundations, earthworks, and geotechnical risk at the Springer site. This role collects and interprets geotechnical information, monitors field conditions, and develops practical recommendations to support safe project execution and operations

Similar jobs