Retail Reset Merchandiser - Kessler's

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 there is real specific content. We need to parse the posting. General info: Company: CRO-US, Location: ABERDEEN, South Dakota, 57401, Ref #: 109302, Pay Rate: $17.00, Experience/skills and/or location may influence position wage rate Range Minimum: $17.00 Range Maximum: $17.00, Function: Merchandising, Employment Duration: Full-time, Benefits: Medical, dental and vision insurance Company-paid life insurance, short-term and long-term disability 401k program Generous Paid Time Off (PTO) program. Then description: "CROSSMARK is seeking an energetic, motivated individual to join our growing team. As part of our family, you’ll support Coborn's, a reputable employee-owned grocery chain. We’ll get you up to speed quickly with our online paid training and learning materials. Representatives work both independently and as part of a great team. Start your next chapter with CROSSMARK! Why Join CROSSMARK? Competitive pay and paid training. Paid drive time between stores and mileage reimbursement. Growth potential, field, corporate, and leadership opportunities. Health, vision, dental, short-term disability, life insurance, 401K, and more are available. Employee Referral Bonus Program. Share our opportunities with your friends and family." Then "What You’ll Do : Reset and stock sections of the store according to a planogram. New item cut-ins and shelf management. Build and maintain professional relationships with store management and associates." Then "What We’re Looking For : Must be 18 years of age or older. Must be available Monday – Thursday, starting at 7 am. Occasional Fridays. Must have access and be comfortable using a smart device. Physical ability to regularly lift 25lbs and occasionally up to 50lbs. Must have reliable transportation and willingness to travel to multiple locations. Experience with planograms is strongly preferred." Then some boilerplate about CROSSMARK etc. Then equal opportunity etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should strip the later paragraphs about Acosta Group, equal opportunity employer, accommodation request, privacy policy, terms. We need to preserve all substantive information. We need to format into sections: maybe About the role (description), Responsibilities (What You’ll Do), Requirements (What We’re Looking For), Benefits, Pay, Schedule (if present). Also maybe Qualifications? Could combine Requirements and Qualifications. We have Pay Rate: $17.00, range min and max both $17.00. So we can include Pay section with that info. Schedule: The posting mentions "Must be available Monday – Thursday, starting at 7 am. Occasional Fridays." That's schedule info. So we can include Schedule section. Benefits: listed: Medical, dental and vision insurance, Company-paid life insurance, short-term and long-term disability, 401k program, Generous Paid Time Off (PTO) program. Also later "Why Join CROSSMARK?" includes health, vision, dental, short-term disability, life insurance, 401K, and more are available. Also competitive pay and paid training, paid drive time between stores and mileage reimbursement, growth potential, employee referral bonus program. Those could be considered benefits as well. But we should not duplicate. We'll include Benefits section with the explicit benefits list. We also have "Competitive pay and paid training." That's more about pay and training; but we already have Pay section. Could add a note in About the role? Probably not needed. We need to avoid filler like "commensurate with experience". Not present. We need to not repeat job title as heading. The job title is not given explicitly; maybe "Merchandising" function. We'll not add heading for it. We need to not put Job ID/requisition numbers as headings; we can fold minor metadata into a short

or drop it. The Ref #: 109302 is minor metadata; we could drop it or include in a paragraph. Probably drop it as per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can drop it. Location: we could include in a short paragraph maybe under About the role? But location is substantive? Might be considered minor metadata; but we could include in a paragraph at top:

Location: ABERDEEN, South Dakota, 57401

. However instruction says "fold minor metadata into a short

or drop it." Location could be considered minor metadata but also maybe relevant. I'd include a short paragraph. Company: CRO-US maybe also minor. We need to output only HTML fragment. Let's structure:

About the role

CROSSMARK is seeking an energetic, motivated individual to join our growing team. As part of our family, you’ll support Coborn's, a reputable employee-owned grocery chain. We’ll get you up to speed quickly with our online paid training and learning materials. Representatives work both independently and as part of a great team. Start your next chapter with CROSSMARK.

