Sr. Mine Engineer

We need to output HTML fragment with sections: About Us? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The posting includes "About Us" and "Position Overview" and "Job Responsibilities" and "Qualifications". Also there is "Eligibility for PE registration" as part of qualifications. No explicit Benefits, Pay, Schedule sections. So we should include sections for About Us (maybe "About the role"? Actually heading examples include "About the role". But we have "About Us" describing company. Should we use heading "About Us"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. Likely we can use appropriate headings like "About Us", "Position Overview", "Responsibilities", "Qualifications". However 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. So we can include headings for sections present. We need to preserve all substantive information. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus we need to parse the content. Content: About Us Solidus Resources is a U.S.-based gold development company backed by Waterton Mining. The company is focused on advancing the Spring Valley Gold Project in Pershing County, Nevada, and specializes in taking high potential gold assets through late-stage development and into production. Solidus applies a technically rigorous, capital-disciplined approach to mine development, with a strong emphasis on environmental stewardship, operational safety, and community engagement. The Spring Valley Gold Project is located in the prolific Humboldt Range, an area with approximately 60 million ounces of gold endowment within a 50-mile radius. Envisioned as a long-life, low-cost open-pit, heap-leach operation, Spring Valley has a robust resource base and considerable exploration upside along a 7-mile strike length across the Black Ridge fault zone. With a leadership team experienced in engineering, permitting, and large-scale project execution, Solidus Resources is advancing Spring Valley through feasibility, permitting, and construction, with a clear path toward operational readiness. The company’s goal is to responsibly unlock the value of U.S.-based gold assets while building a reputation for excellence in project delivery and sustainable development. Position Overview The Sr. Mine Engineer is responsible for developing and delivering executable mine plans aligned with the Life of Mine (LoM) strategy and annual budgets. This role ensures optimal production, cost efficiency, and consistent ore feed to the leach facility for a large-scale open pit operation. The position plays a key role in advancing a digitally enabled, autonomous mining environment through data-driven planning, system integration, and cross-functional collaboration. Job Responsibilities Mine Planning & Scheduling Develop and manage quarterly and annual mine plans aligned with LoM strategy Prepare production forecasts, budgets, and reconciliations Optimize mine sequencing, haulage, and waste dump design Deliver stockpile, leach, and dump plans with supporting economic analysis Strategic & Technical Planning Design pit phases considering geotechnical, operational, and autonomous constraints Support ore reserve estimation and annual plan reviews Evaluate planning software, systems, and emerging technologies Contribute to continuous improvement of planning methodologies Digital Mine & Systems Integration Ensure planning outputs integrate with fleet management and autonomous systems (AHS/ADS) Support implementation of Short Interval Control (SIC) and data-driven workflows Maintain accurate data flows to support operational execution and performance tracking Stakeholder Collaboration Partner with operations, maintenance, processing, and technical teams Provide planning inputs for production, equipment, and infrastructure decisions Communicate plans, risks, and opportunities to stakeholders up to GM level Governance, Compliance & Reporting Ensure compliance with regulatory, safety, and environmental standards (MSHA, Nevada) Apply structured planning and governance methodologies (e.g., PRINCE2) Produce technical reports, KPIs, and value tracking outputs Qualifications Degree in Mining Engineering or related discipline 5–7+ years of experience in open pit hard-rock mine planning Strong experience with mine planning software (e.g., Vulcan, Deswik, Whittle, NPV Scheduler) Proven track record in implementing planning systems and processes Experience in autonomous or digitally enabled mining environments advantageous Strong analytical, problem-solving, and data management skills Excellent communication and cross-functional collaboration abilities Eligibility for PE registration We need to format. We can have sections:

  About Us

  with paragraph(s). Could be one paragraph.

  Position Overview

  with paragraph.

  Responsibilities

  with list items for each bullet. The responsibilities are grouped under headings within the text: Mine Planning & Scheduling, Strategic & Technical Planning, Digital Mine & Systems Integration, Stakeholder Collaboration, Governance, Compliance & Reporting. We could either keep those as subheadings? The instruction only mentions using

  for section headings (like About the role, Responsibilities...). It doesn't forbid using other headings, but we should follow the instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could treat each major bullet group as

  items, maybe with a inside? But they said use

  • for any list of duties/requirements/benefits. So we can make a
    with each duty as
    • . The duty sentences are separated by line breaks? In the text they are separated by spaces but we can split. We need to preserve all substantive information, not invent or summarize away detail. So we need to include each duty sentence exactly as given. Let's extract duties: Mine Planning & Scheduling - Develop and manage quarterly and annual mine plans aligned with LoM strategy - Prepare production forecasts, budgets, and reconciliations - Optimize mine sequencing, haulage, and waste dump design - Deliver stockpile, leach, and dump plans with supporting economic analysis Strategic & Technical Planning - Design pit phases considering geotechnical, operational, and autonomous constraints - Support ore reserve estimation and annual plan reviews - Evaluate planning software, systems, and emerging technologies - Contribute to continuous improvement of planning methodologies Digital Mine & Systems Integration - Ensure planning outputs integrate with fleet management and autonomous systems (AHS/ADS) - Support implementation of Short Interval Control (SIC) and data-driven workflows - Maintain accurate data flows to support operational execution and performance tracking Stakeholder Collaboration - Partner with operations, maintenance, processing, and technical teams - Provide planning inputs for production, equipment, and infrastructure decisions - Communicate plans, risks, and opportunities to stakeholders up to GM level Governance, Compliance & Reporting - Ensure compliance with regulatory, safety, and environmental standards (MSHA, Nevada) - Apply structured planning and governance methodologies (e.g., PRINCE2) - Produce technical reports, KPIs, and value tracking outputs We need to keep the subheadings? Could embed them as inside
    • or as separate

      ? Not specified. Probably better to keep them as part of the list items? But they are headings grouping duties. If we just list all duties as separate

      we lose grouping but still preserve all info. The instruction: "Use

      • for any list of duties/requirements/benefits". It doesn't forbid additional structure. Could we make nested lists? Could have
        with
        • containing heading and then a sublist? That might be overkill. Simpler: keep the headings as plain text before the
          . Eg:

          Responsibilities

          Mine Planning & Scheduling

          • Develop and manage quarterly and annual mine plans aligned with LoM strategy
          ...
          But then we are using

          for prose, which is okay. The heading inside

          maybe not ideal but acceptable. Could also use

          for subheadings but not prohibited. However instruction only mentions using

          for section headings (examples). It doesn't say we cannot use other heading levels. Safer to stick to

          for main sections and use

          or for subheadings. Thus:

          About Us

          Solidus Resources is a U.S.-based gold development company backed by Waterton Mining. The company is focused on advancing the Spring Valley Gold Project in Pershing County, Nevada, and specializes in taking high potential gold assets through late-stage development and into production. Solidus applies a technically rigorous, capital-disciplined approach to mine development, with a strong emphasis on environmental stewardship, operational safety, and community engagement. The Spring Valley Gold Project is located in the prolific Humboldt Range, an area with approximately 60 million ounces of gold endowment within a 50-mile radius. Envisioned as a long-life, low-cost open-pit, heap-leach operation, Spring Valley has a robust resource base and considerable exploration upside along a 7-mile strike length across the Black Ridge fault zone. With a leadership team experienced in engineering, permitting, and large-scale project execution, Solidus Resources is advancing Spring Valley through feasibility, permitting, and construction, with a clear path toward operational readiness. The company’s goal is to responsibly unlock the value of U.S.-based gold assets while building a reputation for excellence in project delivery and sustainable development.

          Position Overview

          The Sr. Mine Engineer is responsible for developing and delivering executable mine plans aligned with the Life of Mine (LoM) strategy and annual budgets. This role ensures optimal production, cost efficiency, and consistent ore feed to the leach facility for a large-scale open pit operation. The position plays a key role in advancing a digitally enabled, autonomous mining environment through data-driven planning, system integration, and cross-functional collaboration.

          Responsibilities

          Mine Planning & Scheduling

          • Develop and manage quarterly and annual mine plans aligned with LoM strategy
          • Prepare production forecasts, budgets, and reconciliations
          • Optimize mine sequencing, haulage, and waste dump design
          • Deliver stockpile, leach, and dump plans with supporting economic analysis

          Strategic & Technical Planning

          • Design pit phases considering geotechnical, operational, and autonomous constraints
          • Support ore reserve estimation and annual plan reviews
          • Evaluate planning software, systems, and emerging technologies
          • Contribute to continuous improvement of planning methodologies

          Digital Mine & Systems Integration

          • Ensure planning outputs integrate with fleet management and autonomous systems (AHS/ADS)
          • Support implementation of Short Interval Control (SIC) and data-driven workflows
          • Maintain accurate data flows to support operational execution and performance tracking

          Stakeholder Collaboration

          • Partner with operations, maintenance, processing, and technical teams
          • Provide planning inputs for production, equipment, and infrastructure decisions
          • Communicate plans, risks, and opportunities to stakeholders up to GM level

          Governance, Compliance & Reporting

          • Ensure compliance with regulatory, safety, and environmental standards (MSHA, Nevada)
          • Apply structured planning and governance methodologies (e.g., PRINCE2)
          • Produce technical reports, KPIs, and value tracking outputs