Jobs · Engineering · Utah

SCADA Engineer - Lead Professional

WSP in the U.S. · Salt Lake City, UT · 1 mo ago
Engineering$102k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to parse the job description. Let's extract content: First paragraph: "This Opportunity WSP is an opportunity..." Actually the description: "Job Description This Opportunity WSP is currently initiating a search for an experienced SCADA Engineer – Lead Professional for our Boise, ID office. Candidates for our offices in Clarkston, WA; Portland, OR; San Diego, CA; Denver, CO; Salt Lake City, UT; and Ft. Lauderdale, FL will also be considered. Be involved in projects with our Electrical Studies, SCADA, and Protection (ESSP) team and be part of a growing organization that meets our clients' objectives and solves their challenges. WSP brings global expertise in power delivery, power generation, and program management, anchored by the acquisition of POWER Engineers, Inc. TRC Companies have now joined WSP, deepening our power practice and expanding our energy advisory and intelligent grid services. We are partnering with clients to shape how energy systems evolve around the world, and we need your help." That's about the role / overview. Could be "About the role". We'll put that as

About the role

with

containing that paragraph. Next: "Provides technical leadership and subject matter expertise for the design, engineering, and commissioning of utility and commercial power projects. Responsibilities include the development and commissioning of transmission and distribution substations, power distribution and regulation systems, renewable energy facilities, and protection and control systems. Guides project teams, resolves complex technical challenges, and ensures designs meet industry standards for quality, safety, and functionality." That's responsibilities. We'll put

Responsibilities

with
  • each bullet? The paragraph is a sentence with multiple responsibilities separated by commas. Could break into list items: development and commissioning of transmission and distribution substations; power distribution and regulation systems; renewable energy facilities; protection and control systems; guides project teams; resolves complex technical challenges; ensures designs meet industry standards for quality, safety, and functionality. Also "Provides technical leadership and subject matter expertise for the design, engineering, and commissioning of utility and commercial power projects." Could be separate bullet. We'll list each as
  • . Next: "Your Impact Candidates for this role will have familiarity, experience, or expertise with some of the items listed below. A willingness to learn in areas where you do not have experience and to teach others in areas where you do have experience is essential to being successful on our team." Then a list of items under "Leadership:", "Data Acquisition:", "Networking:", "Communications:", "Working knowledge or awareness of applicable industry SCADA practices...", "Applicable network and communication protocols:", "Applicable Logic and Control Platforms:", "Applicable Software:", "Logic and Control Systems:", "Exercise responsible and ethical decision-making...". These are essentially skills/requirements. Could be under "Skills" or "Requirements". The posting also has "Required Qualifications" and "Preferred Qualifications". So we need sections: Requirements (maybe Required Qualifications), Qualifications (maybe Preferred Qualifications), Skills (maybe the technical skill list). Also Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role (overview) - Responsibilities (list) - Skills (the long list of technical competencies) - Required Qualifications (Bachelor's degree, 7-10 years experience, flexibility, occasional travel, safety track record) - Preferred Qualifications (Engineer license, Master's degree, consulting experience, mentoring/leadership) - Benefits (WSP Benefits paragraph) - Pay (Compensation Expected Salary ranges) - Schedule? Not explicitly mentioned except "Must be flexible to a variety of schedules to meet business needs". That's a schedule-related statement. Could be under Schedule section. The posting does not give specific schedule like full-time, but mentions flexibility. We could include a Schedule section with that statement. However the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule flexibility, so we can include Schedule. We must not include placeholder text like "commensurate with experience". Not present. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must not include boilerplate like Disclaimer (Relocation assistance is not available) maybe we can keep? It's not boilerplate? It's a specific statement about relocation assistance not available. That's substantive? Might be considered minor metadata; but we could fold into a short p or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." Relocation assistance is minor metadata; we could include in a short p under maybe Benefits? But better to drop? It's not required to keep. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Relocation assistance is substantive? It's a detail about the job. I'd keep it maybe under a short p under Benefits or as its own note. But we have Benefits section already; we could add a sentence: "Relocation assistance is not available for this position." However that is not a benefit; it's a note. Could be placed under Benefits as a note. But maybe better to include as a short p after Benefits heading. We also have "Disclaimer" heading before that; we should remove the heading "Disclaimer" as it's boilerplate. Keep the sentence. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

    About the role

    ... (overview paragraph)

    Responsibilities

    • Provides technical leadership and subject matter expertise for the design, engineering, and commissioning of utility and commercial power projects.
    • Development and commissioning of transmission and distribution substations.
    • Power distribution and regulation systems.
    • Renewable energy facilities.
    • Protection and control systems.
    • Guides project teams.
    • Resolves complex technical challenges.
    • Ensures designs meet industry standards for quality, safety, and functionality.

    Skills

    • Leadership: Coordinate, review and approve electrical infrastructure design plans for mid-level and complex projects, ensuring data integrity and work is compliant with all applicable codes, ordinances, and regulations.
    • Data Acquisition: Prepare points lists of all data to be transferred between control centers and controlled apparatus, assign and program data addressing and routing information, develop Human Machine Interface (HMI) screens, travel to project sites to test and commission data transfer schemes.
    • Networking: Design and configure network and communication paths for Remote Terminal Units (RTUs), Data Concentrators, Intelligent Electronic Devices (IEDs), Human Machine Interfaces (HMIs), and other SCADA system equipment inside substations and facilities.
    • Communications: Specify and design communication networks including data security and availability. Develop basic specifications for fiber optic, microwave, power line carrier, or radio communication paths; infrequent travel to project sites to troubleshoot and commission network and communication systems.
    • Working knowledge or awareness of applicable industry SCADA practices outlined in IEEE, IEC, ANSI, CIGRE, or NERC standards and regulations for design work.
    • Applicable network and communication protocols: DNP, Modbus, and IEC 61850 specified protocols; experience with legacy SCADA protocols a plus.
    • Applicable Logic and Control Platforms: SEL RTAC, NovaTech Orion, Eaton SMP.
    • Applicable Software: Wonderware, AcSELerator RTAC, NovaTech NCD/Inkscape; IEC 61850 System Configuration Tool experience a plus; familiarity with SCADA/EMS/ADMS software a plus.
    • Logic and Control Systems: Develop, document, and implement logic and control schemes for remote and local operation of power system equipment, including Microgrid, Volt/VAR Control, Load Shedding, and other custom control applications. Develop programs on various platforms for implementation of these schemes and travel to project sites to test and commission control solutions.
    • Exercise responsible and ethical decision-making regarding company funds, resources, and conduct, and adhere to WSP’s Code of Conduct and related policies and procedures.
    • Perform additional responsibilities as required by business needs.
    But note: Some of these items are from "Your Impact" and also include "Perform additional responsibilities as required by business needs." That's more like a responsibility. Could be moved to Responsibilities. However we already have responsibilities; we could keep it there. But we might duplicate. Better to keep it under Skills? It's more a generic responsibility. The instruction: preserve ALL substantive information; we can keep it where it appears. It appears after the list of skills under "Your Impact". It says "Exercise responsible and ethical decision-making regarding company funds, resources, and conduct, and adhere to WSP’s Code of Conduct and related policies and procedures. Perform additional responsibilities as required by business needs." That's more like a responsibility/behavior. Could be placed under Responsibilities as well. But we already have responsibilities list; we could add two more items. Let's move those two to Responsibilities. Thus Responsibilities list will include those two. Now Required Qualifications:

    Required Qualifications

    • Bachelor’s Degree in Electrical Engineering (or equivalent experience).
    • 7 to 10 years of relevant post-education experience as an electrical engineer providing design deliverables for capital projects in power generation, transmission, and distribution at a utility or commercial scale.
    • Must be flexible to a variety of schedules to meet business needs and able to prioritize responsibilities and quickly adapt to change.
    • Occasional travel may be required, depending on project-specific requirements.
    • Proven track record of upholding workplace safety and ability to abide by WSP’s health, safety, drug/alcohol, and harassment policies.
    Note: The flexibility statement about schedules could also go to Schedule section, but it's also a qualification. We'll keep it here; we may also create Schedule section with that statement. But to avoid duplication, we could keep it only under Required Qualifications and not create Schedule section. However the instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The schedule flexibility is specific content; we could make a Schedule section with that sentence. But then we would duplicate content. The instruction says preserve ALL substantive information; does not forbid duplication? It says do NOT invent or summarize away detail. Duplication is not summarizing away; it's repeating. Might be okay but could be considered redundant. Better to avoid duplication; we can place schedule flexibility under Schedule section and remove from Required Qualifications. However Required Qualifications also includes "Must be flexible to a variety of schedules to meet business needs and able to prioritize responsibilities and quickly adapt to change." That's a qualification about schedule flexibility. If we move it to Schedule, we lose it from Required Qualifications. But we could keep it in both places? Might be okay but could be considered redundant. I'd rather keep it under Required Qualifications and not create a separate Schedule section unless there is additional schedule info like "full-time", "shift work", etc. There's not. So we may omit Schedule section. But the instruction says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state schedule flexibility, so we could create Schedule section with that statement. However we also have that statement in Required Qual

Similar jobs