PT Sales Associate - Seasonal
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include section ONLY when posting has real, specific content for it
- Never emit heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment, no /, no markdown code fences
Now, let's map content to sections:
- "About the role" or "About the company": The first paragraph describes the company. Could be "About the company" but the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the role" is allowed. But the first paragraph is about the company, not the role. However, "Life @ToryBurch is Special Because" is about benefits/culture. "This Role Is Tailor-Made For You Because" is about the ideal candidate. "A Day In The Life" is responsibilities. "To Land This Role" is requirements/qualifications. "Why You'll Want To Join Our Team" is benefits. "How We Work Together" and "#TeamTory Values" are culture/values. "Compensation Range" is pay. "Benefits Information" mentions benefits but doesn't list specifics - it says "Here are highlights of key benefits available to all eligible Tory Burch team members." but then no list follows. That's placeholder/filler. So we should not create a Benefits section unless there are actual benefits listed. However, "Life @ToryBurch is Special Because" lists specific benefits: competitive pay, well-being benefits, employee discount, retail excellence programs, paid volunteer days. That's substantive. So we can have a Benefits section with that content.
- "Why You'll Want To Join Our Team" also mentions benefits: making customers feel welcome, entrepreneurial thinking, innovative ideas. That's more culture.
- "How We Work Together" and "#TeamTory Values" are values/culture. Could be combined into a "Values" section? But allowed headings don't include "Values". The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map to these. "Values" not allowed. Could be part of "About the role" or "Benefits"? But the rules say use those headings. However, the instruction says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule" - it's not exhaustive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, but we should stick to these or similar semantic headings. But the rule: "include a section ONLY when the posting has real, specific content for it". So we can create headings that match the content. However, the user gave a list of example headings. I think we should use those headings where appropriate. For values/culture, maybe "About the role" can include company culture. But there's a lot of culture content. Could create a "Culture" heading? But not in the example list. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but says "e.g." meaning for example. However, the rule "Prefer a few substantive sections over many thin ones." So we can group related content.
Let's plan sections:
1. About the role: Could include company description and role overview. The first paragraph is company description. "This Role Is Tailor-Made For You Because" describes the ideal candidate. That could be part of "About the role" or "Qualifications". But "Qualifications" is a heading example. "Requirements" is also example. "To Land This Role" is requirements. So we can have "Requirements" for that.
2. Responsibilities: "A Day In The Life" describes typical day. That's responsibilities.
3. Requirements: "To Land This Role" lists specific requirements.
4. Benefits: "Life @ToryBurch is Special Because" lists specific benefits. Also "Why You'll Want To Join Our Team" mentions some benefits. Could combine.
5. Pay: "Compensation Range" gives specific range: 15.00 USD - 17.00 USD. That's specific, so include Pay section.
6. Schedule: The posting mentions "Must have open availability for a flexible work schedule that meets the needs of the business, including overnights, evenings, holidays and weekend shifts". That's schedule information. So we can include a Schedule section.
7. Values/Culture: "How We Work Together" and "#TeamTory Values" are values. Could be part of "About the role" or a separate "Culture" section. But not in example headings. However, the instruction says "use for section headings (e.g. ...)" - it's not exclusive. But to be safe, maybe include as "About the role" or "Qualifications"? Not really. Could create a "Culture" heading. But the rule: "include a section ONLY when the posting has real, specific content for it". It does have specific content. I think it's okay to include a "Culture" or "Values" heading. But the user might expect only the example headings. Let's see the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say "only these". It says "e.g." So we can use other headings if needed. However, the system prompt says "Rules: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the headings to use. But the posting has values content. Could we put values under "About the role"? Might be a stretch. Could create a "Values" heading. I think it's acceptable.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine culture/values into "About the role" or "Benefits". However, "Benefits" is for benefits. "About the role" could include company culture. Let's see: The first paragraph is company description. "Life @ToryBurch is Special Because" is benefits. "How We Work Together" and "#TeamTory Values" are values. Could be a "Culture" section. I'll include a "Culture" section with that content.
But the user might want strict adherence to the example headings. Let's examine the example: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "Qualifications" and "Requirements" are similar. "Skills" separate. The posting has "To Land This Role" which is requirements/qualifications. Could split into Requirements and Qualifications? But they are similar. Could have "Requirements" for the list.
Also "Skills" not explicitly listed but "strong personal selling and customer relations experience, along with verbal and written communication skills" could be skills.
But the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include all details.
Let's structure:
- About the role: Company description + role overview (from "This Role Is Tailor-Made For You Because")
- Responsibilities: "A Day In The Life"
- Requirements: "To Land This Role"
- Benefits: "Life @ToryBurch is Special Because" + "Why You'll Want To Join Our Team" (but the latter is more culture)
- Pay: "Compensation Range"
- Schedule: schedule requirement from "To Land This Role" (open availability, flexible schedule, overnights, evenings, holidays, weekends)
- Culture: "How We Work Together" and "#TeamTory Values"
But "Why You'll Want To Join Our Team" is also benefits/culture. Could merge into Benefits or Culture.
Let's decide on sections:
1. About the role
2. Responsibilities
3. Requirements
4. Benefits
5. Pay
6. Schedule
7. Culture
That's 7 sections. Might be okay.
Now, for each section, use and then
or
- .
Let's extract content:
**About the role**:
- Company description: "We are an American luxury lifestyle brand, founded in 2004. Anchored in the casual elegance of American sportswear, Tory’s design philosophy is defined by effortless silhouettes, innovative materials, eclectic juxtapositions of color, and the tension of past and present. The collections include ready-to-wear, handbags, footwear, accessories, jewelry, home and beauty. Empowering women is the company’s guiding principle, expressed through Tory’s collections and reflected in the company culture as well as the work of the Tory Burch Foundation. Established in 2009, the Foundation provides women entrepreneurs in the United States with access to capital, education and community. You are seeking a work environment where people are encouraged to dream, explore, discover and, as important, laugh together. If you’re prepared to work hard, create impact, and have fun while doing it, we would love to have you join #TeamTory. Apply today!"
- Role overview: "This Role Is Tailor-Made For You Because You are passionate about delivering a transformational client experience, building our brand one customer at a time and driving business through sales. You demonstrate a strong commitment to service, a genuine curiosity and interest in people, authenticity, fashion & style sensibility, and exceptional selling skills. You’re also resourceful and collaborative – a team player who is savvy about the visual and operational aspects of the role and committed to loss prevention. A sense of humor is a plus!"
Could be two paragraphs or combine. Use
for prose.
**Responsibilities**: "A Day In The Life The typical day is… atypical. You might be building and maintaining new and existing customer relationships to drive the business and meet personal sales goals, creating the customer experience
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it - Never emit heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment, no /, no markdown code fences Now, let's map content to sections: - "About the role" or "About the company": The first paragraph describes the company. Could be "About the company" but the allowed headings are specific: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the role" is allowed. But the first paragraph is about the company, not the role. However, "Life @ToryBurch is Special Because" is about benefits/culture. "This Role Is Tailor-Made For You Because" is about the ideal candidate. "A Day In The Life" is responsibilities. "To Land This Role" is requirements/qualifications. "Why You'll Want To Join Our Team" is benefits. "How We Work Together" and "#TeamTory Values" are culture/values. "Compensation Range" is pay. "Benefits Information" mentions benefits but doesn't list specifics - it says "Here are highlights of key benefits available to all eligible Tory Burch team members." but then no list follows. That's placeholder/filler. So we should not create a Benefits section unless there are actual benefits listed. However, "Life @ToryBurch is Special Because" lists specific benefits: competitive pay, well-being benefits, employee discount, retail excellence programs, paid volunteer days. That's substantive. So we can have a Benefits section with that content. - "Why You'll Want To Join Our Team" also mentions benefits: making customers feel welcome, entrepreneurial thinking, innovative ideas. That's more culture. - "How We Work Together" and "#TeamTory Values" are values/culture. Could be combined into a "Values" section? But allowed headings don't include "Values". The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map to these. "Values" not allowed. Could be part of "About the role" or "Benefits"? But the rules say use those headings. However, the instruction says "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule" - it's not exhaustive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, but we should stick to these or similar semantic headings. But the rule: "include a section ONLY when the posting has real, specific content for it". So we can create headings that match the content. However, the user gave a list of example headings. I think we should use those headings where appropriate. For values/culture, maybe "About the role" can include company culture. But there's a lot of culture content. Could create a "Culture" heading? But not in the example list. The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid other headings, but says "e.g." meaning for example. However, the rule "Prefer a few substantive sections over many thin ones." So we can group related content.
Let's plan sections:
1. About the role: Could include company description and role overview. The first paragraph is company description. "This Role Is Tailor-Made For You Because" describes the ideal candidate. That could be part of "About the role" or "Qualifications". But "Qualifications" is a heading example. "Requirements" is also example. "To Land This Role" is requirements. So we can have "Requirements" for that.
2. Responsibilities: "A Day In The Life" describes typical day. That's responsibilities.
3. Requirements: "To Land This Role" lists specific requirements.
4. Benefits: "Life @ToryBurch is Special Because" lists specific benefits. Also "Why You'll Want To Join Our Team" mentions some benefits. Could combine.
5. Pay: "Compensation Range" gives specific range: 15.00 USD - 17.00 USD. That's specific, so include Pay section.
6. Schedule: The posting mentions "Must have open availability for a flexible work schedule that meets the needs of the business, including overnights, evenings, holidays and weekend shifts". That's schedule information. So we can include a Schedule section.
7. Values/Culture: "How We Work Together" and "#TeamTory Values" are values. Could be part of "About the role" or a separate "Culture" section. But not in example headings. However, the instruction says "use for section headings (e.g. ...)" - it's not exclusive. But to be safe, maybe include as "About the role" or "Qualifications"? Not really. Could create a "Culture" heading. But the rule: "include a section ONLY when the posting has real, specific content for it". It does have specific content. I think it's okay to include a "Culture" or "Values" heading. But the user might expect only the example headings. Let's see the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say "only these". It says "e.g." So we can use other headings if needed. However, the system prompt says "Rules: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the headings to use. But the posting has values content. Could we put values under "About the role"? Might be a stretch. Could create a "Values" heading. I think it's acceptable.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine culture/values into "About the role" or "Benefits". However, "Benefits" is for benefits. "About the role" could include company culture. Let's see: The first paragraph is company description. "Life @ToryBurch is Special Because" is benefits. "How We Work Together" and "#TeamTory Values" are values. Could be a "Culture" section. I'll include a "Culture" section with that content.
But the user might want strict adherence to the example headings. Let's examine the example: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "Qualifications" and "Requirements" are similar. "Skills" separate. The posting has "To Land This Role" which is requirements/qualifications. Could split into Requirements and Qualifications? But they are similar. Could have "Requirements" for the list.
Also "Skills" not explicitly listed but "strong personal selling and customer relations experience, along with verbal and written communication skills" could be skills.
But the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include all details.
Let's structure:
- About the role: Company description + role overview (from "This Role Is Tailor-Made For You Because")
- Responsibilities: "A Day In The Life"
- Requirements: "To Land This Role"
- Benefits: "Life @ToryBurch is Special Because" + "Why You'll Want To Join Our Team" (but the latter is more culture)
- Pay: "Compensation Range"
- Schedule: schedule requirement from "To Land This Role" (open availability, flexible schedule, overnights, evenings, holidays, weekends)
- Culture: "How We Work Together" and "#TeamTory Values"
But "Why You'll Want To Join Our Team" is also benefits/culture. Could merge into Benefits or Culture.
Let's decide on sections:
1. About the role
2. Responsibilities
3. Requirements
4. Benefits
5. Pay
6. Schedule
7. Culture
That's 7 sections. Might be okay.
Now, for each section, use and then
for section headings (e.g. ...)" - it's not exclusive. But to be safe, maybe include as "About the role" or "Qualifications"? Not really. Could create a "Culture" heading. But the rule: "include a section ONLY when the posting has real, specific content for it". It does have specific content. I think it's okay to include a "Culture" or "Values" heading. But the user might expect only the example headings. Let's see the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say "only these". It says "e.g." So we can use other headings if needed. However, the system prompt says "Rules: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the headings to use. But the posting has values content. Could we put values under "About the role"? Might be a stretch. Could create a "Values" heading. I think it's acceptable.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine culture/values into "About the role" or "Benefits". However, "Benefits" is for benefits. "About the role" could include company culture. Let's see: The first paragraph is company description. "Life @ToryBurch is Special Because" is benefits. "How We Work Together" and "#TeamTory Values" are values. Could be a "Culture" section. I'll include a "Culture" section with that content.
But the user might want strict adherence to the example headings. Let's examine the example: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "Qualifications" and "Requirements" are similar. "Skills" separate. The posting has "To Land This Role" which is requirements/qualifications. Could split into Requirements and Qualifications? But they are similar. Could have "Requirements" for the list.
Also "Skills" not explicitly listed but "strong personal selling and customer relations experience, along with verbal and written communication skills" could be skills.
But the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include all details.
Let's structure:
- About the role: Company description + role overview (from "This Role Is Tailor-Made For You Because")
- Responsibilities: "A Day In The Life"
- Requirements: "To Land This Role"
- Benefits: "Life @ToryBurch is Special Because" + "Why You'll Want To Join Our Team" (but the latter is more culture)
- Pay: "Compensation Range"
- Schedule: schedule requirement from "To Land This Role" (open availability, flexible schedule, overnights, evenings, holidays, weekends)
- Culture: "How We Work Together" and "#TeamTory Values"
But "Why You'll Want To Join Our Team" is also benefits/culture. Could merge into Benefits or Culture.
Let's decide on sections:
1. About the role
2. Responsibilities
3. Requirements
4. Benefits
5. Pay
6. Schedule
7. Culture
That's 7 sections. Might be okay.
Now, for each section, use and then
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the headings to use. But the posting has values content. Could we put values under "About the role"? Might be a stretch. Could create a "Values" heading. I think it's acceptable.
But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine culture/values into "About the role" or "Benefits". However, "Benefits" is for benefits. "About the role" could include company culture. Let's see: The first paragraph is company description. "Life @ToryBurch is Special Because" is benefits. "How We Work Together" and "#TeamTory Values" are values. Could be a "Culture" section. I'll include a "Culture" section with that content.
But the user might want strict adherence to the example headings. Let's examine the example: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". "Qualifications" and "Requirements" are similar. "Skills" separate. The posting has "To Land This Role" which is requirements/qualifications. Could split into Requirements and Qualifications? But they are similar. Could have "Requirements" for the list.
Also "Skills" not explicitly listed but "strong personal selling and customer relations experience, along with verbal and written communication skills" could be skills.
But the rule: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include all details.
Let's structure:
- About the role: Company description + role overview (from "This Role Is Tailor-Made For You Because")
- Responsibilities: "A Day In The Life"
- Requirements: "To Land This Role"
- Benefits: "Life @ToryBurch is Special Because" + "Why You'll Want To Join Our Team" (but the latter is more culture)
- Pay: "Compensation Range"
- Schedule: schedule requirement from "To Land This Role" (open availability, flexible schedule, overnights, evenings, holidays, weekends)
- Culture: "How We Work Together" and "#TeamTory Values"
But "Why You'll Want To Join Our Team" is also benefits/culture. Could merge into Benefits or Culture.
Let's decide on sections:
1. About the role
2. Responsibilities
3. Requirements
4. Benefits
5. Pay
6. Schedule
7. Culture
That's 7 sections. Might be okay.
Now, for each section, use and then
or
- .
Let's extract content:
**About the role**:
- Company description: "We are an American luxury lifestyle brand, founded in 2004. Anchored in the casual elegance of American sportswear, Tory’s design philosophy is defined by effortless silhouettes, innovative materials, eclectic juxtapositions of color, and the tension of past and present. The collections include ready-to-wear, handbags, footwear, accessories, jewelry, home and beauty. Empowering women is the company’s guiding principle, expressed through Tory’s collections and reflected in the company culture as well as the work of the Tory Burch Foundation. Established in 2009, the Foundation provides women entrepreneurs in the United States with access to capital, education and community. You are seeking a work environment where people are encouraged to dream, explore, discover and, as important, laugh together. If you’re prepared to work hard, create impact, and have fun while doing it, we would love to have you join #TeamTory. Apply today!"
- Role overview: "This Role Is Tailor-Made For You Because You are passionate about delivering a transformational client experience, building our brand one customer at a time and driving business through sales. You demonstrate a strong commitment to service, a genuine curiosity and interest in people, authenticity, fashion & style sensibility, and exceptional selling skills. You’re also resourceful and collaborative – a team player who is savvy about the visual and operational aspects of the role and committed to loss prevention. A sense of humor is a plus!"
Could be two paragraphs or combine. Use
for prose. **Responsibilities**: "A Day In The Life The typical day is… atypical. You might be building and maintaining new and existing customer relationships to drive the business and meet personal sales goals, creating the customer experience