Jobs · Legal · California

Government Relations Senior II - (Riverside County)

SoCalGas · Riverside, CA · 1 mo ago
LegalFull-time
We need to output HTML fragment with sections: About Us? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - About Us paragraph (multiple sentences). This is about the company. Could be "About Us" but the allowed headings list includes "About the role". Not "About Us". But we can still use

    for section headings; they gave examples but not exclusive. However they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings. "About Us" is not in list; maybe we should not create a heading for it; we could embed that prose in a

    without heading? But they said include a section ONLY when posting has real, specific content for it. The "About Us" is substantive. But we don't have a matching heading. Could we use "About the role"? That's not accurate. Perhaps we can treat "About Us" as part of the role description? But better to follow instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to stick to those headings if possible. However we have content that fits "Responsibilities" (Duties And Responsibilities). Also "Pay" (Pay Range). Also maybe "Benefits" (they mention competitive compensation plan, upward mobility opportunities, work life balance). Also "About the role" could be the Primary Purpose paragraph. So we can map: - About the role: Primary Purpose paragraph (Owns policy portfolios...). Also maybe the "About Us" could be considered company overview but not required. Could embed as part of About the role? Might be okay. - Responsibilities: Duties And Responsibilities bullet list (though it's paragraph with semicolons). We need to convert to
    • . The duties are separated by semicolons; we can split into list items. - Benefits: They mention "competitive compensation plan, upward mobility opportunities and the ability to find a true work life balance." Also maybe "As an employee of SoCalGas, you’ll enjoy a competitive compensation plan, upward mobility opportunities and the ability to find a true work life balance." That's benefits. Also maybe "Discover the rewards of joining SoCalGas by exploring our website: Our Mission; Sustainability, In the Community, and Employee Benefits." That's vague. We'll include benefits as those three items. - Pay: Pay Range $129500.00 - $204500.00 / hour (note weird per hour but it's given). Also there is a paragraph about Pay Transparency. That's metadata; we can include in Pay section maybe as a note. - Schedule: Not mentioned. So we should not create Schedule section. - Requirements/Qualifications/Skills: Not explicitly listed. There's mention of "Frequent, independent driving ... essential to this position". That could be a requirement. Also maybe "maintaining a focus on safety and compliance with traffic laws". Could be a requirement. But not a formal list. Could we create a Requirements section with those? The instruction: include a section ONLY when posting has real, specific content for it. The driving requirement is specific. Could be considered a requirement. We could put under Responsibilities? But it's more a requirement. Might be better to create a Requirements section with that bullet. But we need to avoid thin sections. Perhaps combine Requirements and Responsibilities? But they are distinct. Let's see: The posting includes "Frequent, independent driving to meetings, company locations, field locations and/or active incidents sites while maintaining a focus on safety and compliance with traffic laws is essential to this position and cannot reasonably be accomplished via alternative transportation." That's a requirement. Could be placed under Responsibilities as a duty? It's more a requirement. I'd make a Requirements section with that bullet. Also there is "Proposes and shapes the content and topics of discussion, ensuring relevance to business activities; engages directly with government officials at gatherings." etc. Those are duties. Thus sections: - About the role (Primary Purpose) - Responsibilities (list of duties) - Requirements (driving requirement) - Benefits (compensation plan, upward mobility, work-life balance) - Pay (range and transparency note) We should not include Schedule. We need to output only HTML fragment, no /. Use

      for each section heading. Use
      • for lists. Use

        for prose. We must preserve all substantive information. Let's extract text precisely. About Us paragraph: "SoCalGas, the nation’s largest gas distribution utility, is dedicated to providing safe, reliable, and affordable energy to over 21 million Southern California customers. Through innovation, collaboration, and an unwavering commitment to the needs of our communities we proudly uphold our mindset of “Glad to be of Service” and provide exceptional customer service today and ready to meet California’s energy needs with innovative solutions for tomorrow. As an employee of SoCalGas, you will support our core values to do the right thing, champion people, and shape the future. You will play a pivotal role in the energy transition initiatives, supporting our mission: Safe, reliable, and affordable energy delivery today. Ready for tomorrow. We are committed to attracting top talent and fostering a diverse workforce that reflects the vibrant communities we serve. As an employee of SoCalGas, you’ll enjoy a competitive compensation plan, upward mobility opportunities and the ability to find a true work life balance. Discover the rewards of joining SoCalGas by exploring our website: Our Mission; Sustainability, In the Community, and Employee Benefits. Join SoCalGas today and become a vital part of a team that is driving innovation, championing community needs, and shaping the future of energy in California." Primary Purpose: "Owns policy portfolios that require sustained engagement with legislators, regulatory agencies, and external stakeholders. The role develops and executes integrated advocacy strategies, manages issue lifecycles, and ensures alignment between policy positions and organizational objectives with minimal oversight." Duties And Responsibilities: "Engages with a broader set of officials and maintains existing relationships; leads smaller strategic relationship building projects focusing on select initiatives.Proposes and shapes the content and topics of discussion, ensuring relevance to business activities; engages directly with government officials at gatherings.Prepares and proofreads correspondence, forms and other documents, and coordinates the communication of information from the Government Affairs office to internal stakeholders interested in topics related to strategic initiatives, agency actions, and legislative proposals.Drafts and delivers reports for the corporate office as well as briefing notes for management to outline issues that may impact the organization’s operations and project developments.Develops multiple pieces of policy content ensuring coherence and consistency; engages with internal and external stakeholders to refine content.Implements and acts on opportunities to streamline administrative processes associated with managing the office.Supports outreach to industry lobbying coalitions on priority issues.Performs other duties as assigned." Requirement: "Frequent, independent driving to meetings, company locations, field locations and/or active incidents sites while maintaining a focus on safety and compliance with traffic laws is essential to this position and cannot reasonably be accomplished via alternative transportation." Pay: "Pay Range $129500.00 - $204500.00 / hour Pay Transparency In order to support the Fair Compensation Strategy by the US Govt., HR Dept., clients are required to adhere to "Pay Transparency Law"; in the impacted states; that have mandated the employers to list the salary ranges in Job advertisements or postings for job opportunities and Job promotions." Benefits: from About Us: "competitive compensation plan, upward mobility opportunities and the ability to find a true work life balance." Also maybe "Discover the rewards of joining SoCalGas by exploring our website: Our Mission; Sustainability, In the Community, and Employee Benefits." That's more about benefits but vague. We'll include the three items. We need to ensure we don't repeat content. The About Us paragraph includes the benefits sentence; we might not need to repeat benefits separately if we already have that sentence in About Us. But we need a Benefits section; we could extract that sentence and put in Benefits section as list. However the About Us paragraph also contains other info; we could keep About Us paragraph in About the role section? Actually About the role is Primary Purpose; we could also include the About Us paragraph as a separate section maybe "About the company"? But not in allowed headings. Could we incorporate About Us paragraph into About the role section as preamble? 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." It doesn't forbid adding extra headings beyond the examples, but they said "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections. The About Us paragraph is not about the role but about the company. Could we treat it as part of "About the role"? Might be okay to include it there as introductory prose. However the About the role heading expects description of the role; we could put Primary Purpose there and also include the About Us paragraph as part of that section? Might be mixing. Better to create a section "About the role" containing the Primary Purpose paragraph only. Then we could treat the About Us paragraph as part of "Benefits"? No. Alternatively, we could create a section "About the company" but not in list; risk of violating instruction. However they didn't forbid other headings; they just gave examples. The instruction: "Use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as you should use

        for headings, and those are examples of typical headings you might use. Not that you must only use those. So we could add a heading "About the company" if we want. But they said "Prefer a few substantive sections over many thin ones." Adding an extra heading may be okay. But to be safe, we could incorporate the About Us paragraph into the "About the role" section as introductory prose before the Primary Purpose. That would still be under

        About the role

        . That seems acceptable. Thus:

        About the role

        [About Us paragraph] [Primary Purpose paragraph]

        But we need to ensure we don't lose any info. We'll combine them. Then Responsibilities:

        Responsibilities

        • ... each duty.
        Requirements:

        Requirements

        • Frequent, independent driving ...
        Benefits:

        Benefits

        • competitive compensation plan

Similar jobs