You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
LLNL

Computing Undergraduate Student Intern: DevOps Internship Program - Summer 2027

  • Hybrid
  • 0-3 years

Salary

Not stated

Similar roles pay $85K - 105K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

Applications close January 15, 2027. Computing mentors have until February 5, 2027 to make their Summer selections.

Four internship windows are offered: May 17 to August 6, 2027; May 24 to August 13, 2027; June 14 to September 3, 2027; and June 21 to September 10, 2027.

This summer program is for undergraduates who want hands-on research experience that supports their studies.

Interns support DevOps and platform engineering work covering containers, CI/CD automation, cloud-native deployment, Kubernetes, Git and software development.

Projects may include deploying and testing large language models, web services, application containers, infrastructure automation and production software operations.

The company was included in Glassdoor's 2026 Best Places to Work list.

Responsibilities

  • Pick up the basics of Git, containers, CI/CD pipelines and Kubernetes deployments.
  • Work on live DevOps and platform projects such as web services, infrastructure automation and production operations.
  • Help deploy and test large language models and persistent data services.
  • Build or improve automation tools, deployment workflows, monitoring and operations documentation.
  • Take part in code reviews, testing, documentation and other stages of the software lifecycle.
  • Join research planning and evaluation discussions.
  • Attend seminars, at least one per week.
  • Share your work through presentations, poster sessions or both.
  • Take on other assigned duties.

Requirements

  • You must be eligible to access the site under Section 3112 of the National Defense Authorization Act (NDAA). Details are in the conditions.
  • You must be a continuing undergraduate in good standing at an accredited college or university, working toward a degree in Computer Science, Mathematics, Data Science, Machine Learning, Cybersecurity or another related STEM field.
  • If you start a graduate program in Fall 2027, apply for the Computing Scholar Graduate position instead (posting code REF8773S).
  • Show that you can handle hard situations, stay resilient and solve problems through setbacks.
  • Apply basic computational science or mathematical principles to technical problems.
  • Communicate clearly in writing and speech, and present your ideas.
  • Work with personal computers and be comfortable with Word, Excel and PowerPoint.
  • Work well in a team.
  • You must be 18 or older on the internship start date.
  • You must have a GPA of 3.0 or higher.

Conditions

Pay is $23.26 to $31.62 per hour at the 705.1 level, or $26.22 to $33.38 per hour at the 714.0 level.

Pay follows a step structure, and your step is set by your most recent completed academic year.

The role may be hybrid, mixing in-person and virtual work. Depending on your assignment, you may be able to work from home one or more days a week.

Security clearance is listed as a condition for this role.

The 2025 NDAA, Section 3112, generally bars citizens of China, Russia, Iran and North Korea without dual US citizenship or legal permanent residence from specific non-public areas of national security or nuclear weapons facilities. These restrictions apply to this role, and you must be eligible under Section 3112 to qualify.

External hires must pass a post-offer, pre-employment drug test, which includes testing for marijuana because federal law applies to the company as a federal contractor.

In Limited Areas, you may be required to work where personal and laboratory mobile devices are not allowed, including phones, tablets, fitness devices, wireless headphones and other Bluetooth or wireless devices. Medical devices that pair with a mobile device must follow the same rules. Sensitive Compartmented Information Facilities require separate approval. Hearing aids without wireless capability, or with wireless disabled, are allowed in Limited Areas, Secure Space and Transit/Buffer Space within buildings.

All applicant information is kept confidential under EEO guidelines.

Recruitment scams sometimes misuse the company's name. The company never makes an offer without a personal interview and never charges a fee. Current openings are listed on the Career Page under Find Your Job. If a posting or offer looks fraudulent, do not respond.

Benefits

  • Paid holidays.
  • Sick leave accrual.
  • Individual 401(k) contributions.

Where you’d work

Part of the week in the office

You can work from

  • United States

About the company

LLNL

Office in CA, United States

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 4 red flags

Still hiring?

13 checks

2 red flags

How crowded?

6 checks

2 red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details12 facts · Role, Location, Compensation, Employment
Tech stack
  • Kubernetes
  • CI/CD
Seniority
Intern
Type
Internship
Specialty
DevOps
Region
United States
Pay period
Annual
Show 6 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
DevOps
Seniority
Intern
Experience
0-3 years
Tech stack
  • Kubernetes
  • CI/CD

Location

Work model
Hybrid
Region
United States
Office
  • CA, United States
Remote from
  • United States

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Internship

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason