Intern, Technical High School Summer - Mechanical Design, Onsite
Sandia National Laboratories · Albuquerque, NM · 1 mo ago
EngineeringFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions, posting duration, etc.
We need to preserve all substantive information.
Let's parse the posting.
Title: Summer High School Intern (CAD Technologist). Not to repeat as heading.
Content sections:
- "What Your Job Will Be Like": description of duties: bullet list of tasks.
- "Due to the nature of the work, the selected applicant must be able to work onsite." (maybe part of responsibilities or a note)
- "Salary Range": description: competitive pay rates based on earned credit hours, classification, degree level; pay rate determined during hire process; link to Intern Pay Rate chart.
- "Qualifications We Require": list of minimum requirements.
- "Qualifications We Desire": list of desired qualifications.
- "About Our Team": description of Design Engineering Group.
- "About Sandia": description of Sandia National Labs, benefits, flexible work arrangements, etc.
- "Security Clearance": details about clearance not required, drug test, background review, etc. This is substantive but maybe considered boilerplate? It's security info; we need to decide if to include. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Security clearance might be considered legal/boilerplate? It's about eligibility; but it's specific to the job. Might be considered substantive. However, they said remove EEO/equal-opportunity/scam-warning boilerplate. Security clearance is not EEO; it's about eligibility. Might keep.
- "Eeo": EEO statement - remove.
- "NNSA Requirements For MedPEDs": maybe keep? It's specific but could be considered legal/boilerplate. Might be removed as it's not core job duties. The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. This is not EEO but maybe still legal. Safer to remove? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "Legal" includes security clearance? Might be considered legal. But they said "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should remove legal boilerplate. Security clearance is legal. So remove that section.
- "Job ID: 698908 Job Family: 91 Regular/Temporary Position: T Full/Part-Time Status: P": minor metadata, fold into short p or drop. We'll drop or include as short p.
- "Posting Duration": remove (application instructions).
- "Learn more about Sandia at: http://www.sandia.gov": maybe part of About Sandia; we can keep as link.
- "These benefits vary by job classification.": part of About Sandia benefits.
We need to decide sections: About the role (maybe "What Your Job Will Be Like" maps to About the role or Responsibilities). We have responsibilities list. We'll create a section
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions, posting duration, etc.
We need to preserve all substantive information.
Let's parse the posting.
Title: Summer High School Intern (CAD Technologist). Not to repeat as heading.
Content sections:
- "What Your Job Will Be Like": description of duties: bullet list of tasks.
- "Due to the nature of the work, the selected applicant must be able to work onsite." (maybe part of responsibilities or a note)
- "Salary Range": description: competitive pay rates based on earned credit hours, classification, degree level; pay rate determined during hire process; link to Intern Pay Rate chart.
- "Qualifications We Require": list of minimum requirements.
- "Qualifications We Desire": list of desired qualifications.
- "About Our Team": description of Design Engineering Group.
- "About Sandia": description of Sandia National Labs, benefits, flexible work arrangements, etc.
- "Security Clearance": details about clearance not required, drug test, background review, etc. This is substantive but maybe considered boilerplate? It's security info; we need to decide if to include. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Security clearance might be considered legal/boilerplate? It's about eligibility; but it's specific to the job. Might be considered substantive. However, they said remove EEO/equal-opportunity/scam-warning boilerplate. Security clearance is not EEO; it's about eligibility. Might keep.
- "Eeo": EEO statement - remove.
- "NNSA Requirements For MedPEDs": maybe keep? It's specific but could be considered legal/boilerplate. Might be removed as it's not core job duties. The instruction: remove EEO/equal-opportunity/scam-warning boilerplate. This is not EEO but maybe still legal. Safer to remove? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. "Legal" includes security clearance? Might be considered legal. But they said "remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". So we should remove legal boilerplate. Security clearance is legal. So remove that section.
- "Job ID: 698908 Job Family: 91 Regular/Temporary Position: T Full/Part-Time Status: P": minor metadata, fold into short p or drop. We'll drop or include as short p.
- "Posting Duration": remove (application instructions).
- "Learn more about Sandia at: http://www.sandia.gov": maybe part of About Sandia; we can keep as link.
- "These benefits vary by job classification.": part of About Sandia benefits.
We need to decide sections: About the role (maybe "What Your Job Will Be Like" maps to About the role or Responsibilities). We have responsibilities list. We'll create a section Responsibilities
with - for each duty.
We also have "About Our Team" could be About the role? Actually "About Our Team" is about the team; could be a separate section like About the Team but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map "About Our Team" to About the role? Or maybe we can omit if not matching. But we need to preserve substantive information. Could put under About the role (description of team). Or we could create a
About the role
and include both the job description and team description.
Qualifications: we have both required and desired. Could combine into Requirements (maybe required) and Qualifications (desired). Or we could have Requirements for minimum, Qualifications for desired. The allowed headings include Requirements and Qualifications. So we can put minimum requirements under Requirements
and desired under Qualifications
. Or vice versa. Usually Requirements are mandatory, Qualifications are desired. We'll do that.
Skills: we could list desired qualifications like organizational skills, interpersonal skills, initiative, communication, Microsoft Office. Those could go under Skills. But we already have Qualifications desired. Might be redundant. Better to put desired qualifications under Qualifications, and maybe Skills separate for technical skills like CAD software, GD&T, etc. However the posting includes "Classroom experience using a CAD software package (Creo, SolidWorks, AutoCAD, ...etc.)" as desired qualification. Also "Interest in pursuing a career in Mechanical Design". Those could be under Qualifications. Skills could be things like "Excellent organizational skills", "Excellent interpersonal skills", "Proven record of demonstrating initiative", "Strong oral and written communication skills", "Working knowledge of Microsoft Office Products". We'll split.
Pay: we have salary range description. We'll create Pay
with paragraph.
Benefits: we have description of benefits from About Sandia: flexible work arrangements, generous vacation, strong medical benefits, competitive 401k, learning opportunities, relocation assistance, amenities for work/life balance. Also mention "These benefits vary by job classification." We'll include Benefits section.
Schedule: we have mention of ability to work up to 40 hours per week during summer (under requirements). Also mention flexible work arrangements (9/80, 4/10) for many positions. Could be schedule. We'll create Schedule section with info about work hours: up to 40 hours per week summer, flexible work arrangements (9/80, 4/10) etc.
We must not include sections with filler like "commensurate with experience". We have actual content.
Now we need to output only HTML fragment, no /, no markdown.
We'll produce something like:
Responsibilities
- Learn or increase understanding of model and drawing creation using CAD software (Creo, SolidWorks)
... etc.
About the role
... description of team and Sandia? Actually About the role could include the team description and Sandia overview.
But we also have About Sandia separate. Could combine.
Better: About the role
includes description of what the job entails (maybe from "What Your Job Will Be Like") and team description. But we already used Responsibilities for duties. So About the role could be overview of the role and team.
Let's decide:
- Responsibilities: list of duties.
- About the role: overview of the role and team (Design Engineering Group description and Sandia description). Could be two paragraphs.
- Requirements: minimum requirements (attending local high school, GPA, age, work hours, citizenship).
- Qualifications: desired qualifications (CAD experience, interest in mechanical design, organizational skills, interpersonal skills, initiative, communication, Microsoft Office). Could also include "Classroom experience using CAD software".
- Skills: maybe separate technical skills? But we already have CAD experience under Qualifications. Could move CAD experience to Skills. Let's think: The allowed headings include Skills. We could put technical skills like CAD software, GD&T, etc. under Skills. And put soft skills under Qualifications. But the posting lumps them together under "Qualifications We Desire". However we can split.
Given the instruction to prefer a few substantive sections over many thin ones, maybe we combine Qualifications and Skills into one section Qualifications (including both). But we have both headings allowed; we could still use both if they have content. Let's see if we have enough content for each.
Skills: we could list "Working knowledge of Microsoft Office Products", "Excellent organizational skills", "Excellent interpersonal skills", "Proven record of demonstrating initiative", "Strong oral and written communication skills". Those are soft skills but could be considered skills. Qualifications could be "Classroom experience using a CAD software package (Creo, SolidWorks, AutoCAD, ...etc.)", "Interest in pursuing a career in Mechanical Design". That seems thin for Qualifications. Better to put all desired qualifications under Qualifications and maybe not use Skills.
But we need to follow instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's just examples; we can choose which to include. It says "include a section ONLY when the posting has real, specific content for it". So we can include Skills if we have specific content. We have specific content for skills (Microsoft Office, organizational, interpersonal, initiative, communication). So we can include Skills.
Qualifications: we have specific content for desired qualifications (CAD experience, interest in mechanical design). That's also specific. So we can include Qualifications.
Thus we will have both.
Now Requirements: minimum requirements.
Now Benefits: from About Sandia.
Pay: from Salary Range.
Schedule: from ability to work up to 40 hours per week during summer, plus flexible work arrangements (9/80, 4/10) mentioned under About Sandia.
Now About the role: we could include a brief overview of the role (maybe from "What Your Job Will Be Like" summary) and team description. But we already used Responsibilities for duties. About the role could be a short paragraph describing the role's purpose: Summer High School Intern with interest in CAD Technologist, working onsite, contributing to national security, etc. We'll extract from first paragraph: "We are seeking a Summer High School Intern with interest in pursuing a career as a Computer Aided Drafting (CAD) Technologist to join our team! On any given day, you may be called on to: ..." That's basically responsibilities. But we already listed responsibilities. So About the role could be a brief summary: "Summer High School Intern position supporting the Design Engineering Group, focusing on CAD modeling and drafting, GD&T, and product definition, contributing to national security projects." We'll craft from the posting.
We must not invent details; we can paraphrase but must preserve substance. We'll keep close to original.
Let's extract:
- "We are seeking a Summer High School Intern with interest in pursuing a career as a Computer Aided Drafting (CAD) Technologist to join our team!"
- "The Design Engineering Group consists of multiple mechanical design departments that provide design engineering services using CAD software such as PTC Creo, SolidWorks, and other 3D modeling tools. We partner with engineering teams across the lab to produce innovative design solutions based on high quality CAD models and drawings. We ensure fit, form, and function using Geometric Dimensioning and Tolerancing (GD&T), while ensuring manufacturability and maintainability of designs. We determine the physical characteristics of the product including geometric form, interface features, manufacturing specifications, processes, and assembly instructions. We communicate design options and recommended approaches to product development teams, stakeholders, and manufacturing partners. We apply technical judgment based upon engineering principles in the design and development of innovative products in support of our Nation's security programs. We provide a positive and inclusive work environment where staff can master new skills, deliver optimal value, and achieve their career goals."
- "About Sandia Sandia National Laboratories is the nation’s premier science and engineering lab for national security and technology innovation, with teams of specialists focused on cutting-edge work in a broad array of areas. Some of the main reasons we love our jobs: Challenging work with amazing impact that contributes to security, peace, and freedom worldwide; Extraordinary co-workers; Some of the best tools, equipment, and research facilities in the world; Career advancement and enrichment opportunities; Flexible work arrangements for many positions include 9/80 (work 80 hours every two weeks, with every other Friday off) and 4/10 (work 4 ten-hour days each week) compressed workweeks, part-time work, and telecommuting (a mix of onsite work and working from
About the role
and include both the job description and team description. Qualifications: we have both required and desired. Could combine into Requirements (maybe required) and Qualifications (desired). Or we could have Requirements for minimum, Qualifications for desired. The allowed headings include Requirements and Qualifications. So we can put minimum requirements underRequirements
and desired underQualifications
. Or vice versa. Usually Requirements are mandatory, Qualifications are desired. We'll do that. Skills: we could list desired qualifications like organizational skills, interpersonal skills, initiative, communication, Microsoft Office. Those could go under Skills. But we already have Qualifications desired. Might be redundant. Better to put desired qualifications under Qualifications, and maybe Skills separate for technical skills like CAD software, GD&T, etc. However the posting includes "Classroom experience using a CAD software package (Creo, SolidWorks, AutoCAD, ...etc.)" as desired qualification. Also "Interest in pursuing a career in Mechanical Design". Those could be under Qualifications. Skills could be things like "Excellent organizational skills", "Excellent interpersonal skills", "Proven record of demonstrating initiative", "Strong oral and written communication skills", "Working knowledge of Microsoft Office Products". We'll split. Pay: we have salary range description. We'll createPay
with paragraph. Benefits: we have description of benefits from About Sandia: flexible work arrangements, generous vacation, strong medical benefits, competitive 401k, learning opportunities, relocation assistance, amenities for work/life balance. Also mention "These benefits vary by job classification." We'll include Benefits section. Schedule: we have mention of ability to work up to 40 hours per week during summer (under requirements). Also mention flexible work arrangements (9/80, 4/10) for many positions. Could be schedule. We'll create Schedule section with info about work hours: up to 40 hours per week summer, flexible work arrangements (9/80, 4/10) etc. We must not include sections with filler like "commensurate with experience". We have actual content. Now we need to output only HTML fragment, no /, no markdown. We'll produce something like:Responsibilities
- Learn or increase understanding of model and drawing creation using CAD software (Creo, SolidWorks) ... etc.
About the role
... description of team and Sandia? Actually About the role could include the team description and Sandia overview.
But we also have About Sandia separate. Could combine. Better: