Logistics lll IOD with Security Clearance
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. 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")
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the content:
- Pay Rate: "The annual base salary range for this position is TBD." This is placeholder text (TBD). According to rule 7, I should not create a Pay section for filler/placeholder text. So I should not include a Pay section.
- Position Location: Elizabeth City, North Carolina (On-Site) Telework/Work-from-Home Authorized: Yes - When Authorized/Hybrid. This is schedule/location info. Could be a Schedule section? The posting has specific content about location and telework. I could include a Schedule section with this info.
- About the Role: There's a description and then "Additional Responsibilities Include, but are not Limited To:" followed by a long list of bullet points. This should be split: About the role (prose) and Responsibilities (list).
- Experience Requirements: list of items.
- Education Requirements: one item.
- Other Required Skills & Abilities: list.
- Security Clearance Requirements: "? Public Trust" - unclear, but there is content.
- US Citizenship Requirements: prose.
- Benefits at Sawdey Solution Services: extensive list of benefits. This is real content, so include Benefits section.
- About the Organization: company description. Could be a section? The rules mention headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the Organization" is not in that list, but it's substantive. However, the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so other headings may be allowed. But the instruction: "include a section ONLY when the posting has real, specific content for it". The organization description is real content. I could include an "About the Organization" section. But the user might expect only the listed headings. However, the example includes "About the role". "About the Organization" is similar. I'll include it as a section.
- Why Choose Us?: list of points.
- Who We're Looking For: list.
- EOE Statement: boilerplate, remove.
- "This position is currently accepting applications." - application instruction, remove.
Now, I need to structure:
- Possibly a short
for location/telework metadata (since not a heading). But the rule says "fold minor metadata into a short
or drop it". Location and telework are not minor; they are important. Could create a Schedule section with that info. The posting has "Position Location" and "Telework/Work-from-Home Authorized". That's schedule info. I'll create a Schedule section.
- Pay: TBD, so skip.
- About the Role: There's a prose sentence: "Responsible for overseeing all aspects of the kitting process to support Programmed Depot Maintenance (PDM)." Then a list of additional responsibilities. I'll make an "About the Role" section with the prose, and a "Responsibilities" section with the list.
- Experience Requirements: list.
- Education Requirements: list (single item).
- Other Required Skills & Abilities: list.
- Security Clearance Requirements: could be part of Requirements or separate. The heading "Security Clearance Requirements" is specific. I'll include as a subsection maybe under Requirements? But the rule says use h3 for section headings. I could make a "Requirements" section that includes experience, education, skills, security clearance. However, the example headings include "Requirements" and "Qualifications" and "Skills". The posting has separate sections: Experience Requirements, Education Requirements, Other Required Skills & Abilities, Security Clearance Requirements, US Citizenship Requirements. I could combine into a "Requirements" section with sub-lists, but the rule says use
for section headings. I think it's okay to have multiple h3 headings for each requirement type. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one "Requirements" section with subheadings? But we cannot use h4? The rule only mentions h3 for section headings. Could use h3 for each? That would be many thin sections. Better to have a "Requirements" section with prose and lists. However, the posting has distinct categories. I'll create a "Requirements" section with subsections using ? Not allowed. The rule says use for section headings. It doesn't forbid h4, but the example only shows h3. I'll use h3 for each major category: "Experience Requirements", "Education Requirements", "Skills & Abilities", "Security Clearance", "Citizenship Requirements". But that's many. Alternatively, I can create a "Requirements" h3 and then use
and
for each category. That might be better.
Let's see the example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So "Requirements" is a heading. "Qualifications" and "Skills" are separate. The posting has "Experience Requirements", "Education Requirements", "Other Required Skills & Abilities". Those could fall under "Requirements" and "Skills". I'll create:
- Requirements (h3) with sub-lists for Experience, Education.
- Skills (h3) for Other Required Skills & Abilities.
- Security Clearance (h3) maybe separate? But it's a requirement. Could be under Requirements.
But the rule: "include a section ONLY when the posting has real, specific content for it". Each has content. I'll create:
- About the Role (h3)
- Responsibilities (h3)
- Requirements (h3) with Experience and Education
- Skills (h3) with Other Required Skills & Abilities
- Security Clearance (h3) maybe? The content is "? Public Trust". That's thin. Might include as a short p.
- Citizenship Requirements (h3) maybe.
But that's many. Let's combine: "Requirements" section includes Experience, Education, Security Clearance, Citizenship. "Skills" section for Other Required Skills & Abilities.
Benefits section: yes.
Schedule section: location and telework.
About the Organization: maybe include as "About the Organization" h3.
Why Choose Us and Who We're Looking For: could be part of About the Organization or separate. They are marketing fluff but still content. The rule says preserve ALL substantive information. I'll include them as subsections under About the Organization or separate sections. But to avoid many thin sections, I'll include them as part of About the Organization with lists.
Now, let's draft HTML.
First, a short p for metadata? The job title is not repeated. The posting doesn't have a job ID. So maybe start with a p for location and telework? But I'll make a Schedule section.
Let's write:
Schedule
Position Location: Elizabeth City, North Carolina (On-Site)
Telework/Work-from-Home Authorized: Yes - When Authorized/Hybrid
About the Role
Responsible for overseeing all aspects of the kitting process to support Programmed Depot Maintenance (PDM).
Responsibilities
- Attending daily/weekly meetings including Theory of Constraints, Issue Resolution, Full Kit, and Industrial Team Meetings, and reporting any supply/kitting issues affecting the PDM production schedule.
- Reviewing logistics performance with customers against established targets, benchmarks, and service agreements.
- Collaborating with other departments to meet customer requirements and minimize negative impacts on the Product Line and/or Air Stations.
- Evaluating material, supply, and finished product availability and allocation to maximize value and reduce costs.
- Building and maintaining positive business relationships with key personnel involved in logistics activities.
- Presenting proposed solutions to customers, management, or other stakeholders through written proposals and oral presentations.
- Staying updated on logistics technology advancements and applying them to improve processes.
- Estimating quantities, costs, resources, and materials needed for PDM full kitting.
- Ensuring proper receipt of equipment and materials.
- Identifying and resolving inventory discrepancies, making necessary kit adjustments.
- Reporting full kit plans, progress, and delays.
- Monitoring incoming components and supplies, verifying proper identifying documentation.
- Maintaining kit inventory status in Concerto and on respective cabinets and inventory control points.
- Conduct quarterly kit reviews to ensure items are correctly identified (e.g., aircraft-specific, supply candidate, hangar deck items, supply, Auto 6000).
- Performing daily maintenance of two-bin inventory systems.
- Organizing and updating the tag bible for all routed assets.
- Responding to inquiries regarding kit status.
- Reporting back orders or delays in full kitting to managers or other personnel.
- Develop training materials and process guides for full kit processes and conducting internal audits.
- Protecting and controlling proprietary materials handled at CG-AIR.
- Support monthly updates to technical manuals (ATIP).
- Perform other duties, as assigned.
Requirements
Experience
-- but can't use h4? The rule says use h3 for section headings. It doesn't say we can't use h4, but to be safe, I'll use h3 for each? But that would be many h3. The rule: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies top-level sections are h3. Subsections could be h4, but not specified. I'll use h3 for each major section, and within Requirements, I'll use
for category labels and
for items.
Better: Use Requirements
then Experience:
...
Education:
...
Security Clearance:
Public Trust
U.S. Citizenship:
This position supports a U.S. Government Contract whose terms require Sawdey Solution Services to staff it only with U.S. Citizens.
Similarly for Skills.
Skills
Other Required Skills &
for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. 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") 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the content: - Pay Rate: "The annual base salary range for this position is TBD." This is placeholder text (TBD). According to rule 7, I should not create a Pay section for filler/placeholder text. So I should not include a Pay section. - Position Location: Elizabeth City, North Carolina (On-Site) Telework/Work-from-Home Authorized: Yes - When Authorized/Hybrid. This is schedule/location info. Could be a Schedule section? The posting has specific content about location and telework. I could include a Schedule section with this info. - About the Role: There's a description and then "Additional Responsibilities Include, but are not Limited To:" followed by a long list of bullet points. This should be split: About the role (prose) and Responsibilities (list). - Experience Requirements: list of items. - Education Requirements: one item. - Other Required Skills & Abilities: list. - Security Clearance Requirements: "? Public Trust" - unclear, but there is content. - US Citizenship Requirements: prose. - Benefits at Sawdey Solution Services: extensive list of benefits. This is real content, so include Benefits section. - About the Organization: company description. Could be a section? The rules mention headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "About the Organization" is not in that list, but it's substantive. However, the rule says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so other headings may be allowed. But the instruction: "include a section ONLY when the posting has real, specific content for it". The organization description is real content. I could include an "About the Organization" section. But the user might expect only the listed headings. However, the example includes "About the role". "About the Organization" is similar. I'll include it as a section. - Why Choose Us?: list of points. - Who We're Looking For: list. - EOE Statement: boilerplate, remove. - "This position is currently accepting applications." - application instruction, remove. Now, I need to structure: - Possibly a short
for location/telework metadata (since not a heading). But the rule says "fold minor metadata into a short
or drop it". Location and telework are not minor; they are important. Could create a Schedule section with that info. The posting has "Position Location" and "Telework/Work-from-Home Authorized". That's schedule info. I'll create a Schedule section. - Pay: TBD, so skip. - About the Role: There's a prose sentence: "Responsible for overseeing all aspects of the kitting process to support Programmed Depot Maintenance (PDM)." Then a list of additional responsibilities. I'll make an "About the Role" section with the prose, and a "Responsibilities" section with the list. - Experience Requirements: list. - Education Requirements: list (single item). - Other Required Skills & Abilities: list. - Security Clearance Requirements: could be part of Requirements or separate. The heading "Security Clearance Requirements" is specific. I'll include as a subsection maybe under Requirements? But the rule says use h3 for section headings. I could make a "Requirements" section that includes experience, education, skills, security clearance. However, the example headings include "Requirements" and "Qualifications" and "Skills". The posting has separate sections: Experience Requirements, Education Requirements, Other Required Skills & Abilities, Security Clearance Requirements, US Citizenship Requirements. I could combine into a "Requirements" section with sub-lists, but the rule says use
for section headings. I think it's okay to have multiple h3 headings for each requirement type. But the instruction: "Prefer a few substantive sections over many thin ones." So maybe combine into one "Requirements" section with subheadings? But we cannot use h4? The rule only mentions h3 for section headings. Could use h3 for each? That would be many thin sections. Better to have a "Requirements" section with prose and lists. However, the posting has distinct categories. I'll create a "Requirements" section with subsections using ? Not allowed. The rule says use for section headings. It doesn't forbid h4, but the example only shows h3. I'll use h3 for each major category: "Experience Requirements", "Education Requirements", "Skills & Abilities", "Security Clearance", "Citizenship Requirements". But that's many. Alternatively, I can create a "Requirements" h3 and then use
for section headings. It doesn't forbid h4, but the example only shows h3. I'll use h3 for each major category: "Experience Requirements", "Education Requirements", "Skills & Abilities", "Security Clearance", "Citizenship Requirements". But that's many. Alternatively, I can create a "Requirements" h3 and then use
and
- for each category. That might be better.
Let's see the example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So "Requirements" is a heading. "Qualifications" and "Skills" are separate. The posting has "Experience Requirements", "Education Requirements", "Other Required Skills & Abilities". Those could fall under "Requirements" and "Skills". I'll create:
- Requirements (h3) with sub-lists for Experience, Education.
- Skills (h3) for Other Required Skills & Abilities.
- Security Clearance (h3) maybe separate? But it's a requirement. Could be under Requirements.
But the rule: "include a section ONLY when the posting has real, specific content for it". Each has content. I'll create:
- About the Role (h3)
- Responsibilities (h3)
- Requirements (h3) with Experience and Education
- Skills (h3) with Other Required Skills & Abilities
- Security Clearance (h3) maybe? The content is "? Public Trust". That's thin. Might include as a short p.
- Citizenship Requirements (h3) maybe.
But that's many. Let's combine: "Requirements" section includes Experience, Education, Security Clearance, Citizenship. "Skills" section for Other Required Skills & Abilities.
Benefits section: yes.
Schedule section: location and telework.
About the Organization: maybe include as "About the Organization" h3.
Why Choose Us and Who We're Looking For: could be part of About the Organization or separate. They are marketing fluff but still content. The rule says preserve ALL substantive information. I'll include them as subsections under About the Organization or separate sections. But to avoid many thin sections, I'll include them as part of About the Organization with lists.
Now, let's draft HTML.
First, a short p for metadata? The job title is not repeated. The posting doesn't have a job ID. So maybe start with a p for location and telework? But I'll make a Schedule section.
Let's write:
- Attending daily/weekly meetings including Theory of Constraints, Issue Resolution, Full Kit, and Industrial Team Meetings, and reporting any supply/kitting issues affecting the PDM production schedule.
- Reviewing logistics performance with customers against established targets, benchmarks, and service agreements.
- Collaborating with other departments to meet customer requirements and minimize negative impacts on the Product Line and/or Air Stations.
- Evaluating material, supply, and finished product availability and allocation to maximize value and reduce costs.
- Building and maintaining positive business relationships with key personnel involved in logistics activities.
- Presenting proposed solutions to customers, management, or other stakeholders through written proposals and oral presentations.
- Staying updated on logistics technology advancements and applying them to improve processes.
- Estimating quantities, costs, resources, and materials needed for PDM full kitting.
- Ensuring proper receipt of equipment and materials.
- Identifying and resolving inventory discrepancies, making necessary kit adjustments.
- Reporting full kit plans, progress, and delays.
- Monitoring incoming components and supplies, verifying proper identifying documentation.
- Maintaining kit inventory status in Concerto and on respective cabinets and inventory control points.
- Conduct quarterly kit reviews to ensure items are correctly identified (e.g., aircraft-specific, supply candidate, hangar deck items, supply, Auto 6000).
- Performing daily maintenance of two-bin inventory systems.
- Organizing and updating the tag bible for all routed assets.
- Responding to inquiries regarding kit status.
- Reporting back orders or delays in full kitting to managers or other personnel.
- Develop training materials and process guides for full kit processes and conducting internal audits.
- Protecting and controlling proprietary materials handled at CG-AIR.
- Support monthly updates to technical manuals (ATIP).
- Perform other duties, as assigned.
Schedule
Position Location: Elizabeth City, North Carolina (On-Site)
Telework/Work-from-Home Authorized: Yes - When Authorized/Hybrid
About the Role
Responsible for overseeing all aspects of the kitting process to support Programmed Depot Maintenance (PDM).
Responsibilities
Requirements
Experience
-- but can't use h4? The rule says use h3 for section headings. It doesn't say we can't use h4, but to be safe, I'll use h3 for each? But that would be many h3. The rule: "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies top-level sections are h3. Subsections could be h4, but not specified. I'll use h3 for each major section, and within Requirements, I'll use
for category labels and
- for items.
Better: Use
Requirements
thenExperience:
- ...
Education:
- ...
Security Clearance:
Public Trust
U.S. Citizenship:
This position supports a U.S. Government Contract whose terms require Sawdey Solution Services to staff it only with U.S. Citizens.
Similarly for Skills.Skills
Other Required Skills &