Team Member

We need to output HTML fragment with sections: About the role? The posting includes "Overall Job Summary" and "Essential Duties and Responsibilities", "Required Qualifications", "Preferred Knowledge, Skills Or Abilities", "Working Conditions", "Physical Requirements", "Company Info" (benefits). We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. No Pay or Schedule info given, so omit those sections. Benefits: there is Company Info describing benefits. So we can have a Benefits section with that content. About the role: we have Overall Job Summary. Could map to About the role. Responsibilities: Essential Duties and Responsibilities. Requirements: maybe Required Qualifications? Qualifications: maybe Preferred Knowledge, Skills Or Abilities? Skills: maybe Working Conditions? Actually Skills could be Preferred Knowledge, Skills Or Abilities. But we need to avoid duplication. Let's map: - About the role: Overall Job Summary. - Responsibilities: Essential Duties and Responsibilities. - Requirements: Required Qualifications (experience, education). - Qualifications: Preferred Knowledge, Skills Or Abilities (maybe also include Working Conditions? but that's more about environment). - Skills: maybe Working Conditions? Actually Skills could be Preferred Knowledge, Skills Or Abilities (but we already used). Could use Working Conditions as Skills? Not ideal. Perhaps we can omit Skills section if no distinct content. But we have Working Conditions and Physical Requirements; those could be under Skills? Not really. Could treat Working Conditions as Skills? Might be better to have a section for Working Conditions (but not in allowed headings). Allowed headings are limited to those list. So we must fit content into those headings. We can combine Working Conditions and Physical Requirements into maybe "Skills"? Not accurate. Could treat them as "Requirements"? But we already used Requirements for qualifications. Could merge them into Requirements as well. However we must not invent headings; we can only use those headings. We can have multiple sections with same heading? Probably not; each heading once. We need to decide which sections to include based on content. We have content for: - About the role (Overall Job Summary) - Responsibilities (Essential Duties and Responsibilities) - Requirements (Required Qualifications) - Qualifications (Preferred Knowledge, Skills Or Abilities) - Benefits (Company Info benefits) - Possibly Skills? Could use Working Conditions as Skills? Not great but maybe acceptable. However we could omit Skills if no specific skill list beyond what's already covered. The posting includes "Preferred Knowledge, Skills Or Abilities" which is essentially skills. So we can map that to Skills section. Then Qualifications could be Required Qualifications (experience, education). Then we still have Working Conditions and Physical Requirements left. Could we put them under Requirements? Maybe expand Requirements to include working conditions and physical requirements. But the heading "Requirements" is ambiguous; could include both qualifications and working conditions. However we already used Requirements for qualifications; we could rename but we must stick to allowed headings. Could we have two sections both titled Requirements? Probably not ideal but maybe allowed? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are possible headings; we can choose which to include. It doesn't forbid using same heading multiple times, but better to avoid duplication. We could combine Working Conditions and Physical Requirements into a single section under maybe "Skills"? Not accurate. Could create a section "Requirements" that includes both qualifications and working conditions/physical requirements. Then we could have Qualifications for preferred knowledge/skills? Hmm. Let's think: The posting has: - Overall Job Summary (About the role) - Essential Duties and Responsibilities (Responsibilities) - Required Qualifications (Experience, Education) (could be Requirements) - Preferred Knowledge, Skills Or Abilities (Skills) - Working Conditions (maybe could be part of Requirements? but we already used Requirements for qualifications) - Physical Requirements (maybe also part of Requirements) - Company Info (Benefits) We could make: - About the role - Responsibilities - Requirements (combine Required Qualifications + Working Conditions + Physical Requirements) - Skills (Preferred Knowledge, Skills Or Abilities) - Benefits (Company Info benefits) That seems reasonable. We must not include headings with filler text. All sections have real content. Now we need to format content: Use

