Senior Electrical Power System Studies Engineer
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
- Company description: "About Fervo Energy" - this is about the company, not the role specifically. Could be "About the company" or similar.
- Position Description: "As a Senior Electrical Power Engineer..." - this is about the role
- Responsibilities: broken into subsections: Electrical System Studies, Grid Interconnection, Plant-Level Studies, Team Development and Culture, Standards, Design, and Other Duties
- Qualifications: Required and Preferred
- Location: mentions offices and hybrid work
- Benefits & Perks: detailed list
- Our Workplace: hybrid schedule details
- Equal Opportunity Employer: boilerplate - should remove
I need to structure this into appropriate sections. The rules say use
for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But I should only include sections that have real content.
Let me map:
- "About the role" could cover the Position Description paragraph.
- "Responsibilities" - there are detailed responsibilities with subsections. I should include all the bullet points.
- "Qualifications" - there are Required and Preferred qualifications. Could combine into one section with sub-lists.
- "Benefits" - there is a Benefits & Perks section with detailed list.
- "Schedule" - there is "Our Workplace" describing hybrid schedule (3 days in office). That's specific.
- "Location" - there is a Location section. Could be part of Schedule or separate. The rules mention "Schedule" as a heading, but not "Location". However, location is mentioned. I could include a "Location" heading or fold into Schedule. The rules say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't list Location, but it's a common section. I think I should include a "Location" section because it's specific content. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has a Location section. I'll include it.
- "Pay" - not mentioned, so no Pay section.
- "Skills" - not explicitly a separate section; qualifications cover skills. Could include a "Skills" section but qualifications already cover. The rules mention "Skills" as an example heading. But I should prefer fewer substantive sections. I'll keep Qualifications.
- "Requirements" vs "Qualifications": The posting has "Qualifications" with Required and Preferred. The rules mention both "Requirements" and "Qualifications" as example headings. I'll use "Qualifications" as heading.
- "About the role" - the Position Description is about the role. I'll include.
- "Company" - there's "About Fervo Energy". Could be "About the company". The rules don't list that, but it's substantive. I'll include as "About the company" or "About Fervo Energy". The rules say use for section headings (e.g. About the role...). It doesn't forbid other headings. I'll include.
Now, I need to remove boilerplate: Equal Opportunity Employer, duplicated lines, application instructions (none), cookie/navigation/legal/EEO/scam-warning. The EEO paragraph at the end should be removed.
Also, the "Benefits & Perks" section includes a note "Benefits and programs are subject to eligibility requirements and may change." That's fine to keep as prose.
The "Our Workplace" section describes hybrid schedule. That's specific.
Now, I need to output HTML fragment with headings and - for lists,
for prose.
Let me structure:
1.
About Fervo Energy
(or "About the company") - with prose paragraph(s).
2. About the role
- with prose paragraph.
3. Responsibilities
- with subsections? The rules say use - for any list of duties. The responsibilities are grouped into categories. I could either make a flat list of all bullet points, or keep the subcategories as subheadings? The rules say use
for section headings. It doesn't mention subheadings. But the responsibilities have clear subsections: Electrical System Studies, Grid Interconnection, Plant-Level Studies, Team Development and Culture, Standards, Design, and Other Duties. I could make each a ? But the rules only specify for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other heading levels, but to keep it simple, I could make each responsibility category a separate ? That would create many sections. The rules say "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with a list that includes the subcategories as list items with bold labels? Or use nested lists? The rules say "use - for any list of duties/requirements/benefits". It doesn't specify nesting. I think I can use nested
for sub-items. But the subcategories are not just bullet points; they have multiple bullet points each. I could structure as:
Responsibilities
- Electrical System Studies
- Perform transient overvoltage (TOV) studies using PSCAD...
...
- Grid Interconnection
...
...
That would preserve structure. However, the rules say "use - for any list of duties/requirements/benefits". It doesn't forbid nested lists. I think that's acceptable.
Alternatively, I could make each subcategory a separate
but that would be many sections. The rules say prefer a few substantive sections. So I'll keep Responsibilities as one section with nested lists.
Similarly for Qualifications: Required and Preferred. I'll make a Qualifications section with two sublists.
Benefits: list of benefits.
Schedule: prose about hybrid schedule.
Location: prose about offices and hybrid flexibility.
Now, I need to ensure I don't repeat job title. The job title is "Senior Electrical Power Engineer" - not in the provided text? Actually the posting starts with "About Fervo Energy" then "Position Description As a Senior Electrical Power Engineer...". The job title is mentioned in the position description. The rule: "Do NOT repeat the job title as a heading (the page already shows it)". So I should not have a heading "Senior Electrical Power Engineer". That's fine.
Also, "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." There's no Job ID in the text.
Now, let's write the HTML.
I'll start with About Fervo Energy:
About Fervo Energy
Fervo Energy (NASDAQ: FRVO) is a modern power company developing next-generation geothermal resources to meet the growing demand for affordable, reliable, 24/7 carbon-free energy. Our mission is to transform geothermal into America's most dependable and affordable source of clean, around-the-clock power. By combining innovations in horizontal drilling, fiber-optic sensing, and advanced reservoir engineering, Fervo has developed a repeatable approach to building utility-scale enhanced geothermal systems. Our flagship Cape Station development in Utah is planned to deliver 500 MW of firm, carbon-free power, and we are advancing a development pipeline of more than 50 GW. Join us and work alongside world-class engineers, geoscientists, operators, project builders, and business leaders working to make geothermal a cornerstone of a more reliable, affordable, and sustainable energy future.
Then About the role:
About the role
As a Senior Electrical Power Engineer, you will be a technical authority on electrical system studies supporting Fervo's geothermal power plant development and associated transmission interconnections. You will perform and lead a wide range of power system analyses — from grid interconnection studies through to plant-level studies supporting capital, maintenance, and reliability projects — using industry-standard tools including PSCAD, PSLF, and ETAP. You will mentor junior engineers and contribute beyond core system studies to procedure and standards development, design tasks, and other cross-functional engineering work as Fervo scales its fleet. This role will report to the Power Engineering Manager.
Responsibilities:
Responsibilities
- Electrical System Studies
- Perform transient overvoltage (TOV) studies using PSCAD to evaluate switching transients, lightning, and equipment overvoltage risks for geothermal generation facilities and interconnection projects.
- Conduct dynamic stability studies in PSLF or PSSE and ETAP, including generator modeling, voltage/frequency response analysis, and compliance with interconnection stability requirements.
- Execute power flow studies in PSLF or PSSE and ETAP to assess steady-state operating conditions, equipment loading, and voltage profiles across Fervo plant and transmission configurations.
- Perform short circuit analysis in ETAP to size equipment, verify protective device ratings, and support NEC/NESC and applicable code compliance.
- Develop protection system studies and relay coordination in ETAP, including time-overcurrent, differential, and distance protection schemes for generation, transmission, and distribution systems.
- Conduct arc flash incident energy analysis in ETAP in accordance with IEEE 1584; prepare arc flash hazard labels and arc flash mitigation recommendations to support site safety programs.
- Grid Interconnection
- Lead and support interconnection study processes with regional transmission organizations (RTOs), independent system operators (ISOs), and transmission owners, including scoping meetings, study review, and dispute resolution.
- Prepare and review power flow and stability models for submission to transmission providers; coordinate generator model validation per NERC MOD standards.
- Evaluate interconnection study results and translate technical findings into actionable design and equipment requirements for project teams.
- Track applicable interconnection standards and tariff requirements (FERC, NERC, regional) and ensure study methodologies remain compliant.
- Plant-Level Studies
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: - Company description: "About Fervo Energy" - this is about the company, not the role specifically. Could be "About the company" or similar. - Position Description: "As a Senior Electrical Power Engineer..." - this is about the role - Responsibilities: broken into subsections: Electrical System Studies, Grid Interconnection, Plant-Level Studies, Team Development and Culture, Standards, Design, and Other Duties - Qualifications: Required and Preferred - Location: mentions offices and hybrid work - Benefits & Perks: detailed list - Our Workplace: hybrid schedule details - Equal Opportunity Employer: boilerplate - should remove I need to structure this into appropriate sections. The rules say use
for section headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But I should only include sections that have real content.
Let me map:
- "About the role" could cover the Position Description paragraph.
- "Responsibilities" - there are detailed responsibilities with subsections. I should include all the bullet points.
- "Qualifications" - there are Required and Preferred qualifications. Could combine into one section with sub-lists.
- "Benefits" - there is a Benefits & Perks section with detailed list.
- "Schedule" - there is "Our Workplace" describing hybrid schedule (3 days in office). That's specific.
- "Location" - there is a Location section. Could be part of Schedule or separate. The rules mention "Schedule" as a heading, but not "Location". However, location is mentioned. I could include a "Location" heading or fold into Schedule. The rules say use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't list Location, but it's a common section. I think I should include a "Location" section because it's specific content. But the rules say "include a section ONLY when the posting has real, specific content for it". The posting has a Location section. I'll include it.
- "Pay" - not mentioned, so no Pay section.
- "Skills" - not explicitly a separate section; qualifications cover skills. Could include a "Skills" section but qualifications already cover. The rules mention "Skills" as an example heading. But I should prefer fewer substantive sections. I'll keep Qualifications.
- "Requirements" vs "Qualifications": The posting has "Qualifications" with Required and Preferred. The rules mention both "Requirements" and "Qualifications" as example headings. I'll use "Qualifications" as heading.
- "About the role" - the Position Description is about the role. I'll include.
- "Company" - there's "About Fervo Energy". Could be "About the company". The rules don't list that, but it's substantive. I'll include as "About the company" or "About Fervo Energy". The rules say use for section headings (e.g. About the role...). It doesn't forbid other headings. I'll include.
Now, I need to remove boilerplate: Equal Opportunity Employer, duplicated lines, application instructions (none), cookie/navigation/legal/EEO/scam-warning. The EEO paragraph at the end should be removed.
Also, the "Benefits & Perks" section includes a note "Benefits and programs are subject to eligibility requirements and may change." That's fine to keep as prose.
The "Our Workplace" section describes hybrid schedule. That's specific.
Now, I need to output HTML fragment with headings and - for lists,
for prose.
Let me structure:
1.
About Fervo Energy
(or "About the company") - with prose paragraph(s).
2. About the role
- with prose paragraph.
3. Responsibilities
- with subsections? The rules say use - for any list of duties. The responsibilities are grouped into categories. I could either make a flat list of all bullet points, or keep the subcategories as subheadings? The rules say use
for section headings. It doesn't mention subheadings. But the responsibilities have clear subsections: Electrical System Studies, Grid Interconnection, Plant-Level Studies, Team Development and Culture, Standards, Design, and Other Duties. I could make each a ? But the rules only specify for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other heading levels, but to keep it simple, I could make each responsibility category a separate ? That would create many sections. The rules say "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with a list that includes the subcategories as list items with bold labels? Or use nested lists? The rules say "use - for any list of duties/requirements/benefits". It doesn't specify nesting. I think I can use nested
for sub-items. But the subcategories are not just bullet points; they have multiple bullet points each. I could structure as:
Responsibilities
- Electrical System Studies
- Perform transient overvoltage (TOV) studies using PSCAD...
...
- Grid Interconnection
...
...
That would preserve structure. However, the rules say "use - for any list of duties/requirements/benefits". It doesn't forbid nested lists. I think that's acceptable.
Alternatively, I could make each subcategory a separate
but that would be many sections. The rules say prefer a few substantive sections. So I'll keep Responsibilities as one section with nested lists.
Similarly for Qualifications: Required and Preferred. I'll make a Qualifications section with two sublists.
Benefits: list of benefits.
Schedule: prose about hybrid schedule.
Location: prose about offices and hybrid flexibility.
Now, I need to ensure I don't repeat job title. The job title is "Senior Electrical Power Engineer" - not in the provided text? Actually the posting starts with "About Fervo Energy" then "Position Description As a Senior Electrical Power Engineer...". The job title is mentioned in the position description. The rule: "Do NOT repeat the job title as a heading (the page already shows it)". So I should not have a heading "Senior Electrical Power Engineer". That's fine.
Also, "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." There's no Job ID in the text.
Now, let's write the HTML.
I'll start with About Fervo Energy:
About Fervo Energy
Fervo Energy (NASDAQ: FRVO) is a modern power company developing next-generation geothermal resources to meet the growing demand for affordable, reliable, 24/7 carbon-free energy. Our mission is to transform geothermal into America's most dependable and affordable source of clean, around-the-clock power. By combining innovations in horizontal drilling, fiber-optic sensing, and advanced reservoir engineering, Fervo has developed a repeatable approach to building utility-scale enhanced geothermal systems. Our flagship Cape Station development in Utah is planned to deliver 500 MW of firm, carbon-free power, and we are advancing a development pipeline of more than 50 GW. Join us and work alongside world-class engineers, geoscientists, operators, project builders, and business leaders working to make geothermal a cornerstone of a more reliable, affordable, and sustainable energy future.
Then About the role:
About the role
As a Senior Electrical Power Engineer, you will be a technical authority on electrical system studies supporting Fervo's geothermal power plant development and associated transmission interconnections. You will perform and lead a wide range of power system analyses — from grid interconnection studies through to plant-level studies supporting capital, maintenance, and reliability projects — using industry-standard tools including PSCAD, PSLF, and ETAP. You will mentor junior engineers and contribute beyond core system studies to procedure and standards development, design tasks, and other cross-functional engineering work as Fervo scales its fleet. This role will report to the Power Engineering Manager.
Responsibilities:
Responsibilities
- Electrical System Studies
- Perform transient overvoltage (TOV) studies using PSCAD to evaluate switching transients, lightning, and equipment overvoltage risks for geothermal generation facilities and interconnection projects.
- Conduct dynamic stability studies in PSLF or PSSE and ETAP, including generator modeling, voltage/frequency response analysis, and compliance with interconnection stability requirements.
- Execute power flow studies in PSLF or PSSE and ETAP to assess steady-state operating conditions, equipment loading, and voltage profiles across Fervo plant and transmission configurations.
- Perform short circuit analysis in ETAP to size equipment, verify protective device ratings, and support NEC/NESC and applicable code compliance.
- Develop protection system studies and relay coordination in ETAP, including time-overcurrent, differential, and distance protection schemes for generation, transmission, and distribution systems.
- Conduct arc flash incident energy analysis in ETAP in accordance with IEEE 1584; prepare arc flash hazard labels and arc flash mitigation recommendations to support site safety programs.
- Grid Interconnection
- Lead and support interconnection study processes with regional transmission organizations (RTOs), independent system operators (ISOs), and transmission owners, including scoping meetings, study review, and dispute resolution.
- Prepare and review power flow and stability models for submission to transmission providers; coordinate generator model validation per NERC MOD standards.
- Evaluate interconnection study results and translate technical findings into actionable design and equipment requirements for project teams.
- Track applicable interconnection standards and tariff requirements (FERC, NERC, regional) and ensure study methodologies remain compliant.
- Plant-Level Studies
for section headings (e.g. About the role...). It doesn't forbid other headings. I'll include.
Now, I need to remove boilerplate: Equal Opportunity Employer, duplicated lines, application instructions (none), cookie/navigation/legal/EEO/scam-warning. The EEO paragraph at the end should be removed.
Also, the "Benefits & Perks" section includes a note "Benefits and programs are subject to eligibility requirements and may change." That's fine to keep as prose.
The "Our Workplace" section describes hybrid schedule. That's specific.
Now, I need to output HTML fragment with headings and - for lists,
for prose.
Let me structure:
1.
About Fervo Energy
(or "About the company") - with prose paragraph(s).
2. About the role
- with prose paragraph.
3. Responsibilities
- with subsections? The rules say use - for any list of duties. The responsibilities are grouped into categories. I could either make a flat list of all bullet points, or keep the subcategories as subheadings? The rules say use
for section headings. It doesn't mention subheadings. But the responsibilities have clear subsections: Electrical System Studies, Grid Interconnection, Plant-Level Studies, Team Development and Culture, Standards, Design, and Other Duties. I could make each a ? But the rules only specify for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other heading levels, but to keep it simple, I could make each responsibility category a separate ? That would create many sections. The rules say "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with a list that includes the subcategories as list items with bold labels? Or use nested lists? The rules say "use - for any list of duties/requirements/benefits". It doesn't specify nesting. I think I can use nested
for sub-items. But the subcategories are not just bullet points; they have multiple bullet points each. I could structure as:
Responsibilities
- Electrical System Studies
- Perform transient overvoltage (TOV) studies using PSCAD...
...
- Grid Interconnection
...
...
That would preserve structure. However, the rules say "use - for any list of duties/requirements/benefits". It doesn't forbid nested lists. I think that's acceptable.
Alternatively, I could make each subcategory a separate
but that would be many sections. The rules say prefer a few substantive sections. So I'll keep Responsibilities as one section with nested lists.
Similarly for Qualifications: Required and Preferred. I'll make a Qualifications section with two sublists.
Benefits: list of benefits.
Schedule: prose about hybrid schedule.
Location: prose about offices and hybrid flexibility.
Now, I need to ensure I don't repeat job title. The job title is "Senior Electrical Power Engineer" - not in the provided text? Actually the posting starts with "About Fervo Energy" then "Position Description As a Senior Electrical Power Engineer...". The job title is mentioned in the position description. The rule: "Do NOT repeat the job title as a heading (the page already shows it)". So I should not have a heading "Senior Electrical Power Engineer". That's fine.
Also, "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." There's no Job ID in the text.
Now, let's write the HTML.
I'll start with About Fervo Energy:
About Fervo Energy
Fervo Energy (NASDAQ: FRVO) is a modern power company developing next-generation geothermal resources to meet the growing demand for affordable, reliable, 24/7 carbon-free energy. Our mission is to transform geothermal into America's most dependable and affordable source of clean, around-the-clock power. By combining innovations in horizontal drilling, fiber-optic sensing, and advanced reservoir engineering, Fervo has developed a repeatable approach to building utility-scale enhanced geothermal systems. Our flagship Cape Station development in Utah is planned to deliver 500 MW of firm, carbon-free power, and we are advancing a development pipeline of more than 50 GW. Join us and work alongside world-class engineers, geoscientists, operators, project builders, and business leaders working to make geothermal a cornerstone of a more reliable, affordable, and sustainable energy future.
Then About the role:
About the role
As a Senior Electrical Power Engineer, you will be a technical authority on electrical system studies supporting Fervo's geothermal power plant development and associated transmission interconnections. You will perform and lead a wide range of power system analyses — from grid interconnection studies through to plant-level studies supporting capital, maintenance, and reliability projects — using industry-standard tools including PSCAD, PSLF, and ETAP. You will mentor junior engineers and contribute beyond core system studies to procedure and standards development, design tasks, and other cross-functional engineering work as Fervo scales its fleet. This role will report to the Power Engineering Manager.
Responsibilities:
Responsibilities
- Electrical System Studies
- Perform transient overvoltage (TOV) studies using PSCAD to evaluate switching transients, lightning, and equipment overvoltage risks for geothermal generation facilities and interconnection projects.
- Conduct dynamic stability studies in PSLF or PSSE and ETAP, including generator modeling, voltage/frequency response analysis, and compliance with interconnection stability requirements.
- Execute power flow studies in PSLF or PSSE and ETAP to assess steady-state operating conditions, equipment loading, and voltage profiles across Fervo plant and transmission configurations.
- Perform short circuit analysis in ETAP to size equipment, verify protective device ratings, and support NEC/NESC and applicable code compliance.
- Develop protection system studies and relay coordination in ETAP, including time-overcurrent, differential, and distance protection schemes for generation, transmission, and distribution systems.
- Conduct arc flash incident energy analysis in ETAP in accordance with IEEE 1584; prepare arc flash hazard labels and arc flash mitigation recommendations to support site safety programs.
- Grid Interconnection
- Lead and support interconnection study processes with regional transmission organizations (RTOs), independent system operators (ISOs), and transmission owners, including scoping meetings, study review, and dispute resolution.
- Prepare and review power flow and stability models for submission to transmission providers; coordinate generator model validation per NERC MOD standards.
- Evaluate interconnection study results and translate technical findings into actionable design and equipment requirements for project teams.
- Track applicable interconnection standards and tariff requirements (FERC, NERC, regional) and ensure study methodologies remain compliant.
- Plant-Level Studies
- for lists,
for prose. Let me structure: 1.
About Fervo Energy
(or "About the company") - with prose paragraph(s). 2.About the role
- with prose paragraph. 3.Responsibilities
- with subsections? The rules say use- for any list of duties. The responsibilities are grouped into categories. I could either make a flat list of all bullet points, or keep the subcategories as subheadings? The rules say use
for section headings. It doesn't mention subheadings. But the responsibilities have clear subsections: Electrical System Studies, Grid Interconnection, Plant-Level Studies, Team Development and Culture, Standards, Design, and Other Duties. I could make each a
? But the rules only specify
for section headings. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other heading levels, but to keep it simple, I could make each responsibility category a separate
? That would create many sections. The rules say "Prefer a few substantive sections over many thin ones." So maybe keep Responsibilities as one section with a list that includes the subcategories as list items with bold labels? Or use nested lists? The rules say "use
- for any list of duties/requirements/benefits". It doesn't specify nesting. I think I can use nested
- for sub-items. But the subcategories are not just bullet points; they have multiple bullet points each. I could structure as:
- Electrical System Studies
- Perform transient overvoltage (TOV) studies using PSCAD... ...
- Grid Interconnection
-
...
...
- for any list of duties/requirements/benefits". It doesn't forbid nested lists. I think that's acceptable.
Alternatively, I could make each subcategory a separate
but that would be many sections. The rules say prefer a few substantive sections. So I'll keep Responsibilities as one section with nested lists. Similarly for Qualifications: Required and Preferred. I'll make a Qualifications section with two sublists. Benefits: list of benefits. Schedule: prose about hybrid schedule. Location: prose about offices and hybrid flexibility. Now, I need to ensure I don't repeat job title. The job title is "Senior Electrical Power Engineer" - not in the provided text? Actually the posting starts with "About Fervo Energy" then "Position Description As a Senior Electrical Power Engineer...". The job title is mentioned in the position description. The rule: "Do NOT repeat the job title as a heading (the page already shows it)". So I should not have a heading "Senior Electrical Power Engineer". That's fine. Also, "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." There's no Job ID in the text. Now, let's write the HTML. I'll start with About Fervo Energy:
About Fervo Energy
Fervo Energy (NASDAQ: FRVO) is a modern power company developing next-generation geothermal resources to meet the growing demand for affordable, reliable, 24/7 carbon-free energy. Our mission is to transform geothermal into America's most dependable and affordable source of clean, around-the-clock power. By combining innovations in horizontal drilling, fiber-optic sensing, and advanced reservoir engineering, Fervo has developed a repeatable approach to building utility-scale enhanced geothermal systems. Our flagship Cape Station development in Utah is planned to deliver 500 MW of firm, carbon-free power, and we are advancing a development pipeline of more than 50 GW. Join us and work alongside world-class engineers, geoscientists, operators, project builders, and business leaders working to make geothermal a cornerstone of a more reliable, affordable, and sustainable energy future.
Then About the role:About the role
As a Senior Electrical Power Engineer, you will be a technical authority on electrical system studies supporting Fervo's geothermal power plant development and associated transmission interconnections. You will perform and lead a wide range of power system analyses — from grid interconnection studies through to plant-level studies supporting capital, maintenance, and reliability projects — using industry-standard tools including PSCAD, PSLF, and ETAP. You will mentor junior engineers and contribute beyond core system studies to procedure and standards development, design tasks, and other cross-functional engineering work as Fervo scales its fleet. This role will report to the Power Engineering Manager.
Responsibilities:Responsibilities
- Electrical System Studies
- Perform transient overvoltage (TOV) studies using PSCAD to evaluate switching transients, lightning, and equipment overvoltage risks for geothermal generation facilities and interconnection projects.
- Conduct dynamic stability studies in PSLF or PSSE and ETAP, including generator modeling, voltage/frequency response analysis, and compliance with interconnection stability requirements.
- Execute power flow studies in PSLF or PSSE and ETAP to assess steady-state operating conditions, equipment loading, and voltage profiles across Fervo plant and transmission configurations.
- Perform short circuit analysis in ETAP to size equipment, verify protective device ratings, and support NEC/NESC and applicable code compliance.
- Develop protection system studies and relay coordination in ETAP, including time-overcurrent, differential, and distance protection schemes for generation, transmission, and distribution systems.
- Conduct arc flash incident energy analysis in ETAP in accordance with IEEE 1584; prepare arc flash hazard labels and arc flash mitigation recommendations to support site safety programs.
- Grid Interconnection
- Lead and support interconnection study processes with regional transmission organizations (RTOs), independent system operators (ISOs), and transmission owners, including scoping meetings, study review, and dispute resolution.
- Prepare and review power flow and stability models for submission to transmission providers; coordinate generator model validation per NERC MOD standards.
- Evaluate interconnection study results and translate technical findings into actionable design and equipment requirements for project teams.
- Track applicable interconnection standards and tariff requirements (FERC, NERC, regional) and ensure study methodologies remain compliant.
- Plant-Level Studies
- Electrical System Studies
Responsibilities
- Electrical System Studies
- for any list of duties/requirements/benefits". It doesn't specify nesting. I think I can use nested
- for any list of duties. The responsibilities are grouped into categories. I could either make a flat list of all bullet points, or keep the subcategories as subheadings? The rules say use