Principal SME, Utility & Grid Infrastructure, Global

We need to output HTML fragment with sections for headings where content exists. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Sections: - About Vantage: description of company. Could be "About the role"? Actually "About Vantage" is company overview. Could fit under "About the role"? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings if present. "About Vantage" is about company, not role. Could be placed under "About the role"? Might be okay. But we should not invent headings without content. We have content for About Vantage, Position Overview, Essential Job Functions (responsibilities), Job Requirements (requirements), Preferred Qualifications (qualifications/skills?), Physical Demands And Special Requirements (maybe not needed), Additional Details (salary range, benefits, etc). Also there is some culture statements, EEO etc which we should remove. We need to include sections only when posting has real, specific content for it. So we need to decide which headings to include. Potential sections: - About the role: could contain Position Overview and maybe About Vantage? But "About the role" likely expects description of role. We'll put Position Overview there. - Responsibilities: Essential Job Functions. - Requirements: Job Requirements (Bachelor's degree, 10+ years, etc). - Qualifications: Preferred Qualifications. - Skills: maybe we can extract skills from responsibilities/requirements? But we should not invent. If no explicit skills list, we should not create Skills section. The posting does not have a separate skills list; we could combine skills under Qualifications or Requirements. Better to omit Skills section if no explicit list. - Benefits: Additional Details includes benefits description. So we can have Benefits section. - Pay: Additional Details includes Salary Range. So we can have Pay section. - Schedule: Not mentioned (no schedule info). So omit Schedule. Also we might include "About the company" but not a standard heading. Could we put under About the role? Might be okay but could be considered filler. However we have substantive content about Vantage; we could include it as a paragraph under About the role heading (makes sense). Or we could create a separate heading like "About Vantage" but not allowed per instruction (only those headings). So we must fit into allowed headings. We'll put company overview under About the role. Now we need to format: Use

for each section heading. Under each heading, use

for prose,

