Alexandria Tour Guide- Ultimate Tour
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule).
- Use `- ` for lists of duties/requirements/benefits.
- Use `
` for prose.
- Do NOT repeat job title as heading (page already shows it).
- Do NOT put Job ID / requisition numbers as headings.
- 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.
2. **Deconstruct the Job Posting:**
Let me extract the meaningful content from the text:
- Job Title: Tour Guide - Alexandria (already on page, don't repeat as heading)
- Location: Alexandria, VA
- Job Type: Part-time
- Compensation: $50.00 per tour
- Job Description/About: "Are you brave enough to be a ghost tour guide? Ready to share incredible experiences in your city as you bewitch and enchant audiences? Then embrace the shadows and become our next ghost tour guide! This tour starts at 10pm. Our passion at US Ghost Adventures is enchanting storytelling. We specialize in dark, forgotten, and secret history. We are looking for creatives, history buffs, true crime junkies, and paranormal enthusiasts willing to dive deeper into the dark side of humanity. We thrive on igniting a sense of wonder in every guest on our ghost tours, and as a ghost tour guide you will weave enthralling stories as you lead tours down the ghastly streets of your city."
- Pay & Benefits section (explicitly labeled "Ghost Tour Guide Pay & Benefits:"):
- "$50 - $150 a day/night (including tips)"
- "TIPS!! These can range from $20 to over $100 for a 1-2 hour tour"
- "Cash bonuses for good reviews"
- "Free or discounted tours for you and close family/friends all over the country"
- "Flexible schedules, fun part-time work, ability to earn tips in addition to pay"
- "The chance to get to know your city and meet a lot of fun people from all over the country!"
- Requirements section (explicitly labeled "Ghost Tour Guide Requirements:"):
- "Qualified candidates should be skilled in public speaking"
- "Applicants should reside near downtown (within 25 miles) and have reliable transportation"
- "Applicants should be passionate about storytelling and history"
- "Willing to work at 10pm"
- Company description: "US Ghost Adventures offers entertaining, historic, and authentic ghost tours of the United States' most haunted cities – over 100 cities and counting! We aim to deliver fun yet honest accounts of the hauntings that are so prevalent nationwide. While our stories are derived from historic research, a ghost tour wouldn’t be the same without the ghost stories from our guide network across the country!"
- Application instructions: "Have questions about the job or the company? Visit our careers page and fill out the form to contact us! Follow the link below, click “apply now,” choose your city, and tell us why you would make an expert ghost guide and storyteller! One of our Ghost Guide Recruiting Specialists will reach out to you shortly: https://usghostadventures.com/careers/" -> This should be removed per rules ("Remove... application instructions").
- Boilerplate: "Powered by JazzHR 07mzKGAOmr" -> Remove.
- No EEO, equal-opportunity, scam warnings, etc. present, but we should still remove any generic boilerplate.
Now, map to required sections using `
`:
- Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
- Rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text"
- Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them"
- The posting explicitly has "Ghost Tour Guide Pay & Benefits:" with specific content, and "Ghost Tour Guide Requirements:" with specific content.
- It also has implicit "About the role" content, and job type/location info.
- Let's identify what sections to create based on actual content:
Possible sections with real content:
- "About the role" (the main description/what they do)
- "Pay" (explicitly stated: $50-$150 a day/night, tips, etc.)
- "Benefits" (explicitly listed: tips cash bonuses, free/discounted tours, flexible schedules, etc.) But careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them". It does state them under "Ghost Tour Guide Pay & Benefits:". I think we can split Pay and Benefits, or combine as "Pay & Benefits" but the heading must be one of the listed ones. Let's see: "Pay" and "Benefits" are separate options. The posting combines them. I could create a "Pay" section with the pay info, and a "Benefits" section with the benefits info, since both are substantively present. Or I could just use one section. The rule says "Prefer a few substantive sections over many thin ones." I'll pick the most relevant.
- "Requirements" (explicitly listed)
- Maybe "Skills" - but the posting doesn't have a separate "Skills" section beyond requirements. The requirements are: public speaking, reside near downtown, reliable transportation, passionate about storytelling and history, willing to work at 10pm. I could put these under "Requirements" or "Qualifications". The headings allowed include "Qualifications" and "Requirements". I'll use "Requirements" for the listed requirements.
- "About the role" for the main description.
- "Pay" for compensation info.
- "Benefits" for the benefits listed.
Let's re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." These are examples, not a fixed menu, but we should use them if applicable. "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text... and never create Pay/Schedule/Benefits sections unless the posting actually states them."
The posting has:
- Pay: "$50.00 per tour", "$50 - $150 a day/night (including tips)", tip ranges.
- Benefits: "TIPS!! These can range from $20 to over $100 for a 1-2 hour tour", "Cash bonuses for good reviews", "Free or discounted tours for you and close family/friends all over the country", "Flexible schedules, fun part-time work, ability to earn tips in addition to pay", "The chance to get to know your city and meet a lot of fun people from all over the country!"
- Requirements: "Qualified candidates should be skilled in public speaking", "Applicants should reside near downtown (within 25 miles) and have reliable transportation", "Applicants should be passionate about storytelling and history", "Willing to work at 10pm"
- About/Role: the whole description about being a ghost tour guide, storytelling, dark history, etc.
I should NOT create a "Schedule" section because the posting only mentions "This tour starts at 10pm" and "Flexible schedules" as a benefit, not a structured schedule section. Creating "Schedule" with "varies" or "10pm" might be okay if substantive, but the rule says never create unless posting actually states them. It does state the tour starts at 10pm, and flexible schedules as a benefit. I'll probably skip a dedicated "Schedule" heading, or fold it into Benefits or Pay.
I should NOT include "Responsibilities" because the posting doesn't list specific duties/responsibilities beyond the general description of weaving stories and leading tours. It's more about the role description than a list of duties. The rule says use - for any list of duties/requirements/benefits. I could extract duties from the description, but it's not explicitly a "responsibilities" list. I'll be conservative and only include sections with clear, specific content.
Let's plan the sections:
1. "About the role" - the prose about the job, storytelling, etc.
2. "Requirements" - the four requirements listed.
3. "Pay" - the compensation info.
4. "Benefits" - the benefits list.
Check against rules:
- "About the role": has real content. OK.
- "Requirements": has real content. OK.
- "Pay": has real content ($50 per tour, $50-$150 day/night, tips). OK.
- "Benefits": has real content (tips ranges, cash bonuses, free/discounted tours, flexible schedules, meeting people). OK.
- No "Schedule" heading unless I'm sure. I'll skip it.
- No "Skills" heading unless there's specific skills content beyond requirements. The requirements include skills, but I'll use "Requirements".
- No job title heading.
- No Job ID or metadata as headings. The input has "Job Type: Part-time", "Location: Alexandria, VA", "Compensation: $50.00 per tour". I should fold these into prose or a short
, not as headings. The rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll fold job type and location into a
at the top or somewhere appropriate, but not as headings.
- Remove application instructions, boilerplate, etc.
- Output ONLY the HTML fragment, no /, no markdown code fences.
Now, construct the HTML:
I need to use
for headings. Use - for lists. Use
for prose.
Structure:
- Maybe start with a
for location/job type/compensation blurb, or fold into sections. The rule says "fold minor metadata into a short
or drop it." I'll put a brief
at the top with location and job type, then sections.
- But careful: "do NOT repeat the job title as a heading (the page already shows it)" - so I won't have an or for the title.
- I'll structure as:
Location: Alexandria, VA | Job Type: Part-time | Compensation: $50.00 per tour
Then sections:
About the role
...prose...
` for prose. - Do NOT repeat job title as heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings. - 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. 2. **Deconstruct the Job Posting:** Let me extract the meaningful content from the text: - Job Title: Tour Guide - Alexandria (already on page, don't repeat as heading) - Location: Alexandria, VA - Job Type: Part-time - Compensation: $50.00 per tour - Job Description/About: "Are you brave enough to be a ghost tour guide? Ready to share incredible experiences in your city as you bewitch and enchant audiences? Then embrace the shadows and become our next ghost tour guide! This tour starts at 10pm. Our passion at US Ghost Adventures is enchanting storytelling. We specialize in dark, forgotten, and secret history. We are looking for creatives, history buffs, true crime junkies, and paranormal enthusiasts willing to dive deeper into the dark side of humanity. We thrive on igniting a sense of wonder in every guest on our ghost tours, and as a ghost tour guide you will weave enthralling stories as you lead tours down the ghastly streets of your city." - Pay & Benefits section (explicitly labeled "Ghost Tour Guide Pay & Benefits:"): - "$50 - $150 a day/night (including tips)" - "TIPS!! These can range from $20 to over $100 for a 1-2 hour tour" - "Cash bonuses for good reviews" - "Free or discounted tours for you and close family/friends all over the country" - "Flexible schedules, fun part-time work, ability to earn tips in addition to pay" - "The chance to get to know your city and meet a lot of fun people from all over the country!" - Requirements section (explicitly labeled "Ghost Tour Guide Requirements:"): - "Qualified candidates should be skilled in public speaking" - "Applicants should reside near downtown (within 25 miles) and have reliable transportation" - "Applicants should be passionate about storytelling and history" - "Willing to work at 10pm" - Company description: "US Ghost Adventures offers entertaining, historic, and authentic ghost tours of the United States' most haunted cities – over 100 cities and counting! We aim to deliver fun yet honest accounts of the hauntings that are so prevalent nationwide. While our stories are derived from historic research, a ghost tour wouldn’t be the same without the ghost stories from our guide network across the country!" - Application instructions: "Have questions about the job or the company? Visit our careers page and fill out the form to contact us! Follow the link below, click “apply now,” choose your city, and tell us why you would make an expert ghost guide and storyteller! One of our Ghost Guide Recruiting Specialists will reach out to you shortly: https://usghostadventures.com/careers/" -> This should be removed per rules ("Remove... application instructions"). - Boilerplate: "Powered by JazzHR 07mzKGAOmr" -> Remove. - No EEO, equal-opportunity, scam warnings, etc. present, but we should still remove any generic boilerplate. Now, map to required sections using `
`:
- Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
- Rule: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text"
- Rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them"
- The posting explicitly has "Ghost Tour Guide Pay & Benefits:" with specific content, and "Ghost Tour Guide Requirements:" with specific content.
- It also has implicit "About the role" content, and job type/location info.
- Let's identify what sections to create based on actual content:
Possible sections with real content:
- "About the role" (the main description/what they do)
- "Pay" (explicitly stated: $50-$150 a day/night, tips, etc.)
- "Benefits" (explicitly listed: tips cash bonuses, free/discounted tours, flexible schedules, etc.) But careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them". It does state them under "Ghost Tour Guide Pay & Benefits:". I think we can split Pay and Benefits, or combine as "Pay & Benefits" but the heading must be one of the listed ones. Let's see: "Pay" and "Benefits" are separate options. The posting combines them. I could create a "Pay" section with the pay info, and a "Benefits" section with the benefits info, since both are substantively present. Or I could just use one section. The rule says "Prefer a few substantive sections over many thin ones." I'll pick the most relevant.
- "Requirements" (explicitly listed)
- Maybe "Skills" - but the posting doesn't have a separate "Skills" section beyond requirements. The requirements are: public speaking, reside near downtown, reliable transportation, passionate about storytelling and history, willing to work at 10pm. I could put these under "Requirements" or "Qualifications". The headings allowed include "Qualifications" and "Requirements". I'll use "Requirements" for the listed requirements.
- "About the role" for the main description.
- "Pay" for compensation info.
- "Benefits" for the benefits listed.
Let's re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." These are examples, not a fixed menu, but we should use them if applicable. "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text... and never create Pay/Schedule/Benefits sections unless the posting actually states them."
The posting has:
- Pay: "$50.00 per tour", "$50 - $150 a day/night (including tips)", tip ranges.
- Benefits: "TIPS!! These can range from $20 to over $100 for a 1-2 hour tour", "Cash bonuses for good reviews", "Free or discounted tours for you and close family/friends all over the country", "Flexible schedules, fun part-time work, ability to earn tips in addition to pay", "The chance to get to know your city and meet a lot of fun people from all over the country!"
- Requirements: "Qualified candidates should be skilled in public speaking", "Applicants should reside near downtown (within 25 miles) and have reliable transportation", "Applicants should be passionate about storytelling and history", "Willing to work at 10pm"
- About/Role: the whole description about being a ghost tour guide, storytelling, dark history, etc.
I should NOT create a "Schedule" section because the posting only mentions "This tour starts at 10pm" and "Flexible schedules" as a benefit, not a structured schedule section. Creating "Schedule" with "varies" or "10pm" might be okay if substantive, but the rule says never create unless posting actually states them. It does state the tour starts at 10pm, and flexible schedules as a benefit. I'll probably skip a dedicated "Schedule" heading, or fold it into Benefits or Pay.
I should NOT include "Responsibilities" because the posting doesn't list specific duties/responsibilities beyond the general description of weaving stories and leading tours. It's more about the role description than a list of duties. The rule says use - for any list of duties/requirements/benefits. I could extract duties from the description, but it's not explicitly a "responsibilities" list. I'll be conservative and only include sections with clear, specific content.
Let's plan the sections:
1. "About the role" - the prose about the job, storytelling, etc.
2. "Requirements" - the four requirements listed.
3. "Pay" - the compensation info.
4. "Benefits" - the benefits list.
Check against rules:
- "About the role": has real content. OK.
- "Requirements": has real content. OK.
- "Pay": has real content ($50 per tour, $50-$150 day/night, tips). OK.
- "Benefits": has real content (tips ranges, cash bonuses, free/discounted tours, flexible schedules, meeting people). OK.
- No "Schedule" heading unless I'm sure. I'll skip it.
- No "Skills" heading unless there's specific skills content beyond requirements. The requirements include skills, but I'll use "Requirements".
- No job title heading.
- No Job ID or metadata as headings. The input has "Job Type: Part-time", "Location: Alexandria, VA", "Compensation: $50.00 per tour". I should fold these into prose or a short
, not as headings. The rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll fold job type and location into a
at the top or somewhere appropriate, but not as headings.
- Remove application instructions, boilerplate, etc.
- Output ONLY the HTML fragment, no /, no markdown code fences.
Now, construct the HTML:
I need to use
for headings. Use - for lists. Use
for prose.
Structure:
- Maybe start with a
for location/job type/compensation blurb, or fold into sections. The rule says "fold minor metadata into a short
or drop it." I'll put a brief
at the top with location and job type, then sections.
- But careful: "do NOT repeat the job title as a heading (the page already shows it)" - so I won't have an or for the title.
- I'll structure as:
Location: Alexandria, VA | Job Type: Part-time | Compensation: $50.00 per tour
Then sections:
About the role
...prose...
- for any list of duties/requirements/benefits. I could extract duties from the description, but it's not explicitly a "responsibilities" list. I'll be conservative and only include sections with clear, specific content.
Let's plan the sections:
1. "About the role" - the prose about the job, storytelling, etc.
2. "Requirements" - the four requirements listed.
3. "Pay" - the compensation info.
4. "Benefits" - the benefits list.
Check against rules:
- "About the role": has real content. OK.
- "Requirements": has real content. OK.
- "Pay": has real content ($50 per tour, $50-$150 day/night, tips). OK.
- "Benefits": has real content (tips ranges, cash bonuses, free/discounted tours, flexible schedules, meeting people). OK.
- No "Schedule" heading unless I'm sure. I'll skip it.
- No "Skills" heading unless there's specific skills content beyond requirements. The requirements include skills, but I'll use "Requirements".
- No job title heading.
- No Job ID or metadata as headings. The input has "Job Type: Part-time", "Location: Alexandria, VA", "Compensation: $50.00 per tour". I should fold these into prose or a short
, not as headings. The rule: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." I'll fold job type and location into a
at the top or somewhere appropriate, but not as headings. - Remove application instructions, boilerplate, etc. - Output ONLY the HTML fragment, no /, no markdown code fences. Now, construct the HTML: I need to use
for headings. Use
- for lists. Use
for prose. Structure: - Maybe start with a
for location/job type/compensation blurb, or fold into sections. The rule says "fold minor metadata into a short
or drop it." I'll put a brief
at the top with location and job type, then sections. - But careful: "do NOT repeat the job title as a heading (the page already shows it)" - so I won't have an or for the title. - I'll structure as:
Location: Alexandria, VA | Job Type: Part-time | Compensation: $50.00 per tour
Then sections:About the role
...prose...
- for lists. Use