Electronics Technician 2

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. No Job ID. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. We need to parse the posting. Content: - Intro paragraph: "In a world of possibilities, pursue one with endless opportunities. Imagine Next! At Parsons, you can imagine a career where you thrive, work with exceptional people, and be yourself. Guided by our leadership vision of valuing people, embracing agility, and fostering growth, we cultivate an innovative culture that empowers you to achieve your full potential. Unleash your talent and redefine what’s possible." - Job Description: details about FAA contract, T5, etc. Then description of SCA – Electronics Technician role. - Responsibilities: list of duties (installation, modification, testing, troubleshooting, repair, preventive maintenance; perform installation, relocation, removal; troubleshoot and repair; read and work from schematics; assist in field installations; use and care for test equipment; document work activities; follow safety, security, quality practices). These are bullet-like sentences. - Required Skills: "What Required Skills You'll Bring" includes: high school diploma required; may require repetitive movement such as lifting up to 50 lbs., bending, and standing; basic Microsoft suite and Internet, and E-mail; must be able to meet customer security requirements; background check; must be able to travel up to 100% within the USA; five plus years of working knowledge of: basic analog and digital electronics; fundamentals of RF and communications equipment; use of standard electronic test equipment (DMMs, basic scopes, signal generators); ability to: read and interpret basic schematics, wiring diagrams, and technical documentation; follow written and verbal instructions and standard procedures; work safely in field, shop, and facility environment. - Security Clearance Requirement: None. - Then description of Federal Solutions team. - Benefits: "We value our employees and want our employees to take care of their overall wellbeing, which is why we offer best-in-class benefits such as medical, dental, vision, paid time off, 401(k), life insurance, flexible work schedules, and holidays to fit your busy lifestyle!" - No explicit Pay or Schedule info (though flexible work schedules mentioned under benefits). No pay amount. So we should not create Pay or Schedule sections unless posting actually states them. It mentions flexible work schedules as benefit, but not a schedule section. We could include Benefits section with that list. - Also we might include About the role (intro) as a section. - Responsibilities section. - Requirements/Qualifications/Skills: we need to decide which headings to use. The posting has "What Required Skills You'll Bring". Could map to Requirements or Skills. We have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should avoid thin sections. Could combine Requirements and Qualifications and Skills into one? But we need to follow instruction: use those headings for section headings. We can include multiple if content exists. We have content for About the role (intro). Responsibilities (duties). Requirements (high school diploma, physical, travel, background check, etc). Qualifications (maybe the five plus years experience, knowledge). Skills (ability to read schematics, use test equipment, follow procedures, work safely). Could also include Security Clearance Requirement None as part of Requirements. We need to preserve all substantive info; not invent or summarize away detail. Must not include filler like "commensurate with experience". We have no such. We must remove boilerplate: equal opportunity employer, fraudulent recruitment notice, etc. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

In a world of possibilities, pursue one with endless opportunities. Imagine Next! At Parsons, you can imagine a career where you thrive, work with exceptional people, and be yourself. Guided by our leadership vision of valuing people, embracing agility, and fostering growth, we cultivate an innovative culture that empowers you to achieve your full potential. Unleash your talent and redefine what’s possible.

Then maybe a paragraph about the contract? Could be part of About the role or Responsibilities? The job description includes contract details; maybe we include that in About the role as context. But we already used About the role for intro; we could add another paragraph after that about the contract. That's still about the role. So we can include multiple

under same heading. Thus:

About the role

In a world of possibilities, pursue one with endless opportunities. Imagine Next! At Parsons, you can imagine a career where you thrive, work with exceptional people, and be yourself. Guided by our leadership vision of valuing people, embracing agility, and fostering growth, we cultivate an innovative culture that empowers you to achieve your full potential. Unleash your talent and redefine what’s possible.

The Federal Aviation Administration (FAA) awarded the Technical Support Services Contract 5 (T5) to Parsons in April 2023. Parsons is the prime contractor. This $1.8+ billion contract has a 4-year base period with two 3-year options. The statement of work includes a variety of activities that support the FAA’s Capital Investment Plan (CIP) and certain reimbursable programs, the FAA NextGen Program, national security programs and aviation safety. Specifically, work includes site selection and engineering, construction, environmental and fire/life safety, equipment installation and testing, drafting, contract surveillance, and other technical services as required. Work is performed across the nation in each of the FAA’s nine regions as well as the Aeronautical Center in Oklahoma City, Oklahoma, and the Technical Center in Atlantic City, New Jersey and in several U.S. territories. An average staff of 500 with a peak staff over 650 supports this contract, in addition to those subcontractors who perform construction work.

