Field Representative
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Key sections:
- About the role: The first paragraph: "This seasonal, field-based role focuses on executing candidate attraction and community outreach activities within an assigned local market. Working from a clearly defined playbook and under the guidance of a Market Response Specialist, you will carry out grassroots recruiting efforts, build relationships with community partners, and promote referral and hiring programs for entry-level warehouse roles. You will work independently in the field, manage your own weekly schedule within a 32-hour framework, and provide detailed reporting on your activities and local market insights."
That's about the role.
- Responsibilities: The list under "Responsibilities". We need to capture each bullet.
- Essential Skills: This is a list of skills/requirements. Could be under Skills or Requirements. The instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each content.
We have "Essential Skills" list: high school diploma or equivalent; residence within commutable distance; reliable personal transportation; ability to work independently; strong organizational skills; comfort engaging; clear written and verbal communication; customer service mindset; availability to work flexible 32-hour weekly schedule; dependability and accountability.
These could be under Skills or Requirements. The posting also has "Work Environment" which gives details about schedule, etc. Could be under Schedule or maybe under About the role? But we have a Schedule section if schedule details exist. The posting mentions schedule: "manage your own weekly schedule within a 32-hour framework", "Availability to work a flexible 32-hour weekly schedule, including some weekends, and occasional early morning or evening hours based on market needs." Work Environment gives more schedule specifics: typical 32 hours per week, some days as short as 4 hours and others up to 8 hours, rare up to 10 hours, early starts 5 a.m., evening up to 9 p.m., weekend work part of schedule. So we have schedule details.
Thus we can create a Schedule section with those details.
Pay And Benefits section: includes pay range $21.00 - $22.00/hr, and benefits list. So we need Pay and Benefits sections? The instruction: "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits into one section? But they have separate headings possible: Pay and Benefits. However they said include a section ONLY when the posting has real, specific content for it. Both Pay and Benefits have content. Could we combine them? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could have separate Pay and Benefits sections. But they also say prefer a few substantive sections over many thin ones. However having both Pay and Benefits is reasonable as they are distinct. Could we combine them into a single "Compensation and Benefits"? Not in the list. The list includes Benefits and Pay as separate possible headings. I'd follow the list: include Pay and Benefits sections separately if content exists.
But we need to avoid filler. Pay range is specific. Benefits list is specific.
Thus we will have sections: About the role, Responsibilities, Skills (or Requirements?), Benefits, Pay, Schedule. Also maybe Requirements? The Essential Skills could be considered Skills. Could also be Requirements (like high school diploma, residence, transportation). But they are more like qualifications/requirements. The heading list includes Requirements and Qualifications and Skills. We need to decide where to put each piece.
We have "Essential Skills" list: includes high school diploma or equivalent (qualification), residence within commutable distance (requirement), reliable personal transportation (requirement), ability to work independently (skill), strong organizational skills (skill), comfort engaging (skill), clear written and verbal communication (skill), customer service mindset (skill), availability to work flexible 32-hour schedule (schedule/requirement), dependability and accountability (skill). This mixes qualifications and skills.
We could put under Requirements: high school diploma or equivalent, residence within commutable distance, reliable personal transportation, availability to work flexible 32-hour weekly schedule (maybe schedule). Under Skills: ability to work independently, strong organizational skills, comfort engaging, clear written and verbal communication, customer service mindset, dependability and accountability.
But the instruction says prefer a few substantive sections over many thin ones. Having both Requirements and Skills may be thin. Could combine them into a single "Requirements and Skills" but not in list. Could put all under "Skills" as that covers both. Or under "Requirements". The list includes Skills as a possible heading. I'd put all under Skills to keep fewer sections.
Thus sections: About the role, Responsibilities, Skills, Benefits, Pay, Schedule.
We also have Work Environment details that could go under Schedule (already) and maybe under About the role? But we already have About the role covering general description. Work Environment gives more context about schedule, location, etc. Could incorporate schedule details there, but we already have Schedule section.
We need to preserve ALL substantive information. So we must include details from Work Environment: typical 32 hours per week, some days as short as 4 hours and others up to 8 hours, rare up to 10 hours, early starts 5 a.m., evening up to 9 p.m., weekend work part of schedule, work locations vary, you will use own reliable transportation, mileage reimbursement, attire professional yet practical, environment fast-paced, etc. Some of these are not schedule but work environment details. Where to put them? Could be under About the role (expanded) or maybe a separate section like "Work Environment" but not in allowed headings. Since we must only use allowed headings, we need to fit them somewhere. Could add to About the role (makes it longer) or to Schedule (some details like mileage reimbursement, attire, environment). But Schedule is about timing; mileage reimbursement and attire are not schedule. Could put under Benefits? No. Could put under Skills? No.
We could create a section "Work Environment" but not allowed. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning examples, not exhaustive list? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the allowed headings. It does not explicitly forbid other headings, but says use those for section headings. Likely we should stick to those. So we need to fit Work Environment details into one of those.
Probably best to expand About the role to include work environment details. Or we could put under Responsibilities? No.
Thus About the role will include the initial description plus work environment details.
Responsibilities list as given.
Skills list as given (essential skills).
Benefits list as given.
Pay: pay range.
Schedule: schedule details from the posting (including the 32-hour framework, flexible schedule, weekend work, early/evening hours, typical hours per day, etc.) Also include mileage reimbursement? That is more about travel reimbursement, could be under Benefits? Actually mileage reimbursement is a benefit. Could include under Benefits as well. But we already have benefits list; mileage reimbursement is mentioned under Work Environment: "Mileage reimbursement is available for approved travel." That's a benefit. So we should add that to Benefits.
Attire: "Attire should be professional yet practical for field work, community events, and extended periods of walking or standing." That's not a benefit, could be under About the role or maybe under Skills? Not really. Could be under About the role as part of role description.
Environment fast-paced etc: also About the role.
Thus we will incorporate those into About the role.
Now we need to ensure we don't repeat boilerplate: remove EEO, legal, accommodation, etc. Also remove "Application Deadline", "Job Type & Location", "Workplace Type", "About Aston Carter", etc. Also remove "Job Type & Location This is a Contract position based out of Duluth, MN." That's minor metadata; we could fold into a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a short paragraph about job type and location maybe under About the role? But we already have location in About the role? Not yet. We could add a sentence: "This is a seasonal contract position based in Duluth, MN." That's minor metadata; we can include as a short
maybe under About the role or separate? But we should not create a heading for it. Could add a
after About the role heading? Actually About the role heading will have content; we can include that sentence within the About the role
content.
Similarly "Application Deadline This position is anticipated to close on Sep 16, 2026." That's also minor metadata; we could drop it or fold into a short
. Probably drop it as it's not substantive for the role? It's about timing; maybe we could include under About the role as a note. But the instruction says preserve ALL substantive information; is application deadline substantive? It's about when to apply, not about the job itself. Might be considered not substantive for the role description. The instruction says remove application instructions. Application deadline is akin to application instructions. So we should drop it.
"Workplace Type This is a fully onsite position in Duluth,MN." That's also minor metadata; we can incorporate location again.
Thus we will keep location mention maybe once.
Now we need to output only HTML fragment.
Structure:
About the role
... (combined description)
Responsibilities
- ...
...
Skills
- ...
...
Benefits
- ...
...
Pay
The pay range for this position is $21.00 - $22.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
But we need to avoid filler like "Individual compensation offered..." is that filler? It's specific about how compensation determined. It's substantive. Keep.
We could also include eligibility note? The posting says "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." That's generic; maybe we can drop as filler? It's somewhat boilerplate. Might be considered not
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Key sections: - About the role: The first paragraph: "This seasonal, field-based role focuses on executing candidate attraction and community outreach activities within an assigned local market. Working from a clearly defined playbook and under the guidance of a Market Response Specialist, you will carry out grassroots recruiting efforts, build relationships with community partners, and promote referral and hiring programs for entry-level warehouse roles. You will work independently in the field, manage your own weekly schedule within a 32-hour framework, and provide detailed reporting on your activities and local market insights." That's about the role. - Responsibilities: The list under "Responsibilities". We need to capture each bullet. - Essential Skills: This is a list of skills/requirements. Could be under Skills or Requirements. The instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each content. We have "Essential Skills" list: high school diploma or equivalent; residence within commutable distance; reliable personal transportation; ability to work independently; strong organizational skills; comfort engaging; clear written and verbal communication; customer service mindset; availability to work flexible 32-hour weekly schedule; dependability and accountability. These could be under Skills or Requirements. The posting also has "Work Environment" which gives details about schedule, etc. Could be under Schedule or maybe under About the role? But we have a Schedule section if schedule details exist. The posting mentions schedule: "manage your own weekly schedule within a 32-hour framework", "Availability to work a flexible 32-hour weekly schedule, including some weekends, and occasional early morning or evening hours based on market needs." Work Environment gives more schedule specifics: typical 32 hours per week, some days as short as 4 hours and others up to 8 hours, rare up to 10 hours, early starts 5 a.m., evening up to 9 p.m., weekend work part of schedule. So we have schedule details. Thus we can create a Schedule section with those details. Pay And Benefits section: includes pay range $21.00 - $22.00/hr, and benefits list. So we need Pay and Benefits sections? The instruction: "Prefer a few substantive sections over many thin ones." Could combine Pay and Benefits into one section? But they have separate headings possible: Pay and Benefits. However they said include a section ONLY when the posting has real, specific content for it. Both Pay and Benefits have content. Could we combine them? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could have separate Pay and Benefits sections. But they also say prefer a few substantive sections over many thin ones. However having both Pay and Benefits is reasonable as they are distinct. Could we combine them into a single "Compensation and Benefits"? Not in the list. The list includes Benefits and Pay as separate possible headings. I'd follow the list: include Pay and Benefits sections separately if content exists. But we need to avoid filler. Pay range is specific. Benefits list is specific. Thus we will have sections: About the role, Responsibilities, Skills (or Requirements?), Benefits, Pay, Schedule. Also maybe Requirements? The Essential Skills could be considered Skills. Could also be Requirements (like high school diploma, residence, transportation). But they are more like qualifications/requirements. The heading list includes Requirements and Qualifications and Skills. We need to decide where to put each piece. We have "Essential Skills" list: includes high school diploma or equivalent (qualification), residence within commutable distance (requirement), reliable personal transportation (requirement), ability to work independently (skill), strong organizational skills (skill), comfort engaging (skill), clear written and verbal communication (skill), customer service mindset (skill), availability to work flexible 32-hour schedule (schedule/requirement), dependability and accountability (skill). This mixes qualifications and skills. We could put under Requirements: high school diploma or equivalent, residence within commutable distance, reliable personal transportation, availability to work flexible 32-hour weekly schedule (maybe schedule). Under Skills: ability to work independently, strong organizational skills, comfort engaging, clear written and verbal communication, customer service mindset, dependability and accountability. But the instruction says prefer a few substantive sections over many thin ones. Having both Requirements and Skills may be thin. Could combine them into a single "Requirements and Skills" but not in list. Could put all under "Skills" as that covers both. Or under "Requirements". The list includes Skills as a possible heading. I'd put all under Skills to keep fewer sections. Thus sections: About the role, Responsibilities, Skills, Benefits, Pay, Schedule. We also have Work Environment details that could go under Schedule (already) and maybe under About the role? But we already have About the role covering general description. Work Environment gives more context about schedule, location, etc. Could incorporate schedule details there, but we already have Schedule section. We need to preserve ALL substantive information. So we must include details from Work Environment: typical 32 hours per week, some days as short as 4 hours and others up to 8 hours, rare up to 10 hours, early starts 5 a.m., evening up to 9 p.m., weekend work part of schedule, work locations vary, you will use own reliable transportation, mileage reimbursement, attire professional yet practical, environment fast-paced, etc. Some of these are not schedule but work environment details. Where to put them? Could be under About the role (expanded) or maybe a separate section like "Work Environment" but not in allowed headings. Since we must only use allowed headings, we need to fit them somewhere. Could add to About the role (makes it longer) or to Schedule (some details like mileage reimbursement, attire, environment). But Schedule is about timing; mileage reimbursement and attire are not schedule. Could put under Benefits? No. Could put under Skills? No. We could create a section "Work Environment" but not allowed. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning examples, not exhaustive list? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests those are the allowed headings. It does not explicitly forbid other headings, but says use those for section headings. Likely we should stick to those. So we need to fit Work Environment details into one of those.
Probably best to expand About the role to include work environment details. Or we could put under Responsibilities? No.
Thus About the role will include the initial description plus work environment details.
Responsibilities list as given.
Skills list as given (essential skills).
Benefits list as given.
Pay: pay range.
Schedule: schedule details from the posting (including the 32-hour framework, flexible schedule, weekend work, early/evening hours, typical hours per day, etc.) Also include mileage reimbursement? That is more about travel reimbursement, could be under Benefits? Actually mileage reimbursement is a benefit. Could include under Benefits as well. But we already have benefits list; mileage reimbursement is mentioned under Work Environment: "Mileage reimbursement is available for approved travel." That's a benefit. So we should add that to Benefits.
Attire: "Attire should be professional yet practical for field work, community events, and extended periods of walking or standing." That's not a benefit, could be under About the role or maybe under Skills? Not really. Could be under About the role as part of role description.
Environment fast-paced etc: also About the role.
Thus we will incorporate those into About the role.
Now we need to ensure we don't repeat boilerplate: remove EEO, legal, accommodation, etc. Also remove "Application Deadline", "Job Type & Location", "Workplace Type", "About Aston Carter", etc. Also remove "Job Type & Location This is a Contract position based out of Duluth, MN." That's minor metadata; we could fold into a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include a short paragraph about job type and location maybe under About the role? But we already have location in About the role? Not yet. We could add a sentence: "This is a seasonal contract position based in Duluth, MN." That's minor metadata; we can include as a short
maybe under About the role or separate? But we should not create a heading for it. Could add a
after About the role heading? Actually About the role heading will have content; we can include that sentence within the About the role
content. Similarly "Application Deadline This position is anticipated to close on Sep 16, 2026." That's also minor metadata; we could drop it or fold into a short
. Probably drop it as it's not substantive for the role? It's about timing; maybe we could include under About the role as a note. But the instruction says preserve ALL substantive information; is application deadline substantive? It's about when to apply, not about the job itself. Might be considered not substantive for the role description. The instruction says remove application instructions. Application deadline is akin to application instructions. So we should drop it. "Workplace Type This is a fully onsite position in Duluth,MN." That's also minor metadata; we can incorporate location again. Thus we will keep location mention maybe once. Now we need to output only HTML fragment. Structure:
About the role
... (combined description)
Responsibilities
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
The pay range for this position is $21.00 - $22.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
But we need to avoid filler like "Individual compensation offered..." is that filler? It's specific about how compensation determined. It's substantive. Keep. We could also include eligibility note? The posting says "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." That's generic; maybe we can drop as filler? It's somewhat boilerplate. Might be considered not