Test Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the description.
Key sections:
- About the role: The initial paragraph describing Leidos, mission, etc. Could be "About the role" or "About the position". We'll use About the role
then
with that content. - Responsibilities: The "Primary Responsibilities" list. We'll output
Responsibilities
then- each bullet.
- Requirements: Could be "Required Qualifications". We'll treat as Requirements. Use
Requirements
then- .
- Desired Qualifications: Could be "Skills" or "Preferred Qualifications". We'll use
- ... each bullet ... ...
Skills
maybe. Or "Qualifications". But we already used Requirements for required. Desired could be "Preferred Qualifications". We'll usePreferred Qualifications
. - Pay: The posting includes Pay Range $107,900.00 - $195,050.00 plus note. So we need Pay section. UsePay
thenwith that info. - Benefits: There's a "Pay And Benefits" section describing benefits generically. It mentions competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. Also link. We'll include Benefits section with that content. - Schedule: Not mentioned. No schedule info. So omit. - Also maybe "About Leidos" could be separate but we already have About the role. Could also include "About Leidos" as separate but not required. We'll keep About the role covering initial description. We must not include boilerplate like EEO, scam warning, etc. Remove those. We must preserve all substantive info: need to include details like location (National Capital Region (NCR)), that it's a government contract, etc. Also mention that the role is Test Engineer, etc. We need to ensure we don't repeat job title as heading. Not needed. We must not include duplicated lines. Let's extract substantive content. From description: "Looking for an opportunity to make an impact? Leidos delivers solutions through the work of a diverse, dedicated team focused on our customers' success. We're seeking a Test Engineer to support a government contract in the National Capital Region (NCR). Our team enables missions that matter for our customer. People stick with this program because the work is genuinely interesting, and it shows — many of our team members have been here for years. We're looking for smart, eager problem-solvers: people who collaborate well, show up for their teammates and the mission, take ownership and drive things forward on their own, and are comfortable working in a fast-paced, dynamic environment where priorities can shift quickly." That's about the role. Then "In this role, you'll take a customer-designed electrical or mechanical device — the Device Under Test (DUT) — and build the test capability around it: connecting the right bench instrumentation, writing custom automation and analysis in Python and/or LabVIEW, and establishing repeatable, calibrated data that a customer engineer or technician can rely on." That could be part of responsibilities but it's also description. We'll include in responsibilities maybe. Then "Primary Responsibilities" list bullet points. Let's list them: - Take a customer-designed physical DUT (electrical, mechanical, or electromechanical) and determine what must be proven about it - Connect and configure bench instrumentation (oscilloscopes, spectrum/power analyzers, signal/waveform generators, NI hardware, multimeters, power supplies) to the DUT - Write custom test automation and analysis software in Python and/or LabVIEW to control the test setup and interpret results - Develop hardware-in-the-loop (HIL) test environments and simulation to validate the DUT under realistic conditions - Build operator-facing GUIs so engineers or technicians can run the test - Establish and validate repeatable, calibrated, NIST-traceable test data - Maintain and improve existing automated test systems, fixtures, and instrument drivers - Support configuration management for test software and system architecture across platforms - Train engineers and technicians on running the automated test systems you build - Engage with customers to understand testing needs, demonstrate capabilities, and support business development - Document test procedures, system architecture, and requirements, including: - Test and inspection requirements documents - Multimedia/user documentation for the test system - System documentation for hardware and software components - Test program style guides and GUI/architecture updates for current and next-generation systems - Attend meetings and reviews; communicate with the program manager, engineers, and customer team members. - Communicate with external parties such as mission partners and vendors. We need to preserve all. Then "Required Qualifications" list: - Active TS/SCI; must be eligible and willing to upgrade to TS/SCI w/polygraph. - Bachelor of Science degree, preferably in an engineering field, and at least 8 years of relevant experience, or Master's with 6–10 years; at least 12 years of work experience can be used in lieu of degree/combined with education. - Demonstrated hands-on experience taking a physical DUT (electrical/mechanical hardware) and building a custom automated test system around it — not testing an existing software product. - Demonstrated experience with bench test equipment from Agilent, Keysight, HP, Tektronix, and National Instruments, including power supplies, multimeters, oscilloscopes, counters, power meters, signal & waveform generators, electronic loads, and audio/noise/signal/modulation/power analyzers. - Working knowledge of Python and/or LabVIEW used to write custom test automation, instrument drivers, and analysis for hardware. - Understanding of measurement traceability, calibration, and repeatable test data (NIST-traceable). - Demonstrated experience/training operating electronic devices such as transmitters, receivers, and power supplies. - Strong written/verbal communication skills, including the ability to document systems, train others, and work directly with customers. - Able to work well independently and as part of a team. Then "Desired Qualifications" list: - Experience with hardware-in-the-loop (HIL) test environments and simulation - Experience building custom operator-facing GUIs or test dashboards for a DUT - Experience with FPGAs, embedded systems, or microcontrollers - Experience with test fixtures and custom instrument drivers - Knowledge of RF principles and hands-on RF test experience - Knowledge of cellular technologies and/or cellular testing experience - Experience writing scripts to test or interface with robotic systems - Background in manufacturing test, validation engineering, or a test and inspection (T&I) environment - Knowledgeable of electronics and electrical engineering principles (voltage, current, RF) - Experience with customer-facing roles, technical training delivery, or business development support Then "Pay Range" section: Pay Range $107,900.00 - $195,050.00 The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law. Then "Pay And Benefits" section: Pay and benefits are fundamental to any career decision. That's why we craft compensation packages that reflect the importance of the work we do for our customers. 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 should include Benefits section with that content. We should not include the "About Leidos" paragraph after Pay And Benefits? Actually there is an "About Leidos" paragraph earlier after Pay Range? Let's see: after Pay Range, there is "About Leidos Leidos is an industry and technology leader..." That's substantive about company. Could be included in About the role or maybe separate "About Leidos". But we already have About the role covering initial description. Could add another paragraph about Leidos under About the role or maybe a separate "About Leidos" section. The instruction: Prefer a few substantive sections over many thin ones. So we can merge company info into About the role. Thus About the role paragraph will include the initial description plus the About Leidos paragraph. We must not include boilerplate like "Securing Your Data", "Commitment to Non-Discrimination", etc. Now produce HTML. Structure:
About the role
... combined paragraphs ...
Responsibilities
Requirements
- ... required qualifications ...
Preferred Qualifications
- ... desired qualifications ...
Pay
Pay Range $107,900.00 - $195,050.00. The Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary. Additional factors considered in extending an offer include (but are not limited to) responsibilities of the job, education, experience, knowledge, skills, and abilities, as well as internal equity, alignment with market data, applicable bargaining agreement (if any), or other law.
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 might also include a sentence about Pay and benefits being fundamental... but we can incorporate. Check for any duplicated lines: ensure we didn't repeat. Now ensure we preserve all substantive info: Did we miss any? Let's verify. From initial description we included: "Looking for an opportunity to make an impact? Leidos delivers solutions through the work of a diverse, dedicated team focused on our customers' success. We're seeking a Test Engineer to support a government contract in the National Capital Region (NCR). Our team enables missions that matter for our customer. People stick with this program because the work is genuinely interesting, and it shows — many of our team members have been here for years. We're looking for smart, eager problem-solvers: people who collaborate well, show up for their teammates and the mission, take ownership and drive things forward on their own, and are comfortable working in a fast-paced, dynamic environment where priorities can shift quickly." Then we added About Leidos paragraph: "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 should also include the line "In this role, you'll take a customer-designed electrical or mechanical device — the Device Under Test (DUT) — and build the test capability around it: connecting the right bench instrumentation, writing custom automation and analysis in Python and/or LabVIEW, and establishing repeatable, calibrated data that a customer engineer or technician can rely on." This is substantive; we could include it in About the role or Responsibilities. Since it's part of role description, we can add to About the role after the initial paragraph. Thus About the role will have multiple paragraphs maybe separated bytags. We can put multiple
inside the section? The instruction: Use
for prose. So we can have multiple
elements under the heading. Thus: