Software Developer (DAPS)-Journeyman
AMEWAS · Patuxent River, MD · 1 mo ago
On-siteEngineering$105k–$175k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role? Actually the posting includes "About the location", "Position Background", "Must-haves", "Desired Skills", "Security Clearance Requirement Disclaimer", "Employment Eligibility and Sponsorship Disclaimer", "Skills Crucial To Success At AMEWAS", "Physical Environment And Working Conditions", "Our Excellent Benefits And Perks". Also there is a salary range and note about remote work. We need to include Pay section only if posting actually states them. Salary range is given: $105,200.00 - $175,000.00 and is commensurate with experience. The rule: 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. The salary range is stated, so we can include Pay section with that range. However we must avoid filler like "commensurate with experience". We could include the range and maybe note that it's commensurate with experience? That is filler? The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So if we include Pay section, we must not just put "commensurate with experience". We could include the range and maybe omit the phrase. The posting says: "The salary range of this position is $105,200.00 - $175,000.00 and is commensurate with experience." We could keep the range and maybe drop the phrase. That's acceptable.
Schedule: The posting says "This position is not eligible for remote work; on-site support is required." That's schedule/location info. Could be Schedule section? The rule: create Schedule section only if posting actually states them. It does state on-site requirement. Could include Schedule section with that note. However we need to avoid filler like "not specified". It's fine.
Benefits: There's a section "Our Excellent Benefits And Perks" with list. So include Benefits.
We need to use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings.
We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc.
We need to decide which sections to include: About the role? There's a paragraph "The Position AMEWAS is seeking a highly motivated and talented Software Developer (DAPS)-Journeyman to support Advanced Aircraft Research, Development, Test & Evaluation." That's like About the role. Could be a section "About the role". Also there is "Position Background". Could combine? But we should follow headings as they appear: "About the location", "Position Background", maybe "About the role" not present as heading but we could create one? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We can create sections based on content we have, not necessarily exactly matching headings in posting, but we should use the headings given in the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings if we have content. If we don't have content for a heading, we should not include it.
Thus we need to map content to these headings.
- About the role: we have introductory paragraph about the role: "The Position AMEWAS is seeking a highly motivated and talented Software Developer (DAPS)-Journeyman to support Advanced Aircraft Research, Development, Test & Evaluation." Also maybe the first paragraph about AMEWAS mission. That could be About the role.
- Responsibilities: we have a list of typical day activities under "A typical day as a Software Developer (DAPS)-Journeyman may include:" followed by many items. Those are responsibilities/duties. So we can put those under Responsibilities as a .
- Requirements: we have "Must-haves" list. That's requirements. Also maybe "Minimum clearance required". Could be part of Requirements.
- Qualifications: maybe education and experience? Could be separate but we could combine with Requirements. However we have both Must-haves (which includes degree, experience, proficiencies) and Desired Skills. Could treat Must-haves as Requirements, Desired Skills as Skills. Qualifications maybe not needed separately.
- Skills: we have Desired Skills list.
- Benefits: we have "Our Excellent Benefits And Perks" list.
- Pay: we have salary range.
- Schedule: we have on-site requirement.
We also have other sections like "Physical Environment And Working Conditions", "Security Clearance Requirement Disclaimer", "Employment Eligibility and Sponsorship Disclaimer", "Skills Crucial To Success At AMEWAS". Those are not in the prescribed headings list but we could still include them as h3? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely we should stick to those headings only. However we need to preserve ALL substantive information. If we omit sections like Physical Environment, Security Clearance, Employment Eligibility, Skills Crucial To Success, we would lose info. So we need to include them somehow. Perhaps we can incorporate them under existing headings: e.g., Physical Environment could be part of About the role or Responsibilities? But it's not exactly duties. Could be a separate section but we need a heading. The instruction didn't say we cannot add other headings; it gave examples. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use h3 for any section headings, and those are examples. So we can add other headings like "Physical Environment", "Security Clearance", "Employment Eligibility", "Skills Crucial To Success". That seems okay.
We must not include boilerplate like EEO, legal, etc. Remove those.
We must not include duplicated lines.
We must not include application instructions, referral, etc.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate.
Thus we need to strip out:
- "At AMEWAS, we don’t just support defense- we shape it..." That's introductory but maybe part of About the role? It's substantive about company mission. Keep.
- "For over 40 years, we’ve been a trusted partner..." Keep.
- "Our people are the heart of our mission..." Keep.
- "Across our headquarters..." Keep.
- "If you're ready to grow your skills..." Keep maybe as part of About the role.
- "Come do work that matters. Join AMEWAS." Could be considered promotional but still substantive? Might be considered boilerplate? It's a call to action. Might be considered application instruction? Not exactly. Safer to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those. It's a tagline. I'd keep it as part of About the role.
- "The Position AMEWAS is seeking..." Keep.
- Salary range line.
- "This position is not eligible for remote work; on-site support is required." Keep for Schedule.
- "About the location: Patuxent River, MD..." Keep maybe as About the location but we don't have a heading for location; could be part of About the role or Schedule? Might be separate section "Location". Not in examples but we could add.
- "To learn more about the surrounding area, please visit: www.visitstmarysmd.com" That's a link; maybe consider as navigation? It's external link. Might be considered boilerplate? It's not legal/EEO. Could keep as a p with link? But we should avoid navigation? It's not navigation. Might keep.
- "Position Background" heading and its content: keep.
- The typical day list: keep.
- "Must-haves" heading and list: keep as Requirements.
- "Desired Skills" heading and list: keep as Skills.
- "Security Clearance Requirement Disclaimer": keep maybe as Security Clearance.
- "Employment Eligibility and Sponsorship Disclaimer": keep as Employment Eligibility.
- "Skills Crucial To Success At AMEWAS": keep as Skills Crucial To Success.
- "Physical Environment And Working Conditions": keep as Physical Environment.
- "Refer a Friend": that's referral program; maybe consider as referral bonus? It's a perk but also referral instruction. Could be considered part of Benefits? It's a referral bonus. Might keep under Benefits? But we already have Benefits list. Could add a bullet for referral bonus. However the instruction says remove application instructions. Refer a Friend is not exactly application instruction but could be considered a perk. I'd keep it under Benefits maybe as a bullet.
- "Our Excellent Benefits And Perks": keep as Benefits.
- The list of benefits: keep.
- EEO statement: remove.
- Regulatory Notices page: remove.
- Contact Recruiting department: that's application instruction; remove.
- AMEWAS participates in E-Verify: maybe legal? Could be considered boilerplate; remove.
- Note about unsolicited resumes: remove.
Now we need to output HTML fragment.
We'll structure:
About the role
Introductory paragraphs about AMEWAS mission and the role.
Responsibilities
- ... each duty
Requirements
- Must-haves items
Maybe also include clearance requirement under Requirements? Could add a bullet.
Qualifications
Maybe we can include education/experience but already in Must-haves. Could skip Qualifications if no extra content. But we have degree and experience in Must-haves. Could treat Must-haves as Requirements and Qualifications as same? Might be okay to omit Qualifications heading if no distinct content. But we need to preserve all substantive info; the info is already in Requirements. So we can omit Qualifications heading.
Skills
- Desired Skills items
Benefits
- Benefits items
Pay
$105,200.00 - $175,000.00
Schedule
On-site support required; not eligible for remote work.
Location
Patuxent River, MD, located in the California-Lexington Park area.
To learn more about the surrounding area, please visit: www.visitstmarysmd.com
Position Background
Content.
Security Clearance
Minimum clearance required to apply: N/A (candidates who do not currently hold the required clearance will not be considered). Current clearance required upon onboarding: DoD Secret Clearance. Additional Accesses: The ability to obtain and maintain the DoD security clearance eligibility and/or additional security access requirements necessary to perform the duties
for prose. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to decide which sections to include: About the role? There's a paragraph "The Position AMEWAS is seeking a highly motivated and talented Software Developer (DAPS)-Journeyman to support Advanced Aircraft Research, Development, Test & Evaluation." That's like About the role. Could be a section "About the role". Also there is "Position Background". Could combine? But we should follow headings as they appear: "About the location", "Position Background", maybe "About the role" not present as heading but we could create one? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. We can create sections based on content we have, not necessarily exactly matching headings in posting, but we should use the headings given in the list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings if we have content. If we don't have content for a heading, we should not include it.
Thus we need to map content to these headings.
- About the role: we have introductory paragraph about the role: "The Position AMEWAS is seeking a highly motivated and talented Software Developer (DAPS)-Journeyman to support Advanced Aircraft Research, Development, Test & Evaluation." Also maybe the first paragraph about AMEWAS mission. That could be About the role.
- Responsibilities: we have a list of typical day activities under "A typical day as a Software Developer (DAPS)-Journeyman may include:" followed by many items. Those are responsibilities/duties. So we can put those under Responsibilities as a .
- Requirements: we have "Must-haves" list. That's requirements. Also maybe "Minimum clearance required". Could be part of Requirements.
- Qualifications: maybe education and experience? Could be separate but we could combine with Requirements. However we have both Must-haves (which includes degree, experience, proficiencies) and Desired Skills. Could treat Must-haves as Requirements, Desired Skills as Skills. Qualifications maybe not needed separately.
- Skills: we have Desired Skills list.
- Benefits: we have "Our Excellent Benefits And Perks" list.
- Pay: we have salary range.
- Schedule: we have on-site requirement.
We also have other sections like "Physical Environment And Working Conditions", "Security Clearance Requirement Disclaimer", "Employment Eligibility and Sponsorship Disclaimer", "Skills Crucial To Success At AMEWAS". Those are not in the prescribed headings list but we could still include them as h3? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely we should stick to those headings only. However we need to preserve ALL substantive information. If we omit sections like Physical Environment, Security Clearance, Employment Eligibility, Skills Crucial To Success, we would lose info. So we need to include them somehow. Perhaps we can incorporate them under existing headings: e.g., Physical Environment could be part of About the role or Responsibilities? But it's not exactly duties. Could be a separate section but we need a heading. The instruction didn't say we cannot add other headings; it gave examples. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use h3 for any section headings, and those are examples. So we can add other headings like "Physical Environment", "Security Clearance", "Employment Eligibility", "Skills Crucial To Success". That seems okay.
We must not include boilerplate like EEO, legal, etc. Remove those.
We must not include duplicated lines.
We must not include application instructions, referral, etc.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate.
Thus we need to strip out:
- "At AMEWAS, we don’t just support defense- we shape it..." That's introductory but maybe part of About the role? It's substantive about company mission. Keep.
- "For over 40 years, we’ve been a trusted partner..." Keep.
- "Our people are the heart of our mission..." Keep.
- "Across our headquarters..." Keep.
- "If you're ready to grow your skills..." Keep maybe as part of About the role.
- "Come do work that matters. Join AMEWAS." Could be considered promotional but still substantive? Might be considered boilerplate? It's a call to action. Might be considered application instruction? Not exactly. Safer to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those. It's a tagline. I'd keep it as part of About the role.
- "The Position AMEWAS is seeking..." Keep.
- Salary range line.
- "This position is not eligible for remote work; on-site support is required." Keep for Schedule.
- "About the location: Patuxent River, MD..." Keep maybe as About the location but we don't have a heading for location; could be part of About the role or Schedule? Might be separate section "Location". Not in examples but we could add.
- "To learn more about the surrounding area, please visit: www.visitstmarysmd.com" That's a link; maybe consider as navigation? It's external link. Might be considered boilerplate? It's not legal/EEO. Could keep as a p with link? But we should avoid navigation? It's not navigation. Might keep.
- "Position Background" heading and its content: keep.
- The typical day list: keep.
- "Must-haves" heading and list: keep as Requirements.
- "Desired Skills" heading and list: keep as Skills.
- "Security Clearance Requirement Disclaimer": keep maybe as Security Clearance.
- "Employment Eligibility and Sponsorship Disclaimer": keep as Employment Eligibility.
- "Skills Crucial To Success At AMEWAS": keep as Skills Crucial To Success.
- "Physical Environment And Working Conditions": keep as Physical Environment.
- "Refer a Friend": that's referral program; maybe consider as referral bonus? It's a perk but also referral instruction. Could be considered part of Benefits? It's a referral bonus. Might keep under Benefits? But we already have Benefits list. Could add a bullet for referral bonus. However the instruction says remove application instructions. Refer a Friend is not exactly application instruction but could be considered a perk. I'd keep it under Benefits maybe as a bullet.
- "Our Excellent Benefits And Perks": keep as Benefits.
- The list of benefits: keep.
- EEO statement: remove.
- Regulatory Notices page: remove.
- Contact Recruiting department: that's application instruction; remove.
- AMEWAS participates in E-Verify: maybe legal? Could be considered boilerplate; remove.
- Note about unsolicited resumes: remove.
Now we need to output HTML fragment.
We'll structure:
About the role
Introductory paragraphs about AMEWAS mission and the role.
Responsibilities
- ... each duty
Requirements
- Must-haves items
Maybe also include clearance requirement under Requirements? Could add a bullet.
Qualifications
Maybe we can include education/experience but already in Must-haves. Could skip Qualifications if no extra content. But we have degree and experience in Must-haves. Could treat Must-haves as Requirements and Qualifications as same? Might be okay to omit Qualifications heading if no distinct content. But we need to preserve all substantive info; the info is already in Requirements. So we can omit Qualifications heading.
Skills
- Desired Skills items
Benefits
- Benefits items
Pay
$105,200.00 - $175,000.00
Schedule
On-site support required; not eligible for remote work.
Location
Patuxent River, MD, located in the California-Lexington Park area.
To learn more about the surrounding area, please visit: www.visitstmarysmd.com
Position Background
Content.
Security Clearance
Minimum clearance required to apply: N/A (candidates who do not currently hold the required clearance will not be considered). Current clearance required upon onboarding: DoD Secret Clearance. Additional Accesses: The ability to obtain and maintain the DoD security clearance eligibility and/or additional security access requirements necessary to perform the duties
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use h3 for any section headings, and those are examples. So we can add other headings like "Physical Environment", "Security Clearance", "Employment Eligibility", "Skills Crucial To Success". That seems okay.
We must not include boilerplate like EEO, legal, etc. Remove those.
We must not include duplicated lines.
We must not include application instructions, referral, etc.
We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate.
Thus we need to strip out:
- "At AMEWAS, we don’t just support defense- we shape it..." That's introductory but maybe part of About the role? It's substantive about company mission. Keep.
- "For over 40 years, we’ve been a trusted partner..." Keep.
- "Our people are the heart of our mission..." Keep.
- "Across our headquarters..." Keep.
- "If you're ready to grow your skills..." Keep maybe as part of About the role.
- "Come do work that matters. Join AMEWAS." Could be considered promotional but still substantive? Might be considered boilerplate? It's a call to action. Might be considered application instruction? Not exactly. Safer to keep? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those. It's a tagline. I'd keep it as part of About the role.
- "The Position AMEWAS is seeking..." Keep.
- Salary range line.
- "This position is not eligible for remote work; on-site support is required." Keep for Schedule.
- "About the location: Patuxent River, MD..." Keep maybe as About the location but we don't have a heading for location; could be part of About the role or Schedule? Might be separate section "Location". Not in examples but we could add.
- "To learn more about the surrounding area, please visit: www.visitstmarysmd.com" That's a link; maybe consider as navigation? It's external link. Might be considered boilerplate? It's not legal/EEO. Could keep as a p with link? But we should avoid navigation? It's not navigation. Might keep.
- "Position Background" heading and its content: keep.
- The typical day list: keep.
- "Must-haves" heading and list: keep as Requirements.
- "Desired Skills" heading and list: keep as Skills.
- "Security Clearance Requirement Disclaimer": keep maybe as Security Clearance.
- "Employment Eligibility and Sponsorship Disclaimer": keep as Employment Eligibility.
- "Skills Crucial To Success At AMEWAS": keep as Skills Crucial To Success.
- "Physical Environment And Working Conditions": keep as Physical Environment.
- "Refer a Friend": that's referral program; maybe consider as referral bonus? It's a perk but also referral instruction. Could be considered part of Benefits? It's a referral bonus. Might keep under Benefits? But we already have Benefits list. Could add a bullet for referral bonus. However the instruction says remove application instructions. Refer a Friend is not exactly application instruction but could be considered a perk. I'd keep it under Benefits maybe as a bullet.
- "Our Excellent Benefits And Perks": keep as Benefits.
- The list of benefits: keep.
- EEO statement: remove.
- Regulatory Notices page: remove.
- Contact Recruiting department: that's application instruction; remove.
- AMEWAS participates in E-Verify: maybe legal? Could be considered boilerplate; remove.
- Note about unsolicited resumes: remove.
Now we need to output HTML fragment.
We'll structure:
About the role
Introductory paragraphs about AMEWAS mission and the role.
Responsibilities
- ... each duty
Requirements
- Must-haves items
Qualifications
Maybe we can include education/experience but already in Must-haves. Could skip Qualifications if no extra content. But we have degree and experience in Must-haves. Could treat Must-haves as Requirements and Qualifications as same? Might be okay to omit Qualifications heading if no distinct content. But we need to preserve all substantive info; the info is already in Requirements. So we can omit Qualifications heading.Skills
- Desired Skills items
Benefits
- Benefits items
Pay
$105,200.00 - $175,000.00
Schedule
On-site support required; not eligible for remote work.
Location
Patuxent River, MD, located in the California-Lexington Park area.
To learn more about the surrounding area, please visit: www.visitstmarysmd.com
Position Background
Content.
Security Clearance
Minimum clearance required to apply: N/A (candidates who do not currently hold the required clearance will not be considered). Current clearance required upon onboarding: DoD Secret Clearance. Additional Accesses: The ability to obtain and maintain the DoD security clearance eligibility and/or additional security access requirements necessary to perform the duties