Maybe also include "Why Join CROSSMARK?" content as part of About the role or Benefits? Could be separate section "Why Join CROSSMARK?" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit the "Why Join CROSSMARK?" bullet points into Benefits or About the role. The bullet points include competitive pay and paid training, paid drive time and mileage reimbursement, growth opportunities, health/vision/dental etc., employee referral bonus. Those are benefits/perks. So we can incorporate them into Benefits section. Thus Benefits section will list: Medical, dental and vision insurance; Company-paid life insurance; short-term and long-term disability; 401k program; Generous Paid Time Off (PTO) program; Competitive pay and paid training; Paid drive time between stores and mileage reimbursement; Growth potential (field, corporate, leadership opportunities); Employee Referral Bonus Program. We need to avoid duplication; but it's okay. Responsibilities: list from "What You’ll Do": Reset and stock sections of the store according to a planogram; New item cut-ins and shelf management; Build and maintain professional relationships with store management and associates. Requirements: from "What We’re Looking For": Must be 18 years of age or older; Must be available Monday – Thursday, starting at 7 am; Occasional Fridays; Must have access and be comfortable using a smart device; Physical ability to regularly lift 25lbs and occasionally up to 50lbs; Must have reliable transportation and willingness to travel to multiple locations; Experience with planograms is strongly preferred. We could also include "Must be available Monday – Thursday, starting at 7 am. Occasional Fridays." That's schedule info; but we also have Schedule section. Might duplicate. Better to put schedule in Schedule section and not repeat in Requirements. However the requirement includes availability; but we can keep it in Requirements as a requirement, and also have Schedule section with same info? Might be duplicate. The instruction: Prefer a few substantive sections over many thin ones. So we could combine schedule into Requirements, and not have separate Schedule section. But we have explicit Pay and Benefits sections; schedule maybe not needed as separate if we include in Requirements. However the instruction says include a section ONLY when the posting has real, specific content for it. It does have schedule info (Monday-Thursday 7am, occasional Fridays). So we could make a Schedule section. But then we would have duplicate content if we also list it under Requirements. To avoid duplication, we could move the schedule info to Schedule section and remove from Requirements. But the requirement list includes that as a requirement; but we can still keep it in Requirements but maybe rephrase to not include schedule? The requirement list includes availability; it's indeed a requirement. But we could keep it in Requirements and not have Schedule section; but then we would not have a Schedule section despite having schedule info. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must create a Schedule section if schedule info exists; we can choose to include it elsewhere. However they gave list of possible headings including Schedule, implying we could use it if we want. I'd create a Schedule section to keep things clear, and then in Requirements we can omit the schedule line (or keep but note it's covered). To avoid duplication, better to move schedule to Schedule section and not repeat in Requirements. So Requirements will exclude the availability line. Thus Requirements: Must be 18 years of age or older; Must have access and be comfortable using a smart device; Physical ability to regularly lift 25lbs and occasionally up to 50lbs; Must have reliable transportation and willingness to travel to multiple locations; Experience with planograms is strongly preferred. Schedule: Must be available Monday – Thursday, starting at 7 am; Occasional Fridays. Pay: Pay Rate: $17.00; Range Minimum: $17.00; Range Maximum: $17.00. Now About the role: we can include the initial description plus maybe the "Why Join CROSSMARK?" points that are not benefits? Actually those are benefits/perks; we already put them in Benefits. So About the role can be just the initial paragraph: "CROSSMARK is seeking an energetic, motivated individual to join our growing team. As part of our family, you’ll support Coborn's, a reputable employee-owned grocery chain. We’ll get you up to speed quickly with our online paid training and learning materials. Representatives work both independently and as part of a great team. Start your next chapter with CROSSMARK." We could also include the "Why Join CROSSMARK?" introductory sentence: "Why Join CROSSMARK? Competitive pay and paid training. Paid drive time between stores and mileage reimbursement. Growth potential, field, corporate, and leadership opportunities. Health, vision, dental, short-term disability, life insurance, 401K, and more are available. Employee Referral Bonus Program. Share our opportunities with your friends and family." This is basically benefits/perks. We'll incorporate into Benefits. Thus Benefits section will have a list combining the explicit benefits and those from Why Join. Let's craft Benefits list items: - Medical, dental and vision insurance - Company-paid life insurance - Short-term and long-term disability - 401k program - Generous Paid Time Off (PTO) program - Competitive pay and paid training - Paid drive time between stores and mileage reimbursement - Growth potential (field, corporate, and leadership opportunities) - Employee Referral Bonus Program We could also mention "Health, vision, dental, short-term disability, life insurance, 401K, and more are available." but that's redundant with earlier items. Now we need to output HTML fragment. We'll start with maybe a paragraph for location and company? Could include as minor metadata:

Location: ABERDEEN, South Dakota, 57401

Company: CRO-US

. But we might drop them as minor. The instruction: "fold minor metadata into a short

or drop it." So we could include a short paragraph with location and company. Let's do one paragraph:

Location: ABERDEEN, South Dakota, 57401 | Company