ADE - WA
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a 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") and never create Pay/Schedule/Benefits sections unless posting actually states them.
We need to decide which sections have content.
From posting:
- Job Overview: description paragraph. Could be "About the role". That is a section.
- Key Responsibilities: list of duties. That's Responsibilities.
- Required Qualifications: list. That's Requirements or Qualifications? The spec says we can use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content appropriately. Likely "Required Qualifications" goes under Requirements or Qualifications. "Preferred Qualifications" maybe under Qualifications or Skills. There's also "Work Environment" which could be Schedule? Not exactly. There's mention of "Five days per week in the field", "Travel required", "Mileage reimbursement and monthly phone stipend". That's schedule/benefits? Could be Schedule (work schedule) and Benefits (reimbursement, stipend). Also "PTO eligibility after a successful six-month performance review." That's benefit.
- Pay And Benefits: includes pay range $32.00 - $32.00/hr (so fixed). Also benefits list. So we need Pay and Benefits sections.
- Work Environment: could be Schedule? It mentions "Five days per week in the field visiting businesses and attending community events." That's schedule. Also "Travel required throughout the assigned territory, typically within a two-hour driving radius." That's also schedule/travel. Could be Schedule section.
- Job Type & Location: "This is a Contract position based out of Bremerton, WA." That's maybe not a heading; could be part of About the role or omitted? The spec says do not repeat job title as heading; we can include location in About the role paragraph.
- Application Deadline: that's application instruction; we should remove.
- About Aston Carter: boilerplate about company; we should remove as it's not specific to role? It's generic company description; likely remove.
- EEO etc: remove.
Thus we need sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications), Qualifications (maybe Preferred Qualifications), Skills (maybe we can extract skills from qualifications), Benefits, Pay, Schedule.
We must not create sections with filler. Ensure each section has substantive content.
Let's extract content:
About the role: from Job Overview paragraph: "We're looking for a motivated field sales professional to help recruit local small businesses into a new delivery partner program. In this role, you'll work closely with a Field Manager to identify prospects, explain the program, guide businesses through the application process, and support local recruiting events. This is a field-based position requiring regular travel within the assigned territory. In addition to a competitive base rate, the role offers uncapped commission for each successful partner conversion."
We can keep that as prose
.
Responsibilities: list from Key Responsibilities bullet points (each line starts with a verb). We'll make
- each.
Responsibilities list:
- Visit local businesses within the assigned territory to introduce the delivery partner program.
- Build relationships with business owners and decision-makers.
- Present program benefits and answer questions from prospective partners.
- Qualify interested businesses and assist them through the application process.
- Manage leads, activities, and partner information using Salesforce.
- Maintain an organized sales pipeline and track follow-up activities.
- Support community outreach events, including local networking and informational sessions.
- Partner with local organizations and business groups to generate referrals.
- Accurately update activity and lead data in Salesforce and Excel.
- Deliver excellent customer service throughout the recruitment and onboarding process.
Requirements: from Required Qualifications bullet list:
- 2+ years of sales, customer service, or related experience.
- Previous field, outside sales, or door-to-door sales experience.
- Experience using a CRM system (Salesforce preferred).
- Strong communication and relationship-building skills.
- Ability to influence, negotiate, and close opportunities.
- Comfortable working independently in a field-based environment.
- Proficient with technology, including CRM systems and Microsoft Excel.
- Valid driver's license and willingness to travel throughout the territory.
Qualifications: from Preferred Qualifications bullet list:
- Experience managing a sales pipeline or customer accounts.
- Familiarity working with community organizations, chambers of commerce, or local business groups.
- Experience in territory sales or business development.
- Self-motivated with strong problem-solving skills and attention to detail.
Skills: maybe we can extract skills from both lists: Strong communication, relationship-building, ability to influence/negotiate/close, comfortable working independently, proficient with technology/CRM/Excel, etc. But we already have those in Requirements/Qualifications. To avoid duplication, maybe we can omit Skills section if content would be redundant. However spec says we can use Skills heading if we have specific content. We could create a Skills section summarizing skill-based items not covered elsewhere. But we risk duplication. Better to omit Skills if not needed; we can still include if we have distinct skill statements not already captured. Let's see: Required Qualifications includes skills like communication, relationship-building, influence/negotiate/close, comfortable working independently, proficient with technology (CRM, Excel). Preferred Qualifications includes experience managing pipeline, familiarity with community orgs, territory sales experience, self-motivated, problem-solving, attention to detail. Those are more experience/qualities than skills. Could still be under Qualifications. Since we already have Requirements and Qualifications sections, we might not need Skills. The spec says prefer a few substantive sections over many thin ones. So we can omit Skills.
Benefits: from Pay And Benefits section: list of benefits: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). Also mileage reimbursement and monthly phone stipend from Work Environment. Also PTO eligibility after six-month review. So we need to include all.
We should not include boilerplate like "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; we can keep? It's not specific benefit; it's a disclaimer. Might be considered boilerplate; better to remove. Keep only concrete benefits.
Pay: Pay range $32.00 - $32.00/hr (so $32/hour). Also mention base + uncapped commission. The Pay section should include that. The spec says only create Pay section if posting actually states them. Yes.
Schedule: from Work Environment: Field-based role covering Bremerton, WA area. Travel required throughout assigned territory, typically within a two-hour driving radius. Five days per week in the field visiting businesses and attending community events. Mileage reimbursement and monthly phone stipend provided. Fast-paced, goal-oriented environment with uncapped commission opportunities. PTO eligibility after a successful six-month performance review. Some of that overlaps with Benefits and Pay. But schedule specifics: five days per week, travel radius, field-based. We'll put those in Schedule section. Also mention "Field-based role covering the Bremerton, WA area." Could be location but okay.
We must not repeat job title as heading. Not include application deadline. Not include About Aston Carter boilerplate. Not include EEO etc.
Now produce HTML fragment with headings
and content.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
- Mileage reimbursement
- Monthly phone stipend
Pay
The position offers a base rate of $32.00 per hour with uncapped commission for each successful partner conversion.
Schedule
- Field-based role covering the Bremerton, WA area.
- Travel required throughout the assigned territory, typically within a two-hour driving radius.
- Five days per week in the field visiting businesses and attending community events.
We need to ensure we didn't include filler like "commensurate with experience". Not present.
Check for any duplicated lines: we have mileage reimbursement and monthly phone stipend also in Benefits; we also have them maybe in Schedule? We only put them in Benefits; schedule does not include them. Good.
Check if any content missing: The job overview also mentions "competitive base rate" and "uncapped commission". We captured that in Pay.
We also have "PTO eligibility after a successful six-month performance review." That's a benefit; we could add to Benefits as "PTO eligibility after a successful six-month performance review." But we already have Time Off/Leave (PTO, Vacation or Sick Leave). Might be redundant but okay. Could add as separate bullet: "PTO eligibility after a successful six-month performance review." However that's more detail about PTO. Might be okay to include. But we already have generic PTO; adding specific eligibility may be useful. Let's add as separate bullet.
Also "Fast-paced, goal-oriented environment with uncapped commission opportunities." That's more about work environment; could be in Schedule or Benefits? It's not a schedule; maybe we can add to Schedule as a bullet: "Fast-paced, goal-oriented environment with uncapped commission opportunities." But we already have uncapped commission in Pay. Might be redundant. Could omit.
We need to preserve all substantive information; not invent or summarize away detail. So we should include that statement if it's substantive. It's about work environment; we could put under Schedule or maybe a separate section? But we don't have a Work Environment heading; we could incorporate into Schedule as it's about work environment. Let's add bullet: "Fast-paced, goal-oriented environment."
But we must avoid filler. It's substantive.
Thus Schedule bullets:
- Field-based role covering the Bremerton, WA area.
- Travel required throughout the assigned territory, typically within a two-hour driving radius.
- Five days per week in the field visiting businesses and attending community events.
- Fast-paced, goal-oriented environment.
We could also mention "PTO eligibility after a successful six-month performance review." That's more benefit; we already have PTO bullet;
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info; remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a 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") and never create Pay/Schedule/Benefits sections unless posting actually states them. We need to decide which sections have content. From posting: - Job Overview: description paragraph. Could be "About the role". That is a section. - Key Responsibilities: list of duties. That's Responsibilities. - Required Qualifications: list. That's Requirements or Qualifications? The spec says we can use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content appropriately. Likely "Required Qualifications" goes under Requirements or Qualifications. "Preferred Qualifications" maybe under Qualifications or Skills. There's also "Work Environment" which could be Schedule? Not exactly. There's mention of "Five days per week in the field", "Travel required", "Mileage reimbursement and monthly phone stipend". That's schedule/benefits? Could be Schedule (work schedule) and Benefits (reimbursement, stipend). Also "PTO eligibility after a successful six-month performance review." That's benefit. - Pay And Benefits: includes pay range $32.00 - $32.00/hr (so fixed). Also benefits list. So we need Pay and Benefits sections. - Work Environment: could be Schedule? It mentions "Five days per week in the field visiting businesses and attending community events." That's schedule. Also "Travel required throughout the assigned territory, typically within a two-hour driving radius." That's also schedule/travel. Could be Schedule section. - Job Type & Location: "This is a Contract position based out of Bremerton, WA." That's maybe not a heading; could be part of About the role or omitted? The spec says do not repeat job title as heading; we can include location in About the role paragraph. - Application Deadline: that's application instruction; we should remove. - About Aston Carter: boilerplate about company; we should remove as it's not specific to role? It's generic company description; likely remove. - EEO etc: remove. Thus we need sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications), Qualifications (maybe Preferred Qualifications), Skills (maybe we can extract skills from qualifications), Benefits, Pay, Schedule. We must not create sections with filler. Ensure each section has substantive content. Let's extract content: About the role: from Job Overview paragraph: "We're looking for a motivated field sales professional to help recruit local small businesses into a new delivery partner program. In this role, you'll work closely with a Field Manager to identify prospects, explain the program, guide businesses through the application process, and support local recruiting events. This is a field-based position requiring regular travel within the assigned territory. In addition to a competitive base rate, the role offers uncapped commission for each successful partner conversion." We can keep that as prose
. Responsibilities: list from Key Responsibilities bullet points (each line starts with a verb). We'll make
- each.
Responsibilities list:
- Visit local businesses within the assigned territory to introduce the delivery partner program.
- Build relationships with business owners and decision-makers.
- Present program benefits and answer questions from prospective partners.
- Qualify interested businesses and assist them through the application process.
- Manage leads, activities, and partner information using Salesforce.
- Maintain an organized sales pipeline and track follow-up activities.
- Support community outreach events, including local networking and informational sessions.
- Partner with local organizations and business groups to generate referrals.
- Accurately update activity and lead data in Salesforce and Excel.
- Deliver excellent customer service throughout the recruitment and onboarding process.
Requirements: from Required Qualifications bullet list:
- 2+ years of sales, customer service, or related experience.
- Previous field, outside sales, or door-to-door sales experience.
- Experience using a CRM system (Salesforce preferred).
- Strong communication and relationship-building skills.
- Ability to influence, negotiate, and close opportunities.
- Comfortable working independently in a field-based environment.
- Proficient with technology, including CRM systems and Microsoft Excel.
- Valid driver's license and willingness to travel throughout the territory.
Qualifications: from Preferred Qualifications bullet list:
- Experience managing a sales pipeline or customer accounts.
- Familiarity working with community organizations, chambers of commerce, or local business groups.
- Experience in territory sales or business development.
- Self-motivated with strong problem-solving skills and attention to detail.
Skills: maybe we can extract skills from both lists: Strong communication, relationship-building, ability to influence/negotiate/close, comfortable working independently, proficient with technology/CRM/Excel, etc. But we already have those in Requirements/Qualifications. To avoid duplication, maybe we can omit Skills section if content would be redundant. However spec says we can use Skills heading if we have specific content. We could create a Skills section summarizing skill-based items not covered elsewhere. But we risk duplication. Better to omit Skills if not needed; we can still include if we have distinct skill statements not already captured. Let's see: Required Qualifications includes skills like communication, relationship-building, influence/negotiate/close, comfortable working independently, proficient with technology (CRM, Excel). Preferred Qualifications includes experience managing pipeline, familiarity with community orgs, territory sales experience, self-motivated, problem-solving, attention to detail. Those are more experience/qualities than skills. Could still be under Qualifications. Since we already have Requirements and Qualifications sections, we might not need Skills. The spec says prefer a few substantive sections over many thin ones. So we can omit Skills.
Benefits: from Pay And Benefits section: list of benefits: Medical, dental & vision; Critical Illness, Accident, and Hospital; 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available; Life Insurance (Voluntary Life & AD&D for the employee and dependents); Short and long-term disability; Health Spending Account (HSA); Transportation benefits; Employee Assistance Program; Time Off/Leave (PTO, Vacation or Sick Leave). Also mileage reimbursement and monthly phone stipend from Work Environment. Also PTO eligibility after six-month review. So we need to include all.
We should not include boilerplate like "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; we can keep? It's not specific benefit; it's a disclaimer. Might be considered boilerplate; better to remove. Keep only concrete benefits.
Pay: Pay range $32.00 - $32.00/hr (so $32/hour). Also mention base + uncapped commission. The Pay section should include that. The spec says only create Pay section if posting actually states them. Yes.
Schedule: from Work Environment: Field-based role covering Bremerton, WA area. Travel required throughout assigned territory, typically within a two-hour driving radius. Five days per week in the field visiting businesses and attending community events. Mileage reimbursement and monthly phone stipend provided. Fast-paced, goal-oriented environment with uncapped commission opportunities. PTO eligibility after a successful six-month performance review. Some of that overlaps with Benefits and Pay. But schedule specifics: five days per week, travel radius, field-based. We'll put those in Schedule section. Also mention "Field-based role covering the Bremerton, WA area." Could be location but okay.
We must not repeat job title as heading. Not include application deadline. Not include About Aston Carter boilerplate. Not include EEO etc.
Now produce HTML fragment with headings
and content. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
- Mileage reimbursement
- Monthly phone stipend
Pay
The position offers a base rate of $32.00 per hour with uncapped commission for each successful partner conversion.
Schedule
- Field-based role covering the Bremerton, WA area.
- Travel required throughout the assigned territory, typically within a two-hour driving radius.
- Five days per week in the field visiting businesses and attending community events.