• for lists. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like travel required up to 15%, etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove statements like "We operate with No Ego and No Arrogance..." etc? That's company culture; maybe considered boilerplate? It's not EEO but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The culture statements are not explicitly listed to remove, but they might be considered fluff. However they are substantive? They are not required for job description; they are more about company values. Might be considered boilerplate? Safer to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not say to remove culture statements. So we can keep them if they are not boilerplate. But they are not essential job info. However they are not prohibited. I'd keep them maybe under About the role or separate? But we have no heading for culture. Could include them in About the role paragraph. We must not repeat job title as heading. The title is "Principal SME, Utility & Grid Infrastructure". We'll not output that. Now let's extract content. About Vantage paragraph: "Vantage powers, cools, protects and connects the technology of the world’s well-known hyperscalers, cloud providers and large enterprises. Developing and operating across North America, EMEA and Asia Pacific, Vantage has evolved data center design in innovative ways to deliver dramatic gains in reliability, efficiency and sustainability in flexible environments that can scale as quickly as the market demands." Position Overview: "This role can be based remotely anywhere in the US. Vantage is looking for a Principal SME, Utility & Grid Infrastructure, to help provide technical expertise and partner with Energy Strategy team to enable implementation of power delivery across utility-facing and grid connected infrastructure. This is a senior technical-authority SME role for someone who combines deep expertise in utility engagement, transmission and distribution systems, grid interconnection, substations, power quality and regulatory considerations with the ability to work cross-functionally across complex, scaled environments." Essential Job Functions (list many). We'll need to convert each sentence into list items? The instruction: Use
  • for any list of duties/requirements/benefits. So we should make a list. The essential job functions are many sentences separated by periods. We'll make each as a list item. Job Requirements: list items. Preferred Qualifications: list items. Physical Demands And Special Requirements: maybe we could include as a section? Not in allowed headings. Could omit. But it's substantive. However we have no heading for it. Could we put under Requirements? Might be okay but it's not exactly requirements. Could we create a section "Requirements" and include both job requirements and physical demands? Might be mixing. Better to omit physical demands if no appropriate heading. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Physical Demands. Additional Details: includes Salary Range, benefits description, culture statements, etc. We'll split: Pay section for salary range; Benefits section for benefits and maybe culture? But benefits section should contain benefits details. Culture statements could go under About the role or maybe we could add a separate section? Not allowed. We'll include culture statements in About the role paragraph maybe at end. We must not include duplicated lines. Ensure we don't repeat. Now craft HTML. Structure:

    About the role

    Vantage powers, cools, protects and connects the technology of the world’s well-known hyperscalers, cloud providers and large enterprises. Developing and operating across North America, EMEA and Asia Pacific, Vantage has evolved data center design in innovative ways to deliver dramatic gains in reliability, efficiency and sustainability in flexible environments that can scale as quickly as the market demands.

    This role can be based remotely anywhere in the US. Vantage is looking for a Principal SME, Utility & Grid Infrastructure, to help provide technical expertise and partner with Energy Strategy team to enable implementation of power delivery across utility-facing and grid connected infrastructure. This is a senior technical-authority SME role for someone who combines deep expertise in utility engagement, transmission and distribution systems, grid interconnection, substations, power quality and regulatory considerations with the ability to work cross-functionally across complex, scaled environments.

    Responsibilities

    • Be the technical authority for utility engagement, grid interconnection, transmission and distribution infrastructure, substations, power quality, utility tariffs, regulatory considerations and grid-connected Energy Hub architectures within Product Engineering.
    • Be responsible for the integrity, usability and evolution of utility service technical standards, reference architectures, risk assessment frameworks and decision criteria that improve scalable grid integration across global markets.
    • Partner with regional leads on utility and grid strategy on commercial project implementation, including infrastructure readiness reviews, long-range site planning, cross-functional technical alignment and feedback loops that improve future platform strategy.
    • Serve as the technical partner to the Energy Strategy team by identifying utility-interface constraints, defining engineering requirements, validating study assumptions, and recommending practical mitigations that improve infrastructure readiness and support faster, lower-risk power delivery in target markets.
    • Reduce technical, interconnection, delivery and operational risk through clear standards and early engagement.
    • Establish scalable technical frameworks, reference architectures and decision criteria for Product Engineering.
    • Improve cross-functional alignment between Product Strategy, Product Engineering, Development, Energy, Construction, Operations and regional delivery teams.
    • Influence future platform strategy through practical, technically grounded recommendations.
    • Advance utility readiness, improve reliability, reduce interconnection risk and inform long-term energy infrastructure strategy.
    • Partner with Energy Strategy lead and develop utility engagement frameworks and best practices across multiple regions and utility providers.
    • Provide technical input on utility tariffs, rate structures, regulatory considerations and power procurement strategies.
    • Support utility capacity assessments, infrastructure readiness reviews and long-range site planning.
    • Lead evaluation of transmission and distribution infrastructure requirements for large-scale data center developments.
    • Assist in defining grid interconnection strategies, create technical standards and risk assessment frameworks.
    • Advise project teams on utility service configurations, reliability considerations and capacity expansion planning.
    • Establish product-level standards for utility substations and grid-connected power systems.
    • Guide development of reference designs for medium-voltage and high-voltage utility interfaces.
    • Evaluate emerging technologies and infrastructure approaches that improve scalability, resilience and delivery certainty.
    • Provide expertise on power quality, harmonics, voltage regulation, reactive power management and system stability.
    • Collaborate with electrical engineering teams to develop performance requirements and mitigation strategies.
    • Support resolution of complex utility and grid integration challenges during design, delivery and operations.
    • Define grid-connected Energy Hub architectures supporting future energy strategies.
    • Assess integration opportunities involving utility-scale generation, storage and grid services.
    • Support roadmap initiatives that enhance flexibility, capacity availability and system reliability.
    • Handle additional duties as assigned by management

    Requirements

    • Bachelor’s degree in Electrical Engineering or a related technical discipline.
    • 10+ years of experience in utility systems, transmission and distribution infrastructure, grid interconnection or power system engineering.
    • Deep knowledge of utility operations, grid planning and substation design.
    • Experience working directly with utilities, ISOs, RTOs, regulatory organizations or large-load interconnection processes.
    • Strong understanding of power quality, electrical reliability, grid stability and large-scale power delivery requirements and transient modeling.
    • Clear executive-level communication skills with the ability to translate complex technical concepts into practical business decisions.
    • Travel required is expected to be up to 15% but may increase over time as the business evolves.

    Qualifications

    • Professional Engineer (PE) license.
    • Experience supporting hyperscale data centers, industrial power systems or large energy infrastructure programs.
    • Familiarity with regional utility regulatory environments and energy market structures.
    • Experience operating across multiple geographic regions and utility jurisdictions.
    • Demonstrated ability to establish standards, reference architecture and technical governance frameworks.

    Benefits

    • Medical, dental, and vision coverage
    • Life and AD&D
    • Short and long-term disability coverage
    • Paid time off
    • Employee assistance
    • Participation in a 401k program that includes company match
    • Many other additional voluntary benefits

    Pay

    Salary Range: $180,000 - $205,000 Base + Bonus (this range is based on Colorado market data and may vary in other locations)