• for any list of duties/requirements/benefits, and

  for prose. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like cookie/navigation/legal/EEO etc. The posting didn't have obvious boilerplate besides maybe "Disclaimer" and "Company Info". We need to keep Company Info (benefits) but remove disclaimer? The disclaimer is generic; maybe we should remove it as boilerplate? It says "Disclaimer This job description represents an overview..." That's likely boilerplate; we should remove it. Also "Company Info" we keep as benefits. We need to preserve all substantive info: duties list, qualifications, etc. Let's extract content. Overall Job Summary: "The Team Member is responsible for interacting with customers and team members, supporting selling initiatives and performing assigned tasks, while delivering a Legendary Customer Experience. Do you love the life out here and want to share it with others? At Tractor Supply we strive to make the life out here a little bit better each day for both our neighbors and our teams." We'll put that in

  under About the role. Responsibilities: Essential Duties and Responsibilities (Min 5%) ... includes bullet-like sentences. We need to turn into

  • . The paragraph includes many duties separated by periods. We'll split into list items. List: - Maintain regular and predictable attendance. - Work scheduled shifts and have the ability to work varied hours, days, nights, weekends and overtime as dictated by business needs. - Deliver on our promise of Legendary Customer Service through GURA: Greet the Customer. Uncover Customer’s Needs & Wants. Recommend Product Solutions. Ask to Add Value & Appreciate the Customer. - Team Members are required to perform a combination of the following duties during 95 percent of their day. Although the mix may vary from one day to another, our business and staffing model makes it essential that every Team Member be able to perform all of the following duties accurately, efficiently and safely on a regular basis and without advance notice: Then list of duties: - Operate cash register/computer following cash handling procedures as established by Tractor Supply Company. - Recovery of merchandise. - Participate in mandatory freight process. - Complete Plan-o-gram procedures (merchandising, sets, and resets). - Assemble merchandise. - Perform janitorial duties. - Execute price changes/markdowns. - Operate Forklift (unless under the age of 18). - Operate Cardboard Baler (unless under the age of 18). - Assist customers with loading purchases. - Ensure the customer has a Legendary shopping experience that differentiates from the competition. - Ensure the safety and well-being of birds. - Sanitize and maintain poultry holding tanks and care for birds as required. - Complete all documentation associated with any of the above job duties. - Team Members also may be required to perform other duties as assigned. We need to keep the GURA steps maybe as sub-items? Could keep as part of the duty description. We'll keep as part of the li text. We'll produce
    • for each duty. Now Requirements section: combine Required Qualifications, Working Conditions, Physical Requirements. Required Qualifications: - Experience: No experience required. Retail experience and/or farming, ranching, pet/equine, or welding knowledge is strongly preferred. - Education: A high school diploma or equivalent is preferred, but not required. Regardless of education level, Team Members must be able to read, write and count accurately. Working Conditions: - Working environment is favorable, generally working inside with moderate noise. - Indoor floors and outdoor lots generally are hard surfaces (concrete, asphalt, etc.) lighting and temperature are adequate. - Work shifts vary from one store to another, but generally are no less than 4 hours and may exceed 10 hours. - Promote a safe and productive work environment for Team Members and customers and adhere to Company safety training and guidelines Physical Requirements: - Ability to move and transfer merchandise, weighing up to 50 pounds, throughout the store. - Ability to push and pull merchandise up to 2,000 pounds with the assistance of proper material handling equipment (e.g. pallet jack). - Ability to occasionally lift or reach merchandise overhead. - Ability to frequently stand, kneel, twist, crouch, squat, bend, stoop, and climb ladders. - Ability to move throughout the store for an entire shift. - Ability to safely access all areas of the store including selling floor, side lot, stock area, and register area. - Ability to operate and use all equipment necessary to run a store (e.g. dolly, handtruck, forklift, baler, computer, cash register) (forklift and baler requirements do not apply if under the age of 18). - Ability to constantly operate store equipment such as computer, cash register, and other store equipment. - Ability to read, write, and count accurately to complete all documentation. - Ability to utilize strong written and verbal communication skills to communicate effectively with team members. - Ability to process information / merchandise through the point-of-sale system. - Ability to handle and be in contact with birds/poultry. - Ability to successfully complete all required training. - Ability to successfully complete training and certification to dispense propane, and to dispense propane (propane certification and dispensing requirement does not apply if under the age of 18). We'll combine these into a list under Requirements. Now Skills section: Preferred Knowledge, Skills Or Abilities: - Farming, ranching, pet/equine, or welding knowledge is strongly preferred. - Ability to read, write, and count accurately. - Strong communication and problem-solving skills. - Basic computer skills. - Strong interpersonal skills and ability to resolve issues ethically and with minimal conflict. We'll put as list. Benefits section: Company Info benefits paragraph: "At Tractor Supply and Petsense by Tractor Supply, our Team Members are the heart of our success. Their dedication, passion, and hard work drive everything we do, and we are committed to supporting them with a comprehensive and accessible total reward package. We understand the evolving needs of our Team Members and their families, and we strive to offer meaningful, competitive, and sustainable benefits that support their well-being today and in the future. Our benefits extend beyond medical, dental, and vision coverage, including company-paid life and disability insurance, paid parental leave, tuition reimbursement, and family planning resources such as adoption and surrogacy assistance, for all full-time Team Members and all part-time Team Members. Part time new hires gain eligibility for TSC Benefits by averaging at least 15 hours per week during their 90-day lookback period. The lookback period starts the first of the month following the date of hire. If the 15-hour requirement was met, the benefits eligibility date will be the first day of the month following 4 months of continuous service. Please visit this link for more specific information about the benefits and leave policies applicable to the position you’re applying for." We need to keep substantive info; the last sentence about visiting link maybe considered boilerplate? It's a link instruction; could be considered application instruction? It's not exactly application instruction but referencing link for more info. Might be okay to keep. However we should remove any application instructions. This is not exactly instruction to apply; it's just a link for more info. Might be okay. We'll keep the paragraph but maybe remove the "Please visit this link..." as it's a directive. Safer to remove