Electronics Engineering Technician (Kirkland, WA)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none.
We need to avoid duplication: The "What You'll Do" includes some repeated sentences: "Document findings in reports including detailed description of testing performed, resulting failure, and initial root cause investigation results." appears twice. We should keep only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. But we can deduplicate? It says remove duplicated lines. So we should remove duplicate lines.
Also "Key Details" includes metadata like Work Days and Hours, Location, Department, Reports To, Position Type, Work Eligibility. We can fold minor metadata into a short
or drop it. Probably we can include them in a short paragraph under About the role or maybe separate? But we should not create a heading for minor metadata. So we can incorporate them into About the role paragraph.
We need to decide sections:
- About the role: includes introductory paragraph about company and role, plus key details (location, full-time, etc.) maybe as a short paragraph.
- Responsibilities: list of duties from "What You'll Do". Use
- .
- Requirements: maybe "Required Qualifications". Use
- .
- Qualifications: maybe "Preferred Qualifications". Use
- .
- Skills: Could be derived from abilities like "Ability to work in teams...", "Ability to quickly come up to speed...", "Above average personal skills...", "Proficient in soldering...", "Fluent spoken and written English." Those are more like skills/abilities. Could be placed under Skills section as list.
- Benefits: list from Benefits and Perks.
- Pay: single line.
- Schedule: maybe from Work Days and Hours: Full time, onsite position.
We must not create sections with filler like "commensurate with experience". We have actual content.
We must not repeat job title as heading.
We must output only HTML fragment, no /, no markdown.
Let's craft.
First, About the role: combine the initial paragraph and key details.
Paragraph: "Heads Up Technologies is a leading manufacturer of high precision aviation products and innovative solutions for the aerospace industry. We are seeking an Electronics Technician to join our Production Engineering team. Working under limited direction and supervision, the Electronics Technician will be responsible for testing, troubleshooting, repairing, and modifying electronic products, components, equipment, and systems. This role involves working with both digital and analog electronics and applying principles and theories of electronics and electrical circuitry to support production and ensure product quality. The position is a full-time, onsite role located at Innovative Advantage in Kirkland, Washington, within the Production Engineering department, reporting to the Director of Hardware Engineering. Work eligibility requires being a U.S. Person."
That's a
.
Now Responsibilities: list from "What You'll Do". Let's extract bullet points:
- Perform acceptance testing using a variety of automated testing equipment and special test consoles on newly manufactured products and product returns.
- Perform manual testing and interpretation of results from standard and special purpose test equipment such as multi-meters, signal generators, power supplies, bridges, and oscilloscopes.
- Clearly and accurately document findings in reports including detailed description of testing performed, resulting failure, and initial root cause investigation results.
- Perform repairs at the component level.
- Build cables as needed.
- Build and/or modify test equipment and test racks.
- Interpret and work in accordance with drawings and schematics, functional and acceptance test procedures, failure reports, manuals and all other applicable engineering and production specifications.
We had duplicate documentation line; we keep one.
Now Requirements (Required Qualifications):
- At least 2 years’ experience in industries with a focus on high reliability, and compliance, such as aerospace, defense, or medical.
- AA degree in Electronic Technology preferred.
- Knowledge of circuit boards, electronic equipment, systems composed of highly integrated components such as FPGAs and microcontrollers, and software, including applications and programming.
- Working knowledge of both automated and manual test equipment for testing complex assemblies and/or final systems.
- Ability to setup manual test equipment for testing.
- Ability to work in teams and collaborate effectively with people in different functions.
- Ability to quickly come up to speed on unfamiliar hardware and tools.
- Above average personal skills for working directly with our manufacturers and customers.
- Proficient in soldering to meet the workmanship standard of IPC-A-610.
- Fluent spoken and written English.
Now Qualifications (Preferred Qualifications):
- Solder proficiency to J-STD-001
- Experience using Jira software
Now Skills: Could we separate abilities? Many of the above are abilities/skills. But we already have them in Requirements. Might be redundant to create Skills section. However we could create Skills section for things like "Ability to work in teams...", "Ability to quickly come up to speed...", "Above average personal skills...", "Proficient in soldering...", "Fluent spoken and written English." But those are already in Required Qualifications. To avoid duplication, maybe we don't create Skills section; we can keep them under Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Required Qualifications and Preferred Qualifications into a single "Requirements" section? But they differentiate required vs preferred. Could still have two subsections? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications sections.
Thus we keep Requirements (required) and Qualifications (preferred). Skills maybe not needed; we can omit Skills section if no distinct content beyond those. But we have some skill-like statements that are already in Required Qualifications. Could we move some to Skills? Might cause duplication. Better to omit Skills section.
Now Benefits: list from Benefits and Perks.
We need to extract list items:
- Medical plan options through Blue Cross Blue Shield (Company Paid)
- Dental and vision coverage
- Health Savings Account option with company contribution, if eligible
- Company paid Basic Life and AD&D insurance
- Company paid Long Term Disability coverage
- Voluntary Short Term Disability, Accident, and Critical Illness insurance
- Employee Assistance and Wellness Support resources
- Virtual care access
- Benefit Resource Center support
- Paid time off and paid holidays
- Benefit eligibility and coverage are based on employment status, plan documents, and company policy. Official plan documents govern all benefits.
The last two sentences are more prose; we can include as
after list or incorporate.
We'll make a
- for each bullet, and then a
for the eligibility note.
Now Pay:
The Pay Range For This Role Is 31.42 - 41.21 USD per hour (Kirkland, WA)
Schedule: Full time, onsite position.
(or include location? Already in About the role). We'll just state schedule.
Now ensure we don't repeat content. About the role already mentions full-time onsite location. Schedule section could be redundant but it's okay as it's specific schedule info. Could we combine? The instruction: Prefer a few substantive sections over many thin ones. Having both About the role and Schedule may be thin. But schedule is a distinct heading allowed. However we could incorporate schedule into About the role and not create Schedule section. Since we already have full-time onsite in About the role, we could omit Schedule section to avoid thin section. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having a section that repeats info, but we should prefer few substantive sections. So maybe we drop Schedule section.
Similarly, Benefits section is substantive.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if any other sections like Skills? We'll omit.
Now ensure we didn't miss any substantive info: The "Key Details" also had Department: Production Engineer, Reports To: Director of Hardware Engineering. We included those in About the role.
Now check for any other info: "Work Eligibility: Must be a U.S. Person" included.
Now ensure we didn't include boilerplate: none.
Now produce HTML.
We'll wrap each section in heading then content.
For lists, use - .
For prose, use
.
Let's craft.
About the role:
About the role
Heads Up Technologies is a leading manufacturer of high precision aviation products and innovative solutions for the aerospace industry. We are seeking an Electronics Technician to join our Production Engineering team. Working under limited direction and supervision, the Electronics Technician will be responsible for testing, troubleshooting, repairing, and modifying electronic products, components, equipment, and systems. This role involves working with both digital and analog electronics and applying principles and theories of electronics and electrical circuitry to support production and ensure product quality. The position is a full-time, onsite role located at Innovative Advantage in Kirkland, Washington, within the Production Engineering department, reporting to the Director of Hardware Engineering. Work eligibility requires being a U.S. Person.
Responsibilities:
Responsibilities
- Perform acceptance testing using a variety of automated testing equipment and special test consoles on newly manufactured products and product returns.
- Perform manual testing and interpretation of results from standard and special purpose test equipment such as multi-meters, signal generators, power supplies, bridges, and oscilloscopes.
- Clearly and accurately document findings in reports including detailed description of testing performed, resulting failure, and initial root cause investigation results.
- Perform repairs at the component level.
- Build cables as needed.
- Build and/or modify test equipment and test racks.
- Interpret and work in accordance with drawings and schematics, functional and acceptance test procedures, failure reports, manuals and all other applicable engineering and production specifications.
Requirements (Required Qualifications):
Requirements
- At least 2 years’ experience in industries with a focus on high reliability, and compliance, such as aerospace, defense, or medical.
- AA degree in
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO etc. There's none. We need to avoid duplication: The "What You'll Do" includes some repeated sentences: "Document findings in reports including detailed description of testing performed, resulting failure, and initial root cause investigation results." appears twice. We should keep only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. But we can deduplicate? It says remove duplicated lines. So we should remove duplicate lines. Also "Key Details" includes metadata like Work Days and Hours, Location, Department, Reports To, Position Type, Work Eligibility. We can fold minor metadata into a short
or drop it. Probably we can include them in a short paragraph under About the role or maybe separate? But we should not create a heading for minor metadata. So we can incorporate them into About the role paragraph. We need to decide sections: - About the role: includes introductory paragraph about company and role, plus key details (location, full-time, etc.) maybe as a short paragraph. - Responsibilities: list of duties from "What You'll Do". Use
- .
- Requirements: maybe "Required Qualifications". Use
- .
- Qualifications: maybe "Preferred Qualifications". Use
- .
- Skills: Could be derived from abilities like "Ability to work in teams...", "Ability to quickly come up to speed...", "Above average personal skills...", "Proficient in soldering...", "Fluent spoken and written English." Those are more like skills/abilities. Could be placed under Skills section as list.
- Benefits: list from Benefits and Perks.
- Pay: single line.
- Schedule: maybe from Work Days and Hours: Full time, onsite position.
We must not create sections with filler like "commensurate with experience". We have actual content.
We must not repeat job title as heading.
We must output only HTML fragment, no /, no markdown.
Let's craft.
First, About the role: combine the initial paragraph and key details.
Paragraph: "Heads Up Technologies is a leading manufacturer of high precision aviation products and innovative solutions for the aerospace industry. We are seeking an Electronics Technician to join our Production Engineering team. Working under limited direction and supervision, the Electronics Technician will be responsible for testing, troubleshooting, repairing, and modifying electronic products, components, equipment, and systems. This role involves working with both digital and analog electronics and applying principles and theories of electronics and electrical circuitry to support production and ensure product quality. The position is a full-time, onsite role located at Innovative Advantage in Kirkland, Washington, within the Production Engineering department, reporting to the Director of Hardware Engineering. Work eligibility requires being a U.S. Person."
That's a
. Now Responsibilities: list from "What You'll Do". Let's extract bullet points: - Perform acceptance testing using a variety of automated testing equipment and special test consoles on newly manufactured products and product returns. - Perform manual testing and interpretation of results from standard and special purpose test equipment such as multi-meters, signal generators, power supplies, bridges, and oscilloscopes. - Clearly and accurately document findings in reports including detailed description of testing performed, resulting failure, and initial root cause investigation results. - Perform repairs at the component level. - Build cables as needed. - Build and/or modify test equipment and test racks. - Interpret and work in accordance with drawings and schematics, functional and acceptance test procedures, failure reports, manuals and all other applicable engineering and production specifications. We had duplicate documentation line; we keep one. Now Requirements (Required Qualifications): - At least 2 years’ experience in industries with a focus on high reliability, and compliance, such as aerospace, defense, or medical. - AA degree in Electronic Technology preferred. - Knowledge of circuit boards, electronic equipment, systems composed of highly integrated components such as FPGAs and microcontrollers, and software, including applications and programming. - Working knowledge of both automated and manual test equipment for testing complex assemblies and/or final systems. - Ability to setup manual test equipment for testing. - Ability to work in teams and collaborate effectively with people in different functions. - Ability to quickly come up to speed on unfamiliar hardware and tools. - Above average personal skills for working directly with our manufacturers and customers. - Proficient in soldering to meet the workmanship standard of IPC-A-610. - Fluent spoken and written English. Now Qualifications (Preferred Qualifications): - Solder proficiency to J-STD-001 - Experience using Jira software Now Skills: Could we separate abilities? Many of the above are abilities/skills. But we already have them in Requirements. Might be redundant to create Skills section. However we could create Skills section for things like "Ability to work in teams...", "Ability to quickly come up to speed...", "Above average personal skills...", "Proficient in soldering...", "Fluent spoken and written English." But those are already in Required Qualifications. To avoid duplication, maybe we don't create Skills section; we can keep them under Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we can combine Required Qualifications and Preferred Qualifications into a single "Requirements" section? But they differentiate required vs preferred. Could still have two subsections? But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications sections. Thus we keep Requirements (required) and Qualifications (preferred). Skills maybe not needed; we can omit Skills section if no distinct content beyond those. But we have some skill-like statements that are already in Required Qualifications. Could we move some to Skills? Might cause duplication. Better to omit Skills section. Now Benefits: list from Benefits and Perks. We need to extract list items: - Medical plan options through Blue Cross Blue Shield (Company Paid) - Dental and vision coverage - Health Savings Account option with company contribution, if eligible - Company paid Basic Life and AD&D insurance - Company paid Long Term Disability coverage - Voluntary Short Term Disability, Accident, and Critical Illness insurance - Employee Assistance and Wellness Support resources - Virtual care access - Benefit Resource Center support - Paid time off and paid holidays - Benefit eligibility and coverage are based on employment status, plan documents, and company policy. Official plan documents govern all benefits. The last two sentences are more prose; we can include as
after list or incorporate. We'll make a
- for each bullet, and then a
for the eligibility note. Now Pay:
The Pay Range For This Role Is 31.42 - 41.21 USD per hour (Kirkland, WA)
Schedule:Full time, onsite position.
(or include location? Already in About the role). We'll just state schedule. Now ensure we don't repeat content. About the role already mentions full-time onsite location. Schedule section could be redundant but it's okay as it's specific schedule info. Could we combine? The instruction: Prefer a few substantive sections over many thin ones. Having both About the role and Schedule may be thin. But schedule is a distinct heading allowed. However we could incorporate schedule into About the role and not create Schedule section. Since we already have full-time onsite in About the role, we could omit Schedule section to avoid thin section. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid having a section that repeats info, but we should prefer few substantive sections. So maybe we drop Schedule section. Similarly, Benefits section is substantive. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if any other sections like Skills? We'll omit. Now ensure we didn't miss any substantive info: The "Key Details" also had Department: Production Engineer, Reports To: Director of Hardware Engineering. We included those in About the role. Now check for any other info: "Work Eligibility: Must be a U.S. Person" included. Now ensure we didn't include boilerplate: none. Now produce HTML. We'll wrap each section inheading then content. For lists, use
- .
For prose, use
. Let's craft. About the role:
About the role
Heads Up Technologies is a leading manufacturer of high precision aviation products and innovative solutions for the aerospace industry. We are seeking an Electronics Technician to join our Production Engineering team. Working under limited direction and supervision, the Electronics Technician will be responsible for testing, troubleshooting, repairing, and modifying electronic products, components, equipment, and systems. This role involves working with both digital and analog electronics and applying principles and theories of electronics and electrical circuitry to support production and ensure product quality. The position is a full-time, onsite role located at Innovative Advantage in Kirkland, Washington, within the Production Engineering department, reporting to the Director of Hardware Engineering. Work eligibility requires being a U.S. Person.
Responsibilities:Responsibilities
- Perform acceptance testing using a variety of automated testing equipment and special test consoles on newly manufactured products and product returns.
- Perform manual testing and interpretation of results from standard and special purpose test equipment such as multi-meters, signal generators, power supplies, bridges, and oscilloscopes.
- Clearly and accurately document findings in reports including detailed description of testing performed, resulting failure, and initial root cause investigation results.
- Perform repairs at the component level.
- Build cables as needed.
- Build and/or modify test equipment and test racks.
- Interpret and work in accordance with drawings and schematics, functional and acceptance test procedures, failure reports, manuals and all other applicable engineering and production specifications.
Requirements
- At least 2 years’ experience in industries with a focus on high reliability, and compliance, such as aerospace, defense, or medical.
- AA degree in
- .
For prose, use
- for each bullet, and then a
- .
- Skills: Could be derived from abilities like "Ability to work in teams...", "Ability to quickly come up to speed...", "Above average personal skills...", "Proficient in soldering...", "Fluent spoken and written English." Those are more like skills/abilities. Could be placed under Skills section as list.
- Benefits: list from Benefits and Perks.
- Pay: single line.
- Schedule: maybe from Work Days and Hours: Full time, onsite position.
We must not create sections with filler like "commensurate with experience". We have actual content.
We must not repeat job title as heading.
We must output only HTML fragment, no /, no markdown.
Let's craft.
First, About the role: combine the initial paragraph and key details.
Paragraph: "Heads Up Technologies is a leading manufacturer of high precision aviation products and innovative solutions for the aerospace industry. We are seeking an Electronics Technician to join our Production Engineering team. Working under limited direction and supervision, the Electronics Technician will be responsible for testing, troubleshooting, repairing, and modifying electronic products, components, equipment, and systems. This role involves working with both digital and analog electronics and applying principles and theories of electronics and electrical circuitry to support production and ensure product quality. The position is a full-time, onsite role located at Innovative Advantage in Kirkland, Washington, within the Production Engineering department, reporting to the Director of Hardware Engineering. Work eligibility requires being a U.S. Person."
That's a
- .
- Qualifications: maybe "Preferred Qualifications". Use