Lead Seamstress

We need to output HTML fragment HTML with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Now that we’ve popped the question, please say “I do”." etc? That's like a tagline but not essential? Might be considered marketing fluff but not required. We need to preserve all substantive information. Let's parse content. First paragraph: "From Aisle to Algorithm and for All Life’s Moments, at David’s Bridal, we empower our customers and our employees to stay true to their dreams and find the one, whether that means the event or the wedding dress that matches a personal style—or the career that is a perfect fit. Join a company that dominates the products in their category – 1 out of 3 being sold by them and taking care of them with one of the highest customer service scores in retail! If you are passionately enthusiastic, endlessly curious, and customer obsessed, say “I do” and apply today!" That's marketing fluff; could be considered "About the role"? Not exactly. Might be considered "About the role" or "Company overview". The instruction says use headings for sections like About the role, Responsibilities, etc. So we can put an "About the role" section with that paragraph. Next: "Lead Alterations Specialist is responsible for completing all fittings and alterations to the high standards of David’s Bridal and reports to the Store Manager. S/he is responsible for exemplifying friendly, knowledgeable, and technical expertise and providing superior customer service. Lead Alterations Specialist is a member of the store team and demonstrate the value and qualities of the David’s Bridal brand. This role will report to the Store Manager" That's also about role; could be part of About the role. Then "Essential Job Functions" heading appears in original but we should not repeat job title as heading; we can treat as Responsibilities. List of duties: "Welcome all customers with genuine, and friendly enthusiasm over the phone and in person, communicates clearly and concisely adapting style to suit customers by problem solving, excellent phone skills and resolving conflict. Responds promptly to all customer questions by providing product and service information. Drives customer loyalty by making clientele calls to maximize appointments, builds and provides customer service. 80% for Bridal, 30% for Dress. Floor Manager during peak sales times to offer fit and alterations consultations. Assists stylists in closing sales by consulting with customers regarding gown fit and customization. Communicate how alterations can play an important role in perfecting the dress for her event in partnership with Alterations. Promote all alteration services and personalization options Lead and oversee all alterations fittings, sewing, steaming, pressing and spot cleaning of garments to company standards. Maintains quality control guidelines and inspects all garments altered/steamed/pressed to verify pristine condition before final delivery to customer Trains Alterations Specialists in fitting and sewing techniques Ensures ongoing product education for all Alterations team members Communicate daily sales goal achieved to Store Manager Use all approved systems and processes to manage the customer’s flow to deliver a 5 Star Customer Experience Maintain high dress code standards per her/himself per dress code" We need to break into list items. Then "Physical Demands" section: we could include under Responsibilities or maybe a separate section? The instruction only lists certain headings; Physical Demands not listed. Could be omitted? But we need to preserve all substantive information. Could incorporate into Responsibilities as a list? Might be better to include as a separate section not in prescribed headings? The instruction says: "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 prefer those headings. It also 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 forbid other headings, but suggests using those. Safer to stick to those headings; we can put Physical Demands under Responsibilities as a list. Education & Credentials: could go under Requirements or Qualifications. We'll put under Requirements. Then benefits: "Full Time Opportunity – A comprehensive benefits package is available. Rewarding Environment and Competitive Pay Generous Dream Maker Discount After First Pay Period Referral Incentive Program Dayforce Wallet – Get Paid Early! Health/Dental/Vision Insurance 401K Program Paid Vacation, Wellness Days & Holidays, including your Birthday off! Pet Benefits Love wins when love is for Everyone! Our mission at David’s Bridal is to embrace the ideas of Diversity, Equity, and Inclusion. It is our goal to build a workforce that is as representative as the customers we serve. We vow to create a culture where all forms of diversity are celebrated and seen as valuable. David’s Bridal encourages applications from all qualified candidates. David’s Bridal has a great record of accommodating persons with disabilities. Contact Human Resources at humanresources@dbi.com or 610.943.5048 if you need accommodation at any stage of the application process or want more information on our accommodation policies. Policy: Candidate Use of AI in Live Interviews ..." We need to remove boilerplate: EEO, accommodation contact maybe considered boilerplate? It's about accommodation; could be considered legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The accommodation contact is likely legal/EEO; we should remove that. Also the AI policy is likely legal; remove. Also the disclaimer about job description not comprehensive; remove. Also the standard base pay range paragraph; that's about Pay but includes filler like "standard base pay range is posted at a minimum and maximum rate." Might be considered not specific? It says "The standard base pay range for this role is posted at a minimum and maximum rate. The starting rate of pay offered will vary based on factors including, but not limited to, position offered, location, training, and/or experience, and internal equity. This base pay range is specific to the state this role is posted in and may not be applicable to other locations. At David’s Bridal, it is rare for an individual to be hired at the high end of the range in their role, and compensation decisions are dependent upon the details and circumstances of each position and candidate." That's not specific numbers; it's generic. According to rule: 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. The posting does mention "Competitive Pay" but not specific numbers. It also mentions "Full Time Opportunity – A comprehensive benefits package is available." Then lists benefits: Generous Dream Maker Discount After First Pay Period, Referral Incentive Program, Dayforce Wallet – Get Paid Early!, Health/Dental/Vision Insurance, 401K Program, Paid Vacation, Wellness Days & Holidays, including your Birthday off!, Pet Benefits. Those are specific benefits. So we can include Benefits section with those items. Pay: we have "Competitive Pay" but no specific numbers or range. According to rule, we should not create Pay section unless posting actually states them (specific). It says "Competitive Pay" is vague; maybe we should not include Pay section. However we could include a short paragraph under Benefits? But the instruction says prefer a few substantive sections over many thin ones. Since Pay is vague, better to omit Pay section. Schedule: posting mentions "Full Time Opportunity". That's schedule info. Could include Schedule section with "Full Time". That's specific enough? It's not vague like "varies". It states Full Time. So we can include Schedule section with that. Now we need to craft HTML. Sections:

