Cleared Senior R&D Laboratory Support Technologist - Advanced Metal Processing, Onsite

We need to output HTML fragment with sections only if real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. Must include only sections with real content. We need to parse the posting. Key sections: - About the role: The description of what the job will be like: "At the cutting edge of prototype development..." etc. That's prose. - Responsibilities: The list of duties: "On any given day, you may be called on to:" then bullet list: Estimate time and cost..., Discuss component design..., Document work..., Team with others..., Communicate..., Work with machine tool vendors... That's a list. - Requirements: Possibly "Qualifications We Require" list. That's qualifications required. - Qualifications: Might be "Qualifications We Desire". Could be separate "Qualifications" section? The instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We need to decide. We have "Qualifications We Require" and "Qualifications We Desire". Could combine into Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections. Probably Requirements = mandatory qualifications; Qualifications = desired qualifications. We also have Skills: maybe list of skills from qualifications? Could embed within Qualifications. But we could create a Skills section if there is explicit skill list. The posting includes many skill-like items: "Proven experience in ordering materials and tooling", "Familiarity with Lean Six Sigma", etc. Those are qualifications. Could treat them as Skills. But we already have Requirements and Qualifications. Might be redundant. However instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one "Qualifications" section? But they gave both headings as examples; we can choose to include only those with real content. We have Pay: Salary Range $74,700 - $144,400. That's specific. So we should include Pay section. Benefits: The posting mentions benefits earlier: "Some of the main reasons we love our jobs: Challenging work... Extraordinary co-workers... Some of the best tools... Career advancement... Flexible work arrangements... Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance". Also "These benefits vary by job classification." That's benefits info. So we can include Benefits section. Schedule: The posting mentions flexible work arrangements: "Flexible work arrangements for many positions include 9/80 ... and 4/10 compressed workweeks, part-time work, and telecommuting". That's schedule info. So we can include Schedule section. We also have About Sandia intro but that's boilerplate? It's about the organization, not the role. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Sandia" paragraph is generic about the lab; could be considered boilerplate but it's also part of the posting describing the employer. Might be okay to keep as part of About the role? However "About the role" heading is for role description, not about Sandia. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have an "About the role" section that describes the role. The initial "About Sandia" is not about the role; maybe we can omit it as boilerplate? It's not required to preserve all substantive information; but it's about the organization, not the role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. However "About Sandia" is substantive but maybe considered boilerplate? It's not navigation/legal/EEO etc. It's describing the lab. Might be considered relevant to the job posting. But the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." This is not those categories. So we might keep it. However we need to decide where to put it. Could be part of "About the role" or maybe a separate "About Sandia" but not in allowed headings. Since only allowed headings are those listed, we should fit content under those headings. The "About Sandia" could be placed under "About the role" as context, but that might be mixing. Alternatively we could omit it as not directly about the role. The instruction says preserve ALL substantive information; but we could argue that the "About Sandia" is substantive but not required for the role description; still it's part of posting. However the instruction also says "Prefer a few substantive sections over many thin ones." Might be okay to include a brief paragraph under "About the role" that includes both Sandia description and role description. But the heading "About the role" suggests focus on role. Yet we can include a brief intro about Sandia as part of role context. Better: Keep "About the role" section with the paragraph describing the role (starting at "At the cutting edge..."). We can also include a separate "About Sandia" but not allowed heading; maybe we can incorporate into a

before headings? The instruction says output ONLY the HTML fragment; no /. It didn't forbid extra paragraphs outside headings. So we could have a

about Sandia then headings. That would preserve info. However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It didn't say we cannot have other elements. So we can have a leading

about Sandia. But to be safe, we can include a brief

