System Integrator Intern – I – Critical Infrastructure

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, legal, application instructions, navigation, etc. Must preserve all substantive info. We need to parse the posting: It includes company description, position title, location, dates, job summary, essential functions (list of duties), technical growth, completion of tasks, position requirements (interest, basic understanding, willingness, communication, ability to work independently/team, ability to travel), preferred (not required) list, development opportunities (list), physical demands, travel/relocation requirements, education/experience requirements, benefits, pay range. We need to map to sections: About the role (maybe job summary?), Responsibilities (essential functions), Requirements (position requirements), Qualifications (maybe preferred? but we can combine), Skills (maybe technical exposure?), Benefits, Pay, Schedule (maybe travel? but schedule not given; we have travel requirements, but schedule not explicit; we could omit schedule if not present). The instruction: include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. So we need to see if schedule is present: Not explicit schedule like hours per week, but there is travel requirement and extended hours. Not a schedule. So we likely omit Schedule section. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not repeat job title as heading. So we can start with maybe

  About the role

  then a

  with job summary and maybe location/dates? The location and dates could be included in About the role paragraph. We must preserve all substantive info: company description, location, dates, job summary, essential functions (list), technical growth & development (list), completion of assigned tasks (maybe part of responsibilities), position requirements (list), preferred (not required) (list), development opportunities (list), physical demands (list), travel/relocation requirements (list), education/experience requirements (list), benefits (list), pay range (maybe a

  with pay). Also maybe include "Physical Demands" as a section? Not in allowed headings list; but we could put under Requirements or Qualifications? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. Physical demands could go under Requirements or Qualifications? Probably under Requirements (physical demands). Travel/relocation could be under Requirements or maybe under Schedule? But schedule not present. Could put under Requirements as well. We need to avoid duplication. We'll create sections: - About the role: includes company description, position title? Actually we shouldn't repeat position title as heading, but we can mention it in paragraph. Include location, dates, job summary. - Responsibilities: essential functions (list) plus maybe technical growth & development? Actually technical growth is more about learning; could be under Responsibilities or Qualifications. We'll put essential functions under Responsibilities. - Requirements: position requirements (interest, basic understanding, willingness, communication, ability to work independently/team, ability to travel) plus physical demands, travel/relocation requirements, education/experience requirements. - Qualifications: preferred (not required) list. - Skills: maybe technical exposure list from essential functions? But we already used essential functions for responsibilities. Could also list skills like PLC, SCADA, etc. But we might combine. - Benefits: benefits list. - Pay: pay range. We must not create sections with filler. Ensure each section has substantive content. Let's extract content. Company description: "Smart Tech Contracting delivers turnkey BAS & EPMS solutions for mission-critical colocation and hyperscale data centers operating at national program scale. As a Master Systems Integrator (MSI), we unify controls construction (DDC, PLC, SCADA) with software engineering, optimized graphics / UI standards, and program-level governance. Complex integrations are delivered cleanly, consistently, and fast. Our teams thrive in high-stakes environments where quality control and uptime matters, schedules are compressed, and coordination is everything. Join us and be part of a team where your voice matters, your work makes an impact, and your growth is a shared priority." Location: "Remote - work virtually from anywhere in the United States, Atlanta, GA, or Dallas, TX" Dates: "Summer 2027 Internship Dates: May 17th, 2027- August 13th, 2027" Job Summary: paragraph after "Job Summary". We'll combine. Essential Functions: list under Installation, Startup & Field Support; Testing & Commissioning; Controls & Automation Exposure; Technical Documentation & Digital Tools; Technical Growth & Development; Completion of Assigned Tasks and Deliverables on Time and on Budget; Performs Other Related Duties as Assigned. We need to turn each bullet into

