Computing Undergraduate Student Intern: DevOps Internship Program - Summer 2027
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to extract content.
Given posting: Company Description (but we should not repeat job title as heading; we can have About the role? Actually company description maybe "About the role"? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have:
- Company Description: "Join us and make YOUR mark on the World! Lawrence Livermore National Laboratory (LLNL) has turned bold ideas into world-changing...". That's about the organization, could be "About the role"? Actually "About the role" is more about the job. But we can treat company description as "About the role"? Might be okay. Or we could skip if not specific? It's substantive.
- Job Description: includes details about internship dates, positions, what interns will do, etc. That could be Responsibilities.
- Qualifications: list of eligibility, GPA, etc.
- Skills: maybe not explicit but we can infer from responsibilities: Git, containerization, CI/CD, Kubernetes, etc. Could be Skills.
- Benefits: includes Holiday Pay, Sick leave accrual, Individual 401(k) contributions, etc. Also mention "Included in 2026 Best Places to Work by Glassdoor!" That's a benefit? Could be.
- Pay: Pay Range $23.26 - $31.62 Hourly for the 705.1 level $26.22 - $33.38 Hourly for the 714.0 level.
- Schedule: mentions hybrid schedule, flexibility to work from home one or more days per week. Also internship dates (multiple options). So schedule section.
We must not include boilerplate like EEO, scam warnings, etc. Remove those.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics: internship dates list, responsibilities bullet points, qualifications bullet points, etc.
We must not repeat job title as heading. Not include Job ID/requisition numbers.
We must not create sections with filler like "commensurate with experience". Not applicable.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
About the role
Company description paragraph.
Responsibilities
- ... each duty
Qualifications
- ... each qualification
Skills
but we could combine with responsibilities? The instruction says prefer few substantive sections over many thin ones. Could combine skills into responsibilities? But we have explicit skills list: "Learn and apply fundamentals of Git version control, containerization, CI/CD pipeline development, and Kubernetes-based application deployment." That's more like learning outcomes. Could be under Responsibilities or Skills. Since we have responsibilities already covering duties, we could add a Skills section for technical skills required: Git, containerization, CI/CD, Kubernetes, etc. But we might avoid duplication. Better: Have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. Skills maybe not needed separately. Let's extract details. Company Description paragraph: "Join us and make YOUR mark on the World! Lawrence Livermore National Laboratory (LLNL) has turned bold ideas into world-changing impact advancing science and technology to strengthen U.S. security and promote global stability. Our mission spans four critical national security areas nuclear deterrence, threat preparedness, energy security, and multi-domain defense empowering teams to take on the toughest challenges of today and tomorrow. With a culture built on innovation and operational excellence, LLNL is a place where your expertise can make a real impact." We keep that as. Responsibilities: from Job Description bullet-like sentences: - Selected interns will play a key role in supporting DevOps and platform engineering projects involving containerization, CI/CD automation, cloud-native application deployment, Kubernetes, Git version control, and software development. - Interns may contribute to projects involving large language model deployment and testing, web services, application containerization, infrastructure automation, and production software operations. - Depending on your assignment, this position may offer a hybrid schedule, blending in-person and virtual presence. You may have the flexibility to work from home one or more days per week. - You will Learn and apply fundamentals of Git version control, containerization, CI/CD pipeline development, and Kubernetes-based application deployment. - Contribute to real-world DevOps and platform engineering projects, including web services, infrastructure automation, and production software operations. - Assist with deploying and testing large language models and persistent data services. - Develop or enhance automation tools, deployment workflows, monitoring practices, and operational documentation. - Participate in code reviews, testing, documentation, and other software development lifecycle activities. - Participate in research planning and evaluation discussions. - Attend relevant seminars (at least one per week). - Present work through presentations and/or poster sessions. - Perform other duties as assigned. We need to preserve all substantive information; we can combine similar points but must not lose detail. Could list each as
or drop it. This is a posting code for another position; maybe we can drop it as it's not relevant to this role? It says if you are starting a graduate degree program in Fall 2027, you must apply for the Computing Scholar Graduate position (Posting code: REF8773S). That's a condition; we could keep as part of qualifications but maybe fold into a short p. However it's a specific condition; we could keep as
or drop it." This is a posting code, not a Job ID/requisition number, but it's similar metadata. Safer to drop the code but keep the condition: "If you are starting a graduate degree program in Fall 2027, you must apply for the Computing Scholar Graduate position." We'll keep that. - Proven ability to adapt and thrive in challenging situations, demonstrating resilience and problem-solving skills to achieve goals while overcoming setbacks. - Ability to apply basic computational science and/or mathematical principles to solve technical problems. - Demonstrated effective communication skills. - Ability to present and communicate concepts and ideas. - Experience working with personal computers and familiarity with Word, Excel and PowerPoint. - Ability to work in a team environment. - Age 18 or older at the start of the internship. - Must have GPA of 3.0 or higher. Benefits: from Additional Information: "Included in 2026 Best Places to Work by Glassdoor! Holiday Pay Sick leave accrual Individual 401(k) contributions Our values - visit https://www.llnl.gov/inclusion/our-values". Also maybe other benefits? That's it. We'll keep those as list. Pay: "Pay Range $23.26 - $31.62 Hourly for the 705.1 level $26.22 - $33.38 Hourly for the 714.0 level This position is under a step structure. Please note that the step placement is determined by your most recent completed academic year." We'll keep as
.
Schedule: Internship dates list: "May 17, 2027 - August 6, 2027May 24, 2027 - August 13, 2027June 14, 2027 - September 3, 2027June 21, 2027 - September 10, 2027". Note there is no spacing between dates; we need to preserve but maybe add commas? We must preserve ALL substantive information; we cannot invent or summarize away detail. The original text has no spaces between date ranges; we should keep exactly as given? It appears they concatenated without spaces. We'll keep as is but maybe we can add
between? That would be adding formatting not present; but we can keep as a single string; it's okay.
Also schedule includes hybrid schedule and flexibility to work from home one or more days per week. We'll include that.
We must not include boilerplate like EEO, scam warnings, etc. Remove those.
Now produce HTML.
We'll wrap each section in
and then content.
For lists, use - ...
.
For prose, use
. Let's craft. About the role:
Join us and make YOUR mark on the World! Lawrence Livermore National Laboratory (LLNL) has turned bold ideas into world-changing impact advancing science and technology to strengthen U.S. security and promote global stability. Our mission spans four critical national security areas nuclear deterrence, threat preparedness, energy security, and multi-domain defense empowering teams to take on the toughest challenges of today and tomorrow. With a culture built on innovation and operational excellence, LLNL is a place where your expertise can make a real impact.
Responsibilities: list each bullet. We'll need to ensure we don't lose any detail. Let's list: - Selected interns will play a key role in supporting DevOps and platform engineering projects involving containerization, CI/CD automation, cloud-native application deployment, Kubernetes, Git version control, and software development. - Interns may contribute to projects involving large language model deployment and testing, web services, application containerization, infrastructure automation, and production software operations. - Depending on your assignment, this position may offer a hybrid schedule, blending in-person and virtual presence. You may have the flexibility to work from home one or more days per week. - You will Learn and apply fundamentals of Git version control, containerization, CI/CD pipeline development, and Kubernetes-based application deployment. - Contribute to real-world DevOps and platform engineering projects, including web services, infrastructure automation, and production software operations. - Assist with deploying and testing large language models and persistent data services. - Develop or enhance automation tools, deployment workflows, monitoring practices, and operational documentation. - Participate in code reviews, testing, documentation, and other software development lifecycle activities. - Participate in research planning and evaluation discussions. - Attend relevant seminars (at least one per week). - Present work through presentations and/or poster sessions. - Perform other duties as assigned. Note: Some sentences start with capital letters; we keep. Qualifications list: - Must be eligible to access the Laboratory in compliance with Section 3112 of the National Defense Authorization Act (NDAA). - Must be a continuing college or university student in good standing at an accredited institution pursuing an undergraduate degree in Computer Science, Mathematics, Data Science, Machine Learning, Cybersecurity, or other related STEM fields. - If you are starting a graduate degree program in Fall 2027, you must apply for the Computing Scholar Graduate position. - Proven ability to