Logistician, Journeyman
AVIAN · Patuxent River, MD · 4 wk ago
Management$80k–$90k/yrFull-time
We need to output HTML fragment with sections for headings: 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. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "AVIAN is a service-based organization..." etc (EEO). Also remove "Why Join Us?" maybe not needed unless it's Benefits etc. But we need to preserve substantive info.
Let's parse the posting.
Content:
Intro paragraph: "Join a Company Where You Can Make a Real Impact - and Own a Piece of the Future ..." up to "Our company primarily serves the Navy and other Department of Defense clients, offering a dynamic environment where your expertise will make a difference."
Then "About The Role" heading.
Then description of role: "AVIAN is seeking a Logistics Journeyman responsible to the PMA-276 Product Support Manager (PSM) for establishing and managing the wholesale and retail supply support/supply chain requirements. These responsibilities include the planning, coordination and management of all PMA-276 Supply Chain aspects for systems, subsystems and equipment to include the supply support facilities and developing, monitoring and evaluating the technical accuracy of the supply chain program for PMA-276 products and systems."
Then "Responsibilities" heading.
Then a long paragraph with many responsibilities separated by periods. Could be turned into list items.
Then after responsibilities, there is a paragraph that seems to continue responsibilities? Actually after responsibilities heading, the text includes many sentences. Then after that, there is "BS or BA Degree in Acquisition, Logistics Management, Business, Engineering, or Management." etc. That seems like qualifications/requirements.
Then "At least three (3) to 10 years’ full time experience in operational logistics support or maintenance engineering. Three (3) years’ experience in technical analysis of operational IPS requirements. Three (3) years of specific experience in operational logistics planning. Experience demonstrating ability to perform IPS studies, analysis, and evaluations in support of DOD weapons systems/equipment. Access to Deck Plate and One Touch along with expertise with Individual Component Repair Lists (ICRL's) are required. Must have a Department of Defense security clearance. Due to the sensitivity of customer-related requirements, U.S. Citizenship is required."
Then "Salary range $80,000 - $90,000 (The offered rate will be based on the selected candidate’s knowledge, skills, abilities, and/or experience and in consideration of internal parity.)"
Then "About Being a Part Of Team AVIAN" paragraph about employee-owner etc.
Then "You’ll Succeed Here If You..." bullet list (but not formatted as list in source). Then "Why Join Us?" with subpoints: Employee Ownership, Real Growth, Purpose-Driven Work, Culture of Collaboration, Comprehensive Benefits Package..., Flexible Leave Benefits...
Then EEO statement.
We need to extract sections:
- About the role: we have content after "About The Role". Should be a
About the role
thenwith that paragraph. - Responsibilities: heading
Responsibilities
then- items for each responsibility sentence.
We need to split responsibilities into sensible items. The paragraph after Responsibilities heading:
"Responsible for the logistics functions associated with managing the supply support requirements for the PMA-276 program, involving many technical/ program decisions and major DOD Service operating forces/components. As such, the incumbent exerts and exercises extraordinary leadership in establishing and monitoring the necessary logistics posture. This includes interfacing with the DOD, OPNAV, other services and agencies (including NAVSUP WSS and DLA), the fleet, field activities and contractors.Manages and guides supply logistics activities in support of the program office to ensure effective and efficient planning, integration, and phasing of all efforts.Provide input, review and updates to BAM (APN-6 spares) process, briefs, requirements, adjustments as they apply to supply support spares for all assigned systems and/or equipment.Makes recommendations based on use of forecasting tools and methodologies, other technical information, feedback, and funding, as to what is the best approach in expending resources to ensure an adequate logistics support posture in the area supply support.Provides supporting cost data and develops tailored application of the elements of life cycle costing based on authoritative knowledge (e.g., Maintenance Plans, Level of Repair Analysis, historical data) of the unique characteristics of the weapon system and its support system.Monitor inventory levels and interact with fleet commands when required.Capitalizes on emerging technologies and capabilities, recommends changes to basic NAVAIR integrated logistic support management policies and procedures in supply support.Manages the planning, implementation, and execution of modification programs and maintenance programs as related to supply support.Performs various tasks related to the development, operation, evaluation, and improvement of weapon systems supportability and/or maintainability programs and information systems. Works on logistics and maintainability programs and with logistics and maintenance control organizations on issues such as technical evaluation and identification of weapons systems logistics requirements and resources; development of logistics support and maintainability programs or plans; systems acquisition requirements analysis; budgetary or financial analysis and control; LCC analysis and control; weapons systems HW and SW standardization and compatibility; IPS/ R&M program T&E planning and execution; and, IPS/R&M program management analysis. Collects, compiles, analyzes, investigates, researches, or applies logistics, maintenance, acquisition, or financial data and information.Develops, modifies, prepares, or validates documentation in relation to automated logistics or maintenance data reporting systems, and management information systems."
We can split each sentence into a list item. Need to ensure we keep all info.
- Requirements/Qualifications/Skills: The posting includes qualifications: degree, years experience, specific experience, access to tools, security clearance, US citizenship. Also maybe skills: forecasting tools, life cycle costing, etc. But we can combine into Requirements section.
We need to decide headings: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only those with real content. We have: - About the role: yes. - Responsibilities: yes. - Requirements: we have degree, experience, clearance, citizenship. Could be Requirements. - Qualifications: maybe same as Requirements; but we should not duplicate. Could combine into Requirements. - Skills: maybe we could extract skills like forecasting tools, life cycle costing, etc. But we might not need separate Skills if content thin. - Benefits: we have Comprehensive Benefits Package description: medical, dental, vision, telemedicine, TRICARE supplement for veterans. Also Flexible Leave Benefits: flexible and paid time off, 11 paid holidays, paid sick leave, maternity and bonding leave, military training leave. Also employee ownership etc but that's more culture. Benefits section should include those. - Pay: Salary range $80,000 - $90,000. - Schedule: not mentioned. So omit. We also have "About Being a Part Of Team AVIAN" and "You’ll Succeed Here If You..." and "Why Join Us?" These could be considered culture but not required headings. We could incorporate into About the role or maybe a separate section like "About the Company" but not in allowed headings. Since only allowed headings list, we should not create extra headings. We could embed that content into About the role or maybe into a
after About the role? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should only use those headings if we have content. It doesn't forbid other headings, but says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. Safer to stick to those. Thus we need to place the culture/benefits etc into Benefits section maybe. But Benefits already defined. Could add a paragraph about employee ownership etc under Benefits? Might be okay. Alternatively we could create a section "About the role" includes the intro and role description. Then Responsibilities. Then Requirements (degree, experience, clearance, citizenship). Then Benefits (including compensation? but Pay separate). Then Pay. We'll omit Qualifications and Skills if not distinct. Now we need to preserve all substantive information. Let's extract. Intro paragraph before About The Role: "Join a Company Where You Can Make a Real Impact - and Own a Piece of the Future Are you energized by the idea of helping a company grow smarter, serve our customers better, and connect more deeply? Do you thrive in an environment where your ideas matter, your voice is heard, and your work drives real results? If so, we’d love to meet you. We’re a mid-sized, employee-owned company on a mission to create meaningful value for both our employees and our customers. That means we’re not just looking for someone to fill a seat — we’re looking for someone who wants to build, innovate, and evolve with us. Our company primarily serves the Navy and other Department of Defense clients, offering a dynamic environment where your expertise will make a difference." We could include this as part of About the role or maybe a separate "About the Company" but not allowed. Probably include in About the role section as preamble. Thus About the role section will contain that intro plus the role description. Now Responsibilities list items. Now Requirements: list degree, years experience, specific experience, access to tools, clearance, citizenship. Now Benefits: list medical, dental, vision, telemedicine, TRICARE supplement for veterans; flexible leave: flexible and paid time off, 11 paid holidays, paid sick leave, maternity and bonding leave, military training leave. Also employee ownership? Might be considered benefit but we can include as a bullet under Benefits: employee ownership stake. But the posting also mentions "Comprehensive Benefits Package Designed to support your health, financial security, and overall well-being, our health and wellness benefits include medical, dental, and vision coverage, along with telemedicine services and a TRICARE supplement for veterans." and "Flexible Leave Benefits we prioritize a balanced, supportive environment that allows you to thrive both personally and professionally and offer flexible and paid time off, 11 paid holidays, paid sick leave, maternity and bonding leave, and military training leave." Thus we can put those. Now Pay: Salary range $80,000 - $90,000 with note about based on KSAs and internal parity. Now we must not include boilerplate: EEO statement, "AVIAN is a service-based organization..." etc. Also remove "Why Join Us?" etc. But we might have captured some of that content in Benefits etc. However "Why Join Us?" includes Employee Ownership, Real Growth, Purpose-Driven Work, Culture of Collaboration. Those are substantive but not under allowed headings. Could we incorporate them into About the role or Benefits? Employee Ownership could be a benefit. Real Growth, Purpose-Driven Work, Culture of Collaboration maybe could be part of About the role (company description). We'll incorporate those sentences into About the role paragraph. Thus we need to extract those sentences: From "Why Join Us?": - Employee Ownership: "We’re not just building a company — we’re building a legacy. As an employee-owner, you’ll share in our success and have a direct stake in our future." - Real Growth: "We’re expanding, evolving, and exploring new ways to serve. Your contributions will shape our direction and help us grow stronger." - Purpose-Driven Work: "Every improvement you help make is one that adds value — not just for us, but for the people and missions we support." - Culture of Collaboration: "We’re big enough to take on meaningful challenges, but small enough that everyone still knows your name." We can incorporate these into About the role