Project Engineer – Renewable Energy
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading and include description about role and maybe company? The "About Us" is generic company description; maybe we can include it under "About the role" as context. But we should preserve all substantive information. The "About Us" is substantive but not about role. However we can still include it under "About the role" heading? Might be okay. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. We could also include "About Us" as a heading? Not in list. Safer to stick to those headings. We can put company description under "About the role". Or we could omit it? But we must preserve ALL substantive information. So we need to include company description somewhere. Could be under "About the role". That seems acceptable.
Now "About The Role" section: includes description of GreenPowerMonitor, role, etc. We'll combine.
Then "What to expect?" and "What You Will Do": responsibilities.
We need to extract responsibilities list:
- Analyzing photovoltaic and wind projects to monitor all the variables needed
- Generating single line diagrams of the cabinets including the hardware for the SCADA solution to be deployed, given the project descriptions and Project Manager Indications
- Collaborating with colleagues to reach the schedules for deliveries, and providing assistance with general group activities
- Supporting the commissioning of SCADA systems, including travel for on-site plant visits. You can expect to spend up to 50% of your time at renewable energy sites.
- Configuration of the software to get the best value of the data
- Technical report writing, critical reviewing, and professional presentation to clients
Also: "You will join our On-site Solutions team of Project Engineers and Project Managers. Our commitment is to successfully deliver On-site Solutions (SCADA and PPC) projects, while ensuring adherence to scope, schedule, and budget constraints. This involves a comprehensive approach that not only prioritizes excellence but also emphasizes efficiency and performance to provide the optimum experience and highest quality to our customers. To achieve this, we actively create specific tools and automation processes, enabling us to deliver intelligently and uphold our position as industry leaders."
That's more description, could be part of responsibilities or about role.
Now "What we offer": benefits list.
Benefits:
- Generous paid time off (vacation, sick days, company holidays, personal days)
- Multiple Medical and Dental benefit plans to choose from, Vision benefits
- Spending accounts – FSA, Dependent Care, Commuter Benefits, company-seeded HSA
- Employer-paid, therapist-led, virtual care services through Talkspace
- 401(k) with company match
- Company provided life insurance, short-term, and long-term disability benefits
- Education reimbursement program
- Flexible work schedule with hybrid opportunities
- Charitable Matched Giving and Volunteer Rewards through our Impact Program
- Volunteer time off (VTO) paid by the company
- Career advancement opportunities
- Note: Benefits vary based on position, tenure, location, and employee election (we should not include as filler? It's substantive but maybe we can include as a sentence.)
Now Pay: For certain states: starting pay range $90,000-$110,000. That's specific. So we can include Pay section with that range.
Schedule: Not explicitly given besides flexible work schedule with hybrid opportunities (that's more benefit). No explicit schedule like full-time, etc. Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule like "Full-time", "40 hours/week". So we omit Schedule.
Qualifications: The posting has "About You" with required and preferred. We can split into Requirements (required) and Qualifications (maybe preferred) or Skills. The instruction lists Requirements, Qualifications, Skills as possible headings. We need to decide what to put where.
We have required:
- Bachelor´s or Master´s degree in Engineering
- At least 3 years of hands-on experience providing engineering and technical advice to renewable energy projects within solar PV, wind and/or BESS
- Knowledge about industrial communication protocols like MODBUS or other relevant
- Ability to create single line diagrams (AutoCAD)
- Excellent planning and organizational skills to navigate seamlessly through the demands of handling multiple projects simultaneously
- Strong communication skills with the ability to craft clear and accurate reports and share technical concepts in concise manner
- Fluency in written and spoken English and Spanish
- Strong written and verbal English communication skills (some duplication)
Also: "We conduct pre-employment drug and background screening" - could be a requirement but not a skill; maybe include under Requirements.
Preferred:
- Experience working with SCADA systems
- Knowledge of Linux and networking
- As a person, you demonstrate proactivity and infuse enthusiasm and self-motivation to learn and embrace challenges.
- You exhibit outstanding interpersonal skills, effectively managing both internal and external stakeholders.
- Overall, you have a collaborative spirit and team-oriented approach.
We could put preferred under Qualifications or Skills. Since Skills heading is for skills, we could put technical skills under Skills, and preferred personal attributes under Qualifications. But we need to avoid thin sections. Let's think.
We could have:
- Requirements: list of required qualifications (degree, experience, knowledge, ability, skills, language, background check)
- Qualifications: list of preferred qualifications (SCADA experience, Linux/networking, proactivity, interpersonal, collaborative)
- Skills: maybe we could combine some skill items like "Ability to create single line diagrams (AutoCAD)", "Knowledge of industrial communication protocols like MODBUS", "Strong communication skills", "Fluency in English and Spanish", "Excellent planning and organizational skills". Those are skills. But we already put them in Requirements. Might be okay to have Requirements include those. Then Qualifications for preferred. Skills maybe not needed.
But we need to follow instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But we have headings list; we can choose to include only those with real content. Could include Requirements (required) and Qualifications (preferred). That's two sections. Skills maybe not needed if we already covered.
Benefits we have.
Pay we have.
About the role we have.
Responsibilities we have.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We must not include Schedule.
Now we need to format as HTML fragment: use for each heading, then content:
for each heading, then content:
for prose,
- for lists.
We must not repeat job title as heading. The job title is "Project Engineer for On-Site Solutions". Not used.
We must not include Job ID etc.
We must remove boilerplate: EEO, equal-opportunity, scam-warning, navigation, cookie, legal, application instructions. The posting includes EEO statement at end: "DNV is a proud equal-opportunity employer..." etc. Must remove.
Also remove "We conduct pre-employment drug and background screening" - that's not boilerplate; it's a requirement. Keep.
Now let's craft content.
About the role: combine About Us and About The Role paragraphs.
We need to preserve all substantive information. Let's extract:
About Us paragraph: "We are the independent expert in assurance and risk management. Driven by our purpose, to safeguard life, property, and the environment, we empower our customers and their stakeholders with facts and reliable insights so that critical decisions can be made with confidence. As a trusted voice for many of the world’s most successful organizations, we use our knowledge to advance safety and performance, set industry benchmarks, and inspire and invent solutions to tackle global transformations."
About The Role paragraph: "GreenPowerMonitor, a DNV company, is at the heart of the global energy transformation. We use data-driven digital solutions to optimize the performance of renewable energy installations around the world. Our work contributes to a more diverse, more sustainable global energy mix. Are you ready to be part of a growing team and drive technical project execution of our On-Site Solutions for renewable energy? Would you like to work in a collaborative, global, and dynamic environment while supporting companies in accelerating their energy transition? If so, seize this opportunity to make a real impact. Apply today and join us as Project Engineer for On-Site Solutions at GreenPowerMonitor. Together, we can create a greener tomorrow!"
Also "What to expect? As a Project Engineer , you will work in a project matrix organization to implement SCADA and PPC in renewable energy sites." That could be part of About the role or Responsibilities. We'll put under Responsibilities maybe.
But we already have Responsibilities section; we can include that sentence there.
Now Responsibilities: list items as above plus maybe the "What to expect" sentence as intro paragraph.
Let's draft:
About the role
We are the independent expert in assurance and risk management. Driven by our purpose, to safeguard life, property, and the environment, we empower our customers and their stakeholders with facts and reliable insights so that critical decisions can be made with confidence. As a trusted voice for many of the world’s most successful organizations, we use our knowledge to advance safety and performance, set industry benchmarks, and inspire and invent solutions to tackle global transformations.
GreenPowerMonitor, a DNV company, is at the heart of the global energy transformation. We use data-driven digital solutions to optimize the performance of renewable energy installations around the world. Our work contributes to a more diverse, more sustainable global energy mix. Are you ready to be part of a growing team and drive technical project execution of our On-Site Solutions for renewable energy? Would you like to work in a collaborative, global, and dynamic environment while supporting companies in accelerating their energy transition? If so, seize this opportunity to make a real impact. Join us as Project Engineer for On-Site Solutions at GreenPowerMonitor. Together, we can create a greener tomorrow!
Now Responsibilities:Responsibilities
As a Project Engineer, you will work in a project matrix organization to implement SCADA and PPC in renewable energy sites.
- Analyzing photovoltaic and wind projects to monitor all the variables needed
- Generating single line diagrams of the cabinets including the hardware for the SCADA solution to be deployed, given the project descriptions and Project Manager Indications
- Collaborating with colleagues to reach the schedules for deliveries, and providing assistance with general group activities
- Supporting the commissioning of SCADA systems, including travel for on-site plant visits. You can expect to spend up to 50% of your time at renewable energy sites.
- Configuration of the software to get the best value of the data
- Technical report writing, critical reviewing, and professional presentation to clients
You will join our On-site Solutions team of Project Engineers and Project Managers. Our commitment is to successfully deliver On-site Solutions (SCADA and PPC) projects, while ensuring adherence to scope, schedule, and budget constraints. This involves a comprehensive approach that not only prioritizes excellence but also emphasizes efficiency and performance to provide the optimum experience and highest quality to our customers. To achieve this, we actively create specific tools and automation processes, enabling us to deliver intelligently and uphold our position as industry leaders.
Now