Manager, Interconnection
Copia Power · Lake Oswego, OR · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: About the role? Actually the job description includes "Job Description" and then description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We have:
- About the role: The job description paragraph: "Copia is seeking a Manager, Interconnection to manage generation interconnection requests, coordinate application and study processes, and lead interconnection agreement negotiations, as well as support facility construction for renewable energy projects in the US. The ideal candidate will be responsible for managing, coordinating, and leading all aspects of the generation interconnection process and related engineering for solar, energy storage, and natural gas projects. This role requires extensive knowledge of FERC large generator interconnection processes and tariff requirements, experience supporting early-stage development of utility-scale interconnection projects and GIA negotiations/executions, and familiarity with interconnection and power flow studies. The Manager, Interconnection will report directly to the Director of Transmission & Interconnection, working closely with Copia’s asset management, energy markets, legal, and finance teams in an individual contributor capacity."
That's about the role.
- Responsibilities: The "Key Responsibilities" bullet list. We need to extract each bullet as . The bullet list includes many items separated by periods but likely each line is a bullet. We'll need to parse them.
Let's list them:
"Support and coordinate the generation and load interconnection process for utility-scale solar, energy storage, natural gas, and data center projects, including pre-application feasibility analysis, interconnection application submission, interconnection study & agreement processes, communicating study results, and EPC milestone management."
"Provide responses and analysis to internal site selection processes to determine feasible transmission locations to apply for interconnection, timed and coordinated to support queue application open windows"
"Request and coordinate application technical packages prepared by transmission consulting engineers"
"Submit interconnection applications to ISOs/Utilities"
"Support timely execution of study agreement and payment of deposits and study fees"
"Track execution of queue milestones such as: Deficiency corrections Scoping meetings Study agreement execution and funding Study results meetings Generator and Load Interconnection Agreement negotiation and execution GIA and Load Milestone tracking and execution"
"Coordinate with utilities, regulatory agencies, and other stakeholders to obtain interconnection approvals."
"Participate in ISO/PTO Generation Interconnection and other stakeholder forums to stay current on industry changes and trends."
"Coordinate with Land Acquisition, Engineering, Permitting, EPC, and Operations teams to develop a strong pipeline of solar, energy storage, natural gas, and data center projects"
"Provide interconnection support for project acquisition and financing activities"
"Provide coordination support for co-location of generation projects with data center campuses"
"Support development and maintenance of company tracking tools"
"Ensures all milestones are kept up to date in company tracking tools"
"Support consultant and other service provider activities, including tracking work order status"
We need to ensure each bullet is a . Some bullets have internal lists (like "Track execution of queue milestones such as: Deficiency corrections Scoping meetings ..."). We can keep as text inside .
- Requirements: The "What We Look For" bullet list: "Ability to communicate effectively in verbal and written correspondence.", "Highly driven with problem-solving abilities, integrity, and strong work ethic.", "Proactive mindset with the ability to thrive in a fast-paced, dynamic environment.", "Ability to work effectively within a rapidly changing organization.", "Demonstrated collaborative partnerships with peers, management, and vendors.", "Resourcefulness and polite persistence."
We'll put those as under Requirements.
- Qualifications: "Minimum Qualifications" bullet list: "6+ years’ professional experience, preferably in the renewable energy industry", "Bachelor’s degree preferred", "Proven experience with Microsoft Office, including advanced proficiency in PowerPoint & Excel", "Experience with project management software", "Ability to work in the Dana Point, CA, Salt Lake City, UT, Phoenix, AZ, or Lake Oswego office a minimum of 3 days per week.", "Ability to travel up to 25%", "Applicants must be authorized to work in the United States without employer sponsorship.", "We are partnering with select search firms for this role and are not accepting inquiries or candidates from additional third-party agencies or recruiters."
We need to include only substantive content; the last line about search firms is maybe meta but still part of qualifications? It's more about hiring process; but we can include as part of Qualifications? Might be considered metadata; but it's not boilerplate. However it's about recruitment process; maybe we can keep it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short maybe.
- Skills: Not explicitly listed separate; maybe we can combine some skills under Requirements or Qualifications. There's no separate Skills section. So we omit Skills heading.
- Benefits: The "Our Benefits:" list includes many items: "Medical, Dental & Vision Coverage (with no premiums)", "Company contribution to 401(k) plans", "Annual bonus eligibility", "Flexible work hours", "Unlimited paid time off for a healthy work-life balance", "Paid holidays to celebrate and recharge", "Wellness and cell phone credits to support personal well-being", "Life and AD&D insurance for peace of mind", "Employee Resource Groups (ERGs) for community and support", "Opportunities for professional development to grow and thrive within the company". We'll put those as under Benefits.
- Pay: The posting includes "Compensation: At Copia, we carefully consider a wide range of factors when determining compensation, including your skills, qualifications, location, and experience. This role may also be eligible for benefits, performance bonuses, and other perks. We encourage all interested candidates to apply." This is vague, no specific numbers or range. According to rule: never create Pay section unless posting actually states them (specific). It does not state specific pay; it's generic. So we should NOT include Pay section.
- Schedule: Not mentioned specifically; there is flexible work hours mentioned under benefits, but not a schedule requirement. So we omit Schedule.
- About the company: There's "About Copia" section at end. Could be considered "About the role"? Already we have About the role. The "About Copia" is more company overview; could be included as a separate section maybe "About the company". But headings list only includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we should not add extra heading. However we could incorporate that info into About the role? But the instruction: "Use . We'll list them as separate .
Let's write them exactly as extracted.
Responsibilities bullets:
1. Support and coordinate the generation and load interconnection process for utility-scale solar, energy storage, natural gas, and data center projects, including pre-application feasibility analysis, interconnection application submission, interconnection study & agreement processes, communicating study results, and EPC milestone management.
2. Provide responses and analysis to internal site selection processes to determine feasible transmission locations to apply for interconnection, timed and coordinated to support queue application open windows
3. Request and coordinate application technical packages prepared by transmission consulting engineers
4. Submit interconnection applications to ISOs/Utilities
5. Support timely execution of study agreement and payment of deposits and study fees
6. Track execution of queue milestones such as: Deficiency corrections Scoping meetings Study agreement execution and funding Study results meetings Generator and Load Interconnection Agreement negotiation and execution GIA and Load Milestone tracking and execution
7. Coordinate with utilities, regulatory agencies, and other stakeholders to obtain interconnection approvals.
8. Participate in ISO/PTO Generation Interconnection and other stakeholder forums to stay current on industry changes and trends.
9. Coordinate with Land Acquisition, Engineering, Permitting, EPC, and Operations teams to develop a strong pipeline of solar, energy storage, natural gas, and data center projects
10. Provide interconnection support for project acquisition and financing activities
11. Provide coordination support for co-location of generation projects with data center campuses
12. Support development and maintenance of company tracking tools
13. Ensures all milestones are kept up to date in company tracking tools
14. Support consultant and other service provider activities, including tracking work order status
Note bullet 6 includes a colon and list; we keep as is.
Now Requirements bullets:
- Ability to communicate effectively in verbal and written correspondence.
- Highly driven with problem-solving abilities, integrity, and strong work
or drop it." This is not a job ID; it's a note about search firms. Could be considered minor metadata; but it's still part of the posting. I'd include it as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings if content exists. The "About Copia" is not one of those headings; we could drop it or fold into About the role as a short paragraph. The About the role currently includes description of role; we could add a brief sentence about Copia from that section. But we must preserve all substantive information; we cannot drop it. So we need to include that info somewhere. Since we cannot create a heading not in list, we could put it as a
under About the role (or maybe under Responsibilities?). 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 short
or drop it." So we can fold the About Copia info into a short
under About the role (or maybe as a separate
without heading). That seems acceptable. Thus final HTML:
About the role
[role description paragraph] plus maybe a sentence about Copia from About Copia.
ThenResponsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
or two
under the heading. Probably two
is fine. Now Responsibilities list: need to ensure each bullet is a