Stock Clerk

Here's a thinking process: 1. **Analyze the Request:** - Input: A job posting text with duties, experience/certifications, security clearance, work environment, and an EEO statement. - Task: Reformat into clean, well-structured semantic HTML. - Rules: - Use `

` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). - Use `

• ` for lists of duties/requirements/benefits. - Use `

  ` for prose. - Do NOT repeat job title as heading (already shown). - Do NOT put Job ID / requisition numbers as headings. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no `/`, no markdown code fences. 2. **Analyze the Input Text:** Let me parse the input into sections and identify what's substantive vs. boilerplate to remove. Input text: Duties The employee is assigned by the Government to tool cribs, Mega Centers and plant services. Stock Clerks shall monitor, make adjustments, maintain appropriate stock levels or replenish items for material carried and stock in Mega Centers and will prepare requisitions to refill onsite stock and shall perform any combination of the following duties: Receive, store, inventory and issue IMRL gear, equipment, materials, supplies, merchandise, foodstuffs, or tools, and compile stock records of items in stockrooms, warehouses, or storage yards. Count, sort, or weigh incoming articles to verify receipt of items on requisition or invoice Examine stock to verify conformance to specifications Store articles in bins, on floor or on shelves, according to identifying information, such as style, size or type of material Fill orders or issue supplies from stock; prepare periodic, special or perpetual inventory of stock (using current data systems such as ATICTS/MAXIMO) Requisition articles to fill incoming orders Compile reports on use of stock handling equipment, adjustments of inventory counts and stock records, spoilage of or damage to stock, location changes, and refusal of shipments Mark identifying codes, figures, or letters on articles; distribute stock among production workers, keeping records of material issued Make adjustments or repairs to articles carried in stock Cut stock to site to fill order Maintain Commodities and HAZMAT lockers throughout each location and shall issue HAZMAT using HMMS or Regional CHRIMP Follow appropriate HAZMAT waste procedures IAW the latest version of FRCSEINST 5090.3 Participate in quarterly and yearly HW handlers and spill drill training and may also be members of the HMCC. Required Experience, Training And Certifications Should have a basic knowledge of Naval Aviation hand tools and measuring devises. Past experience working in an aviation maintenance organizational tool room is desired. Past documented experience with handling Hazardous Material. Must be comfortable in the use of Microsoft Office applications, a mature and respectful demeanor and a professional appearance are a must. Any candidate that has past ATICS and MAXIMO data system experience is a plus. History of working in a well-structured industrial environment, a working knowledge of lean six sigma and ISO 9000 principles is desirable. Must be able to lift at least 50 pounds. Required Security Clearance Eligibility Applicantmust be a US Citizen andable to pass a background check with theDepartment of Defense. Work Environment This role operates within a hangar and warehouse environment. The employee may be exposed to moderate discomforts, such as noise, dust, heat, cold, and wind. The position requires the ability to work effectively in an active, industrial setting. Equal Employment Opportunity Statement Strategic Support Solutions, LLC is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, disability, or status as a protected veteran. We are committed to providing a workplace free of discrimination and harassment. Now, map to the requested HTML structure headings: - Allowed heading phrases: "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule" - But the input has natural sections: Duties, Required Experience, Training And Certifications, Required Security Clearance Eligibility, Work Environment, Equal Employment Opportunity Statement. I need to fit these into the allowed heading style, or adapt. The rules say: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't strictly say I can't use other headings, but it gives examples. I think I should map the content to the closest meaningful heading from the list, or use the exact section names but as

  . Let me re-read: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's giving examples of valid headings. I can use any of those, or perhaps the actual section titles from the posting, but the instruction says to use those as the structure. However, it also says "Preserve ALL substantive information; do NOT invent or summarize away detail." and "Include a section ONLY when the posting has real, specific content for it". Let's look at the sections in the posting and decide how to map them: - "Duties" -> This maps well to "Responsibilities" or I could keep "Duties" as an h3. The examples list "Responsibilities" but not "Duties". I think using "Responsibilities" is fine, or I could use "Duties" since it's the actual heading. The rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid using "Duties", but to be safe, I'll map it to "Responsibilities" or keep "Duties" if it's the exact text. Actually, the instruction says: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't say I can't use the section titles from the posting. I'll use the exact section names that make sense, but map them to the semantic categories if needed. Let's see: The posting has "Duties", "Required Experience, Training And Certifications", "Required Security Clearance Eligibility", "Work Environment", "Equal Employment Opportunity Statement". I need to remove: EEO boilerplate, equal opportunity statement, scam warnings, etc. The rule says: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So I should remove the entire "Equal Employment Opportunity Statement" section and its content. Also remove: Any job ID, requisition numbers (not present here). Now, decide on sections to include based on "real, specific content" and "never emit a heading followed by filler/placeholder text". The rule: "IMPORTANT: 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones." So I need to only include sections that have actual content from the posting, and no section if it would be thin or filler. Let's evaluate each potential section from the mapping: 1. **Responsibilities/Duties**: The posting has a long list of duties. This is substantive. I'll include it under "Responsibilities" or "Duties". I'll use "Responsibilities" as it's in the example list, but I could also use "Duties". To be faithful to the content, I'll use "Responsibilities" as the heading, since it's one of the examples. Actually, the examples are just that - examples. I think it's safer to use the exact heading from the posting if it's clear, but the rule gives a specific list. Let me re-read carefully: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This likely means I should use these as the permitted heading names. I'll map the posting's sections to these names where appropriate: - "Duties" -> "Responsibilities" (or keep "Duties"? I'll use "Responsibilities" as it's in the list, but the content is about duties. I could also just use "Duties" since it's the actual section name. I think using the posting's own section titles is fine as long as they're among the allowed or semantically equivalent. To be safe, I'll use "Responsibilities" for the duties section, as it's the closest match in the example list.) - "Required Experience, Training And Certifications" -> This maps to "Requirements" or "Qualifications". The example has both "Requirements" and "Qualifications". I'll use "Requirements" since it's about experience/training/certifications. - "Required Security Clearance Eligibility" -> This is specific content. It could go under "Requirements" or as a separate section. But the rule says prefer a few substantive sections over many thin ones. I'll fold it into "Requirements" or make a separate "Security Clearance" section if it has real content. It has real content: "Applicant must be a US Citizen and able to pass a background check with the Department of Defense." That's specific. I'll include it, maybe under "Requirements" or as its own section. But to keep it few, I'll fold into Requirements. - "Work Environment" -> This has specific content: "This role operates within a hangar and warehouse environment. The employee may be exposed to moderate discomforts, such as noise, dust, heat, cold, and wind. The position requires the ability to work effectively in an active, industrial setting." This is substantive. I'll map it to "Skills" or maybe "Schedule"? No, "Work Environment" doesn't map perfectly. The example list doesn't have "Work Environment". I could use "Skills" but that's not right. Maybe I should only use the headings that have exact matches, or I can use any h3 but the instruction gives examples. I think I should stick to the examples given, but the content must fit. Let me re-read: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say I'm limited to these, but it's a strong hint. However, the content has "Work Environment" and "Equal Employment Opportunity Statement" which I must remove the EEO part. I need to decide how to handle sections that don't neatly map. I think the best approach is to map the substantive content to the closest heading, or use the heading names that make sense semantically. Since the rule says "e.g.", it's not exhaustive. I'll use headings that fit the content: "Responsibilities", "Requirements", "Work Environment" (maybe I can't use that name, but I can describe it under a heading? Actually, I'll just use the heading names from the posting but as

  . Wait, the rule says "use