• . The text includes headings like "Installation, Startup & Field Support" etc. We could treat each heading as a
• with sub-items? But we need to preserve all substantive info. Could flatten: each bullet point after heading is a duty. Could make each heading as a
• and then sub-items as nested
  . But instruction: use
  • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do top-level
    with each major heading as
    • and then inner
      for sub-items. Let's extract each: Installation, Startup & Field Support: - Assist with verification of controls installations and field wiring - Support point-to-point checkout and I/O verification activities - Assist with startup and testing of BAS, EPMS, PLC, and SCADA systems - Help verify field devices, sensors, actuators, instrumentation, and network communications - Support troubleshooting efforts during startup and commissioning activities - Document field observations, deficiencies, and corrective actions Testing & Commissioning: - Participate in system startup, commissioning, and Integrated Systems Testing (IST) activities - Assist with execution of test procedures and validation of system operation - Support functional testing of equipment and control sequences - Help verify system operation against project requirements and sequences of operation - Assist with owner demonstrations and turnover activities when appropriate Controls & Automation Exposure: - Gain exposure to Rockwell Automation PLC platforms and industrial control systems - Assist with PLC startup, troubleshooting, and communications testing - Learn SCADA fundamentals, including Ignition 8.3 deployment and operation - Learn software deployment, gateway administration, and system validation practices - Gain exposure to industrial communication protocols including Ethernet/IP, Modbus, BACnet, MQTT, and OPC UA - Assist with validating connectivity between PLCs, SCADA systems, databases, APIs, and enterprise applications - Gain exposure to operational technology (OT) and information technology (IT) integration concepts - Learn how industrial protocols are used to integrate PLCs, SCADA systems, BAS systems, EPMS systems, field devices, and enterprise applications Technical Documentation & Digital Tools: - Complete daily reports, field notes, issue logs, and testing documentation - Assist with updating redlines, as-built documentation, and punch lists - Use Microsoft Office and digital project tools to organize project information - Gain exposure to Git, Azure DevOps, and software development workflows - Utilize approved AI-enabled tools to improve reporting, documentation, and learning Technical Growth & Development: - Participate in Ignition 8.3 training with the potential opportunity to earn an Ignition Core Certification - Participate in OSHA 10 safety training and other professional development opportunities as applicable - Learn commissioning, startup, deployment, and troubleshooting best practices from experienced field personnel - Gain practical exposure to mission-critical infrastructure environments - Participate in technical training, toolbox talks, and project coordination meetings - Demonstrate continuous improvement through feedback, learning, and hands-on experience Completion of Assigned Tasks and Deliverables on Time and on Budget: (no sub-items) maybe just a statement. Performs Other Related Duties as Assigned: statement. We'll include those as list items. Position Requirements (list): - Interest in controls, automation, commissioning, PLCs, SCADA, and industrial systems - Basic understanding of electrical systems, networking, automation, or mechanical systems - Willingness to work in construction and commissioning environments - Strong communication skills and willingness to learn - Ability to work both independently and as part of a project team - Ability to travel to project sites as required Physical Demands (list): - Frequently standing, walking, climbing ladders, and working in active construction environments - Working in mechanical rooms, electrical rooms, rooftops, and confined spaces - Lifting and carrying equipment weighing up to 50 pounds - Working in varying environmental conditions, including heat, cold, humidity, dust, noise, and outdoor weather - Using hand tools, test equipment, laptops, and instrumentation for extended periods - Traveling to customer sites and working extended hours during project startup and commissioning activities as required Travel / Relocation Requirements (list): - Approximately 50–75% travel is required based on project assignments - Travel may include overnight stays, extended assignments at customer project sites, and temporary relocation for the duration of major construction projects - Employees who reside within a reasonable commuting distance of the assigned project site will be expected to travel to and from the site daily rather than utilize overnight accommodations - Must possess and maintain a valid driver's license and be able to travel by automobile and commercial air as required - Availability to work extended schedules, weekends, holidays, and multiple shifts during critical project milestones, startup, commissioning, and Integrated Systems Testing (IST) Education / Experience Requirements (list): - Currently pursuing or recently completed technical education in: - Industrial Automation - Electrical Engineering - Mechanical Engineering - Controls Engineering - Engineering Technology - Computer Engineering - Industrial Technology - A related technical discipline Preferred (not Required) (list): - Exposure to PLCs, SCADA systems, BAS, EPMS, or industrial automation systems - Familiarity with Rockwell Automation products - Exposure to Ignition, Modbus, BACnet, MQTT, OPC UA, or industrial networking - Exposure to Git, Azure DevOps, Docker, Kubernetes, or modern software deployment tools - Familiarity with APIs, JSON, MQTT, software integration concepts, or AI-assisted development - Previous internship, trade school, laboratory, military, or hands-on technical experience - Experience using hand tools, meters, testing equipment, or troubleshooting electrical systems Development Opportunities (list): - Ignition 8.3 SCADA deployment, administration, and development - Potential opportunity to earn an Ignition Core Certification - OSHA 10 Certification - Rockwell Automation PLC hardware and software platforms - Startup, commissioning, Integrated Systems Testing (IST), and owner acceptance activities - BAS, EPMS, PLC, and SCADA integration - Industrial networking fundamentals including switches, VLANs, routing, and network troubleshooting - Industrial communication protocols including EtherNet/IP, BACnet/IP, BACnet MS/TP, Modbus TCP, Modbus RTU, MQTT, and OPC UA - Troubleshooting communications between PLCs, SCADA systems, field controllers, sensors, meters, and third-party equipment - System integration between operational technology (OT) and information technology (IT) environments - Git, Azure DevOps, and modern software delivery practices - Docker containers, Kubernetes, and orchestration fundamentals - APIs, databases, and software integration concepts - Generative AI, agentic AI, and AI-assisted engineering workflows - Field troubleshooting, deployment, operational support, and system validation - Mentorship from