Electrical Engineer- Tooling
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
We have location, experience, minimum education, compensation, "Who We Are", "Summary", responsibilities, required experience/capability, additional desired experience/capability, benefits summary, EEO boilerplate (to remove), security clearance requirement (should keep? It's substantive). Also mention "All applicants must possess or be qualified to obtain a U.S. DoD Personnel Security Clearance." That's substantive.
We need to avoid duplication.
We need to format with
headings.
Potential sections: About the Company (Who We Are), Role Summary (Summary), Responsibilities, Requirements (maybe combine required experience and qualifications), Additional Desired Experience (maybe Skills), Benefits, Security Clearance (maybe as a note), Pay (Compensation), Location? The instructions say we can include Pay and Schedule sections only if posting actually states them. Compensation is given: $130,000-170,000 based on experience. So we can include a Pay section.
Schedule? Not mentioned. So omit.
Location: given as "Location: Longmont, CO (onsite)". Should we include? It's minor metadata; we could fold into a short
maybe under a heading like "Job Details"? But instructions say do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a
at top before sections. Probably include a
with location and maybe experience/education? But we have separate sections for qualifications.
Better: Provide a short
for location and maybe note onsite. Then sections: About the Company, Role Summary, Responsibilities, Requirements, Additional Desired Experience (Skills), Benefits, Pay, Security Clearance.
But we need to avoid too many thin sections. Perhaps combine Requirements and Additional Desired Experience into one "Requirements" section with sublists? But instructions: use
- for any list of duties/requirements/benefits. Could have separate headings for Responsibilities, Requirements, Benefits, Pay. Additional Desired Experience could be under Requirements as "Preferred Qualifications". That's okay.
Thus sections: About the Company (Who We Are), Role Summary (Summary), Responsibilities, Requirements (including minimum education, experience, required capabilities, plus desired), Benefits, Pay, Security Clearance.
Check if any content duplicated: "Who We Are" and "Summary" are separate paragraphs; we keep both.
Now we need to strip EEO boilerplate and security clearance link? The security clearance requirement is substantive; we keep the sentence but maybe drop the link? The link is not essential but could be considered boilerplate? It's a reference for further info; but it's part of the posting. Might keep as a
with the sentence and maybe the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The link to DCSA is not exactly EEO; it's about security clearance. Might keep but could be considered legal? I'd keep the requirement sentence but maybe drop the link to keep clean. However we must preserve ALL substantive information; the link is substantive info about where to get more info. But it's a URL; could be considered reference. I'd keep it as part of the sentence.
Now craft HTML.
We'll start with a
for location and maybe note onsite.
Then
About the Company
... (Who We Are paragraph).
Then Role Summary
... (Summary paragraph).
Then Responsibilities
- ... each responsibility line.
We need to extract responsibilities bullet points from the posting. They are a paragraph with sentences separated by periods but also some lines start with capital letters and no bullet. We need to split into list items. Let's parse:
"Design and implement electrical test equipment, control systems, data acquisition solutions, optical alignment tooling, and mechanical fixtures that support the assembly, integration, testing, and production of high-energy laser weapon systems, with a focus on improving quality, repeatability, efficiency, and operator safety."
"Lead electrical design efforts across both quick-turn and long-duration tooling projects, including requirements development, schematic design, component selection, wiring architecture, documentation, prototyping, integration, troubleshooting, and deployment into production environments."
"Partner with Electrical, Software, Optical, Mechanical, Manufacturing, and Production teams to define tooling requirements, resolve technical challenges, and deliver robust, production-ready solutions that support program objectives and manufacturing schedules."
"Develop tooling and support equipment for low-volume, high-precision electro-optical assemblies, including electrical subsystem checkout, functional verification, data collection, troubleshooting, and production support activities throughout the manufacturing process."
"Ensure tooling designs comply with applicable electrical, safety, and environmental standards, including UL, CE, IEC, and RoHS requirements, while supporting documentation, risk assessments, and design reviews as needed."
That's 5 items.
Now Requirements: we have minimum education, experience, required capabilities list.
We need to capture:
- Bachelor's degree in Electrical Engineering or related technical discipline. Degrees in Mechanical Engineering, Optical Engineering, or other engineering disciplines may be considered with relevant tooling and electrical design experience.
- 5+ years of experience designing, developing, and implementing electrical test equipment, tooling, fixtures, automated test systems, or other manufacturing support equipment.
- Strong understanding of electrical systems, wiring harnesses, PCB design fundamentals, power distribution, component selection, and system integration principles.
- Experience developing, executing, or supporting electrical subsystem testing, including troubleshooting, verification, validation, data collection, and performance characterization activities.
- Proficiency with Altium, wiring diagram software, and SolidWorks for electrical design, documentation, and tooling development.
- Experience supporting low-volume, high-mix, high-precision products where accuracy, repeatability, and process control are critical to product performance and quality.
- Highly organized and detail-oriented, with the ability to manage multiple priorities, adapt to changing requirements, and collaborate effectively in a fast-paced, cross-functional environment.
- Exposure to fiber-optic systems, laser-based technologies, or optical alignment processes is preferred, including experience working with precision optical components and test equipment.
That's required capabilities.
Additional Desired Experience / Capability list:
- Experience designing, wiring, programming, and integrating automated test hardware and equipment, including the use of C-based programming languages or similar software tools for test and control applications.
- Experience with data acquisition systems, automated test data collection, database management, and manufacturing traceability systems.
- Familiarity with high-bandwidth fiber-optic communication protocols, high-speed data transfer systems, and high-voltage DC power distribution used in advanced electro-optical and defense applications.
- Knowledge of machine safety principles and safety system integration, including interlocks, emergency-stop systems, risk mitigation strategies, and safe operation of production equipment.
We could combine required and desired under Requirements heading, maybe split into "Required Qualifications" and "Preferred Qualifications" subheadings? But we only allowed for section headings; we could still use for each subsection? Might be too many sections. But we can keep one Requirements section and include both required and desired as lists, maybe with a note.
But instructions: Prefer a few substantive sections over many thin ones. So maybe combine into one Requirements section with two sublists: Required and Preferred. Could use ? Not allowed; only for section headings. Could use inside to denote. But better to keep separate headings? Might be okay to have multiple
sections: Responsibilities, Requirements, Benefits, Pay, Security Clearance, About the Company, Role Summary. That's 7 sections; not too many.
We could also have a separate "Preferred Qualifications" section. That's okay.
Thus sections: About the Company, Role Summary, Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Pay, Security Clearance.
Now Benefits: we have list:
- 4 weeks of Paid Time Off per year
- 11 paid Holidays
- Employee Stock Purchase Plan
- Tuition Assistance Program
- Health (ACA Gold Plan), Vision and Dental Care paid by employer 100% for Employee and 75% for Dependents
- Paid Family Leave, Short and Long Term Disability paid by employer 100%
- Competitive 401k with company match and immediate vesting
We need to output as - .
Pay: Compensation: $130,000-170,000 based on experience.
Security Clearance: "All applicants must possess or be qualified to obtain a U.S. DoD Personnel Security Clearance. Preference will be given to candidates with an existing U.S. DoD Personnel Security Clearance. Further information on requirements to obtain a security clearance is available at: https://www.dcsa.mil/mc/pv/mbi/gicp/. Please review this information before applying."
We should keep the sentences but maybe drop the "Please review this information before applying." as it's application instruction? It's not exactly instruction to apply but a note. Might be considered boilerplate? It's about the clearance; keep it.
Now we need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The EEO paragraph at end should be removed entirely.
Also remove "Equal Opportunity Employer..." etc.
Now ensure we preserve all substantive info.
Let's craft HTML.
Start with location paragraph:
Location: Longmont, CO (onsite)
Then About the Company: About the Company
... (Who We Are paragraph).
Who We Are paragraph: "nLIGHT-DEFENSE Systems, Inc. is one of the nation’s leading developers of Directed Energy systems, which is a top modernization priority of the Department of Defense. Our High Energy Laser (HEL) systems, Adaptive Optical (AO) systems, and Acquisition / Pointing / Tracking (APT) solutions are designed to overcome the most difficult challenges facing the deployment of high energy laser solutions to the United States military and our allies. Located in Longmont, Colorado, nLIGHT-DEFENSE Systems, Inc. is a vertically integrated business that leverages internal capabilities – from semiconductor device through target identification – to develop systems that are both high-performance and cost-effective. We continue to invest in capabilities, facilities and technology to bring leading edge HEL solutions to the warfighter. This is a great opportunity to work at a company that is on the leading edge of the HEL industry and provides a culture of excellence and commitment to delivering solutions to the warfighter and our country. Headquartered in Camas, Washington, nLIGHT is a publicly listed company (NAS
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have location, experience, minimum education, compensation, "Who We Are", "Summary", responsibilities, required experience/capability, additional desired experience/capability, benefits summary, EEO boilerplate (to remove), security clearance requirement (should keep? It's substantive). Also mention "All applicants must possess or be qualified to obtain a U.S. DoD Personnel Security Clearance." That's substantive. We need to avoid duplication. We need to format with
headings. Potential sections: About the Company (Who We Are), Role Summary (Summary), Responsibilities, Requirements (maybe combine required experience and qualifications), Additional Desired Experience (maybe Skills), Benefits, Security Clearance (maybe as a note), Pay (Compensation), Location? The instructions say we can include Pay and Schedule sections only if posting actually states them. Compensation is given: $130,000-170,000 based on experience. So we can include a Pay section. Schedule? Not mentioned. So omit. Location: given as "Location: Longmont, CO (onsite)". Should we include? It's minor metadata; we could fold into a short
maybe under a heading like "Job Details"? But instructions say do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a
at top before sections. Probably include a
with location and maybe experience/education? But we have separate sections for qualifications. Better: Provide a short
for location and maybe note onsite. Then sections: About the Company, Role Summary, Responsibilities, Requirements, Additional Desired Experience (Skills), Benefits, Pay, Security Clearance. But we need to avoid too many thin sections. Perhaps combine Requirements and Additional Desired Experience into one "Requirements" section with sublists? But instructions: use
- for any list of duties/requirements/benefits. Could have separate headings for Responsibilities, Requirements, Benefits, Pay. Additional Desired Experience could be under Requirements as "Preferred Qualifications". That's okay.
Thus sections: About the Company (Who We Are), Role Summary (Summary), Responsibilities, Requirements (including minimum education, experience, required capabilities, plus desired), Benefits, Pay, Security Clearance.
Check if any content duplicated: "Who We Are" and "Summary" are separate paragraphs; we keep both.
Now we need to strip EEO boilerplate and security clearance link? The security clearance requirement is substantive; we keep the sentence but maybe drop the link? The link is not essential but could be considered boilerplate? It's a reference for further info; but it's part of the posting. Might keep as a
with the sentence and maybe the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The link to DCSA is not exactly EEO; it's about security clearance. Might keep but could be considered legal? I'd keep the requirement sentence but maybe drop the link to keep clean. However we must preserve ALL substantive information; the link is substantive info about where to get more info. But it's a URL; could be considered reference. I'd keep it as part of the sentence. Now craft HTML. We'll start with a
for location and maybe note onsite. Then
About the Company
... (Who We Are paragraph).
ThenRole Summary
... (Summary paragraph).
ThenResponsibilities
- ... each responsibility line.
for section headings; we could still use
for each subsection? Might be too many sections. But we can keep one Requirements section and include both required and desired as lists, maybe with a note. But instructions: Prefer a few substantive sections over many thin ones. So maybe combine into one Requirements section with two sublists: Required and Preferred. Could use
? Not allowed; only
for section headings. Could use inside
to denote. But better to keep separate headings? Might be okay to have multiple
sections: Responsibilities, Requirements, Benefits, Pay, Security Clearance, About the Company, Role Summary. That's 7 sections; not too many. We could also have a separate "Preferred Qualifications" section. That's okay. Thus sections: About the Company, Role Summary, Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Pay, Security Clearance. Now Benefits: we have list: - 4 weeks of Paid Time Off per year - 11 paid Holidays - Employee Stock Purchase Plan - Tuition Assistance Program - Health (ACA Gold Plan), Vision and Dental Care paid by employer 100% for Employee and 75% for Dependents - Paid Family Leave, Short and Long Term Disability paid by employer 100% - Competitive 401k with company match and immediate vesting We need to output as
- .
Pay: Compensation: $130,000-170,000 based on experience.
Security Clearance: "All applicants must possess or be qualified to obtain a U.S. DoD Personnel Security Clearance. Preference will be given to candidates with an existing U.S. DoD Personnel Security Clearance. Further information on requirements to obtain a security clearance is available at: https://www.dcsa.mil/mc/pv/mbi/gicp/. Please review this information before applying."
We should keep the sentences but maybe drop the "Please review this information before applying." as it's application instruction? It's not exactly instruction to apply but a note. Might be considered boilerplate? It's about the clearance; keep it.
Now we need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The EEO paragraph at end should be removed entirely.
Also remove "Equal Opportunity Employer..." etc.
Now ensure we preserve all substantive info.
Let's craft HTML.
Start with location paragraph:
Location: Longmont, CO (onsite)
Then About the Company:About the Company
... (Who We Are paragraph).
Who We Are paragraph: "nLIGHT-DEFENSE Systems, Inc. is one of the nation’s leading developers of Directed Energy systems, which is a top modernization priority of the Department of Defense. Our High Energy Laser (HEL) systems, Adaptive Optical (AO) systems, and Acquisition / Pointing / Tracking (APT) solutions are designed to overcome the most difficult challenges facing the deployment of high energy laser solutions to the United States military and our allies. Located in Longmont, Colorado, nLIGHT-DEFENSE Systems, Inc. is a vertically integrated business that leverages internal capabilities – from semiconductor device through target identification – to develop systems that are both high-performance and cost-effective. We continue to invest in capabilities, facilities and technology to bring leading edge HEL solutions to the warfighter. This is a great opportunity to work at a company that is on the leading edge of the HEL industry and provides a culture of excellence and commitment to delivering solutions to the warfighter and our country. Headquartered in Camas, Washington, nLIGHT is a publicly listed company (NAS