Technology Development Manager
Duke Energy Corporation · Holly, NC · 4 days ago
Full-time
We need to output HTML fragment with sections: About the role? Actually job summary is like About the role. Responsibilities And Duties -> Responsibilities. Basic/Required Qualifications -> Requirements or Qualifications. Desired Qualifications -> Skills maybe. Working Conditions maybe not a standard heading; but we can include if content. Travel Requirements maybe part of Schedule? Actually schedule not given. Pay not given. Benefits not given. So we should include only sections with real content: About the role (Job Summary), Responsibilities, Requirements (Basic/Required Qualifications), Skills (Desired Qualifications), maybe Working Conditions (but not a standard heading list; but we could include as a section like "Working Conditions" if we want but not in list of allowed headings? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It says use
items for each bullet point.
Let's extract responsibilities sections:
Technology Evaluation & Demonstration
- Monitor emerging technology trends, market developments, and industry activity to identify opportunities and inform ETO strategy.
- Provide analytical leadership for technology assessment, evaluation, road mapping, and emerging technology valuations.
- Manage emerging technology focused venture capital and external innovation relationships.
- Conduct engineering, research, and related studies of emerging technologies with areas of expertise and apply technical knowledge to support technology development decisions.
- Key technology focus areas include but are not limited to generation, energy storage, transmission and distribution, transformers, energy efficiency and demand response, electric vehicles, robotics, and artificial intelligence.
- Facilitate the development and execution of pilot project plans, ensuring alignment among project objectives, technical scope, stakeholder expectations, resources, timelines, and deliverables.
- Develop test plans, analyze test data, and communicate test results to key stakeholders.
- Apply necessary project management and control policies and standards for emerging technology initiatives, including planning, scheduling, resource coordination, risk management, and performance monitoring.
- Lead the full project lifecycle from opportunity identification and assessment through development, demonstration, technology transfer, and closeout.
Strategic Partnerships, Industry Engagement & Communications
- Develop and implement partnership strategies that support Emerging Technology organizational objectives.
- Build and maintain effective working relationships with internal stakeholders, industry partners, startups, universities, venture capital firms, and other external organizations.
- Lead industry benchmarking efforts and integrate external insights and lessons learned into ETO strategy and innovation practices.
- Lead ETO support for regulatory filings and other external or internal communications requiring technology development information.
- Represent the company at customer forums, industry organizations, trade associations, and other external engagements while exemplifying what it means to be a Duke Energy employee.
- Lead education sessions, including lunch and learns, seminars, and tours.
- Demonstrate effective oral and written communication skills and maintain accurate project records, documentation, and files.
Innovation & Organizational Enablement
- Support the development and continuous improvement of innovation, project lifecycle, technology transfer, and portfolio management processes.
- Assess and prioritize R&D activities with other Lines of Business (LOB) and ensure they are aligned with their technology roadmaps and Duke Energy’s strategic objectives.
- Support required legislative and/or regulatory programs, documentation and filings to ensure successful implementation of pilots/programs (e.g. NC Non-DSM/EE Rapid Prototyping)
- Contribute technical and analytical expertise to the identification, analysis, and resolution of problems in areas of specialization.
Now Basic/Required Qualifications:
- Bachelor's Degree in Information Systems, Engineering, or Computer Science
- Minimum of 7 years of related work experience.
- In lieu of degree, a High School Diploma/GED and a minimum of 11 years of related work experience
Desired Qualifications:
- Understanding of fundamental engineering theories, principles, and practices, with the ability to interpret technical information and apply it to business and technology development decisions.
- Demonstrated experience conducting technology assessments, gathering and analyzing industry data, developing business cases, evaluation alternatives, and making data-driven recommendations.
- Strong understanding of technology trends and drivers shaping the future of the electric utility industry and their potential business, operational, and customer implications.
- Demonstrate ability to work independently and effectively manage project and initiatives with ambiguous or evolving objectives.
- Demonstrated ability to lead and facilitate cross-functional teams and collaborate effectively with internal and external stakeholders at all organizational levels.
- Demonstrated project management and project controls experience, including planning, scheduling, budgeting, resource coordination, risk management, and performance monitoring.
- Prior experience in utility planning, operations, or strategy, with an understanding of generation, transmission and distribution, and customer-facing business segments.
- Strong understanding of the utility regulatory construct and demonstrated ability to assess regulatory and policy considerations affecting emerging technologies.
- Excellent written, oral, and presentation skills, with the ability to communicate complex technical and strategic concepts to diverse audiences.
- Proficiency with Microsoft 365 and related digital tools, including Excel, PowerPoint, Planner, SharePoint, Power BI, and Copilot.
Working Conditions:
- Normal office environment.
- Some field working conditions, including substation and distribution environments.
- Travel required 5-15%
- Hybrid Mobility Classification – Work will be performed from both remote and onsite locations after the onboarding period. However, hybrid employees must live within a reasonable commute to their designated Duke Energy facility, not greater than 50 miles one way. Employees are expected to report to their assigned Duke Energy facility as required and directed by their manager, on average 3 full workdays per regular workweek.
- Specific Requirement Valid Driver's License
- A Masters degree in Information Systems, Engineering, or Computer Science + 5 years related experience will be considered in lieu of the Bachelor’s in Information Systems, Engineering, or Computer Science + years related experience.
- A PhD in Information Systems, Engineering, or Computer Science + 3 years related experience will be considered in lieu of the Bachelor’s in Information Systems, Engineering, or Computer Science + 7 years related experience.
- Travel Requirements 5-15%
- Relocation Assistance Provided (as applicable)
- No Represented/Union Position
- No Visa Sponsored Position. This is not a Visa Sponsored Position. This role requires the ability to work lawfully in the U.S. without employment-based immigration sponsorship, now or in the future.
- Please note that in order to be considered for this position, you must possess all of the basic/required qualifications.
We need to fold minor metadata like relocation assistance, union position, visa sponsored into a short p.
We should not include boilerplate like Privacy, Do Not Sell My Personal Information, Terms of Use, Accessibility.
Now craft HTML.
We'll have sections: About the role, Responsibilities, Requirements, Skills, Working Conditions (maybe not standard but we can include as a section). But we could put Working Conditions under Responsibilities? Might be okay but it's separate.
Given instruction: prefer a few substantive sections over many thin ones. So we could combine Working Conditions and Travel etc into a section "Working Conditions & Travel". But we don't have that heading in examples. Could use "Working Conditions". It's okay.
Let's produce:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings; we could also add other headings but better stick to those. Working Conditions not in list; maybe we can omit or fold into Responsibilities? But it's substantive. Could include as a paragraph under Responsibilities? Better to create a section "Working Conditions" but not in allowed list; risk. However instruction says use those as examples, not exclusive. It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings; we could also add others but safer to stick to those. Working Conditions could be placed under Responsibilities as a bullet? Might be okay.
Travel Requirements maybe part of Schedule? Not exactly schedule. Could be omitted? But it's substantive. Could be placed under Responsibilities as bullet.
We must not include boilerplate like application instructions, EEO, etc.
We need to preserve all substantive information: job summary, responsibilities, duties, basic/required qualifications, desired qualifications, working conditions, travel requirements, relocation assistance, union position, visa sponsored, etc. Some of those are minor metadata; we can fold into short p.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings.
We need to output only HTML fragment.
Let's craft:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings; we could also add others but safer to stick to those. Working Conditions could be placed under Responsibilities as a bullet? Might be okay.
Travel Requirements maybe part of Schedule? Not exactly schedule. Could be omitted? But it's substantive. Could be placed under Responsibilities as bullet.
We must not include boilerplate like application instructions, EEO, etc.
We need to preserve all substantive information: job summary, responsibilities, duties, basic/required qualifications, desired qualifications, working conditions, travel requirements, relocation assistance, union position, visa sponsored, etc. Some of those are minor metadata; we can fold into short p.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings.
We need to output only HTML fragment.
Let's craft:
About the role
Job Summary ...
Responsibilities
- Technology Evaluation & Demonstration: ...
- Strategic Partnerships, Industry Engagement & Communications: ...
- Innovation & Organizational Enablement: ...
About the role
[Job Summary text]
Responsibilities
- Technology Evaluation & Demonstration: Monitor emerging technology trends, market developments, and industry activity to identify opportunities and inform ETO strategy; provide analytical leadership for technology assessment, evaluation, road mapping, and emerging technology valuations; manage emerging technology focused venture capital and external innovation relationships; conduct engineering, research, and related studies of emerging technologies with areas of expertise and apply technical knowledge to support technology development decisions; key technology focus areas include but are not limited to generation, energy storage, transmission and distribution, transformers, energy efficiency and demand response, electric vehicles, robotics, and artificial intelligence; facilitate the development and execution of pilot project plans, ensuring alignment among project objectives, technical scope, stakeholder expectations, resources, timelines, and deliverables; develop test plans, analyze test data, and communicate test results to key stakeholders; apply necessary project management and control policies and standards for emerging technology initiatives, including planning, scheduling, resource coordination, risk management, and performance monitoring; lead the full project lifecycle from opportunity identification and assessment through development, demonstration, technology transfer, and closeout.
- Strategic Partnerships, Industry Engagement & Communications: Develop and implement partnership strategies that support Emerging Technology organizational objectives; build and maintain effective working relationships with internal stakeholders, industry partners, startups, universities, venture capital firms, and other external organizations; lead industry benchmarking efforts and integrate external insights and lessons learned into ETO strategy and innovation practices; lead ETO support for regulatory filings and other external or internal communications requiring technology development information; represent the company at customer forums, industry organizations, trade associations, and other external engagements while exemplifying what it means to be a Duke Energy employee; lead education sessions, including lunch and learns, seminars, and tours; demonstrate effective oral and written communication skills and maintain accurate project records, documentation, and files.
- Innovation & Organizational Enablement: Support the development and continuous improvement of innovation, project lifecycle, technology transfer, and portfolio management processes; assess and prioritize R&D activities with other Lines of Business (LOB) and ensure they are aligned with their technology roadmaps and Duke Energy’s strategic objectives; support required legislative and/or regulatory programs, documentation and filings to ensure successful implementation of pilots/programs (e.g. NC Non-DSM/EE Rapid Prototyping); contribute technical and analytical expertise to the identification, analysis, and resolution of problems in areas of specialization.
Requirements
- Bachelor's Degree in Information Systems, Engineering, or Computer Science
- Minimum of 7 years of related work experience
- In lieu of degree, a High School Diploma/GED and a minimum of 11 years of related work experience
Skills
- Understanding of fundamental engineering theories, principles, and practices, with the ability to interpret technical information and apply it to business