Electronics Engineer
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.
We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings.
We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate.
We need to output only HTML fragment.
Let's craft sections:
- About the role: could be the introductory paragraph describing the role and mission. Use prose.
- Responsibilities: list of job duties.
- Requirements: basic qualifications.
- Qualifications: desired qualifications.
- Skills: maybe combine some skills like proficiency with Microsoft Office, AutoCAD, communication skills etc. But we already have those in qualifications. Could create Skills section for technical skills: Microsoft Office, AutoCAD, etc. But we need to avoid thin sections. Perhaps we can merge skills into Requirements or Qualifications. However the instruction says use sections only when posting has real specific content. We have specific content for skills: "Proficiency with Microsoft Office applications. Experience using AutoCAD or similar CAD software." Also communication skills etc. Could create a Skills section.
- Benefits: list of benefits.
- Pay: pay range.
We should not include Schedule.
Let's extract content precisely.
About the role: combine the paragraph after "We Want You!" up to before "Job Duties". That includes: "The National Airspace System Integration Support (NISC) program at Leidos is seeking an Electronics Engineer to support the Federal Aviation Administration (FAA) Central Service Area – Engineering Services Group located in Fort Worth, Texas. The ideal candidate will support the daily planning, engineering, and implementation activities associated with the FAA's Brand-New Air Traffic Control System (BNATCS) modernization initiative. This position supports the deployment of next-generation air traffic control infrastructure through site assessments, facility engineering, project coordination, and installation oversight."
Also maybe include the earlier fluff about Leidos being ethical etc? That's more about company, not role. Could be part of About the role? Might be considered boilerplate? It's about Leidos values. Might be okay but could be considered generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ethical company statement is not necessarily boilerplate but could be considered fluff. However it's substantive about company values. Might keep? But we prefer few substantive sections. Could include in About the role as part of company culture. But we might keep it brief.
Better to keep About the role as the description of the role and its purpose.
Responsibilities: list each duty from "Job Duties May Include but not limited to:" bullet points.
Let's extract them:
- Conduct site surveys at FAA facilities to identify infrastructure requirements supporting BNATCS implementation.
- Develop detailed site preparation scopes of work based on field surveys, facility data, and engineering requirements.
- Develop cost estimates for site preparation and infrastructure improvements.
- Review contractor site preparation proposals for technical accuracy, completeness, and compliance with project requirements.
- Coordinate with FAA Service Centers (SSC), Technical Services (TSC), Air Traffic (AT), and other stakeholders to implement risk mitigations supporting BNATCS projects.
- Coordinate and schedule site preparation, installation, and commissioning activities with FAA personnel, contractors, and project stakeholders.
- Generate periodic project status reports and communicate progress to project leadership.
- Maintain Corporate Work Plan (CWP) data and project documentation.
- Update facility drawings and redline documentation for drafting and as-built records.
We need to put each as
- .
Requirements: basic qualifications paragraph. Could break into list? It's prose with multiple items: Bachelor's degree in Electronics Engineering. Two (2) years of relevant experience is preferred; however, candidates with less experience may be considered based on their education, technical aptitude, internships, and other relevant experience. Ability to travel 25–50%. Ability to obtain an FAA Public Trust Suitability determination. (To be eligible, applicants must be U.S. Citizens or Green Card holders who have resided in the United States for the previous three years.) Proficiency with Microsoft Office applications. Experience using AutoCAD or similar CAD software.
We could make a list for clarity. But the instruction says use
- for any list of duties/requirements/benefits. So we should convert requirements to list.
Thus:
- Bachelor's degree in Electronics Engineering.
- Two (2) years of relevant experience is preferred; however, candidates with less experience may be considered based on their education, technical aptitude, internships, and other relevant experience.
- Ability to travel 25–50%.
- Ability to obtain an FAA Public Trust Suitability determination (U.S. Citizens or Green Card holders who have resided in the United States for the previous three years).
- Proficiency with Microsoft Office applications.
- Experience using AutoCAD or similar CAD software.
Qualifications: desired qualifications list:
- Strong written and verbal communication skills with the ability to coordinate among government, contractor, and technical stakeholders.
- Demonstrates professionalism, strong interpersonal and communication skills, and the ability to collaborate effectively with multidisciplinary teams and FAA stakeholders.
- Shows initiative, adaptability, and a willingness to learn in a fast-paced technical environment.
- Demonstrates sound judgment, accountability, and the ability to receive and incorporate feedback while continuing to develop professionally.
Skills: maybe we could separate technical skills: Proficiency with Microsoft Office applications, Experience using AutoCAD or similar CAD software. But those are already in Requirements. Could move them to Skills. However we need to avoid duplication. The instruction says preserve all substantive information; we can place them in either section but not duplicate. Let's decide: Keep Requirements as education/experience/travel/clearance. Put technical proficiencies in Skills. Also communication skills could be in Skills but we already have them in Qualifications. Might be okay to have overlapping but better to avoid duplication. Let's assign:
Requirements: education, experience, travel, clearance.
Skills: Microsoft Office, AutoCAD, communication skills (written/verbal), interpersonal, collaboration, initiative, adaptability, willingness to learn, sound judgment, accountability, feedback incorporation.
But that repeats many from Desired Qualifications. Perhaps better to keep Desired Qualifications as Qualifications section, and Skills as technical skills only. Let's do:
Qualifications: desired qualifications (soft skills, professional attributes).
Skills: technical skills (Microsoft Office, AutoCAD). Also maybe mention proficiency with Microsoft Office applications and Experience using AutoCAD or similar CAD software.
Thus we avoid duplication.
Benefits: list: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave, Retirement.
Pay: pay range: $69,550.00 - $125,725.00 (with note that it's guideline). We'll include the range and note.
We should not include the note about it being guideline? It's substantive. We'll include as prose.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Skills
- Proficiency with Microsoft Office applications.
- Experience using AutoCAD or similar CAD software.
Benefits
- Competitive compensation
- Health and Wellness programs
- Income Protection
- Paid Leave
- Retirement
Pay
The pay range for this position is $69,550.00 - $125,725.00. This range is a general guideline only and not a guarantee of compensation or salary; actual offers consider responsibilities
for prose. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate. We need to output only HTML fragment. Let's craft sections: - About the role: could be the introductory paragraph describing the role and mission. Use prose. - Responsibilities: list of job duties. - Requirements: basic qualifications. - Qualifications: desired qualifications. - Skills: maybe combine some skills like proficiency with Microsoft Office, AutoCAD, communication skills etc. But we already have those in qualifications. Could create Skills section for technical skills: Microsoft Office, AutoCAD, etc. But we need to avoid thin sections. Perhaps we can merge skills into Requirements or Qualifications. However the instruction says use sections only when posting has real specific content. We have specific content for skills: "Proficiency with Microsoft Office applications. Experience using AutoCAD or similar CAD software." Also communication skills etc. Could create a Skills section. - Benefits: list of benefits. - Pay: pay range. We should not include Schedule. Let's extract content precisely. About the role: combine the paragraph after "We Want You!" up to before "Job Duties". That includes: "The National Airspace System Integration Support (NISC) program at Leidos is seeking an Electronics Engineer to support the Federal Aviation Administration (FAA) Central Service Area – Engineering Services Group located in Fort Worth, Texas. The ideal candidate will support the daily planning, engineering, and implementation activities associated with the FAA's Brand-New Air Traffic Control System (BNATCS) modernization initiative. This position supports the deployment of next-generation air traffic control infrastructure through site assessments, facility engineering, project coordination, and installation oversight." Also maybe include the earlier fluff about Leidos being ethical etc? That's more about company, not role. Could be part of About the role? Might be considered boilerplate? It's about Leidos values. Might be okay but could be considered generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The ethical company statement is not necessarily boilerplate but could be considered fluff. However it's substantive about company values. Might keep? But we prefer few substantive sections. Could include in About the role as part of company culture. But we might keep it brief. Better to keep About the role as the description of the role and its purpose. Responsibilities: list each duty from "Job Duties May Include but not limited to:" bullet points. Let's extract them: - Conduct site surveys at FAA facilities to identify infrastructure requirements supporting BNATCS implementation. - Develop detailed site preparation scopes of work based on field surveys, facility data, and engineering requirements. - Develop cost estimates for site preparation and infrastructure improvements. - Review contractor site preparation proposals for technical accuracy, completeness, and compliance with project requirements. - Coordinate with FAA Service Centers (SSC), Technical Services (TSC), Air Traffic (AT), and other stakeholders to implement risk mitigations supporting BNATCS projects. - Coordinate and schedule site preparation, installation, and commissioning activities with FAA personnel, contractors, and project stakeholders. - Generate periodic project status reports and communicate progress to project leadership. - Maintain Corporate Work Plan (CWP) data and project documentation. - Update facility drawings and redline documentation for drafting and as-built records. We need to put each as
- for any list of duties/requirements/benefits. So we should convert requirements to list.
Thus:
- Bachelor's degree in Electronics Engineering.
- Two (2) years of relevant experience is preferred; however, candidates with less experience may be considered based on their education, technical aptitude, internships, and other relevant experience.
- Ability to travel 25–50%.
- Ability to obtain an FAA Public Trust Suitability determination (U.S. Citizens or Green Card holders who have resided in the United States for the previous three years).
- Proficiency with Microsoft Office applications.
- Experience using AutoCAD or similar CAD software.
Qualifications: desired qualifications list:
- Strong written and verbal communication skills with the ability to coordinate among government, contractor, and technical stakeholders.
- Demonstrates professionalism, strong interpersonal and communication skills, and the ability to collaborate effectively with multidisciplinary teams and FAA stakeholders.
- Shows initiative, adaptability, and a willingness to learn in a fast-paced technical environment.
- Demonstrates sound judgment, accountability, and the ability to receive and incorporate feedback while continuing to develop professionally.
Skills: maybe we could separate technical skills: Proficiency with Microsoft Office applications, Experience using AutoCAD or similar CAD software. But those are already in Requirements. Could move them to Skills. However we need to avoid duplication. The instruction says preserve all substantive information; we can place them in either section but not duplicate. Let's decide: Keep Requirements as education/experience/travel/clearance. Put technical proficiencies in Skills. Also communication skills could be in Skills but we already have them in Qualifications. Might be okay to have overlapping but better to avoid duplication. Let's assign:
Requirements: education, experience, travel, clearance.
Skills: Microsoft Office, AutoCAD, communication skills (written/verbal), interpersonal, collaboration, initiative, adaptability, willingness to learn, sound judgment, accountability, feedback incorporation.
But that repeats many from Desired Qualifications. Perhaps better to keep Desired Qualifications as Qualifications section, and Skills as technical skills only. Let's do:
Qualifications: desired qualifications (soft skills, professional attributes).
Skills: technical skills (Microsoft Office, AutoCAD). Also maybe mention proficiency with Microsoft Office applications and Experience using AutoCAD or similar CAD software.
Thus we avoid duplication.
Benefits: list: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave, Retirement.
Pay: pay range: $69,550.00 - $125,725.00 (with note that it's guideline). We'll include the range and note.
We should not include the note about it being guideline? It's substantive. We'll include as prose.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Skills
- Proficiency with Microsoft Office applications.
- Experience using AutoCAD or similar CAD software.
Benefits
- Competitive compensation
- Health and Wellness programs
- Income Protection
- Paid Leave
- Retirement
Pay
The pay range for this position is $69,550.00 - $125,725.00. This range is a general guideline only and not a guarantee of compensation or salary; actual offers consider responsibilities