Data Entry

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invented details. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "If you're looking for comfort, keep scrolling..." etc. Also remove "Original Posting September 16, 2026" maybe not needed? It's metadata but not job ID; could be minor metadata folded into short p or drop. Probably drop. Also remove "Pay And Benefits" section? We have Pay range given; we can include Pay section with that range. Benefits: posting mentions "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." That's generic but still specific? It mentions types. Could include Benefits section with those items. However we must not include placeholder like "commensurate with experience". The benefits listed are specific enough? Might be okay. But we need to avoid boilerplate; the benefits paragraph is generic but still part of posting. We'll include. Schedule: posting mentions "Must be able to work full time onsite in Puyallup, WA", "Required to be on-call 24 hours/7 days a week. Must be able to respond to mission alerts within 15 minutes with a recall of 90 minutes to report to designated location." That's schedule info. So we can include Schedule section. Qualifications: Basic Qualifications: Bachelor’s Degree and 2 years of related experience or High School Diploma and 8 years of related experience. Knowledge in Supply Chain Management, Data Entry and Warehouse Management System(s). Must be able accurately and independently execute routine and complex transactions within the ERP system, following established procedures and business rules. Must be able to demonstrate strong knowledge of ERP processes, transaction workflows, and downstream impacts to ensure data integrity. Required to be on-call 24/7 etc. Must carry a cell phone at all times. Must have ability to handle requests from multiple groups. Ability to lift up to 50 lbs. Ability to prioritize tasks and scope with occasional periods of stress when dealing with critical situations. Possesses excellent English language skills, proficiency with Microsoft Office applications. Demonstrate strong customer relations capabilities to achieve customer satisfaction. Strong ERP (Oracle) system knowledge and experience. Inventory Management. Technically savvy. Preference for Previous experience supporting a government agency. Also "Candidate MUST Be a US Citizen with the ability to obtain a Public Trust Clearance AND Be able to work full time onsite in Puyallup, WA". That's a requirement. We need sections: About the role (maybe description paragraph), Responsibilities (list), Requirements (maybe combine Qualifications and Skills?), but we have separate headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what to put where. The posting has "Primary Responsibilities" list. So Responsibilities section with

