Intern, R&D Graduate Summer, North Carolina A&T Fall 2026 Career Week, Onsite
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info.
Let's parse the posting.
Content:
- "What Your Job Will Be Like": description of role: looking for graduate students, opportunity, tasks: Conduct independent research..., Design and implement..., Analyze..., Collaborate..., Prepare..., Students will also be expected to work full time onsite for the duration of their summer experience.
- "Salary Range At Sandia...": talk about competitive pay rates, based on earned credit hours, classification, degree level, pay rate determined during hire process, included in offer package, link to Intern Pay Rate chart.
- "Qualifications We Require": list: Must Attend the North Carolina A&T Fall 2026 Career Week Events; Earned bachelor's degree; Currently attending and enrolled full time in the spring term immediately preceding the internship (or scheduled to graduate in the spring) in an accredited science, engineering, or math graduate program; Minimum cumulative GPA of 3.0/4.0; Ability to work up to 40 hours per week during the summer; Ability to secure and maintain a U.S. security clearance which requires U.S. citizenship; Note about undergraduate intern if not started grad program.
- "Qualifications We Desire": list: Currently pursuing a degree in Mechanical Engineering, Electrical Engineering, Computer Engineering, Computer Science, Mathematics, Physics, Chemistry, Cybersecurity, Nuclear Engineering, Aerospace Engineering, or a closely related field; Strong analytical and problem-solving skills with a hands-on, technical approach; Proficiency in at least one programming language (e.g., Python, C++, MATLAB); Excellent communication skills and the ability to work effectively in a team environment; Passion for research and a strong desire to contribute to national security and scientific advancement.
- "Posting Duration": posting open for minimum three calendar days, etc. This is metadata; maybe we can include as short paragraph? Not a section heading unless we have specific content. Could be considered "About the posting" but not required. Probably we can drop it as minor metadata.
- "About Our Team": description of Sandia, START Intern Institute, etc.
- "About Sandia": description of Sandia, benefits list (flexible work arrangements, generous vacation, strong medical benefits, etc). This includes benefits info.
- "Security Clearance": details about pre-employment drug test, background review, DOE L-level clearance, etc. This is substantive.
- "Eeo": boilerplate, remove.
- "NNSA Requirements For MedPEDs": maybe keep? It's specific about MedPED compliance. Might be considered substantive but could be considered boilerplate? It's specific to MedPEDs; maybe keep as part of Security Clearance or separate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is not EEO but it's a requirement for MedPEDs; it's somewhat legal but specific. Might keep? However, we might consider it as part of Security Clearance or separate "Security Clearance" section. Since it's about MedPEDs, could be included under Security Clearance as additional note.
- "Job ID: 698842 Job Family: 91 Regular/Temporary Position: T Full/Part-Time Status: P": drop.
We need sections: maybe About the role (or About the role?), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for:
- About the role: could be the introductory paragraph "What Your Job Will Be Like". That's about role.
- Responsibilities: list of tasks (conduct independent research, design..., analyze..., collaborate..., prepare..., work full time onsite). That's responsibilities.
- Requirements: "Qualifications We Require" (must attend career week, bachelor's degree, enrollment, GPA, work hours, security clearance). Also maybe "Ability to work up to 40 hours per week during the summer" is a requirement.
- Qualifications: "Qualifications We Desire" (desired qualifications). Could be under Qualifications or Skills? The instruction says use headings like Qualifications, Skills. We could separate: Qualifications (desired) and Skills (maybe programming language proficiency, analytical skills, communication). But we can combine desired qualifications under Qualifications.
- Skills: maybe we can extract programming language proficiency, analytical/problem-solving, communication, teamwork. Could be separate.
- Benefits: from About Sandia: "Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance". Also flexible work arrangements (9/80, 4/10 compressed workweeks, part-time work, telecommuting). That's benefits.
- Pay: Salary Range section.
- Schedule: maybe mention "work full time onsite for the duration of their summer experience" and "Ability to work up to 40 hours per week during the summer". That's schedule info. Could be under Schedule.
We must not create sections with filler like "commensurate with experience". We have actual content.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
We are looking for talented graduate students pursuing advanced degrees in Science, Engineering, and Mathematics fields to join our team. This is an exciting opportunity to engage in impactful educational workforce development initiatives. As part of our team, you will have the chance to participate in advanced research projects, collaborate with and learn from leading experts, and contribute to groundbreaking solutions that have significant implications for national security and scientific progress.
Responsibilities
- Conduct independent research under the guidance of experienced mentors.
- Design and implement experiments, simulations, or computational models.
- Analyze complex data sets and interpret results to draw meaningful conclusions.
- Collaborate with interdisciplinary teams to develop innovative approaches to research challenges.
- Prepare technical reports, presentations, and publications to communicate research findings.
- Work full time onsite for the duration of the summer experience.
Requirements
- Must attend the North Carolina A&T Fall 2026 Career Week Events.
- Earned bachelor's degree.
- Currently attending and enrolled full time in the spring term immediately preceding the internship (or scheduled to graduate in the spring) in an accredited science, engineering, or math graduate program.
- Minimum cumulative GPA of 3.0/4.0.
- Ability to work up to 40 hours per week during the summer.
- Ability to secure and maintain a U.S. security clearance which requires U.S. citizenship.
Qualifications (Desired)
- Currently pursuing a degree in Mechanical Engineering, Electrical Engineering, Computer Engineering, Computer Science, Mathematics, Physics, Chemistry, Cybersecurity, Nuclear Engineering, Aerospace Engineering, or a closely related field.
- Strong analytical and problem-solving skills with a hands‑on, technical approach.
- Proficiency in at least one programming language (e.g., Python, C++, MATLAB).
- Excellent communication skills and the ability to work effectively in a team environment.
- Passion for research and a strong desire to contribute to national security and scientific advancement.
Skills
Proficiency in at least one programming language (e.g., Python, C++, MATLAB); strong analytical and problem‑solving abilities; excellent communication and teamwork skills.
But we already listed programming language etc in Qualifications; maybe we can avoid duplication. Better to keep Qualifications as desired qualifications and Skills separate maybe not needed. Could combine Qualifications and Skills into one section "Qualifications and Skills". But instruction says we can use those headings; we can decide to have Qualifications (desired) and Skills (maybe programming language). However duplication is okay if we keep distinct. But we should avoid repeating same content. Let's think: Qualifications We Desire includes degree field, analytical skills, programming language, communication, passion. That's basically qualifications and skills. So we could have a single section "Qualifications" covering those. Then we could have a separate "Skills" maybe not needed. But we could keep Skills as a short summary of technical skills (programming language). However that duplicates. Better to have: - About the role - Responsibilities - Requirements - Qualifications (desired) - Benefits - Pay - Schedule We can omit Skills separate. Now Benefits: include flexible work arrangements, generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance, amenities for work/life balance. Pay: talk about competitive pay rates based on earned credit hours, classification, degree level, pay rate determined during hire process, included in offer package, link to Intern Pay Rate chart. Schedule: mention full time onsite for duration of summer experience, ability to work up to 40 hours per week. We also have "Posting Duration" maybe we can drop as minor metadata. Now ensure we preserve all substantive info: we must not lose any details like "Must Attend the North Carolina A&T Fall 2026 Career Week Events". Keep that. Also note about "If you have not yet started your graduate program, please apply to an undergraduate intern position." That's a note under Requirements; we should keep it maybe as a note. Also note about "Students will also be expected to work full time onsite for the duration of their summer experience." Already in responsibilities. Also note about "Ability to work up to 40 hours per week during the summer." Already in requirements. Also note about "Your pay rate will be determined during the hire process and included in your offer package." Keep. Also note about "You can view the Intern Pay Rate chart here (link)". Keep as link. Also note about "Posting Duration This posting will be open for application submissions for a minimum of three (3) calendar days, including the 'posting date'. Sandia reserves the right to extend the posting date at any time." This is metadata; we could drop as per instruction to remove boilerplate? It's not exactly boilerplate but it's about posting duration; maybe we can drop as minor metadata. The instruction says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So we could fold posting duration into a short p maybe under a generic "About the posting" but we don't have a heading for that. Safer to drop it. Also "About Our Team" and "About Sandia" we used for benefits and mission. We need to preserve substantive info about mission? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the description of Sandia's mission, START Intern Institute, etc. That's substantive. Where to put? Could be under "About the team" heading? But we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we can also add other headings if they have real content? The instruction says "Use