Program Manager
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The instruction says: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings where appropriate. We should not repeat job title as heading. We should not include Job ID etc. We should include sections only when posting has real specific content. We must not create Pay/Schedule/Benefits unless posting actually states them. Benefits are stated, so include Benefits section. Pay not stated, so omit Pay. Schedule: we have Position Type and Expected Hours of Work, plus Travel. Could treat as Schedule? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Schedule section for hours and travel. We'll include Schedule.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the AAP/EEO Statement, maybe also "Work Authorization / Security Clearance" is substantive? It says Top Secret with SCI Eligibility - that's a requirement, so keep. The EEO statement is boilerplate, remove.
Also remove "Our Firmware" maybe not needed but it's substantive description of company culture; could be included under About the role? But we have Company Overview and Group Overview already. We could include a section "About the role" maybe summarizing Position Summary? Actually About the role could be Position Summary. We'll map:
- About the role: Position Summary paragraph.
- Responsibilities: What You'll Do (list)
- Requirements: What You Bring (list) plus Additional Eligibility Qualifications (list) maybe combine? Could separate Requirements and Qualifications? The instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide.
We have: What You Bring includes experience, knowledge, proficiency, experience with deployment, familiarity with tools, leadership skills, PMP/DAU certification. Additional Eligibility Qualifications includes passport, driver's license, BS degree (waived). Also Work Authorization / Security Clearance (Top Secret with SCI). Those are requirements.
We could have:
- Requirements: What You Bring (list)
- Qualifications: Additional Eligibility Qualifications (list) plus Security Clearance (maybe as part of Qualifications)
- Skills: maybe not separate; we could embed skills in Requirements.
But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section "Requirements". But instruction says we can use those headings; we can choose to include only those with substantive content. Let's think: We have responsibilities list, we have requirements list (experience, knowledge, proficiency, familiarity, leadership, certification). We have additional eligibility (passport, driver's license, degree). We have security clearance. We have benefits list. We have schedule (hours, travel). We have company overview and group overview maybe as About the role? Actually About the role could be Position Summary plus maybe Company Overview? But we should not duplicate.
We need to preserve all substantive information. So we need to include Company Overview and Group Overview somewhere. Could be under "About the role" or maybe a separate section "About the company". But the instruction only gave examples of headings; we can use other headings? It 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 those. Safer to stick to those. So we need to map company overview and group overview into About the role? Possibly About the role can include a brief description of the team and role. But we must preserve all substantive information; we cannot omit company overview. So we need to include it somewhere. Perhaps we can treat Company Overview and Group Overview as part of "About the role" (the role within the company). We'll include paragraphs under About the role that contain that info.
Thus:
About the role
Company overview paragraph(s) + Group overview paragraph(s) + Position summary paragraph.
Then Responsibilities: Responsibilities
- ...
Requirements: Requirements
- ...
(including What You Bring and Additional Eligibility Qualifications and Security Clearance)
Benefits: Benefits
- ...
Schedule: Schedule
Position Type and Expected Hours of Work paragraph + Travel paragraph.
We must not include Pay.
We must not include Work Environment? Could be omitted if not required; but it's substantive. Could be included under Schedule? Not ideal. Maybe we can add a section "Work Environment" but not in examples. However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could incorporate Work Environment into Schedule or About the role. Probably better to add a separate section "Work Environment" as it's substantive. But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies examples, not exclusive. So we can add other headings if needed. However to be safe, we could add Work Environment as a heading.
But we must not create thin sections. Work Environment has a paragraph: "This job operates in an office setting." That's thin but still substantive. Could be merged into Schedule? Not ideal. Could be added as a paragraph under Schedule? Might be okay.
Alternatively we could add a section "Work Environment" with that paragraph.
Given the instruction to prefer a few substantive sections over many thin ones, maybe we should avoid a separate thin section. We'll incorporate it into Schedule or About the role.
Let's incorporate Work Environment into Schedule: after hours paragraph, add sentence about office setting.
Thus Schedule section will have two paragraphs: one about position type/hours, one about work environment and travel.
Now we need to ensure we removed boilerplate: AAP/EEO Statement, maybe also "Our Firmware" is not boilerplate but could be considered company culture; we could incorporate into About the role as well. But it's quite long; we could include as a paragraph under About the role after company overview. That preserves info.
Thus About the role will contain:
- Company Overview paragraph(s)
- Group Overview paragraph(s)
- Position Summary paragraph
- Our Firmware paragraph(s) (maybe summarizing? But we must preserve all substantive information, not summarize away detail. We cannot summarize; we must keep the detail. So we need to include the Firmware description verbatim? That's a lot of text but it's substantive. We'll include it as a paragraph.
Thus About the role will be long but okay.
Now Responsibilities: list items from "What You'll Do". Let's extract:
- Lead ISR program planning and execution, including deployment stand-ups and spoke operations
- Coordinate with government and industry stakeholders to ensure mission success
- Manage program schedules, budgets, and deliverables in compliance with contract requirements
- Support proposal development and contract modifications
- Oversee operational readiness and sustainment of ISR platforms
- CONUS Travel required (50%)
Note: The last item is travel; but we already have travel in Schedule. Might duplicate. We could keep it in Responsibilities as it's a duty. But we should not duplicate lines? The instruction says remove duplicated lines. The travel appears both in What You'll Do and later under Travel. It's duplicated. We should keep only one instance. Since travel is more of a schedule/logistics, we could keep it under Schedule and remove from Responsibilities. But we need to preserve all substantive information; removing it would lose info. However we can keep it in either place but not duplicate. Let's keep it under Schedule (as travel requirement) and remove from Responsibilities list. That way we avoid duplication.
Thus Responsibilities list will have first five items.
Now Requirements: list items from What You Bring and Additional Eligibility Qualifications and Security Clearance.
What You Bring items:
- 6-12 years of experience in manned airborne ISR operations management
- Strong knowledge of U.S. government contracting and acquisition processes
- Proficiency in Microsoft Office tools (Word, Excel, PowerPoint, Project)
- Experience with ISR deployment stand-ups and spoke operations
- Familiarity with operational planning tools and mission management systems
- Strong leadership, communication, and stakeholder engagement skills
- PMP and/or DAU Certification (waived with experience in lieu of on a case-by-case basis)
Additional Eligibility Qualifications:
- Valid U.S. passport and driver’s license
- BS in Engineering, Business Administration, or similar discipline (waived with experience in lieu of on a case-by-case basis)
Work Authorization / Security Clearance:
- Top Secret with SCI Eligibility
We should keep each as separate list items.
Now Benefits list: extract from Benefits paragraph:
- Comprehensive medical plan options
- HSA/FSA accounts
- Dental and vision coverage
- 6% employer 401(k) match
- Fully paid parental leave for all new parents
- Generous PTO
- Life and disability insurance
- Long-term and Short-term disability coverage
- AD&D Coverage
- Pet Insurance
- Employee Assistance Program
- Subsidized gym membership / plans through Wellhub
Note: "Generous PTOLife" seems a typo; we keep as "Generous PTO". Also "Life and disability insurance" separate from "Long-term and Short-term disability coverage". We'll keep as separate items.
Now Schedule section: include:
- Position Type and Expected Hours of Work: "This is a full-time non-exempt position with typical working hours of Monday through Friday, 9:00 a.m. to 6:00 p.m. Hours and work shifts may change in accordance with department and business needs. Exempt Employees must have the ability to be on-call and available, as business needs require."
- Work Environment: "This job operates in an office setting."
- Travel: "Travel Yes, 50% CONUS"
We could combine into two paragraphs: first paragraph about position type/hours, second about work environment and travel.
Now we need to ensure we didn't include any boilerplate like EEO, etc. Also remove "Position Type and Expected Hours of Work" heading as we are using Schedule heading.
Now produce HTML fragment.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll output:
About the role
Company overview paragraph(s)...
Group overview paragraph(s)...
Position summary paragraph...
Our Firmware paragraph(s)...
Then Responsibilities ul.
Then Requirements ul.
Then Benefits ul.
Then Schedule p's.
Make sure no extra whitespace? It's fine.
Now let's write the paragraphs exactly as in source, preserving detail.
Company Overview:
"Metrea delivers effects-as-a-service to national security partners across five domains and more than a dozen mission areas. These include airborne ISR, electronic warfare, secure communications, aerial refueling, special air missions, aerial firefighting,
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Schedule section for hours and travel. We'll include Schedule.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the AAP/EEO Statement, maybe also "Work Authorization / Security Clearance" is substantive? It says Top Secret with SCI Eligibility - that's a requirement, so keep. The EEO statement is boilerplate, remove.
Also remove "Our Firmware" maybe not needed but it's substantive description of company culture; could be included under About the role? But we have Company Overview and Group Overview already. We could include a section "About the role" maybe summarizing Position Summary? Actually About the role could be Position Summary. We'll map:
- About the role: Position Summary paragraph.
- Responsibilities: What You'll Do (list)
- Requirements: What You Bring (list) plus Additional Eligibility Qualifications (list) maybe combine? Could separate Requirements and Qualifications? The instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide.
We have: What You Bring includes experience, knowledge, proficiency, experience with deployment, familiarity with tools, leadership skills, PMP/DAU certification. Additional Eligibility Qualifications includes passport, driver's license, BS degree (waived). Also Work Authorization / Security Clearance (Top Secret with SCI). Those are requirements.
We could have:
- Requirements: What You Bring (list)
- Qualifications: Additional Eligibility Qualifications (list) plus Security Clearance (maybe as part of Qualifications)
- Skills: maybe not separate; we could embed skills in Requirements.
But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section "Requirements". But instruction says we can use those headings; we can choose to include only those with substantive content. Let's think: We have responsibilities list, we have requirements list (experience, knowledge, proficiency, familiarity, leadership, certification). We have additional eligibility (passport, driver's license, degree). We have security clearance. We have benefits list. We have schedule (hours, travel). We have company overview and group overview maybe as About the role? Actually About the role could be Position Summary plus maybe Company Overview? But we should not duplicate.
We need to preserve all substantive information. So we need to include Company Overview and Group Overview somewhere. Could be under "About the role" or maybe a separate section "About the company". But the instruction only gave examples of headings; we can use other headings? It 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 those. Safer to stick to those. So we need to map company overview and group overview into About the role? Possibly About the role can include a brief description of the team and role. But we must preserve all substantive information; we cannot omit company overview. So we need to include it somewhere. Perhaps we can treat Company Overview and Group Overview as part of "About the role" (the role within the company). We'll include paragraphs under About the role that contain that info.
Thus:
About the role
Company overview paragraph(s) + Group overview paragraph(s) + Position summary paragraph.
Then Responsibilities: Responsibilities
- ...
Requirements: Requirements
- ...
(including What You Bring and Additional Eligibility Qualifications and Security Clearance)
Benefits: Benefits
- ...
Schedule: Schedule
Position Type and Expected Hours of Work paragraph + Travel paragraph.
We must not include Pay.
We must not include Work Environment? Could be omitted if not required; but it's substantive. Could be included under Schedule? Not ideal. Maybe we can add a section "Work Environment" but not in examples. However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could incorporate Work Environment into Schedule or About the role. Probably better to add a separate section "Work Environment" as it's substantive. But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies examples, not exclusive. So we can add other headings if needed. However to be safe, we could add Work Environment as a heading.
But we must not create thin sections. Work Environment has a paragraph: "This job operates in an office setting." That's thin but still substantive. Could be merged into Schedule? Not ideal. Could be added as a paragraph under Schedule? Might be okay.
Alternatively we could add a section "Work Environment" with that paragraph.
Given the instruction to prefer a few substantive sections over many thin ones, maybe we should avoid a separate thin section. We'll incorporate it into Schedule or About the role.
Let's incorporate Work Environment into Schedule: after hours paragraph, add sentence about office setting.
Thus Schedule section will have two paragraphs: one about position type/hours, one about work environment and travel.
Now we need to ensure we removed boilerplate: AAP/EEO Statement, maybe also "Our Firmware" is not boilerplate but could be considered company culture; we could incorporate into About the role as well. But it's quite long; we could include as a paragraph under About the role after company overview. That preserves info.
Thus About the role will contain:
- Company Overview paragraph(s)
- Group Overview paragraph(s)
- Position Summary paragraph
- Our Firmware paragraph(s) (maybe summarizing? But we must preserve all substantive information, not summarize away detail. We cannot summarize; we must keep the detail. So we need to include the Firmware description verbatim? That's a lot of text but it's substantive. We'll include it as a paragraph.
Thus About the role will be long but okay.
Now Responsibilities: list items from "What You'll Do". Let's extract:
- Lead ISR program planning and execution, including deployment stand-ups and spoke operations
- Coordinate with government and industry stakeholders to ensure mission success
- Manage program schedules, budgets, and deliverables in compliance with contract requirements
- Support proposal development and contract modifications
- Oversee operational readiness and sustainment of ISR platforms
- CONUS Travel required (50%)
Note: The last item is travel; but we already have travel in Schedule. Might duplicate. We could keep it in Responsibilities as it's a duty. But we should not duplicate lines? The instruction says remove duplicated lines. The travel appears both in What You'll Do and later under Travel. It's duplicated. We should keep only one instance. Since travel is more of a schedule/logistics, we could keep it under Schedule and remove from Responsibilities. But we need to preserve all substantive information; removing it would lose info. However we can keep it in either place but not duplicate. Let's keep it under Schedule (as travel requirement) and remove from Responsibilities list. That way we avoid duplication.
Thus Responsibilities list will have first five items.
Now Requirements: list items from What You Bring and Additional Eligibility Qualifications and Security Clearance.
What You Bring items:
- 6-12 years of experience in manned airborne ISR operations management
- Strong knowledge of U.S. government contracting and acquisition processes
- Proficiency in Microsoft Office tools (Word, Excel, PowerPoint, Project)
- Experience with ISR deployment stand-ups and spoke operations
- Familiarity with operational planning tools and mission management systems
- Strong leadership, communication, and stakeholder engagement skills
- PMP and/or DAU Certification (waived with experience in lieu of on a case-by-case basis)
Additional Eligibility Qualifications:
- Valid U.S. passport and driver’s license
- BS in Engineering, Business Administration, or similar discipline (waived with experience in lieu of on a case-by-case basis)
Work Authorization / Security Clearance:
- Top Secret with SCI Eligibility
We should keep each as separate list items.
Now Benefits list: extract from Benefits paragraph:
- Comprehensive medical plan options
- HSA/FSA accounts
- Dental and vision coverage
- 6% employer 401(k) match
- Fully paid parental leave for all new parents
- Generous PTO
- Life and disability insurance
- Long-term and Short-term disability coverage
- AD&D Coverage
- Pet Insurance
- Employee Assistance Program
- Subsidized gym membership / plans through Wellhub
Note: "Generous PTOLife" seems a typo; we keep as "Generous PTO". Also "Life and disability insurance" separate from "Long-term and Short-term disability coverage". We'll keep as separate items.
Now Schedule section: include:
- Position Type and Expected Hours of Work: "This is a full-time non-exempt position with typical working hours of Monday through Friday, 9:00 a.m. to 6:00 p.m. Hours and work shifts may change in accordance with department and business needs. Exempt Employees must have the ability to be on-call and available, as business needs require."
- Work Environment: "This job operates in an office setting."
- Travel: "Travel Yes, 50% CONUS"
We could combine into two paragraphs: first paragraph about position type/hours, second about work environment and travel.
Now we need to ensure we didn't include any boilerplate like EEO, etc. Also remove "Position Type and Expected Hours of Work" heading as we are using Schedule heading.
Now produce HTML fragment.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll output:
About the role
Company overview paragraph(s)...
Group overview paragraph(s)...
Position summary paragraph...
Our Firmware paragraph(s)...
Then Responsibilities ul.
Then Requirements ul.
Then Benefits ul.
Then Schedule p's.
Make sure no extra whitespace? It's fine.
Now let's write the paragraphs exactly as in source, preserving detail.
Company Overview:
"Metrea delivers effects-as-a-service to national security partners across five domains and more than a dozen mission areas. These include airborne ISR, electronic warfare, secure communications, aerial refueling, special air missions, aerial firefighting,
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the AAP/EEO Statement, maybe also "Work Authorization / Security Clearance" is substantive? It says Top Secret with SCI Eligibility - that's a requirement, so keep. The EEO statement is boilerplate, remove. Also remove "Our Firmware" maybe not needed but it's substantive description of company culture; could be included under About the role? But we have Company Overview and Group Overview already. We could include a section "About the role" maybe summarizing Position Summary? Actually About the role could be Position Summary. We'll map: - About the role: Position Summary paragraph. - Responsibilities: What You'll Do (list) - Requirements: What You Bring (list) plus Additional Eligibility Qualifications (list) maybe combine? Could separate Requirements and Qualifications? The instruction says we can use headings like Requirements, Qualifications, Skills. We need to decide. We have: What You Bring includes experience, knowledge, proficiency, experience with deployment, familiarity with tools, leadership skills, PMP/DAU certification. Additional Eligibility Qualifications includes passport, driver's license, BS degree (waived). Also Work Authorization / Security Clearance (Top Secret with SCI). Those are requirements. We could have: - Requirements: What You Bring (list) - Qualifications: Additional Eligibility Qualifications (list) plus Security Clearance (maybe as part of Qualifications) - Skills: maybe not separate; we could embed skills in Requirements. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section "Requirements". But instruction says we can use those headings; we can choose to include only those with substantive content. Let's think: We have responsibilities list, we have requirements list (experience, knowledge, proficiency, familiarity, leadership, certification). We have additional eligibility (passport, driver's license, degree). We have security clearance. We have benefits list. We have schedule (hours, travel). We have company overview and group overview maybe as About the role? Actually About the role could be Position Summary plus maybe Company Overview? But we should not duplicate. We need to preserve all substantive information. So we need to include Company Overview and Group Overview somewhere. Could be under "About the role" or maybe a separate section "About the company". But the instruction only gave examples of headings; we can use other headings? It 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 those. Safer to stick to those. So we need to map company overview and group overview into About the role? Possibly About the role can include a brief description of the team and role. But we must preserve all substantive information; we cannot omit company overview. So we need to include it somewhere. Perhaps we can treat Company Overview and Group Overview as part of "About the role" (the role within the company). We'll include paragraphs under About the role that contain that info.
Thus:
About the role
Company overview paragraph(s) + Group overview paragraph(s) + Position summary paragraph.
Then Responsibilities:Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Schedule
Position Type and Expected Hours of Work paragraph + Travel paragraph.
We must not include Pay. We must not include Work Environment? Could be omitted if not required; but it's substantive. Could be included under Schedule? Not ideal. Maybe we can add a section "Work Environment" but not in examples. However instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could incorporate Work Environment into Schedule or About the role. Probably better to add a separate section "Work Environment" as it's substantive. But the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies examples, not exclusive. So we can add other headings if needed. However to be safe, we could add Work Environment as a heading.
But we must not create thin sections. Work Environment has a paragraph: "This job operates in an office setting." That's thin but still substantive. Could be merged into Schedule? Not ideal. Could be added as a paragraph under Schedule? Might be okay.
Alternatively we could add a section "Work Environment" with that paragraph.
Given the instruction to prefer a few substantive sections over many thin ones, maybe we should avoid a separate thin section. We'll incorporate it into Schedule or About the role.
Let's incorporate Work Environment into Schedule: after hours paragraph, add sentence about office setting.
Thus Schedule section will have two paragraphs: one about position type/hours, one about work environment and travel.
Now we need to ensure we removed boilerplate: AAP/EEO Statement, maybe also "Our Firmware" is not boilerplate but could be considered company culture; we could incorporate into About the role as well. But it's quite long; we could include as a paragraph under About the role after company overview. That preserves info.
Thus About the role will contain:
- Company Overview paragraph(s)
- Group Overview paragraph(s)
- Position Summary paragraph
- Our Firmware paragraph(s) (maybe summarizing? But we must preserve all substantive information, not summarize away detail. We cannot summarize; we must keep the detail. So we need to include the Firmware description verbatim? That's a lot of text but it's substantive. We'll include it as a paragraph.
Thus About the role will be long but okay.
Now Responsibilities: list items from "What You'll Do". Let's extract:
- Lead ISR program planning and execution, including deployment stand-ups and spoke operations
- Coordinate with government and industry stakeholders to ensure mission success
- Manage program schedules, budgets, and deliverables in compliance with contract requirements
- Support proposal development and contract modifications
- Oversee operational readiness and sustainment of ISR platforms
- CONUS Travel required (50%)
Note: The last item is travel; but we already have travel in Schedule. Might duplicate. We could keep it in Responsibilities as it's a duty. But we should not duplicate lines? The instruction says remove duplicated lines. The travel appears both in What You'll Do and later under Travel. It's duplicated. We should keep only one instance. Since travel is more of a schedule/logistics, we could keep it under Schedule and remove from Responsibilities. But we need to preserve all substantive information; removing it would lose info. However we can keep it in either place but not duplicate. Let's keep it under Schedule (as travel requirement) and remove from Responsibilities list. That way we avoid duplication.
Thus Responsibilities list will have first five items.
Now Requirements: list items from What You Bring and Additional Eligibility Qualifications and Security Clearance.
What You Bring items:
- 6-12 years of experience in manned airborne ISR operations management
- Strong knowledge of U.S. government contracting and acquisition processes
- Proficiency in Microsoft Office tools (Word, Excel, PowerPoint, Project)
- Experience with ISR deployment stand-ups and spoke operations
- Familiarity with operational planning tools and mission management systems
- Strong leadership, communication, and stakeholder engagement skills
- PMP and/or DAU Certification (waived with experience in lieu of on a case-by-case basis)
Additional Eligibility Qualifications:
- Valid U.S. passport and driver’s license
- BS in Engineering, Business Administration, or similar discipline (waived with experience in lieu of on a case-by-case basis)
Work Authorization / Security Clearance:
- Top Secret with SCI Eligibility
We should keep each as separate list items.
Now Benefits list: extract from Benefits paragraph:
- Comprehensive medical plan options
- HSA/FSA accounts
- Dental and vision coverage
- 6% employer 401(k) match
- Fully paid parental leave for all new parents
- Generous PTO
- Life and disability insurance
- Long-term and Short-term disability coverage
- AD&D Coverage
- Pet Insurance
- Employee Assistance Program
- Subsidized gym membership / plans through Wellhub
Note: "Generous PTOLife" seems a typo; we keep as "Generous PTO". Also "Life and disability insurance" separate from "Long-term and Short-term disability coverage". We'll keep as separate items.
Now Schedule section: include:
- Position Type and Expected Hours of Work: "This is a full-time non-exempt position with typical working hours of Monday through Friday, 9:00 a.m. to 6:00 p.m. Hours and work shifts may change in accordance with department and business needs. Exempt Employees must have the ability to be on-call and available, as business needs require."
- Work Environment: "This job operates in an office setting."
- Travel: "Travel Yes, 50% CONUS"
We could combine into two paragraphs: first paragraph about position type/hours, second about work environment and travel.
Now we need to ensure we didn't include any boilerplate like EEO, etc. Also remove "Position Type and Expected Hours of Work" heading as we are using Schedule heading.
Now produce HTML fragment.
Let's craft.
We'll need to escape any HTML special characters? Not needed.
We'll output:
About the role
About the role
Company overview paragraph(s)...
Group overview paragraph(s)...
Position summary paragraph...
Our Firmware paragraph(s)...
Then Responsibilities ul. Then Requirements ul. Then Benefits ul. Then Schedule p's. Make sure no extra whitespace? It's fine. Now let's write the paragraphs exactly as in source, preserving detail. Company Overview: "Metrea delivers effects-as-a-service to national security partners across five domains and more than a dozen mission areas. These include airborne ISR, electronic warfare, secure communications, aerial refueling, special air missions, aerial firefighting,