Director, Field Operations
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only sections that have real content.
We need to extract content from posting.
First, we have "About Us" which is not a heading we need; we can ignore or maybe incorporate into About the role? The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. We need to preserve all substantive information; remove boilerplate, navigation, legal, EEO, equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Thus we need to decide which sections have content. From posting: - About Us: description of company, mission, etc. Could map to "About the role"? Actually "About the role" is about the role, not company. But we have "Overview" describing the role. So we can put that under "About the role". The "About Us" could be omitted or maybe included under "About the role"? The instruction says use headings like About the role, Responsibilities, etc. We can include an "About the role" section summarizing the overview. The "About Us" is company info, not role-specific, but could be considered part of "About the role"? Might be okay to include as part of About the role? However they said do not repeat job title as heading; they didn't forbid including company info. But they said preserve ALL substantive information; do not invent or summarize away detail. So we need to keep company info somewhere. Could put it under "About the role" as a paragraph? But that might be mixing. Better to create a section "About the role" that includes the overview of the role (the paragraph starting "Overview The Director, Field Operations..."). Company info could be placed under a separate heading? Not in list. But we could omit it? The instruction says preserve ALL substantive information; we cannot drop company info unless it's boilerplate. It's not boilerplate; it's substantive about the company. However the allowed headings are limited; we could still include a
without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but they gave examples. Likely they expect we only use those headings. But we need to preserve company info; we could incorporate it into "About the role" as a preamble. That would be okay: we keep the info.
Thus "About the role" will contain both company overview and role overview.
Next, Responsibilities: we have a big block with headings: Field Leadership & Team Development, Operational & Financial Performance, Member Experience & Operational Excellence, Strategic Partnership & Change Leadership. Those are subheadings within responsibilities. We can keep them as ? Not specified. But we can just put them as
with bold? However we need to use
- for any list of duties/requirements/benefits. The responsibilities are not a simple list; they are paragraphs with subheadings. We could treat each responsibility area as a
- containing the paragraph. Or we could keep as
with headings inside? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So if we have a list of duties, we should use
- . The responsibilities block is essentially a list of duty areas. So we can make each bullet a
- containing the prose (maybe with internal headings as or
? Not sure). Safer: treat each duty area as a
- with the text. Similarly, Requirements: we have "Qualifications" block with many bullet-like sentences. Could be a list. Skills: Not explicitly separated; qualifications include skills. Could combine Qualifications and Skills? But we have separate headings possible. The posting includes "Qualifications" with many items. Could treat that as Qualifications section. Skills maybe not separate; we could omit Skills if no specific content. Benefits: we have "Perks" paragraph describing benefits. So we can create Benefits section. Pay: we have salary range and bonus info. So Pay section. Schedule: we have travel requirement: "Willing and able to travel approximately 100% of the time. Some evenings and weekends are required". Also "Currently reside near a major airport". That's schedule/travel. So we can create Schedule section. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is "Note to Applicants: ..." about fraud schemes. That's application instruction/scam warning; we should remove it. Also "This is a good faith estimate..." is part of Pay; keep. Now we need to ensure we don't include placeholder text like "commensurate with experience". Not present. Now produce HTML fragment. Structure:
About the role
... company overview + role overview ...
Responsibilities
- Field Leadership & Team Development: ...
- Operational & Financial Performance: ...
- Member Experience & Operational Excellence: ...
- Strategic Partnership & Change Leadership: ...
Qualifications
- ... each bullet ...
- with the text. Similarly, Requirements: we have "Qualifications" block with many bullet-like sentences. Could be a list. Skills: Not explicitly separated; qualifications include skills. Could combine Qualifications and Skills? But we have separate headings possible. The posting includes "Qualifications" with many items. Could treat that as Qualifications section. Skills maybe not separate; we could omit Skills if no specific content. Benefits: we have "Perks" paragraph describing benefits. So we can create Benefits section. Pay: we have salary range and bonus info. So Pay section. Schedule: we have travel requirement: "Willing and able to travel approximately 100% of the time. Some evenings and weekends are required". Also "Currently reside near a major airport". That's schedule/travel. So we can create Schedule section. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is "Note to Applicants: ..." about fraud schemes. That's application instruction/scam warning; we should remove it. Also "This is a good faith estimate..." is part of Pay; keep. Now we need to ensure we don't include placeholder text like "commensurate with experience". Not present. Now produce HTML fragment. Structure:
- for any list of duties/requirements/benefits, and
- containing the paragraph. Or we could keep as