Williamsburg 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 the job title as a heading (page already shows it).
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a 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.
2. **Analyze the Input Job Posting:**
Let me extract the meaningful content from the provided text:
- Job Title: Tour Guide - Williamsburg Ultimate Tour (but I shouldn't output this as a heading)
- Location: Williamsburg, 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! One of our Ghost Guide Recruiting Specialists will reach out to you shortly: https://usghostadventures.com/careers/ Follow the link below, click “apply now,” choose your city, and tell us why you would make an expert ghost guide and storyteller!" (Rule says remove application instructions)
- Footer/powered by: "Powered by JazzHR II0kLh32pH" (remove)
- Also remove: EEO, equal opportunity, scam warnings, etc. (not present explicitly, but good to note)
Now, I need to map this to the required HTML structure using `
` for section headings. The allowed headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's parse the content into appropriate sections:
- "About the role" or similar: The part about bravery, sharing experiences, bewitching/enchanting audiences, 10pm start, passion for storytelling, dark/forgotten/history, creatives/history buffs/true crime/junkies/paranormal enthusiasts, weaving enthralling stories, leading tours down ghastly streets.
- "Responsibilities": Not explicitly separated, but the duties are described in the "About" and "Pay & Benefits" sections. I might need to infer responsibilities from the description, but the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." and "include a section ONLY when the posting has real, specific content for it". The posting doesn't have a clear "Responsibilities" section with bullet points separate from "Requirements". It has "Ghost Tour Guide Requirements" explicitly. I should probably use "About the role" for the descriptive part, and "Requirements" for the requirements list. I could maybe use "Pay & Benefits" for the compensation/benefits part, but need to be careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Pay & Benefits explicitly: "$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!" So I can have a Pay/Benefits section. But the heading examples include "Benefits, Pay, Schedule". I need to decide on headings. The posting has "Ghost Tour Guide Pay & Benefits:" as a label. I could use `Pay
` or `Benefits
`, but need to match content. Actually, the rule says: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists them as examples. I should pick headings that fit the content and avoid creating thin sections.
Let's outline sections based on actual content:
- "About the role" - contains the descriptive text about the job, when it starts, who they're looking for, the storytelling aspect.
- "Requirements" - the explicit requirements listed: skilled in public speaking, reside near downtown within 25 miles, reliable transportation, passionate about storytelling and history, willing to work at 10pm.
- "Pay & Benefits" - the explicit pay and benefits list. I'll use `Pay
` and maybe `Benefits
` but the rule says prefer a few substantive sections over many thin ones. The pay and benefits are all in one block labeled "Ghost Tour Guide Pay & Benefits:". I could combine them under one heading, or use two. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. I'll likely use a single `Pay & Benefits
` or just `Pay
` with the benefits included, or `Benefits
` with pay included. Looking at the examples: "Benefits, Pay, Schedule" are listed as possible headings. I think I'll use `Pay
` and include the benefits text within the `
` or `
`, or maybe use `Pay & Benefits
` but that's not in the example list. I'll stick to the examples given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to pick those that apply. The posting has requirements explicitly, pay/benefits explicitly. It doesn't have a separate "Qualifications" section beyond "Requirements", but sometimes Qualifications and Requirements are similar. I'll use "Requirements" for the listed requirements, and "Pay" for the pay info, and maybe include benefits under Pay or separate. To keep it few and substantive, I'll do: About the role, Requirements, Pay. I could also add Skills if there's something, but the requirements cover skills. The posting mentions "skilled in public speaking" as a requirement. I'll stick to the three sections that have real content.
Wait, let re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." These are examples of valid headings. I should use them if the content fits. The posting has:
- Content about the role/description -> "About the role"
- Explicit requirements -> "Requirements"
- Explicit pay & benefits -> "Pay" and/or "Benefits"
- No clear "Responsibilities" separate from requirements/description. I could fold responsibilities into "About the role" or "Requirements", but the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I shouldn't create a "Responsibilities" section if there aren't bullet points labeled as such, unless I extract duties from the prose. The prose does describe what the guide does: "weave enthralling stories as you lead tours down the ghastly streets of your city", "lead tours", "share incredible experiences", "bewitch and enchant audiences". But it's not a list of duties. I'll probably include those details in the "About the role" paragraph/text, not as a separate section.
Let's decide on sections:
1. `About the role
` - will contain the descriptive prose about the job, when it starts, who they're looking for, the storytelling mission.
2. `Requirements
` - will contain the explicit requirements list.
3. `Pay
` - will contain the pay info. Benefits are intertwined, but I can include them under Pay or use a `
` note. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. I'll use `
Pay
` and include the compensation and benefits text within the associated markup. Actually, the benefits are quite specific: tips, cash bonuses, free/discounted tours, flexible schedules, etc. I could use `Pay
` and `` for the rest, or maybe `
Benefits
`. To keep it minimal and compliant, I'll use `Pay
` and list the pay and benefits together in the `` or `
`, since they're given in one block. But the rule says "Prefer a few substantive sections over many thin ones." So maybe one section for Pay & Benefits combined under `Pay
`, or I could split if it makes sense. I think I'll use `Pay
` and include all the pay/
` for prose. - Do NOT repeat the job title as a heading (page already shows it). - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into a 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. 2. **Analyze the Input Job Posting:** Let me extract the meaningful content from the provided text: - Job Title: Tour Guide - Williamsburg Ultimate Tour (but I shouldn't output this as a heading) - Location: Williamsburg, 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! One of our Ghost Guide Recruiting Specialists will reach out to you shortly: https://usghostadventures.com/careers/ Follow the link below, click “apply now,” choose your city, and tell us why you would make an expert ghost guide and storyteller!" (Rule says remove application instructions) - Footer/powered by: "Powered by JazzHR II0kLh32pH" (remove) - Also remove: EEO, equal opportunity, scam warnings, etc. (not present explicitly, but good to note) Now, I need to map this to the required HTML structure using `
` for section headings. The allowed headings examples: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Let's parse the content into appropriate sections:
- "About the role" or similar: The part about bravery, sharing experiences, bewitching/enchanting audiences, 10pm start, passion for storytelling, dark/forgotten/history, creatives/history buffs/true crime/junkies/paranormal enthusiasts, weaving enthralling stories, leading tours down ghastly streets.
- "Responsibilities": Not explicitly separated, but the duties are described in the "About" and "Pay & Benefits" sections. I might need to infer responsibilities from the description, but the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." and "include a section ONLY when the posting has real, specific content for it". The posting doesn't have a clear "Responsibilities" section with bullet points separate from "Requirements". It has "Ghost Tour Guide Requirements" explicitly. I should probably use "About the role" for the descriptive part, and "Requirements" for the requirements list. I could maybe use "Pay & Benefits" for the compensation/benefits part, but need to be careful: the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Pay & Benefits explicitly: "$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!" So I can have a Pay/Benefits section. But the heading examples include "Benefits, Pay, Schedule". I need to decide on headings. The posting has "Ghost Tour Guide Pay & Benefits:" as a label. I could use `Pay
` or `Benefits
`, but need to match content. Actually, the rule says: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists them as examples. I should pick headings that fit the content and avoid creating thin sections.
Let's outline sections based on actual content:
- "About the role" - contains the descriptive text about the job, when it starts, who they're looking for, the storytelling aspect.
- "Requirements" - the explicit requirements listed: skilled in public speaking, reside near downtown within 25 miles, reliable transportation, passionate about storytelling and history, willing to work at 10pm.
- "Pay & Benefits" - the explicit pay and benefits list. I'll use `Pay
` and maybe `Benefits
` but the rule says prefer a few substantive sections over many thin ones. The pay and benefits are all in one block labeled "Ghost Tour Guide Pay & Benefits:". I could combine them under one heading, or use two. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. I'll likely use a single `Pay & Benefits
` or just `Pay
` with the benefits included, or `Benefits
` with pay included. Looking at the examples: "Benefits, Pay, Schedule" are listed as possible headings. I think I'll use `Pay
` and include the benefits text within the `
Pay
` and maybe `Benefits
` but the rule says prefer a few substantive sections over many thin ones. The pay and benefits are all in one block labeled "Ghost Tour Guide Pay & Benefits:". I could combine them under one heading, or use two. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. I'll likely use a single `Pay & Benefits
` or just `Pay
` with the benefits included, or `Benefits
` with pay included. Looking at the examples: "Benefits, Pay, Schedule" are listed as possible headings. I think I'll use `Pay
` and include the benefits text within the `` or `
- `, or maybe use `
Pay & Benefits
` but that's not in the example list. I'll stick to the examples given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. I need to pick those that apply. The posting has requirements explicitly, pay/benefits explicitly. It doesn't have a separate "Qualifications" section beyond "Requirements", but sometimes Qualifications and Requirements are similar. I'll use "Requirements" for the listed requirements, and "Pay" for the pay info, and maybe include benefits under Pay or separate. To keep it few and substantive, I'll do: About the role, Requirements, Pay. I could also add Skills if there's something, but the requirements cover skills. The posting mentions "skilled in public speaking" as a requirement. I'll stick to the three sections that have real content. Wait, let re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." These are examples of valid headings. I should use them if the content fits. The posting has:
- Content about the role/description -> "About the role"
- Explicit requirements -> "Requirements"
- Explicit pay & benefits -> "Pay" and/or "Benefits"
- No clear "Responsibilities" separate from requirements/description. I could fold responsibilities into "About the role" or "Requirements", but the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." So I shouldn't create a "Responsibilities" section if there aren't bullet points labeled as such, unless I extract duties from the prose. The prose does describe what the guide does: "weave enthralling stories as you lead tours down the ghastly streets of your city", "lead tours", "share incredible experiences", "bewitch and enchant audiences". But it's not a list of duties. I'll probably include those details in the "About the role" paragraph/text, not as a separate section.
Let's decide on sections:
1. `About the role
` - will contain the descriptive prose about the job, when it starts, who they're looking for, the storytelling mission.
2. `Requirements
` - will contain the explicit requirements list.
3. `Pay
` - will contain the pay info. Benefits are intertwined, but I can include them under Pay or use a `
` note. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. I'll use `
Pay
` and include the compensation and benefits text within the associated markup. Actually, the benefits are quite specific: tips, cash bonuses, free/discounted tours, flexible schedules, etc. I could use `Pay
` and `` for the rest, or maybe `
Benefits
`. To keep it minimal and compliant, I'll use `Pay
` and list the pay and benefits together in the `` or `
- `, since they're given in one block. But the rule says "Prefer a few substantive sections over many thin ones." So maybe one section for Pay & Benefits combined under `