Jobs · Engineering · Texas

Intern - Artificial Intelligence

Itron, Inc. · Austin, TX · 2 wk ago
Engineering$44.23/hrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description: "Itron is innovating...". We'll create sections: About the role (maybe a paragraph), Responsibilities (list), Required Skills & Experience (list), Preferred Skills & Experience (list), Travel (maybe not needed as not specific?), Physical Demands (maybe not needed?), Duration & Location (maybe include as paragraph), Pay (they gave hourly range: "hourly, state minimum up to $44.23/hr" – that's a pay range, we can include Pay section), Schedule (they gave part-time hours during academic year (~20-25 hrs), full-time 40 hours per week Summer 2027 – we can include Schedule). Also location: Liberty Lake, WA. We must not include boilerplate like EEO, accommodation, etc. Also not repeat job title. No Job ID. We must only include sections when posting has real specific content. So we will include: - About the role (maybe a paragraph summarizing the mission and role) - Responsibilities (list) - Required Skills & Experience (list) - Preferred Skills & Experience (list) - Pay (hourly range) - Schedule (part-time/full-time) - Duration & Location (maybe combine as a paragraph) We should not include Travel (they gave 1-10% but that's minor; maybe we can include but it's not required; but we can include if we want but it's okay to omit as not essential. The instruction: prefer a few substantive sections over many thin ones. Travel is thin; we can omit. Physical Demands: typical office job, no special requirements – that's filler; we can omit. Now we need to preserve all substantive information. Let's extract details. About the role: "Itron is innovating new ways for utilities and cities to manage energy and water. We create a more resourceful world to protect essential resources for today and tomorrow. Join us. Our Information Security team within Corporate IT is looking for an intern to support AI-enabled security engineering initiatives. This position provides the opportunity to gain hands-on experience applying artificial intelligence, automation, software development, and security engineering practices while completing your education." We can put that as a paragraph under About the role. Responsibilities: bullet list from "Duties & Responsibilities". Let's list each line: - Assist with developing, testing, and documenting AI-enabled security tools, workflows, and prototypes - Use scripting and APIs to automate security engineering tasks, data collection, enrichment, analysis, and reporting - Support the integration and evaluation of security technologies across cloud, identity, endpoint, network, and data environments - Analyze security data to identify patterns, anomalies, potential threats, and opportunities to improve controls - Help assess the security of AI solutions, including access controls, data protection, prompt and model risks, and responsible-use safeguards - Build and maintain technical documentation, test plans, code repositories, and repeatable engineering procedures - Collaborate with security engineers and internal stakeholders to define requirements, troubleshoot issues, demonstrate solutions, and deliver project outcomes Required Skills & Experience: list items: - Education: Currently enrolled in a degree program in Cybersecurity, Computer Science, Software Engineering, Data Science, Artificial Intelligence, or a related technical field - Foundational knowledge of cybersecurity concepts such as identity and access management, cloud security, endpoint security, networking, secure software development, or threat detection - Intermediate programming or scripting language skill, such as Python, PowerShell, JavaScript, or C# - Understanding of AI and machine learning concepts, large language models, or data analysis - Ability to troubleshoot technical problems, learn unfamiliar technologies, and take ownership through resolution - Ability to work independently and collaborate effectively while sharing knowledge as part of a team - Ability to manage time, prioritize tasks, and communicate technical information clearly in writing and conversation Preferred Skills & Experience: list items: - Academic, personal, or work projects involving generative AI, machine learning, security automation, or data engineering - Experience using APIs, Git-based development workflows, notebooks, or development environments - Knowledge of security capabilities within Microsoft Azure or Microsoft 365, including identity, endpoint, cloud, or security monitoring technologies - Exposure to cloud platforms, containers, Linux, infrastructure as code, CI/CD pipelines, or policy as code - Understanding of secure coding, threat modeling, vulnerability management, or common security frameworks - Experience working with structured or unstructured security data and creating useful analyses or visualizations Travel: 1 - 10% (maybe we can include but it's thin; we could omit.) Physical Demands: typical office job – we can omit. Duration & Location: "Start ASAP, part-time hours during the academic year (~20-25 hrs), full-time 40 hours per week Summer 2027. This is not a remote position. Preference for candidate to be in Liberty Lake, WA." We can put as paragraph under Duration & Location. Pay: "Liberty Lake, WA: hourly, state minimum up to $44.23/hr". So we can state Pay: hourly rate up to $44.23/hr (state minimum). We'll include as paragraph. Schedule: Already covered in Duration & Location; but we could separate Schedule section: part-time ~20-25 hrs during academic year, full-time 40 hrs/week Summer 2027. However we already have that in Duration & Location. To avoid duplication, we could combine Duration & Location and Schedule into one section, but instruction says use headings for sections like Schedule, Pay, Benefits. We can have Schedule section with the hours info, and Duration & Location maybe just location and start date. But we must not create filler. Let's see: we have start ASAP, part-time hours during academic year (~20-25 hrs), full-time 40 hours per week Summer 2027. This is not a remote position. Preference for candidate to be in Liberty Lake, WA. We could make two sections: Schedule (part-time/full-time) and Location (Liberty Lake, WA). But Location heading not in list; they only listed specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Location. So we should not create a Location heading; we can fold location into a paragraph under About the role or Schedule or Pay. Probably best to include location in About the role paragraph or maybe in a short paragraph under About the role. But we already have About the role paragraph; we can add location there. Schedule: we can give the hours info. Pay: we give hourly rate. Thus sections: About the role, Responsibilities, Required Skills & Experience (maybe heading "Required Skills & Experience" but they said use headings like Requirements, Qualifications, Skills. They said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "Required Skills & Experience" as a heading? Not exactly in list but similar to Skills. Could use "Skills". But we have both required and preferred. Could combine into Skills section with required and preferred sublists? But they said prefer a few substantive sections over many thin ones. Could have Skills section containing both required and preferred, maybe with subheadings? But we cannot add extra headings beyond h3? We could use

for Skills and then inside have

for required and

    for preferred? Might be messy. Better to follow their examples: they gave examples of headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "Requirements" for required skills, "Preferred Skills" maybe not in list but could be under Skills. But we could use "Skills" for both required and preferred, but we need to differentiate. Could do:

    Skills

    then

    Required:

      ... then

      Preferred:

        ... That seems okay. Thus sections: - About the role (h3) - Responsibilities (h3) - Skills (h3) with required and preferred lists - Pay (h3) - Schedule (h3) We must not include Benefits if not specified. Now ensure we preserve all substantive information: we have included all duties, required skills, preferred skills, pay, schedule, start ASAP, location preference, not remote. We omitted Travel and Physical Demands as they are thin. Now produce HTML fragment: only the HTML, no markdown. We'll write:

        About the role

        Itron is innovating new ways for utilities and cities to manage energy and water. We create a more resourceful world to protect essential resources for today and tomorrow. Join us. Our Information Security team within Corporate IT is looking for an intern to support AI-enabled security engineering initiatives. This position provides the opportunity to gain hands-on experience applying artificial intelligence, automation, software development, and security engineering practices while completing your education. Preference for candidates located in Liberty Lake, WA; this is not a remote position.

        Responsibilities

        • Assist with developing, testing, and documenting AI-enabled security tools, workflows, and prototypes
        • Use scripting and APIs to automate security engineering tasks, data collection, enrichment, analysis, and reporting
        • Support the integration and evaluation of security technologies across cloud, identity, endpoint, network, and data environments
        • Analyze security data to identify patterns, anomalies, potential threats, and opportunities to improve controls
        • Help assess the security of AI solutions, including access controls, data protection, prompt and model risks, and responsible-use safeguards
        • Build and maintain technical documentation, test plans, code repositories, and repeatable engineering procedures
        • Collaborate with security engineers and internal stakeholders to define requirements, troubleshoot issues, demonstrate solutions, and deliver project outcomes

        Skills

        Required:

        • Currently enrolled in a degree program in Cybersecurity, Computer Science, Software Engineering, Data Science, Artificial Intelligence, or a related technical field
        • Foundational knowledge of cybersecurity concepts such as identity and access management, cloud security, endpoint security, networking, secure software development, or threat detection
        • Intermediate programming or scripting language skill, such as Python, PowerShell, JavaScript, or C#
        • Understanding of AI and machine learning concepts, large language models, or data analysis
        • Ability to troubleshoot technical problems, learn unfamiliar technologies, and take ownership through resolution
        • Ability to work independently and collaborate effectively while sharing knowledge as part of a team
        • Ability to manage time, prioritize tasks, and communicate technical information clearly in writing and conversation

        Preferred:

        • Academic, personal, or work projects involving generative AI, machine learning, security automation, or data engineering
        • Experience using APIs, Git-based development workflows, notebooks, or development environments
        • Knowledge of security capabilities within Microsoft Azure or Microsoft 365, including identity, endpoint, cloud, or security monitoring technologies
        • Exposure to cloud platforms, containers, Linux, infrastructure as code, CI/CD pipelines, or policy as code
        • Understanding of secure coding, threat modeling, vulnerability management, or common security frameworks
        • Experience working with structured or unstructured security data and creating useful analyses or visualizations

        Pay

        Hourly rate: state minimum up to $44.23/hr (based on Liberty Lake, WA location).

        Schedule

        Part‑time during the academic year (~20‑25 hours per week); full‑time 40 hours per week Summer 2027. Start ASAP.

        Check that we didn't repeat job title. Good. We omitted any boilerplate. Ensure no extra

Similar jobs