Lead SCADA Engineer - Critical Infrastructure

We need to output HTML fragment with sections: About the role? The posting includes Job Summary, Essential Functions, Position Requirements, Physical Demands, Travel/Relocation, Education Requirements, Preferred, Benefits, Pay Range. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must include a section only when posting has real, specific content. We must not emit filler like "commensurate with experience". We must preserve all substantive info; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Notice To Third Party Agencies" etc. Also remove "Are you ready..." etc. Also remove "Smart Tech Contracting offers a very competitive benefits package; highlights include ..."? That's benefits, we keep. Also remove "CO, CA, IL, NY, WA, and Washington DC residents only: ..."? That's about pay range location specifics; we can keep pay range but maybe incorporate? The pay range is given: "The Pay Range For This Role Is 99,750 - 120,225 USD per year(Remote (United States))". We'll keep Pay section with that range. Also we have benefits details. We need to decide sections: About the role (maybe Job Summary), Responsibilities (Essential Functions), Requirements (Position Requirements), Qualifications (Education Requirements + maybe Preferred?), Skills (maybe not explicit), Benefits, Pay, Schedule (maybe travel? but schedule not given). We have travel/relocation requirements; maybe we can put under Schedule? But schedule is about work hours; not given. Could omit Schedule if no specific content. The instruction: include a section ONLY when posting has real, specific content for it. So we should not create Schedule if no schedule info. We have travel requirements; maybe we could put under "Travel" but not a listed heading. The allowed headings are limited to those examples; but we could still use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we could use others if needed, but better to stick to those. Travel could be part of Responsibilities? Not really. Could be part of Requirements? Might be okay to include a "Travel" section but not in list; but instruction says use those for section headings; maybe we should only use those headings. However we have travel info; we could incorporate into Responsibilities or Requirements as a bullet. Probably better to add a "Travel" subsection under Responsibilities? But we need 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 says use

