Project Manager Business Operations
Alta Resource Technologies · Boulder, CO · 3 wk ago
On-siteProject Management$90k–$120k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and Preferred Qualifications?), Benefits, Pay, Schedule? The posting includes Pay: salary range $90k-$120k, benefits listed. No schedule specifics. So we include Pay and Benefits sections. Also maybe "About Alta" is repeated but we should not repeat job title heading. The "About Alta" description appears twice; we can include a short paragraph about the company maybe under a heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says include a section ONLY when posting has real, specific content for it. So we need sections: About the role (we have that paragraph), Responsibilities (list), Requirements (maybe combine Required Qualifications and Preferred Qualifications? Could split into Required Qualifications and Preferred Qualifications but both are under Qualifications. Could have a single Requirements section with both required and preferred? Might be better to have Required Qualifications and Preferred Qualifications as sub-sections? But only allowed headings from list; we could use Requirements for required qualifications and maybe Skills for preferred? However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Requirements (for required qualifications) and Skills (for preferred qualifications). Or we could combine both into Requirements and not have Skills. But we need to preserve all substantive info. Let's create:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says include a section ONLY when posting has real, specific content for it. So we need sections: About the role (we have that paragraph), Responsibilities (list), Requirements (maybe combine Required Qualifications and Preferred Qualifications? Could split into Required Qualifications and Preferred Qualifications but both are under Qualifications. Could have a single Requirements section with both required and preferred? Might be better to have Required Qualifications and Preferred Qualifications as sub-sections? But only allowed headings from list; we could use Requirements for required qualifications and maybe Skills for preferred? However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Requirements (for required qualifications) and Skills (for preferred qualifications). Or we could combine both into Requirements and not have Skills. But we need to preserve all substantive info. Let's create:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
The starting salary range for this position is $90,000 to $120,000 annually, commensurate with experience.
We should not include Schedule because not specified. We need to remove boilerplate: duplicate About Alta paragraphs, EOE, privacy policy, etc. Also remove "About Alta Alta Resource Technologies (Alta) is a next generation mining company..." repeated twice; we can keep one short paragraph about the company maybe not needed as a heading; but we could include it under About the role? The instruction: 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 shortor drop it. The "About Alta" description is not a heading; we could include it as a paragraph before About the role? But they said use
for section headings (e.g. About the role, Responsibilities...). They didn't forbid having a paragraph about the company outside headings. However they said "Prefer a few substantive sections over many thin ones." Including a company description paragraph may be okay but not required. The posting already has "About Alta" repeated; we could keep one instance as a brief intro paragraph before the About the role heading. That would preserve substantive info about the company. Let's do that: a
with the company description (once). Then
About the role
etc. We need to ensure we don't include any boilerplate like "EOE", "equal opportunity employer", "privacy policy", "e-Verify", etc. Let's extract the company description: "About Alta Alta Resource Technologies (Alta) is a next generation mining company that uses synthetic biology to separate critical minerals from conventional and unconventional resources, including e-waste. Founded in 2023, the company is expanding its team in Boulder, CO. The exponential growth of new tech industries, as well as the information technology sector, are driving historic growth in mineral demand and stressing existing supply streams. Meeting new demand, diversifying the supply chain, and producing minerals in a more sustainable manner requires the rapid development, deployment and scaling of new technologies. This mineral challenge represents a historic opportunity for technology development and value creation. Alta is proud to be at the vanguard of this mega trend." We'll keep that as a paragraph. Now About the role paragraph: "Alta is seeking a Project Manager, Business Operations to sit at the intersection of commercial expansion and disciplined project execution. You will provide project management support, structure, and leadership across all business operations activity, with exclusive focus on U.S. and international expansion, government-associated contracts and deliverables, and the operating rhythm that keeps growth work visible and on track. The role carries a meaningful financial-analysis load and ownership of day-to-day project management tooling, especially Confluence and Jira, and helps support company-wide OKR management. Success requires commercial judgment, strong cross-functional coordination, and comfort working with direct exposure to senior leadership. This is a PM-centered seat for someone who wants to operate across strategy and hands-on execution in a high-impact, early-stage environment." Now Responsibilities list: we need to capture each bullet. List from posting: - Provide project management structure, discipline, and follow-through for all business operations activity, focused on expansion across the U.S. and internationally. - Manage government-associated contracts and deliverables end to end: tracking, documentation, milestones, reporting, and cross-functional coordination through completion. - Build and maintain plans, timelines, risk registers, and status reporting for business operations and expansion workstreams. - Perform financial analysis in support of business operations decisions (deal framing, scenario modeling, and tracking as needed). - Own day-to-day quality of core PM tooling, especially Confluence and Jira: structure, hygiene, templates, and adoption so information stays findable and current. - Support company-wide OKR management: drafting, tracking, cadence, and reporting with exposure to executive leadership. - Drive clear stakeholder communication across commercial, technical, operations, and leadership stakeholders. - Step into ambiguous workstreams, structure them into actionable plans, and drive them to completion with minimal hand-holding. - Identify process gaps and stand up lightweight, durable ways of working as the company scales. Now Required Qualifications list: - Bachelor’s degree or equivalent practical experience. - 3–5 years of professional experience, including project management experience of any kind (PMO, operations, commercial, consulting, or similar). - Bias for getting work done in ambiguous, fast-moving environments as a strong generalist. - Working fluency with modern collaboration and PM tools, with ability to keep Confluence and Jira well organized and useful. - Strong written and verbal communication skills, including comfort briefing and working alongside senior leaders. - U.S. citizenship required. Preferred Qualifications list: - Experience supporting contracts, commercial agreements, or legal/process coordination (not required to be an attorney). - Financial modeling or analytical experience (Excel or equivalent). - Exposure to government, regulated, dual-use, or high-growth startup environments. - Familiarity with critical minerals, industrial tech, or national-security supply chains. - PMP or similar project management credential. Now Benefits list: - Competitive compensation and benefits package: The starting salary range for this position is $90,000 to $120,000 annually, commensurate with experience. Benefits include 401(k), medical/dental/vision coverage, flexible time off, paid parental leave, paid sick leave, and company holidays. We need to separate Pay and Benefits sections. The posting says "Competitive compensation and benefits package: The starting salary range for this position is $90,000 to $120,000 annually, commensurate with experience. Benefits include 401(k), medical/dental/vision coverage, flexible time off, paid parental leave, paid sick leave, and company holidays." We could put Pay section with salary range, Benefits section with list of benefits. Pay:The starting salary range for this position is $90,000 to $120,000 annually, commensurate with experience.
Benefits:- 401(k)
- medical/dental/vision coverage
- flexible time off
- paid parental leave
- paid sick leave
- company holidays
then list. But instruction: Use
for prose. So we can have a
describing the package then
- for benefits.
Now ensure we don't include any boilerplate like "EOE", "equal opportunity employer", "privacy policy", "e-Verify", etc.
Now produce HTML fragment.
We need to output only HTML, no markdown fences.
Let's craft:
- Provide project management structure, discipline, and follow-through for all business operations activity, focused on expansion across the U.S. and internationally.
- Manage government-associated contracts and deliverables end to end: tracking, documentation, milestones, reporting, and cross-functional coordination through completion.
- Build and maintain plans, timelines, risk registers, and status reporting for business operations and expansion workstreams.
- Perform financial analysis in support of business operations decisions (deal framing, scenario modeling, and tracking as needed).
- Own day-to-day quality of core PM tooling, especially Confluence and Jira: structure, hygiene, templates, and adoption so information stays findable and current.
- Support company-wide OKR management: drafting, tracking, cadence, and reporting with exposure to executive leadership.
- Drive clear stakeholder communication across commercial, technical, operations, and leadership stakeholders.
- Step into ambiguous workstreams, structure them into actionable plans, and drive them to completion with minimal hand-holding.
- Identify process gaps and stand up lightweight, durable ways of working as the company scales.
- Bachelor’s degree or equivalent practical experience.
- 3–5 years of professional experience, including project management experience of any kind (PMO, operations, commercial, consulting, or similar).
- Bias for getting work done in ambiguous, fast-moving environments as a strong generalist.
- Working
About Alta Alta Resource Technologies (Alta) is a next generation mining company that uses synthetic biology to separate critical minerals from conventional and unconventional resources, including e-waste. Founded in 2023, the company is expanding its team in Boulder, CO. The exponential growth of new tech industries, as well as the information technology sector, are driving historic growth in mineral demand and stressing existing supply streams. Meeting new demand, diversifying the supply chain, and producing minerals in a more sustainable manner requires the rapid development, deployment and scaling of new technologies. This mineral challenge represents a historic opportunity for technology development and value creation. Alta is proud to be at the vanguard of this mega trend.
About the role
Alta is seeking a Project Manager, Business Operations to sit at the intersection of commercial expansion and disciplined project execution. You will provide project management support, structure, and leadership across all business operations activity, with exclusive focus on U.S. and international expansion, government-associated contracts and deliverables, and the operating rhythm that keeps growth work visible and on track. The role carries a meaningful financial-analysis load and ownership of day-to-day project management tooling, especially Confluence and Jira, and helps support company-wide OKR management. Success requires commercial judgment, strong cross-functional coordination, and comfort working with direct exposure to senior leadership. This is a PM-centered seat for someone who wants to operate across strategy and hands-on execution in a high-impact, early-stage environment.