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 need to decide which headings to use. We have:
- About the role (maybe "About the role") - we can put the introductory paragraph about the role.
- Responsibilities - list.
- Requirements - maybe combine Required Qualifications and Preferred Qualifications? Could have Requirements and Preferred Qualifications separate? The instruction list includes Requirements, Qualifications, Skills. We could use Requirements for required qualifications, and maybe Skills for preferred? But better to follow typical: Requirements (required), Preferred Qualifications (maybe under Requirements as well). But we can have a section "Requirements" for required, and another "Preferred Qualifications" if we want. However they said prefer few substantive sections over many thin ones. So maybe combine required and preferred into one "Requirements" section with sub-lists? But we need to use
- for any list. Could have two lists: one for Required, one for Preferred. Could still be under same heading with
indicating required and preferred.
Alternatively we could have headings: Responsibilities, Requirements, Pay, Benefits. That's four sections.
We also have "About Leidos" maybe as a section.
Let's decide to include: About the role, Responsibilities, Requirements, Pay, Benefits.
We must not repeat job title as heading.
Now extract content:
About the role: "Your Next Great Adventure Awaits! Leidos is seeking an Electronics Engineer to join the National Airspace System Integration Support Contract (NISC IV) Team. This position will support the Federal Aviation Administration (FAA) Communications Engineering Center in Anchorage, AK."
We could also include the earlier fluff about mission etc? That's generic but maybe part of About the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The mission statement is generic but still part of posting. However it's not specific to the role. Might be considered boilerplate? It's about Leidos values. Could be considered part of About Leidos. But we already have About Leidos section maybe. Let's include the mission/vision/values paragraph under About Leidos? Actually we have a separate About Leidos paragraph later. The earlier paragraph: "Looking for an opportunity to make an impact? At Leidos, we deliver innovative solutions through the efforts of our diverse and talented people who are dedicated to our customers’ success. We empower our teams, contribute to our communities, and operate sustainable. Everything we do is built on a commitment to do the right thing for our customers, our people, and our community. Our Mission, Vision, and Values guide the way we do business. If this sounds like the kind of environment where you can thrive, keep reading!" That's generic fluff but still part of posting. It's not navigation/legal. Could be considered part of About Leidos or About the role. I'd include it in About Leidos section maybe.
But we already have About Leidos paragraph later: "Leidos is an industry and technology leader serving government and commercial customers with smarter, more efficient digital and mission innovations. Headquartered in Reston, Virginia, with 47,000 global employees, Leidos reported annual revenues of approximately $16.7 billion for the fiscal year ended January 3, 2025. For more information, visit www.Leidos.com."
We could combine both into About Leidos.
Thus About Leidos section: include both paragraphs.
Now Responsibilities: list items:
- Provide electronics engineering support for various LIFT related electronics projects and other NAS modernization projects throughout the FAA Western Service Area (WSA).
- Provide engineering system design packages for installation including communications equipment, radar automation equipment, control and monitoring equipment, and weather communication equipment.
- Prepare transition plans, testing plans, and training plans, and coordinate the implementation of transition plan elements with all affected stakeholders.
- Assist in preparing Draft project scope agreements and project schedules.
- Analyze project business and feasibility components from an engineering perspective and provide recommendations.
- Prepare engineering risk assessments, and provide recommendations and proposals of actions or improvements to mitigate potential risks resulting from site, facility, and project/program changes.
Also earlier: "The Electronics Engineers will provide electronics engineering support to the FAA Anchorage Communications Engineering Center with project engineering, management and planning for Legacy Infrastructure Future Technologies (LIFT) program related projects such as NEXCOM Radios, Air-to-Ground Protocol Converter and Airport Cable Loop, and other National Airspace System (NAS) modernization projects." That's also a responsibility. Could be included as first bullet.
Now Requirements (required qualifications):
- Electrical and/or Electronic Engineering degree and 4+ years of prior relevant experience OR Master's with 2+ years of prior relevant experience.
- Additional years of relevant experience may be accepted / considered in lieu of degree.
- Systems engineering experience integrating electronics components/systems together.
- 4+ years’ work experience in electrical and/or electronic engineering.
- Ability to obtain a Public Trust Security Clearance Suitability (To be eligible for Public Trust Security Clearance, one must be either a U.S. Citizen OR a U.S. Permanent Resident/Green Card holder who has resided in the U.S.A for the past 3 years of the past 5 years consecutively with no breaks).
We could combine some duplicates: "Electrical and/or Electronic Engineering degree and 4+ years of prior relevant experience OR Master's with 2+ years of prior relevant experience." and "Additional years of relevant experience may be accepted / considered in lieu of degree." and "4+ years’ work experience in electrical and/or electronic engineering." There's overlap. We'll keep as listed.
Preferred Qualifications:
- Familiarity with FAA and the National Airspace System (NAS).
Pay:
- Program budget salary for this role could fall anywhere between $105,000 to $125,000 with a slight wiggle room (no guarantees) based on relevant experience and assessment.
- Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary: $87,100.00 - $157,450.00.
We could present as two bullet points.
Benefits:
- Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement.
- More details are available at www.leidos.com/careers/pay-benefits.
We could list as bullet.
Now produce HTML.
We need to wrap each section in
heading then content.
For lists, use - .
For prose, use
.
We must not include any extra text outside HTML fragment.
Let's craft.
First section:
About Leidos
then paragraphs.
Paragraph 1: "Looking for an opportunity to make an impact? At Leidos, we deliver innovative solutions through the efforts of our diverse and talented people who are dedicated to our customers’ success. We empower our teams, contribute to our communities, and operate sustainable. Everything we do is built on a commitment to do the right thing for our customers, our people, and our community. Our Mission, Vision, and Values guide the way we do business. If this sounds like the kind of environment where you can thrive, keep reading!"
Paragraph 2: "Leidos is an industry and technology leader serving government and commercial customers with smarter, more efficient digital and mission innovations. Headquartered in Reston, Virginia, with 47,000 global employees, Leidos reported annual revenues of approximately $16.7 billion for the fiscal year ended January 3, 2025. For more information, visit www.Leidos.com."
Second section: About the role
then paragraph: "Your Next Great Adventure Awaits! Leidos is seeking an Electronics Engineer to join the National Airspace System Integration Support Contract (NISC IV) Team. This position will support the Federal Aviation Administration (FAA) Communications Engineering Center in Anchorage, AK."
Third: Responsibilities
then with bullets.
Fourth: Requirements
then maybe split into Required and Preferred? Could do two headings inside? But we cannot add extra headings besides
. Could use
to label Required Qualifications and Preferred Qualifications inside the section. That's allowed.
Thus inside Requirements section:
Required Qualifications:
then list. Then Preferred Qualifications:
then list.
But we must not invent headings; using with bold is okay.
Fifth:
Pay
then list.
Sixth:
for prose. We need to decide which headings to use. We have: - About the role (maybe "About the role") - we can put the introductory paragraph about the role. - Responsibilities - list. - Requirements - maybe combine Required Qualifications and Preferred Qualifications? Could have Requirements and Preferred Qualifications separate? The instruction list includes Requirements, Qualifications, Skills. We could use Requirements for required qualifications, and maybe Skills for preferred? But better to follow typical: Requirements (required), Preferred Qualifications (maybe under Requirements as well). But we can have a section "Requirements" for required, and another "Preferred Qualifications" if we want. However they said prefer few substantive sections over many thin ones. So maybe combine required and preferred into one "Requirements" section with sub-lists? But we need to use
- for any list. Could have two lists: one for Required, one for Preferred. Could still be under same heading with
indicating required and preferred. Alternatively we could have headings: Responsibilities, Requirements, Pay, Benefits. That's four sections. We also have "About Leidos" maybe as a section. Let's decide to include: About the role, Responsibilities, Requirements, Pay, Benefits. We must not repeat job title as heading. Now extract content: About the role: "Your Next Great Adventure Awaits! Leidos is seeking an Electronics Engineer to join the National Airspace System Integration Support Contract (NISC IV) Team. This position will support the Federal Aviation Administration (FAA) Communications Engineering Center in Anchorage, AK." We could also include the earlier fluff about mission etc? That's generic but maybe part of About the role? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The mission statement is generic but still part of posting. However it's not specific to the role. Might be considered boilerplate? It's about Leidos values. Could be considered part of About Leidos. But we already have About Leidos section maybe. Let's include the mission/vision/values paragraph under About Leidos? Actually we have a separate About Leidos paragraph later. The earlier paragraph: "Looking for an opportunity to make an impact? At Leidos, we deliver innovative solutions through the efforts of our diverse and talented people who are dedicated to our customers’ success. We empower our teams, contribute to our communities, and operate sustainable. Everything we do is built on a commitment to do the right thing for our customers, our people, and our community. Our Mission, Vision, and Values guide the way we do business. If this sounds like the kind of environment where you can thrive, keep reading!" That's generic fluff but still part of posting. It's not navigation/legal. Could be considered part of About Leidos or About the role. I'd include it in About Leidos section maybe. But we already have About Leidos paragraph later: "Leidos is an industry and technology leader serving government and commercial customers with smarter, more efficient digital and mission innovations. Headquartered in Reston, Virginia, with 47,000 global employees, Leidos reported annual revenues of approximately $16.7 billion for the fiscal year ended January 3, 2025. For more information, visit www.Leidos.com." We could combine both into About Leidos. Thus About Leidos section: include both paragraphs. Now Responsibilities: list items: - Provide electronics engineering support for various LIFT related electronics projects and other NAS modernization projects throughout the FAA Western Service Area (WSA). - Provide engineering system design packages for installation including communications equipment, radar automation equipment, control and monitoring equipment, and weather communication equipment. - Prepare transition plans, testing plans, and training plans, and coordinate the implementation of transition plan elements with all affected stakeholders. - Assist in preparing Draft project scope agreements and project schedules. - Analyze project business and feasibility components from an engineering perspective and provide recommendations. - Prepare engineering risk assessments, and provide recommendations and proposals of actions or improvements to mitigate potential risks resulting from site, facility, and project/program changes. Also earlier: "The Electronics Engineers will provide electronics engineering support to the FAA Anchorage Communications Engineering Center with project engineering, management and planning for Legacy Infrastructure Future Technologies (LIFT) program related projects such as NEXCOM Radios, Air-to-Ground Protocol Converter and Airport Cable Loop, and other National Airspace System (NAS) modernization projects." That's also a responsibility. Could be included as first bullet. Now Requirements (required qualifications): - Electrical and/or Electronic Engineering degree and 4+ years of prior relevant experience OR Master's with 2+ years of prior relevant experience. - Additional years of relevant experience may be accepted / considered in lieu of degree. - Systems engineering experience integrating electronics components/systems together. - 4+ years’ work experience in electrical and/or electronic engineering. - Ability to obtain a Public Trust Security Clearance Suitability (To be eligible for Public Trust Security Clearance, one must be either a U.S. Citizen OR a U.S. Permanent Resident/Green Card holder who has resided in the U.S.A for the past 3 years of the past 5 years consecutively with no breaks). We could combine some duplicates: "Electrical and/or Electronic Engineering degree and 4+ years of prior relevant experience OR Master's with 2+ years of prior relevant experience." and "Additional years of relevant experience may be accepted / considered in lieu of degree." and "4+ years’ work experience in electrical and/or electronic engineering." There's overlap. We'll keep as listed. Preferred Qualifications: - Familiarity with FAA and the National Airspace System (NAS). Pay: - Program budget salary for this role could fall anywhere between $105,000 to $125,000 with a slight wiggle room (no guarantees) based on relevant experience and assessment. - Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary: $87,100.00 - $157,450.00. We could present as two bullet points. Benefits: - Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. - More details are available at www.leidos.com/careers/pay-benefits. We could list as bullet. Now produce HTML. We need to wrap each section in
heading then content. For lists, use
- .
For prose, use
. We must not include any extra text outside HTML fragment. Let's craft. First section:
About Leidos
then paragraphs. Paragraph 1: "Looking for an opportunity to make an impact? At Leidos, we deliver innovative solutions through the efforts of our diverse and talented people who are dedicated to our customers’ success. We empower our teams, contribute to our communities, and operate sustainable. Everything we do is built on a commitment to do the right thing for our customers, our people, and our community. Our Mission, Vision, and Values guide the way we do business. If this sounds like the kind of environment where you can thrive, keep reading!" Paragraph 2: "Leidos is an industry and technology leader serving government and commercial customers with smarter, more efficient digital and mission innovations. Headquartered in Reston, Virginia, with 47,000 global employees, Leidos reported annual revenues of approximately $16.7 billion for the fiscal year ended January 3, 2025. For more information, visit www.Leidos.com." Second section:About the role
then paragraph: "Your Next Great Adventure Awaits! Leidos is seeking an Electronics Engineer to join the National Airspace System Integration Support Contract (NISC IV) Team. This position will support the Federal Aviation Administration (FAA) Communications Engineering Center in Anchorage, AK." Third:Responsibilities
then- with bullets.
Fourth:
Requirements
then maybe split into Required and Preferred? Could do twoheadings inside? But we cannot add extra headings besides
. Could use
to label Required Qualifications and Preferred Qualifications inside the section. That's allowed. Thus inside Requirements section:
Required Qualifications:
then- list. Then
Preferred Qualifications:
then- list.
But we must not invent headings; using
with bold is okay. Fifth:
Pay
then- list.
Sixth:
- .
For prose, use