NETA III and NETA IV Technicians-SIGN ON UP TO $10k
High Voltage Maintenance Corporation · Fort Belvoir, VA · 2 days ago
Engineering$175k–$230k/yrFull-time
We need to output only HTML fragment, with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions.
We need to parse the posting.
Key sections:
- About the role: The paragraph after "As a NETA founding company..." maybe that is about the role/company. Also "You won't be a number here..." etc. That's about the role/company. Could be "About the role" or "About Us". We'll include "About the role" with that content.
- Responsibilities: The bullet list after "What You'll Do". That's responsibilities.
- Requirements: The list after "Required NETA Level III or Level IV Certification..." includes required qualifications.
- Qualifications: maybe "Preferred" list? Could be "Preferred Qualifications". But we have "Preferred" bullet list. Could treat as "Qualifications" (preferred). Or separate "Skills"? The posting includes "Preferred NETA Level IV Certification..." etc. That's qualifications/skills. We'll put under "Qualifications" maybe.
- Skills: Could be separate but we may combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include only those with real content. We have content for About the role, Responsibilities, Requirements (required), Qualifications (preferred), Benefits, Pay, Schedule? Travel info maybe schedule? Travel up to 75% could be schedule? Not exactly schedule but travel. There's no explicit schedule (like shift). Could omit Schedule if no specific content. Pay: we have compensation details: Up to $110/hour, overtime, signing bonus, etc. That's pay. Benefits: list of benefits.
We must not include placeholder like "commensurate with experience". We have specific numbers.
We need to preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
We must remove duplicated lines: there are duplicated paragraphs about salary ranges for various localities repeated twice. We need to keep only one instance? The instruction: remove duplicated lines. So we should include the salary range info only once. However the posting includes two similar blocks: one for CA, Cleveland-OH, etc and another for State of Washington. Both are substantive but duplicated? They are not identical; they differ in locality and numbers. Both are substantive. However they are similar structure; but they are not exact duplicates. The instruction says remove duplicated lines, meaning if same line appears twice, we should keep one. The two blocks are not identical but similar. We'll keep both as they provide different locality info. But we could combine? Might be considered duplicated content? Safer to keep both as they are distinct.
We also need to remove boilerplate like "Work Authorization No calls or agencies please..." etc. That's legal/boilerplate; remove. Also Equal Opportunity Employer block; remove. Also "About Us" and "About Vertiv" maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" and "About Vertiv" are not explicitly listed as boilerplate but could be considered company description; maybe we keep as part of About the role? The posting includes "As a NETA founding company..." then later "About Us" and "About Vertiv". The "About Us" section includes core principles and behaviors. That might be considered substantive? It's about company culture. Might be considered part of About the role? The instruction: we should include a section ONLY when the posting has real, specific content for it. The "About Us" section is specific content about company principles. Could be included under "About the role" or separate "About Us" but we only have headings list; we could put under "About the role". We'll incorporate that content.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions.
We need to parse the posting.
Key sections:
- About the role: The paragraph after "As a NETA founding company..." maybe that is about the role/company. Also "You won't be a number here..." etc. That's about the role/company. Could be "About the role" or "About Us". We'll include "About the role" with that content.
- Responsibilities: The bullet list after "What You'll Do". That's responsibilities.
- Requirements: The list after "Required NETA Level III or Level IV Certification..." includes required qualifications.
- Qualifications: maybe "Preferred" list? Could be "Preferred Qualifications". But we have "Preferred" bullet list. Could treat as "Qualifications" (preferred). Or separate "Skills"? The posting includes "Preferred NETA Level IV Certification..." etc. That's qualifications/skills. We'll put under "Qualifications" maybe.
- Skills: Could be separate but we may combine. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include only those with real content. We have content for About the role, Responsibilities, Requirements (required), Qualifications (preferred), Benefits, Pay, Schedule? Travel info maybe schedule? Travel up to 75% could be schedule? Not exactly schedule but travel. There's no explicit schedule (like shift). Could omit Schedule if no specific content. Pay: we have compensation details: Up to $110/hour, overtime, signing bonus, etc. That's pay. Benefits: list of benefits.
We must not include placeholder like "commensurate with experience". We have specific numbers.
We need to preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists.
We must remove duplicated lines: there are duplicated paragraphs about salary ranges for various localities repeated twice. We need to keep only one instance? The instruction: remove duplicated lines. So we should include the salary range info only once. However the posting includes two similar blocks: one for CA, Cleveland-OH, etc and another for State of Washington. Both are substantive but duplicated? They are not identical; they differ in locality and numbers. Both are substantive. However they are similar structure; but they are not exact duplicates. The instruction says remove duplicated lines, meaning if same line appears twice, we should keep one. The two blocks are not identical but similar. We'll keep both as they provide different locality info. But we could combine? Might be considered duplicated content? Safer to keep both as they are distinct.
We also need to remove boilerplate like "Work Authorization No calls or agencies please..." etc. That's legal/boilerplate; remove. Also Equal Opportunity Employer block; remove. Also "About Us" and "About Vertiv" maybe considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" and "About Vertiv" are not explicitly listed as boilerplate but could be considered company description; maybe we keep as part of About the role? The posting includes "As a NETA founding company..." then later "About Us" and "About Vertiv". The "About Us" section includes core principles and behaviors. That might be considered substantive? It's about company culture. Might be considered part of About the role? The instruction: we should include a section ONLY when the posting has real, specific content for it. The "About Us" section is specific content about company principles. Could be included under "About the role" or separate "About Us" but we only have headings list; we could put under "About the role". We'll incorporate that content.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
... (combined paragraphs about Vertiv being NETA founding company, elite specialist, etc.)
Responsibilities
- ... each bullet from "What You'll Do"
Requirements
- ... required bullet list
Qualifications
- ... preferred bullet list
Benefits
- ... benefits list from "What We Offer"
Pay
- ... compensation details