Then Responsibilities:

Responsibilities

• Perform installation, modification, testing, troubleshooting, repair, and preventive maintenance on a variety of electronic systems and equipment that support the National Airspace System (NAS).
• Perform installation, relocation, and removal of electronic systems and equipment, which may include: Navigation aids (NAVAIDS); Communications systems (VHF/UHF, data/voice); Surveillance and support systems; Associated power, grounding, and control equipment.
• Troubleshoot and repair systems to the unit, board, or module level as assigned: Use standard test equipment (digital multimeters, signal generators, oscilloscopes, etc.); Follow step-by-step troubleshooting guides, fault isolation procedures, and technical manuals; Escalate complex or recurring issues to crew lead, FAA counterparts, and project management.
• Read and work from schematics, wiring diagrams, and interconnect drawings; Equipment manuals, technical orders, and job plans; FAA orders, work instructions, and site-specific procedures.
• Assist in field installations and site work under TSSC‑5: Support pre-installation checks and site preparation; Install racks, cabinets, and equipment per drawings and installation standards; Route, terminate, label, and test cables (coax, fiber, copper) under guidance; Assist with system power-up, basic alignment, and functional testing.
• Use and care for test and measurement equipment: Configure and operate standard electronic test instruments; Perform basic measurements, alignments, and performance checks; Maintain proper calibration and handle equipment in accordance with procedure.
• Document work activities in accordance with contract and FAA requirements: Complete maintenance logs, service tickets, and test forms; Record parts used, corrective actions taken, and test results; Provide redline/as-built information to senior technicians or engineers.
• Follow all safety, security, and quality practices: Comply with FAA and Parsons safety policies, OSHA regulations, and site Risk Management Plans; Adhere to physical and information security requirements at FAA facilities; Follow configuration control and quality assurance procedures; Collaborate effectively with senior technicians, engineers, project managers, and FAA representatives to support project objectives.

Then Requirements:

Requirements

• High school diploma is required.
• May require repetitive movement such as lifting up to 50 lbs., bending, and standing.
• Basic Microsoft suite and Internet, and E-mail proficiency.
• Must be able to meet customer security requirements.
• A background check by federal authorities will be performed.
• Must be able to travel up to 100% within the USA.
• Security clearance requirement: None.

Then Qualifications (experience/knowledge):

Qualifications

• Five plus years of working knowledge of basic analog and digital electronics.
• Five plus years of working knowledge of fundamentals of RF and communications equipment.
• Five plus years of working knowledge of use of standard electronic test equipment (DMMs, basic scopes, signal generators).

Then Skills:

Skills

• Ability to read and interpret basic schematics, wiring diagrams, and technical documentation.
• Ability to follow written and verbal instructions and standard procedures.
• Ability to work safely in field, shop, and facility environment.

Then Benefits:

Benefits

• Medical, dental, vision coverage.
• Paid time off.
• 401(k) plan.
• Life insurance.
• Flexible work schedules.
• Holidays.

We should not include Pay or Schedule sections because no explicit pay or schedule details beyond flexible work schedules (which is benefit). So omit. Check for any duplicated content: we have not repeated. We have preserved all substantive info: intro, contract details, responsibilities list, requirements, qualifications, skills, benefits, federal solutions team description? We omitted the paragraph about Federal Solutions team. That is substantive info about the team; we should include it maybe under About the role or a separate section like "About Parsons Federal Solutions". But we only have allowed headings list; we could add another

About the team

but not in list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning examples, not exhaustive list? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. But we could still include other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are the typical headings; but we could still use other headings if needed? It says "Use

for section headings (e.g. ...)" meaning we should use h3 for headings, and those are examples. It doesn't forbid other headings. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add a section for "Federal Solutions Team" if we want. But better to stick to given examples to be safe. We could incorporate that content into About the role or Benefits? It's about the team; maybe we can add a paragraph under About the role after contract details