About the role

with paragraphs summarizing the introductory marketing fluff and role description.

Responsibilities

with

• items for each duty. We need to split duties into sensible items. List of duties from text: - Welcome all customers with genuine, friendly enthusiasm over the phone and in person; communicate clearly and concisely adapting style to suit customers by problem solving, excellent phone skills and resolving conflict. - Respond promptly to all customer questions by providing product and service information. - Drive customer loyalty by making clientele calls to maximize appointments, build and provide customer service. - 80% for Bridal, 30% for Dress. (This seems odd; maybe it's a metric? Could be a note: "80% for Bridal, 30% for Dress." Might be a target? We'll keep as a bullet. - Act as Floor Manager during peak sales times to offer fit and alterations consultations. - Assist stylists in closing sales by consulting with customers regarding gown fit and customization. - Communicate how alterations can play an important role in perfecting the dress for her event in partnership with Alterations. - Promote all alteration services and personalization options. - Lead and oversee all alterations fittings, sewing, steaming, pressing and spot cleaning of garments to company standards. - Maintain quality control guidelines and inspect all garments altered/steamed/pressed to verify pristine condition before final delivery to customer. - Train Alterations Specialists in fitting and sewing techniques. - Ensure ongoing product education for all Alterations team members. - Communicate daily sales goal achieved to Store Manager. - Use all approved systems and processes to manage the customer’s flow to deliver a 5 Star Customer Experience. - Maintain high dress code standards per dress code. Physical Demands: we can add as bullet items under Responsibilities or separate? Could add a subheading? Not allowed. We'll add as bullet items under Responsibilities as well. Physical Demands bullets: - Stand, walk, and sit for extended periods of time. - Reach for tools and objects with hands and arms. - Climb stairs. - Stoop, kneel, crouch, or crawl. - Talk to and hear customers. - Occasionally lift up to 25 pounds. - See up close and at a distance, use peripheral vision and depth perception. - Use a computer and all other electronic devices for long periods of time. Education & Credentials: we can put under Requirements.

  Requirements

  with
  • items: - High School Diploma or degree. - Prior sewing experience required, preferably in bridal and/or special occasion production environment. - 1-2 years prior retail experience in an apparel or specialty store environment. - Prior experience with computerized POS system and ability to use one. Maybe also "Prior seeing experience required" is a typo for sewing. Now Benefits section:

    Benefits

    with
    • items: - Full Time Opportunity (maybe schedule but we have schedule separate) - Comprehensive benefits package - Generous Dream Maker Discount after first pay period - Referral Incentive Program - Dayforce Wallet – Get Paid Early! - Health/Dental/Vision Insurance - 401K Program - Paid Vacation, Wellness Days & Holidays, including Birthday off - Pet Benefits But we separated schedule; maybe we keep Full Time under Schedule. Schedule section:

      Schedule

      with

      Full Time Opportunity

      or
      • Full Time
      . Use

      for prose. Now we need to ensure we don't repeat job title as heading. We haven't. We must not include any markdown code fences. Just raw HTML. Let's craft. We'll start with

      About the role

      then

      ...

      . Combine marketing fluff and role description into maybe two paragraphs. Paragraph 1: "From Aisle to Algorithm and for