about Sandia before the sections. Now we need to extract content. Let's list sections: About the role: The paragraph starting "At the cutting edge of prototype development and testing hardware fabrication, the Rapid Development Machine Shop team delivers precision machining solutions..." continues through "This position offers an excellent opportunity to gain hands-on experience..." That's the role description. We could also include the earlier sentence "We are seeking a motivated and detail-oriented Laboratory Support Technologist to join our Rapid Development Machine Shop team." That's part of role. Thus About the role paragraph(s) combine. Responsibilities: The bullet list after "On any given day, you may be called on to:" includes: - Estimate time and cost to fabricate a component - Discuss component design and manufacturability with customers - Document work in a database - Team with others to define process strategies including techniques, tooling, and fixture design - Communicate with staff, technologists, machinists, and management - Work with machine tool vendors, repair teams, and maintenance teams to keep equipment safe and operational We should output as

• each. Requirements: "Qualifications We Require" list: - High school diploma plus three years or more years of directly related experience or combination of education and relevant experience - Proven experience in ordering materials and tooling to support manufacturing operations - Familiarity with Lean Six Sigma principles and tools to drive continuous process improvement. - Experience storing, handling, and transporting classified materials in compliance with security protocols - Skilled in operating material handling equipment such as forklifts, pallet jacks, and lift gates - Strong communication skills with experience in coordinating with tooling and equipment vendors and maintenance technicians - Knowledge of preparing and organizing feedstock and raw materials for manufacturing processes - Proficient in working with classified computing systems and adhering information security requirements - Possess a current and active DOE Q-level security clearance We should output as
  • . Qualifications: "Qualifications We Desire" list: - Associates or Bachelor's degree in related STEM discipline - Experience working on or around machine tool equipment in a manufacturing or laboratory setting - Proficient in using hand tools, band saws, drilling, tapping, and installing threaded inserts - Knowledge of proper handling and disposal procedures for hazardous waste materials - Skilled in writing and updating operational documentation, including operating procedures and pressure safety packages - Experience maintaining and tracking equipment service intervals and usage records - Familiarity with working on and modifying CAD files to support manufacturing processes We could also include "Experience working on or around machine tool equipment..." etc. Skills: Could be extracted from qualifications but we already have Requirements and Qualifications. Might be redundant. However we could create a Skills section that lists skill-based items like "Strong communication skills", "Proficient in working with classified computing systems", etc. But we already have those in Requirements. To avoid thin sections, maybe we skip Skills. Benefits: The paragraph: "Some of the main reasons we love our jobs: Challenging work with amazing impact that contributes to security, peace, and freedom worldwideExtraordinary co-workersSome of the best tools, equipment, and research facilities in the worldCareer advancement and enrichment opportunitiesFlexible 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 home)Generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance and amenities aimed at creating a solid work/life balance* World-changing technologies. Life-changing careers. Learn more about Sandia at: http://www.sandia.gov These benefits vary by job classification." We need to extract benefits: Challenging work, extraordinary co-workers, best tools, career advancement, flexible work arrangements (but that's also schedule), generous vacation, strong medical and other benefits, competitive 401k, learning opportunities, relocation assistance, amenities for work/life balance. Also "World-changing technologies. Life-changing careers." Might be fluff. We should produce a Benefits section with list items. Schedule: The flexible work arrangements: "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 home)". That's schedule. Pay: Salary Range $74,700 - $144,400. Now we need to output HTML fragment. We'll start with a

    about Sandia? Might be optional. But we can include a brief

    summarizing Sandia description: "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." That's from the About Sandia paragraph. We'll keep that. Then

    About the role

    with paragraphs. Then

    Responsibilities

    with
    . Then

    Requirements

    with
    . Then

    Qualifications

    with
    . Then

    Benefits

    with
    . Then

    Schedule

    with

    (or

    ? It's a sentence). Could be

    . Then

    Pay

    with

    . We must not include duplicated lines, boilerplate like EEO, security clearance details beyond what's needed? The security clearance is part of Requirements (we included). The rest of security clearance details (pre-employment drug test, background review, etc.) is boilerplate legal; we should remove. Also remove "Posting Duration", "Security Clearance Position requires..." etc beyond the requirement. Also