Maintainability Engineer
Thunderbolt Solutions · Port Hueneme, CA · 3 wk ago
Engineering$100k–$112k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we have "About Thunderbolt Solutions" and "Position Summary". The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
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. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting and decide sections.
We have:
- About Thunderbolt Solutions (company description)
- Position Summary (summary)
- Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships)
- Company Background Investigation, CAC, US Citizenship, and a secret security clearance is required for this position.
- Key Responsibilities (list)
- Education/Certification Requirements (list)
- Compensation Statement (California Pay Transparency Notice) (salary range, bonus, benefits)
- Equal Opportunity Statement (boilerplate, remove)
We need to remove EEO boilerplate.
We need to include sections only if real content.
Potential sections: About the company (maybe "About Thunderbolt Solutions") but the instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but not strict; we can use those headings if appropriate. However we have "About Thunderbolt Solutions" which is about company, not role. Could we map to "About the role"? Probably not. But we can still use
for any heading we want? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when applicable. But we can also use other headings? It says use for section headings (e.g. ...). Likely they expect us to use those standard headings. So we need to map content to those headings.
We have:
- About the role: could be Position Summary.
- Responsibilities: Key Responsibilities.
- Requirements: Education/Certification Requirements (maybe also clearance, citizenship, etc.)
- Qualifications: maybe overlapping with Requirements; but we could combine.
- Skills: maybe from responsibilities? Could extract skills like Microsoft Excel, Power BI, etc. But we might not need separate Skills if we already have Requirements.
- Benefits: from Compensation Statement: company bonus and comprehensive benefits, including health insurance, paid time off (PTO), and a 401(k) retirement plan.
- Pay: Compensation Statement includes salary range.
- Schedule: Travel percentage maybe? Travel is not schedule but could be considered schedule? The instruction says include Schedule section only if posting actually states them. Travel is not schedule but could be considered schedule? Might be better to include Travel under Responsibilities or a separate section? There's no standard heading for Travel. Could we include it under Responsibilities as a bullet? The posting includes Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships). That's substantive. We could include it under Responsibilities as a bullet or maybe under a separate "Travel" heading but not in list. Since they didn't give a heading for Travel, we could incorporate it into Responsibilities as a bullet.
We also have Company Background Investigation, CAC, US Citizenship, and a secret security clearance is required for this position. That's a requirement (clearance). Could be under Requirements.
We need to preserve all substantive information.
We must not include boilerplate like Equal Opportunity Statement.
We must not include duplicated lines.
We need to avoid creating sections with filler text.
Thus we will produce sections:
About the role
Position Summary: This position is aimed at the Reliability, Maintainability, and Availability (RM&A) data collection and analysis of the Aegis Weapon System (AWS) and Operational Readiness Test System (ORTS) Program for a variety of U.S. Navy Warships.
Maybe also include About Thunderbolt Solutions? Could be part of About the role? But we could add a separate About the company
but not in list. However instruction says prefer few substantive sections over many thin ones. Might be okay to include About Thunderbolt Solutions as a paragraph under About the role? But they said "About the role" heading example; we could put company description there as part of role context. However the posting includes "About Thunderbolt Solutions" separate. Might be better to include as a separate section but not in the prescribed list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings.
Thus we can incorporate company description into About the role paragraph.
Now Responsibilities: we need to list each responsibility as - . We'll extract bullet points from Key Responsibilities.
Key Responsibilities paragraph is long; we need to split into distinct responsibilities.
Let's parse:
"Actively support maintainability testing encompassing in-depth, pre-event coordination to develop the fault lists with the In-Service Engineering Agents (ISEAs) prior to each event execution."
"Support event planning with the test site personnel and ISEAs."
"Participate in the communication of event planning, execution and results as well as providing recommendations with the program office."
"Actively support data collection for land based developmental testing, shipboard using established Standard Operating Procedure (SOP). Utilize knowledge of the Aegis Weapon System (AWS) and ORTS to record and evaluate system faults."
"Coordinate Data Scoring Boards and participate in data analysis Working Groups to finalize RMA data; follow up on formally documented issues and assess the system design for supportability issues."
"Review and evaluate the ship and system concepts, designs and technologies, review system data deliverables and provide comments using established reporting procedures."
"Evaluate the reliability of the system against Measure of Performance and Measures of Effectiveness."
"Support the analysis to determine root cause."
"Support program reporting requirements."
"Performing data analysis using various programs including Microsoft Excel, Power BI, and other programs, and formatting and standardization of data to prepare for Power BI, AI implementation, and dashboard creation."
"Support the development of system RMA assessment plan to identify data collection opportunities by coordinating with government agencies across commands, and with industry partners."
"Assess the system design for supportability issues; review and evaluate the ship and system concepts, designs and technologies, review system data deliverables and provide comments using established reporting procedures." (duplicate of earlier? similar)
"Develop daily reports, quick look reports, final RM&A report, and SITREP as required by programs."
"Lead and develop formal presentations, participate in working groups, and communicate formally and informally with a broad spectrum of high-level military and civilian personnel."
"Lead and participate in Working Groups to support Plan development and ensure program MOE/MOP requirements are captured and assessed properly."
"Travel to Land Based Test sites and Shipboard both in port and underway to conduct associated work."
We need to avoid duplication. Some items repeat similar content. We'll consolidate.
We'll produce a list of unique responsibilities.
Now Requirements/Education/Certification Requirements: we have:
"The best candidate should be an Engineer at the Bachelor’s Degree level or higher. An Electrical Engineer or a Mechanical Engineer is preferred."
"Should have a background in Aegis Weapon System (AWS) and Operational Readiness Test System (ORTS) Programs."
"Preferred: Possess technical knowledge to be able to review technical documentation and logistic products to assist with determining the level of maintainability of the system during test."
"Must possess or be eligible to receive a DoD Secret clearance"
"Tasking will include visiting U.S. Navy Ships/vessels. Must be able to climb tall shipboard ladders, wear Personal Protective Equipment (PPE) and work in adverse environments."
"Communication skills in briefing at all levels of the organization and be able to work with and foster a strong team environment."
"Analytical skills to effectively track, manage, and status multiple technical issues."
"Must have strong skills in analyzing related data utilizing various software and engineering analysis tools."
"Must have strong Microsoft Office Suite computer skills."
"Must have strong organizational and time management skills."
Also we have Company Background Investigation, CAC, US Citizenship, and a secret security clearance is required for this position. (clearance again)
We need to avoid duplication.
We'll create a Requirements section with list items.
Now Benefits: from Compensation Statement: "This position may also be eligible for a company bonus and comprehensive benefits, including health insurance, paid time off (PTO), and a 401(k) retirement plan."
We'll list benefits.
Pay: "The anticipated annual salary range for this position is $100,000 to $112,000."
Schedule: Travel percentage maybe considered schedule? Could include Travel as part of Responsibilities but we could also add a Schedule section with travel info. Since they said include Schedule only if posting actually states them. Travel is not exactly schedule but could be considered schedule. However we already have Travel bullet in Responsibilities. Might be okay to keep Travel under Responsibilities.
But we need to decide: Should we create a Schedule section? The posting includes "Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships)". That's a schedule/travel expectation. Could be placed under Schedule heading. Since they gave Schedule as an example heading, we could use it.
Thus we will have Schedule section with that info.
Now we need to ensure we don't create sections with filler text. All sections have real content.
We must not include EEO statement.
Now produce HTML fragment.
Structure:
About the role
... (company description + position summary)
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
The anticipated annual salary range for this position is $100,000 to $112,000.
Schedule
Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships).
We need to ensure we didn't miss any substantive info: The company background investigation, CAC, US Citizenship, secret security clearance is required. We'll include under Requirements.
Also mention "Must possess or be eligible to receive a DoD Secret clearance" (duplicate). We'll include once.
Also mention "Must be able to climb tall shipboard ladders, wear Personal Protective Equipment (PPE) and work in adverse environments."
Also mention "Communication skills in briefing at all levels of the organization and be able to work with and foster a strong team environment."
Also mention "Analytical skills to effectively track, manage, and status multiple technical issues."
Also mention "Must have strong skills in analyzing related data utilizing various software and engineering analysis tools."
Also mention "Must have strong Microsoft Office Suite computer skills."
Also mention "Must have strong organizational
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and decide sections. We have: - About Thunderbolt Solutions (company description) - Position Summary (summary) - Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships) - Company Background Investigation, CAC, US Citizenship, and a secret security clearance is required for this position. - Key Responsibilities (list) - Education/Certification Requirements (list) - Compensation Statement (California Pay Transparency Notice) (salary range, bonus, benefits) - Equal Opportunity Statement (boilerplate, remove) We need to remove EEO boilerplate. We need to include sections only if real content. Potential sections: About the company (maybe "About Thunderbolt Solutions") but the instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but not strict; we can use those headings if appropriate. However we have "About Thunderbolt Solutions" which is about company, not role. Could we map to "About the role"? Probably not. But we can still use
for any heading we want? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when applicable. But we can also use other headings? It says use for section headings (e.g. ...). Likely they expect us to use those standard headings. So we need to map content to those headings.
We have:
- About the role: could be Position Summary.
- Responsibilities: Key Responsibilities.
- Requirements: Education/Certification Requirements (maybe also clearance, citizenship, etc.)
- Qualifications: maybe overlapping with Requirements; but we could combine.
- Skills: maybe from responsibilities? Could extract skills like Microsoft Excel, Power BI, etc. But we might not need separate Skills if we already have Requirements.
- Benefits: from Compensation Statement: company bonus and comprehensive benefits, including health insurance, paid time off (PTO), and a 401(k) retirement plan.
- Pay: Compensation Statement includes salary range.
- Schedule: Travel percentage maybe? Travel is not schedule but could be considered schedule? The instruction says include Schedule section only if posting actually states them. Travel is not schedule but could be considered schedule? Might be better to include Travel under Responsibilities or a separate section? There's no standard heading for Travel. Could we include it under Responsibilities as a bullet? The posting includes Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships). That's substantive. We could include it under Responsibilities as a bullet or maybe under a separate "Travel" heading but not in list. Since they didn't give a heading for Travel, we could incorporate it into Responsibilities as a bullet.
We also have Company Background Investigation, CAC, US Citizenship, and a secret security clearance is required for this position. That's a requirement (clearance). Could be under Requirements.
We need to preserve all substantive information.
We must not include boilerplate like Equal Opportunity Statement.
We must not include duplicated lines.
We need to avoid creating sections with filler text.
Thus we will produce sections:
About the role
for section headings (e.g. ...). Likely they expect us to use those standard headings. So we need to map content to those headings.
We have:
- About the role: could be Position Summary.
- Responsibilities: Key Responsibilities.
- Requirements: Education/Certification Requirements (maybe also clearance, citizenship, etc.)
- Qualifications: maybe overlapping with Requirements; but we could combine.
- Skills: maybe from responsibilities? Could extract skills like Microsoft Excel, Power BI, etc. But we might not need separate Skills if we already have Requirements.
- Benefits: from Compensation Statement: company bonus and comprehensive benefits, including health insurance, paid time off (PTO), and a 401(k) retirement plan.
- Pay: Compensation Statement includes salary range.
- Schedule: Travel percentage maybe? Travel is not schedule but could be considered schedule? The instruction says include Schedule section only if posting actually states them. Travel is not schedule but could be considered schedule? Might be better to include Travel under Responsibilities or a separate section? There's no standard heading for Travel. Could we include it under Responsibilities as a bullet? The posting includes Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships). That's substantive. We could include it under Responsibilities as a bullet or maybe under a separate "Travel" heading but not in list. Since they didn't give a heading for Travel, we could incorporate it into Responsibilities as a bullet.
We also have Company Background Investigation, CAC, US Citizenship, and a secret security clearance is required for this position. That's a requirement (clearance). Could be under Requirements.
We need to preserve all substantive information.
We must not include boilerplate like Equal Opportunity Statement.
We must not include duplicated lines.
We need to avoid creating sections with filler text.
Thus we will produce sections:
About the role
Position Summary: This position is aimed at the Reliability, Maintainability, and Availability (RM&A) data collection and analysis of the Aegis Weapon System (AWS) and Operational Readiness Test System (ORTS) Program for a variety of U.S. Navy Warships.
Maybe also include About Thunderbolt Solutions? Could be part of About the role? But we could add a separateAbout the company
but not in list. However instruction says prefer few substantive sections over many thin ones. Might be okay to include About Thunderbolt Solutions as a paragraph under About the role? But they said "About the role" heading example; we could put company description there as part of role context. However the posting includes "About Thunderbolt Solutions" separate. Might be better to include as a separate section but not in the prescribed list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings.
Thus we can incorporate company description into About the role paragraph.
Now Responsibilities: we need to list each responsibility as - . We'll extract bullet points from Key Responsibilities.
Key Responsibilities paragraph is long; we need to split into distinct responsibilities.
Let's parse:
"Actively support maintainability testing encompassing in-depth, pre-event coordination to develop the fault lists with the In-Service Engineering Agents (ISEAs) prior to each event execution."
"Support event planning with the test site personnel and ISEAs."
"Participate in the communication of event planning, execution and results as well as providing recommendations with the program office."
"Actively support data collection for land based developmental testing, shipboard using established Standard Operating Procedure (SOP). Utilize knowledge of the Aegis Weapon System (AWS) and ORTS to record and evaluate system faults."
"Coordinate Data Scoring Boards and participate in data analysis Working Groups to finalize RMA data; follow up on formally documented issues and assess the system design for supportability issues."
"Review and evaluate the ship and system concepts, designs and technologies, review system data deliverables and provide comments using established reporting procedures."
"Evaluate the reliability of the system against Measure of Performance and Measures of Effectiveness."
"Support the analysis to determine root cause."
"Support program reporting requirements."
"Performing data analysis using various programs including Microsoft Excel, Power BI, and other programs, and formatting and standardization of data to prepare for Power BI, AI implementation, and dashboard creation."
"Support the development of system RMA assessment plan to identify data collection opportunities by coordinating with government agencies across commands, and with industry partners."
"Assess the system design for supportability issues; review and evaluate the ship and system concepts, designs and technologies, review system data deliverables and provide comments using established reporting procedures." (duplicate of earlier? similar)
"Develop daily reports, quick look reports, final RM&A report, and SITREP as required by programs."
"Lead and develop formal presentations, participate in working groups, and communicate formally and informally with a broad spectrum of high-level military and civilian personnel."
"Lead and participate in Working Groups to support Plan development and ensure program MOE/MOP requirements are captured and assessed properly."
"Travel to Land Based Test sites and Shipboard both in port and underway to conduct associated work."
We need to avoid duplication. Some items repeat similar content. We'll consolidate.
We'll produce a list of unique responsibilities.
Now Requirements/Education/Certification Requirements: we have:
"The best candidate should be an Engineer at the Bachelor’s Degree level or higher. An Electrical Engineer or a Mechanical Engineer is preferred."
"Should have a background in Aegis Weapon System (AWS) and Operational Readiness Test System (ORTS) Programs."
"Preferred: Possess technical knowledge to be able to review technical documentation and logistic products to assist with determining the level of maintainability of the system during test."
"Must possess or be eligible to receive a DoD Secret clearance"
"Tasking will include visiting U.S. Navy Ships/vessels. Must be able to climb tall shipboard ladders, wear Personal Protective Equipment (PPE) and work in adverse environments."
"Communication skills in briefing at all levels of the organization and be able to work with and foster a strong team environment."
"Analytical skills to effectively track, manage, and status multiple technical issues."
"Must have strong skills in analyzing related data utilizing various software and engineering analysis tools."
"Must have strong Microsoft Office Suite computer skills."
"Must have strong organizational and time management skills."
Also we have Company Background Investigation, CAC, US Citizenship, and a secret security clearance is required for this position. (clearance again)
We need to avoid duplication.
We'll create a Requirements section with list items.
Now Benefits: from Compensation Statement: "This position may also be eligible for a company bonus and comprehensive benefits, including health insurance, paid time off (PTO), and a 401(k) retirement plan."
We'll list benefits.
Pay: "The anticipated annual salary range for this position is $100,000 to $112,000."
Schedule: Travel percentage maybe considered schedule? Could include Travel as part of Responsibilities but we could also add a Schedule section with travel info. Since they said include Schedule only if posting actually states them. Travel is not exactly schedule but could be considered schedule. However we already have Travel bullet in Responsibilities. Might be okay to keep Travel under Responsibilities.
But we need to decide: Should we create a Schedule section? The posting includes "Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships)". That's a schedule/travel expectation. Could be placed under Schedule heading. Since they gave Schedule as an example heading, we could use it.
Thus we will have Schedule section with that info.
Now we need to ensure we don't create sections with filler text. All sections have real content.
We must not include EEO statement.
Now produce HTML fragment.
Structure:
About the role
... (company description + position summary)
Responsibilities
- ...
...
Requirements
- ...
...
Benefits
- ...
...
Pay
The anticipated annual salary range for this position is $100,000 to $112,000.
Schedule
Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships).
We need to ensure we didn't miss any substantive info: The company background investigation, CAC, US Citizenship, secret security clearance is required. We'll include under Requirements.
Also mention "Must possess or be eligible to receive a DoD Secret clearance" (duplicate). We'll include once.
Also mention "Must be able to climb tall shipboard ladders, wear Personal Protective Equipment (PPE) and work in adverse environments."
Also mention "Communication skills in briefing at all levels of the organization and be able to work with and foster a strong team environment."
Also mention "Analytical skills to effectively track, manage, and status multiple technical issues."
Also mention "Must have strong skills in analyzing related data utilizing various software and engineering analysis tools."
Also mention "Must have strong Microsoft Office Suite computer skills."
Also mention "Must have strong organizational
About the role
... (company description + position summary)
Responsibilities
- ... ...
Requirements
- ... ...
Benefits
- ... ...
Pay
The anticipated annual salary range for this position is $100,000 to $112,000.
Schedule
Travel: 20%-30% (Travel could include underway periods aboard US Navy Ships).
We need to ensure we didn't miss any substantive info: The company background investigation, CAC, US Citizenship, secret security clearance is required. We'll include under Requirements. Also mention "Must possess or be eligible to receive a DoD Secret clearance" (duplicate). We'll include once. Also mention "Must be able to climb tall shipboard ladders, wear Personal Protective Equipment (PPE) and work in adverse environments." Also mention "Communication skills in briefing at all levels of the organization and be able to work with and foster a strong team environment." Also mention "Analytical skills to effectively track, manage, and status multiple technical issues." Also mention "Must have strong skills in analyzing related data utilizing various software and engineering analysis tools." Also mention "Must have strong Microsoft Office Suite computer skills." Also mention "Must have strong organizational