Test Technician
Actalent · Middletown, RI · 1 mo ago
On-site$32–$35/hrContract
We need to output HTML fragment with sections: h3 headings for sections present: About the role? The description includes "Job Description" but we should not repeat job title. Use headings: About the role (maybe from description), Responsibilities, Essential Skills, Additional Skills & Qualifications, Work Environment, Job Type & Location, Pay And Benefits, Workplace Type? Actually Workplace Type is duplicate of Job Type & Location. We should include sections only if they have real specific content. The posting includes:
- Job Description paragraph (intro) -> could be "About the role" (or maybe "Job Description").
- Responsibilities list.
- Essential Skills list.
- Additional Skills & Qualifications list.
- Work Environment paragraph.
- Job Type & Location paragraph.
- Pay And Benefits paragraph with pay range and benefits list.
- Workplace Type paragraph (maybe redundant). Could combine with Job Type & Location? But we can keep separate if content distinct. Workplace Type says "This is a fully onsite position in Middletown,RI." That's similar to Job Type & Location which says "This is a Contract to Hire position based out of Middletown, RI." Both mention location and onsite. Could merge but we need to follow rule: include a section only when posting has real specific content for it. Both have content; we could keep both but might be redundant. However we can keep both as separate sections; each has specific content.
- Application Deadline: "This position is anticipated to close on Oct 5, 2026." That's specific; could be its own section maybe "Application Deadline". But rule: we should not create sections for filler like "not specified". This is specific. So include.
- About Actalent etc is boilerplate; we should remove cookie/navigation/legal/EEO etc. The About Actalent section is promotional but not required? It's not boilerplate legal; it's company description. Might be considered not essential? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Actalent is not those; it's company overview. Might keep? But they said "Prefer a few substantive sections over many thin ones." Could include "About the company" but not required. However they said "include a section ONLY when the posting has real, specific content for it". The About Actalent is specific content. Could include as "About the company". But they didn't list that as a standard heading; they gave list of possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't include About the company. So maybe we should not add extra headings beyond those. So we should stick to those headings. So we will use: About the role (intro), Responsibilities, Skills (maybe combine Essential Skills and Additional Skills & Qualifications into Skills?), Requirements/Qualifications? The posting has Essential Skills and Additional Skills & Qualifications; we could treat them as Skills. Could also have Requirements (maybe same as Skills). But we need to preserve all substantive info; we can split into two sections: Essential Skills and Additional Skills & Qualifications, but headings must be from allowed list? The list includes Skills. Could we use "Skills" heading and put both lists under? That would combine but still preserve info. However we might lose distinction but still all info present. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we could use other headings if appropriate, but better to stick to given examples. We could use "Skills" for both essential and additional. Could also use "Requirements" for essential skills and "Qualifications" for additional. That would map.
Thus sections:
- About the role (intro paragraph)
- Responsibilities (ul)
- Requirements (essential skills list)
- Qualifications (additional skills & qualifications list)
- Work Environment (maybe not in list but we could use "Work Environment" as heading? Not in examples but could be okay. However they said e.g., not exclusive. Might be okay. But to be safe, we could incorporate work environment into About the role? But that would lose detail. Better to include as its own heading "Work Environment". It's specific.
- Job Type & Location (maybe "Job Type & Location" not in examples but okay). Could use "Schedule"? Not present. Could use "Pay" for pay range and benefits.
- Pay (pay range and benefits list)
- Application Deadline (maybe not in examples but okay). Could treat as "Schedule"? Not exactly. But we can include as its own heading.
We must not include boilerplate like equal opportunity etc. Remove Actalent description etc.
We need to output only HTML fragment, no html/body tags, no markdown.
Let's extract content.
Intro paragraph: "The Test Technician supports the Tactical Control System (TCS) portion of the AN/BYG-1 combat system used in United States and Royal Australian Navy submarine fleets. This role focuses on testing and validating the tactical control, weapons/payload control, information assurance, and tactical network subsystems that enable high-stakes national security missions. You will leverage your US Navy Submarine Fire Control experience to help build and deliver a reliable, high-performance submarine combat system as part of a close-knit, mission-driven team."
That's About the role.
Responsibilities: list items (each sentence). Let's capture each:
- Conduct subsystem and system-of-systems testing on blackbox components at on-site facilities and other locations as required.
- Work within an Agile development environment alongside engineers across the program to verify system deliveries to the Navy.
- Analyze how software meets system, functional, and performance requirements, ensuring compliance with test requirements and specifications.
- Install test bays and configure test setups to support subsystem and integrated system testing activities.
- Troubleshoot test anomalies, identify root causes, and collaborate with engineering teams to drive resolution.
- Communicate issues clearly and proactively with engineers from other subsystems to determine where problems originate and how to address them as a project team.
- Apply knowledge of test engineering concepts, principles, and theories to develop and execute effective test approaches.
- Support testing activities in a DoD production delivery environment, ensuring readiness and reliability of delivered systems.
- Work proactively with both local and remote test team members to coordinate test efforts and share findings.
- Use Microsoft Office products to prepare test documentation, reports, and communications with solid verbal and written clarity.
- Participate in requirements management and system modeling activities to ensure test coverage and traceability.
- Travel as needed to support testing, integration, and collaboration at various program and Navy-related sites.
That's 12 items.
Essential Skills (Requirements): list:
- Strong US Navy Submarine Fire Control Technician experience, including hands-on work with submarine fire control systems.
- Hands-on experience with the Navy's AN/BYG-1 Tactical Control System (TCS).
- US Navy Submarine experience, with familiarity in submarine operations and combat systems.
- Experience testing in an Agile development environment, including collaboration with cross-functional engineering teams.
- Experience conducting subsystem testing, system testing, and software testing in a DoD production delivery environment.
- Knowledge of test engineering concepts, principles, and theories and their application to complex combat systems.
- Knowledge of requirements management and system modeling and how they relate to test planning and execution.
- Proven troubleshooting skills for identifying and resolving anomalies in hardware, software, and integrated systems.
- Experience working proactively with local and remote test team members to achieve program goals.
- Solid verbal and written communication skills, including the ability to use Microsoft Office products for documentation and reporting.
- Ability to travel to support testing and integration activities at various locations.
Additional Skills & Qualifications (Qualifications): list:
- Experience working in the Submarine Warfare Federated Tactical System (SWFTS) submarine community.
- Prior experience as a Navy Fire Control Technician with direct involvement in submarine combat systems.
- Familiarity with sonar, fire control systems, and related tactical functionality.
- Experience with system testing, functionality verification, and test requirements analysis in complex defense systems.
- Ability to communicate effectively with peers and leadership, including clear escalation of issues and alternatives.
- Skill in recognizing relevant information quickly and conveying technical details in an understandable manner.
- Experience working on large, multi-year funded defense programs with cross-disciplinary teams.
Work Environment paragraph:
"This role is 100% on-site at NUWC facilities, with flexible seating available nearby at the Middletown, RI office. You will work in a secure, mission-focused environment alongside approximately 150 professionals on a well-funded program with support projected through 2027. The setting involves close collaboration with the submarine community and engineering teams, using modern test equipment, software tools, and Agile practices to validate complex combat systems. The work environment emphasizes teamwork, clear communication, and a shared commitment to delivering high-quality, reliable solutions for naval operations."
Job Type & Location paragraph:
"This is a Contract to Hire position based out of Middletown, RI."
Pay And Benefits paragraph:
"The pay range for this position is $32.00 - $35.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)"
We need to format benefits as a list. The benefits list appears as a sentence with commas. We'll split into items:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
We should keep as list items.
Workplace Type paragraph: "This is a fully onsite position in Middletown,RI." This is similar to Job Type & Location but we could keep as separate section "Workplace Type". However it's redundant; maybe we can omit to avoid thin sections. But we need to preserve all substantive information; the info is already covered in Job Type & Location (Contract to Hire based out of Middletown, RI) and Work Environment (100% on-site at NUWC facilities...). The Workplace Type adds "fully onsite position in Middletown,RI." That's already implied. Could be considered duplicate. Safer to include? Might be considered duplicated lines. The instruction: remove duplicated lines. This line is duplicated in essence. I'd drop Workplace Type section.
Application Deadline paragraph: "This position is anticipated to close on Oct 5, 2026."
We could make a section "Application Deadline". Not in examples but okay.
Now produce HTML.
Structure:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not exclusive. So we could use other headings if appropriate, but better to stick to given examples. We could use "Skills" for both essential and additional. Could also use "Requirements" for essential skills and "Qualifications" for additional. That would map.
Thus sections:
- About the role (intro paragraph)
- Responsibilities (ul)
- Requirements (essential skills list)
- Qualifications (additional skills & qualifications list)
- Work Environment (maybe not in list but we could use "Work Environment" as heading? Not in examples but could be okay. However they said e.g., not exclusive. Might be okay. But to be safe, we could incorporate work environment into About the role? But that would lose detail. Better to include as its own heading "Work Environment". It's specific.
- Job Type & Location (maybe "Job Type & Location" not in examples but okay). Could use "Schedule"? Not present. Could use "Pay" for pay range and benefits.
- Pay (pay range and benefits list)
- Application Deadline (maybe not in examples but okay). Could treat as "Schedule"? Not exactly. But we can include as its own heading.
We must not include boilerplate like equal opportunity etc. Remove Actalent description etc.
We need to output only HTML fragment, no html/body tags, no markdown.
Let's extract content.
Intro paragraph: "The Test Technician supports the Tactical Control System (TCS) portion of the AN/BYG-1 combat system used in United States and Royal Australian Navy submarine fleets. This role focuses on testing and validating the tactical control, weapons/payload control, information assurance, and tactical network subsystems that enable high-stakes national security missions. You will leverage your US Navy Submarine Fire Control experience to help build and deliver a reliable, high-performance submarine combat system as part of a close-knit, mission-driven team."
That's About the role.
Responsibilities: list items (each sentence). Let's capture each:
- Conduct subsystem and system-of-systems testing on blackbox components at on-site facilities and other locations as required.
- Work within an Agile development environment alongside engineers across the program to verify system deliveries to the Navy.
- Analyze how software meets system, functional, and performance requirements, ensuring compliance with test requirements and specifications.
- Install test bays and configure test setups to support subsystem and integrated system testing activities.
- Troubleshoot test anomalies, identify root causes, and collaborate with engineering teams to drive resolution.
- Communicate issues clearly and proactively with engineers from other subsystems to determine where problems originate and how to address them as a project team.
- Apply knowledge of test engineering concepts, principles, and theories to develop and execute effective test approaches.
- Support testing activities in a DoD production delivery environment, ensuring readiness and reliability of delivered systems.
- Work proactively with both local and remote test team members to coordinate test efforts and share findings.
- Use Microsoft Office products to prepare test documentation, reports, and communications with solid verbal and written clarity.
- Participate in requirements management and system modeling activities to ensure test coverage and traceability.
- Travel as needed to support testing, integration, and collaboration at various program and Navy-related sites.
That's 12 items.
Essential Skills (Requirements): list:
- Strong US Navy Submarine Fire Control Technician experience, including hands-on work with submarine fire control systems.
- Hands-on experience with the Navy's AN/BYG-1 Tactical Control System (TCS).
- US Navy Submarine experience, with familiarity in submarine operations and combat systems.
- Experience testing in an Agile development environment, including collaboration with cross-functional engineering teams.
- Experience conducting subsystem testing, system testing, and software testing in a DoD production delivery environment.
- Knowledge of test engineering concepts, principles, and theories and their application to complex combat systems.
- Knowledge of requirements management and system modeling and how they relate to test planning and execution.
- Proven troubleshooting skills for identifying and resolving anomalies in hardware, software, and integrated systems.
- Experience working proactively with local and remote test team members to achieve program goals.
- Solid verbal and written communication skills, including the ability to use Microsoft Office products for documentation and reporting.
- Ability to travel to support testing and integration activities at various locations.
Additional Skills & Qualifications (Qualifications): list:
- Experience working in the Submarine Warfare Federated Tactical System (SWFTS) submarine community.
- Prior experience as a Navy Fire Control Technician with direct involvement in submarine combat systems.
- Familiarity with sonar, fire control systems, and related tactical functionality.
- Experience with system testing, functionality verification, and test requirements analysis in complex defense systems.
- Ability to communicate effectively with peers and leadership, including clear escalation of issues and alternatives.
- Skill in recognizing relevant information quickly and conveying technical details in an understandable manner.
- Experience working on large, multi-year funded defense programs with cross-disciplinary teams.
Work Environment paragraph:
"This role is 100% on-site at NUWC facilities, with flexible seating available nearby at the Middletown, RI office. You will work in a secure, mission-focused environment alongside approximately 150 professionals on a well-funded program with support projected through 2027. The setting involves close collaboration with the submarine community and engineering teams, using modern test equipment, software tools, and Agile practices to validate complex combat systems. The work environment emphasizes teamwork, clear communication, and a shared commitment to delivering high-quality, reliable solutions for naval operations."
Job Type & Location paragraph:
"This is a Contract to Hire position based out of Middletown, RI."
Pay And Benefits paragraph:
"The pay range for this position is $32.00 - $35.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors. Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms. If eligible, the benefits available for this temporary role may include the following: Medical, dental & vision Critical Illness, Accident, and Hospital 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available Life Insurance (Voluntary Life & AD&D for the employee and dependents) Short and long-term disability Health Spending Account (HSA) Transportation benefits Employee Assistance Program Time Off/Leave (PTO, Vacation or Sick Leave)"
We need to format benefits as a list. The benefits list appears as a sentence with commas. We'll split into items:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
We should keep as list items.
Workplace Type paragraph: "This is a fully onsite position in Middletown,RI." This is similar to Job Type & Location but we could keep as separate section "Workplace Type". However it's redundant; maybe we can omit to avoid thin sections. But we need to preserve all substantive information; the info is already covered in Job Type & Location (Contract to Hire based out of Middletown, RI) and Work Environment (100% on-site at NUWC facilities...). The Workplace Type adds "fully onsite position in Middletown,RI." That's already implied. Could be considered duplicate. Safer to include? Might be considered duplicated lines. The instruction: remove duplicated lines. This line is duplicated in essence. I'd drop Workplace Type section.
Application Deadline paragraph: "This position is anticipated to close on Oct 5, 2026."
We could make a section "Application Deadline". Not in examples but okay.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ...
Qualifications
- ...
Work Environment
...
Job Type & Location
...
Pay
The pay range for this position is $32.00 - $35.