for section headings (e.g. those). Likely they expect us to use those headings where applicable. Travel could be part of Responsibilities (since it's about job duties). We'll include travel bullet under Responsibilities. Physical Demands: could be part of Requirements? Might be a separate section but not in list. Could be under Requirements as a bullet. We'll include under Requirements. Education Requirements: could be under Qualifications. Preferred: could be under Qualifications as well. Benefits: we have. Pay: we have. Thus sections: About the role (Job Summary), Responsibilities (Essential Functions + travel), Requirements (Position Requirements + Physical Demands), Qualifications (Education Requirements + Preferred), Benefits, Pay. We must not repeat job title as heading. So no heading for Lead SCADA Engineer. We must not include duplicated lines. We'll need to extract content. Let's parse the posting. Job Summary paragraph: "The Lead SCADA Engineer – Level IV is a senior technical authority responsible for SCADA system architecture, development, and technical quality across multiple mission-critical infrastructure projects. This role is intentionally broad and platform-agnostic. It is designed to attract senior engineers with deep experience in SCADA systems, supervisory control, system integration, and control-system development, not narrow PLC specialists tied to a single platform or methodology. The Lead SCADA Engineer sets technical direction, establishes development standards, and ensures scalable, secure, and reliable SCADA solutions that support complex, high-availability environments (data centers, utilities, industrial infrastructure, mission-critical facilities)." Essential Functions broken down with percentages and bullet-like sentences. We'll convert to

• items. Essential Functions sections: - SCADA Architecture, Standards, & Development (40%): * Define and maintain SCADA system architecture, development standards, and best practices. * Establish design intent for supervisory control systems, including data modeling, alarm strategy, graphics philosophy, and system performance expectations. * Lead development of SCADA code, scripts, templates, and reusable components where appropriate. * Ensure SCADA systems are scalable, maintainable, and aligned with long‑term operational needs. * Provide technical governance across multiple projects and platforms. - Project-Level Technical Leadership (25%): * Serve as senior technical lead for SCADA systems across multiple concurrent projects. * Partner with Project Managers, Engineers, and Field Leadership during planning, sequencing, and commissioning strategy development. * Translate operational requirements into high‑level SCADA system solutions. * Identify technical risks early and recommend mitigation strategies. * Act as escalation point for complex integration, development, or commissioning challenges. - Quality, Risk, & Commissioning Support (20%): * Review and approve SCADA system designs, configurations, and development approaches. * Perform peer reviews of SCADA configurations, scripts, and logic developed by others. * Validate alignment with standards, cybersecurity considerations, and design intent. * Support FAT, IST, commissioning, and live system cutovers as a senior technical authority. * Assist in diagnosing and resolving critical system issues during high‑risk events. - Mentorship & Technical Development (15%): * Mentor mid‑ and senior‑level engineers through technical review, guidance, and coaching. * Support development of internal documentation, standards, and training materials. * Promote continuous improvement, knowledge sharing, and engineering excellence. - Completion of Assigned Tasks and Deliverables on Time and on Budget - Performs Other Related Duties as Assigned We'll include those as list items. Position Requirements: - 6-8+ years of experience engineering SCADA control systems in mission-critical, industrial, or infrastructure environments - Demonstrated experience designing and developing SCADA systems, not just configuring them - Strong understanding of: * SCADA architecture and data modeling * Alarm management and HMI/graphics philosophy * System integration and communications * Commissioning workflows, IST, and live cutovers - Proven ability to review, critique, and improve complex control system implementations - Ability to operate as a technical authority without direct people management - Strong communication skills with the ability to translate technical concepts for non technical stakeholders - Comfortable supporting multiple projects concurrently in a fast paced environment Physical Demands: - Ability to remain in a stationary position for extended periods while working on a computer - Ability to move through offices, job sites, control rooms, and equipment spaces as needed - Ability to occasionally lift or move tools or equipment weighing up to 50 pounds Travel / Relocation Requirements: - Must have a valid driver’s license and ability to rent vehicles - Limited (up to 30%), targeted travel for FAT, IST, commissioning strategy, or critical issue resolution - Willingness to support extended hours during major commissioning or cutover events as needed - Domestic travel required as project needs dictate; valid REAL ID or passport required Education Requirements: - Bachelor’s degree in Engineering (Electrical, Controls, Automation, Computer, Mechanical) or a related technical discipline preferred - Equivalent combination of education and demonstrated, hands-on engineering experience will be considered - Relevant industry certifications or advanced technical training are a plus but not required Preferred (Not Required): - SCADA platform certifications (e.g., Ignition Gold, AVEVA/Wonderware, Siemens, Rockwell, or equivalent) - Ongoing professional development in control systems, automation, or mission-critical infrastructure Benefits: - Choice of comprehensive medical plans (including two PPO-style plans and a HDHP w/ HSA option) - Dental and vision plans - Comprehensive medical, dental and vision benefits extended to spouse / domestic partner and dependent children up to age 26 - 401k with company match and self-directed brokerage account option - PTO including additional paid time off during the last week of the year - Company paid life insurance coverage for employees and their eligible dependents - Short and long-term disability, AD&D coverage - Professional development opportunities, tuition reimbursement and professional licensing assistance - Paid parental leave after one year of employment Pay Range: - The Pay Range For This Role Is 99,750 - 120,225 USD per year (Remote (United States)) We need to output HTML fragment only. We'll structure:

  About the role

  Job Summary paragraph.

  Responsibilities

  ...

  Requirements

  ... include Position Requirements and Physical Demands and Travel? We'll include Position Requirements and Physical Demands and Travel as list items.

  Qualifications

  ... Education Requirements and Preferred.

  Benefits

  ... Benefits.

  Pay

  Pay range: 99,750 - 120,225 USD per year (Remote United States).

  We must not include boilerplate like EEO, etc. Also remove duplicated lines. Ensure we preserve all substantive info. Let's craft. Be careful to not include any extra text outside HTML. We'll output:

  About the role

  The Lead SCADA Engineer – Level IV is a senior technical authority responsible for SCADA system architecture, development, and technical quality across multiple mission-critical infrastructure projects. This role is intentionally broad and platform-agnostic. It is designed to attract senior engineers with deep experience in SCADA systems, supervisory control, system integration, and control-system development, not narrow PLC specialists tied to a single platform or methodology. The Lead SCADA Engineer sets technical direction, establishes development standards, and ensures scalable, secure, and reliable SCADA solutions that support complex, high-availability environments (data centers, utilities, industrial infrastructure, mission-critical facilities).

  Responsibilities

  • Define and maintain SCADA system architecture, development standards, and best practices.
  • Establish design intent for supervisory control systems, including data modeling, alarm strategy, graphics philosophy, and system performance expectations.
  • Lead development of SCADA code, scripts, templates, and reusable components where appropriate.
  • Ensure SCADA systems are scalable, maintainable, and aligned with long‑term operational needs.
  • Provide technical governance across multiple projects and platforms.
  • Serve as senior technical lead for SCADA systems across multiple concurrent projects.
  • Partner with Project Managers, Engineers, and Field Leadership during planning, sequencing, and commissioning strategy development.
  • Translate operational requirements into high‑level SCADA system solutions.
  • Identify technical risks early and recommend mitigation strategies.
  • Act as escalation point for complex integration, development, or commissioning challenges.
  • Review and approve SCADA system designs, configurations, and development approaches.