• . Then "Basic Qualifications" could go under Qualifications. Also "Knowledge in Supply Chain Management..." could be Skills. Also "Must be able accurately..." etc could be Requirements. But we can combine overlapping. However we must not create thin sections; prefer few substantive sections. Could combine Requirements and Qualifications into one? But headings are prescribed; we can include only those with content. We could include About the role (description paragraph), Responsibilities, Qualifications (including basic qualifications and skills), Benefits, Pay, Schedule. That seems reasonable. We must not repeat job title. No markdown. Let's extract description: "The Strategic National Stockpile (SNS) team at Leidos currently has an opening for a Data Entry in Puyallup, WA. This is an exciting opportunity to provide logistics and data entry, support to maintain accurate inventory records to assist in operating and maintaining the SNS national stockpiled inventory. In this mission, we assist in ensuring the SNS inventory is ready for deployment, providing the ability to respond 24 x 7 in an emergency. The successful candidate will serve as Data Entry in the Logistics Office." That's About the role. Responsibilities: list of items after "Primary Responsibilities". We'll capture each bullet as
• . Need to ensure we preserve all. Let's list them: - Conduct inventory management functions utilizing inventory control systems, electronic documentation workflows, shipping and receiving documentation processes, and data entry applications to support program operations - Enter inventory transaction data into the Government-designated Inventory Management System based on Government-provided source documentation and direction. - Review source documentation for completeness and accuracy prior to data entry and notify Government personnel of discrepancies for resolution. - Compile system-generated reports and inventory data extracts to assist Government personnel in monitoring asset accountability and system performance. - Perform data verification and conversion activities to ensure accurate transfer of information from source documents into electronic systems. - Provide administrative and analytical support to Repository Managers by compiling workload data, preparing reports, and identifying system issues for Government review and resolution. - Coordinate with Government personnel to document and communicate inventory discrepancies, transaction errors, or system-related issues. - Verify and enter product information (e.g., description, lot/serial number, expiration date, unit of measure, storage location, National Drug Code (NDC), or part number) into designated systems based on Government-provided documentation. - Maintain organized electronic and hard-copy supporting documentation in accordance with Government established procedures. - Support Government-led Quality Assurance and Quality Control (QA/QC) activities by compiling inventory records and assisting with documentation during scheduled reviews. - Analyze repository-level logistics data and provide written recommendations to improve efficiency and process performance. - Execute data entry and documentation tasks associated with inventory and distribution transactions in accordance with written Government procedures and site SOPs. - Assist Government personnel in organizing workload data related to expedited or emergency shipments and document transaction timelines for reporting purposes. - Provide documentation and tracking support associated with biological products requiring cold chain management, in accordance with Government-established protocols. - Maintain documentation to support compliance with applicable regulatory standards, including cGMP, as directed by Government personnel. - Provide on-call documentation and data entry support to assist Government personnel in processing emergency shipment transactions within required response timeframes. - Respond to emergency shipments within 90-minute timeframes. That's many. Now Qualifications: Basic Qualifications bullet list: - Bachelor’s Degree and 2 years of related experience or High School Diploma and 8 years of related experience. - Knowledge in Supply Chain Management, Data Entry and Warehouse Management System(s). - Must be able accurately and independently execute routine and complex transactions within the ERP system, following established procedures and business rules. - Must be able to demonstrate strong knowledge of ERP processes, transaction workflows, and downstream impacts to ensure data integrity. - Required to be on-call 24 hours/7 days a week. - Must be able to respond to mission alerts within 15 minutes with a recall of 90 minutes to report to designated location. - Must carry a cell phone at all times. - Must have the ability to handle requests from multiple groups/organizations. - Ability to lift up to 50 lbs. - Ability to prioritize tasks and scope with occasional periods of stress when dealing with critical situations. - Possesses excellent English language skills, proficiency with Microsoft Office applications. - Demonstrate strong customer relations capabilities to achieve customer satisfaction. - Strong ERP (Oracle) system knowledge and experience. - Inventory Management. - Technically savvy. - Preference for Previous experience supporting a government agency. Also citizenship and clearance: "Candidate MUST Be a US Citizen with the ability to obtain a Public Trust Clearance AND Be able to work full time onsite in Puyallup, WA". That could be part of Qualifications or Requirements. We'll include in Qualifications. Skills: maybe we can extract specific skills: ERP (Oracle), Inventory Management, Data Entry, Supply Chain, Warehouse Management, Microsoft Office, etc. But we already have many in Qualifications. To avoid thin sections, we could omit Skills section and put those under Qualifications. But the instruction says we can include sections only when posting has real specific content. It doesn't require us to use all headings. So we can skip Skills if we think it's redundant. However we might still include Skills if we can pull out distinct skills not covered. But we already have many. To keep few substantive sections, we can combine Requirements and Qualifications into one? But we have separate headings; we could include Requirements (maybe the citizenship/clearance, on-call, lift, etc.) and Qualifications (education/experience, knowledge). But that may create many sections. Let's think: The instruction: "Prefer a few substantive sections over many thin ones." So we should aim for maybe 4-5 sections: About the role, Responsibilities, Qualifications (including education, experience, skills, citizenship, clearance), Benefits, Pay, Schedule. That's 6 sections. Could be okay. We'll not include Requirements separate. Now Benefits: we have "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." Also maybe mention "Pay and benefits are fundamental..." but that's generic. We'll list those benefits as
  . Pay: we have Pay Range $45,500.00 - $82,250.00. Also note that it's a guideline. We'll include that as

  . Schedule: we have full-time onsite, on-call 24/7, respond within 15 minutes, recall 90 minutes, must carry cell phone. We'll put as

  . Now we need to ensure we don't include boilerplate like "Original Posting September 16, 2026", "For U.S. Positions: While subject to change...", "About Leidos", "Leidos is an industry...", "Pay And Benefits" heading (we are making our own), "Securing Your Data", "Commitment to Non-Discrimination". Remove those. Also remove duplicated lines like "Pay Range Pay Range $45,500.00 - $82,250.00". We'll keep one. Now produce HTML fragment:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • Competitive compensation
  • Health and Wellness programs
  • Income Protection
  • Paid Leave
  • Retirement

  Pay

  Pay Range: $45,500.00 - $82,250.00 (guideline only; actual compensation based on responsibilities, education, experience, knowledge, skills, internal equity, market data, etc.)

  Schedule

  • Full-time onsite in Puyallup, WA
  • Required to be on-call 24 hours/7 days a week
  • Must respond to mission alerts within 15 minutes with a 90‑minute recall to report to designated location
  • Must carry a cell phone at all times
  Check we didn't miss any substantive info: The description about mission, 24x7 readiness, etc. Already in About the role. We included citizenship and public trust clearance in Qualifications? Not yet. Let's add a bullet: "Must be a U.S. Citizen with ability to obtain a Public Trust Clearance". Also "Must be able to work full time onsite in Puyallup, WA" (but we already have schedule). Could keep in Qualifications as well but maybe redundant. We'll add to Qualifications. Also "Preference for Previous experience supporting a government agency." Already. Now ensure we didn't include any boilerplate like "If you're looking for comfort, keep scrolling."