Parking Cashier - University of Vermont Medical Center
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. 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.
Content:
- Company description: "About Towne Towne is an exceptional arrival through departure experience company. With its best-in-class parking and hospitality solutions and its fully integrated technology platform, we deliver seamless parking and mobility experiences in the places where people live, learn, work, play, rejuvenate, and recover. Towne’s 14,000 team members create smiles by delivering exceptional experiences for the millions of people we proudly serve each year. For nearly 40 years, Towne has been committed to providing the best experience, delivered by the best team, powered by innovative technology, enhancing lives and communities. For more information, visit www.towne.com and follow us on LinkedIn. Click here for important notices that may be applicable to you. For more information about our privacy policy, please click here."
We should remove navigation/legal/EEO etc. The lines about "Click here for important notices..." and privacy policy are likely boilerplate; we should remove them. Also "For more information, visit www.towne.com and follow us on LinkedIn." Might be considered boilerplate but it's substantive? It's a link to company site; maybe we keep as part of About the company? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Click here for important notices..." and privacy policy are legal boilerplate; remove. The "For more information, visit www.towne.com and follow us on LinkedIn." Might be considered navigation? It's a link to company site; but it's not navigation per se. Might keep as part of About the company description.
Then "Job Details $14-$17 per hour Part-time shifts (day/night/weekends) Compensation: Towne Park is committed to offering competitive, fair, and commensurate compensation. Actual compensation will be based on a candidate’s job-related skills, experience, education or training, and location. The hourly base pay range for this position is $14-$17 per hour. Work Schedule: The work schedule for this position is part-time shifts. Benefits: Employees are eligible to enroll in accident insurance, critical illness insurance, hospital indemnity insurance, and telemedicine benefits. Employees are also able to enroll in the company’s 401k retirement savings plan. Eligibility requirements depend on your job classification, length of employment and number of hours worked. Benefits are subject to change and may be subject to a specific plan or program terms. Seasonal and temporary roles are not eligible for benefits outlined above."
We need to extract Pay, Schedule, Benefits sections if they have real specific content. Pay: they gave hourly base pay range $14-$17 per hour. That's specific. So we can have a Pay section with that info. Schedule: they said part-time shifts (day/night/weekends). That's specific enough. Benefits: they list specific insurances and 401k. So we can have Benefits section.
We also have a Summary and Essential Functions (list of duties with percentages). That's Responsibilities. Also Qualifications: Education, Licensure, Work Experience, Knowledge, etc. Also SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, etc. Those could be considered Requirements or Qualifications. We need to decide sections.
We should not create sections with filler text. Avoid sections like "About the role" if we don't have specific content. We have company description; maybe we can put that under a section "About the company" but not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? That seems odd but maybe acceptable. However "About the role" usually describes the role, not company. But we could treat it as About the role (summary). The posting includes a Summary section: "The Cashier is responsible for accurately collecting and reconciling revenue while providing exceptional hospitality services to all guests in an attentive, friendly and efficient manner." That's a good fit for About the role.
Thus we can have:
About the role
The Cashier is responsible for accurately collecting and reconciling revenue while providing exceptional hospitality services to all guests in an attentive, friendly and efficient manner.
Then Responsibilities: we have Essential Functions with bullet points and percentages. We should output as - each duty. Should we include percentages? The posting includes percentages like "-20%" after each bullet. We should preserve all substantive information, so include the percentages. The bullet list lines: "Maintains pleasant, friendly and professional demeanor with all guests, co-workers and clients. Acknowledges and greets guests immediately while maintaining a professional and friendly demeanor. Addresses guests using last names when appropriate. Treats guests and associates with courtesy, respect and dignity.-20%" etc. We'll keep the text as is, including the percentage at end.
Thus Responsibilities section with
- each.
Then Qualifications: includes Education, Licensure, Work Experience, Knowledge, etc. Also SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel, etc. Those could be considered Requirements. But we have both Qualifications and Requirements headings allowed. We need to decide which to use. The posting has a "Qualifications" heading with subheadings Education, Licensure, Certification, Etc., Work Experience, Knowledge, etc. Then later there are sections like SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel. Those could be considered Requirements or maybe Skills. But we have Skills heading allowed. However the posting does not have a separate Skills section; the Knowledge section includes skills like basic math, reading, etc. So we could put Knowledge under Skills. But we also have Qualifications section for Education, Experience, Licensure. We could combine Education, Experience, Licensure under Qualifications. Then Knowledge under Skills. Then SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel could be under Requirements (maybe as "Requirements").
But we must avoid creating sections with filler text. Ensure each section has real content.
Let's extract:
Qualifications:
- Education: High school diploma or general education degree (GED)
- Licensure, Certification, Etc.: N/A (but N/A is placeholder; we should not include if it's just N/A? The instruction: 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. So we should not include a Licensure subsection if it's just N/A. We could omit that line entirely. Since it's N/A, we can drop it.
- Work Experience: One to three month(s) related experience and/or training; OR equivalent combination of education and experience.
- Knowledge: list of items: Basic Math Skills, Must be able to read and write standard English language, Must be able to read and comprehend simple instructions, short correspondence and memos, Must be able to write simple correspondence, Must be able to effectively present information in one-on-one and small group situations to guests, clients and other employees of the organization, Ability to add and subtract three digit numbers and to multiply and divide with 10’s and 100’s; ability to perform these operations using units of American money, Ability to understand 24 hour and military time systems, Ability to understand rates applicable to time passed.
We could treat Knowledge as Skills.
Then SCOPE Authority To Act: description.
Budget Responsibility: description.
WORKING CONDITIONS & PHYSICAL DEMANDS: includes Physical Requirements, Lifting Requirements, Working Environment, Travel.
Travel: Travel of up to 5% may be required.
We could group WORKING CONDITIONS & PHYSICAL DEMANDS under Requirements (or maybe under a separate section but not allowed). Since we have Requirements heading allowed, we can put all those under Requirements.
Thus sections:
- About the role (summary)
- Responsibilities (essential functions)
- Qualifications (education, work experience)
- Skills (knowledge/abilities)
- Requirements (scope, budget, working conditions, physical demands, travel)
- Benefits
- Pay
- Schedule
We need to ensure we don't create sections with filler text. All have content.
Now we need to format.
We'll output HTML fragment:
About the role
The Cashier is responsible for accurately collecting and reconciling revenue while providing exceptional hospitality services to all guests in an attentive, friendly and efficient manner.
Responsibilities
- Maintains pleasant, friendly and professional demeanor with all guests, co-workers and clients. Acknowledges and greets guests immediately while maintaining a professional and friendly demeanor. Addresses guests using last names when appropriate. Treats guests and associates with courtesy, respect and dignity.-20%
- Maintains accuracy and composure while under pressure. Appropriately uses the salutation of the day and welcomes guests to the location. Uses proper Towne Park phone etiquette.-15%
- Assists guests with directions and all other inquiries. Provides guests with information about outlets, meeting rooms and/or amenities of the facility as well as main attractions in the area.-10%
- Determines guest charges and processes payments via cash, credit, or direct billing. Accurately categorizes tickets for audit purposes. Collects and reconciles revenue accurately and furnishes payment receipts.-20%
- Completes accurate and timely shift reports. Follows all standard operating procedures related to cash banks. Operates equipment, including registers, gates, and credit card machines. Obtains information about daily events and rates to be charged.-20%
- Completes all tasks in a timely manner as instructed by the Lead Cashier/Account Manager.-15%
Qualifications
- Education: High school diploma or general education degree (GED)
- Work Experience: One to three month(s) related experience and/or training; OR equivalent combination of education and experience.
Skills
- Basic Math Skills
- Must be able to read and write standard English language
- Must be able to read and comprehend simple instructions, short correspondence and memos
- Must be able to write simple correspondence
- Must
for prose. 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. 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. Content: - Company description: "About Towne Towne is an exceptional arrival through departure experience company. With its best-in-class parking and hospitality solutions and its fully integrated technology platform, we deliver seamless parking and mobility experiences in the places where people live, learn, work, play, rejuvenate, and recover. Towne’s 14,000 team members create smiles by delivering exceptional experiences for the millions of people we proudly serve each year. For nearly 40 years, Towne has been committed to providing the best experience, delivered by the best team, powered by innovative technology, enhancing lives and communities. For more information, visit www.towne.com and follow us on LinkedIn. Click here for important notices that may be applicable to you. For more information about our privacy policy, please click here." We should remove navigation/legal/EEO etc. The lines about "Click here for important notices..." and privacy policy are likely boilerplate; we should remove them. Also "For more information, visit www.towne.com and follow us on LinkedIn." Might be considered boilerplate but it's substantive? It's a link to company site; maybe we keep as part of About the company? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Click here for important notices..." and privacy policy are legal boilerplate; remove. The "For more information, visit www.towne.com and follow us on LinkedIn." Might be considered navigation? It's a link to company site; but it's not navigation per se. Might keep as part of About the company description. Then "Job Details $14-$17 per hour Part-time shifts (day/night/weekends) Compensation: Towne Park is committed to offering competitive, fair, and commensurate compensation. Actual compensation will be based on a candidate’s job-related skills, experience, education or training, and location. The hourly base pay range for this position is $14-$17 per hour. Work Schedule: The work schedule for this position is part-time shifts. Benefits: Employees are eligible to enroll in accident insurance, critical illness insurance, hospital indemnity insurance, and telemedicine benefits. Employees are also able to enroll in the company’s 401k retirement savings plan. Eligibility requirements depend on your job classification, length of employment and number of hours worked. Benefits are subject to change and may be subject to a specific plan or program terms. Seasonal and temporary roles are not eligible for benefits outlined above." We need to extract Pay, Schedule, Benefits sections if they have real specific content. Pay: they gave hourly base pay range $14-$17 per hour. That's specific. So we can have a Pay section with that info. Schedule: they said part-time shifts (day/night/weekends). That's specific enough. Benefits: they list specific insurances and 401k. So we can have Benefits section. We also have a Summary and Essential Functions (list of duties with percentages). That's Responsibilities. Also Qualifications: Education, Licensure, Work Experience, Knowledge, etc. Also SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, etc. Those could be considered Requirements or Qualifications. We need to decide sections. We should not create sections with filler text. Avoid sections like "About the role" if we don't have specific content. We have company description; maybe we can put that under a section "About the company" but not in the list of allowed headings. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description under About the role? That seems odd but maybe acceptable. However "About the role" usually describes the role, not company. But we could treat it as About the role (summary). The posting includes a Summary section: "The Cashier is responsible for accurately collecting and reconciling revenue while providing exceptional hospitality services to all guests in an attentive, friendly and efficient manner." That's a good fit for About the role. Thus we can have:
About the role
The Cashier is responsible for accurately collecting and reconciling revenue while providing exceptional hospitality services to all guests in an attentive, friendly and efficient manner.
Then Responsibilities: we have Essential Functions with bullet points and percentages. We should output as- each duty. Should we include percentages? The posting includes percentages like "-20%" after each bullet. We should preserve all substantive information, so include the percentages. The bullet list lines: "Maintains pleasant, friendly and professional demeanor with all guests, co-workers and clients. Acknowledges and greets guests immediately while maintaining a professional and friendly demeanor. Addresses guests using last names when appropriate. Treats guests and associates with courtesy, respect and dignity.-20%" etc. We'll keep the text as is, including the percentage at end.
Thus Responsibilities section with
- each.
Then Qualifications: includes Education, Licensure, Work Experience, Knowledge, etc. Also SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel, etc. Those could be considered Requirements. But we have both Qualifications and Requirements headings allowed. We need to decide which to use. The posting has a "Qualifications" heading with subheadings Education, Licensure, Certification, Etc., Work Experience, Knowledge, etc. Then later there are sections like SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel. Those could be considered Requirements or maybe Skills. But we have Skills heading allowed. However the posting does not have a separate Skills section; the Knowledge section includes skills like basic math, reading, etc. So we could put Knowledge under Skills. But we also have Qualifications section for Education, Experience, Licensure. We could combine Education, Experience, Licensure under Qualifications. Then Knowledge under Skills. Then SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel could be under Requirements (maybe as "Requirements").
But we must avoid creating sections with filler text. Ensure each section has real content.
Let's extract:
Qualifications:
- Education: High school diploma or general education degree (GED)
- Licensure, Certification, Etc.: N/A (but N/A is placeholder; we should not include if it's just N/A? The instruction: 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. So we should not include a Licensure subsection if it's just N/A. We could omit that line entirely. Since it's N/A, we can drop it.
- Work Experience: One to three month(s) related experience and/or training; OR equivalent combination of education and experience.
- Knowledge: list of items: Basic Math Skills, Must be able to read and write standard English language, Must be able to read and comprehend simple instructions, short correspondence and memos, Must be able to write simple correspondence, Must be able to effectively present information in one-on-one and small group situations to guests, clients and other employees of the organization, Ability to add and subtract three digit numbers and to multiply and divide with 10’s and 100’s; ability to perform these operations using units of American money, Ability to understand 24 hour and military time systems, Ability to understand rates applicable to time passed.
We could treat Knowledge as Skills.
Then SCOPE Authority To Act: description.
Budget Responsibility: description.
WORKING CONDITIONS & PHYSICAL DEMANDS: includes Physical Requirements, Lifting Requirements, Working Environment, Travel.
Travel: Travel of up to 5% may be required.
We could group WORKING CONDITIONS & PHYSICAL DEMANDS under Requirements (or maybe under a separate section but not allowed). Since we have Requirements heading allowed, we can put all those under Requirements.
Thus sections:
- About the role (summary)
- Responsibilities (essential functions)
- Qualifications (education, work experience)
- Skills (knowledge/abilities)
- Requirements (scope, budget, working conditions, physical demands, travel)
- Benefits
- Pay
- Schedule
We need to ensure we don't create sections with filler text. All have content.
Now we need to format.
We'll output HTML fragment:
About the role
The Cashier is responsible for accurately collecting and reconciling revenue while providing exceptional hospitality services to all guests in an attentive, friendly and efficient manner.
Responsibilities
- Maintains pleasant, friendly and professional demeanor with all guests, co-workers and clients. Acknowledges and greets guests immediately while maintaining a professional and friendly demeanor. Addresses guests using last names when appropriate. Treats guests and associates with courtesy, respect and dignity.-20%
- Maintains accuracy and composure while under pressure. Appropriately uses the salutation of the day and welcomes guests to the location. Uses proper Towne Park phone etiquette.-15%
- Assists guests with directions and all other inquiries. Provides guests with information about outlets, meeting rooms and/or amenities of the facility as well as main attractions in the area.-10%
- Determines guest charges and processes payments via cash, credit, or direct billing. Accurately categorizes tickets for audit purposes. Collects and reconciles revenue accurately and furnishes payment receipts.-20%
- Completes accurate and timely shift reports. Follows all standard operating procedures related to cash banks. Operates equipment, including registers, gates, and credit card machines. Obtains information about daily events and rates to be charged.-20%
- Completes all tasks in a timely manner as instructed by the Lead Cashier/Account Manager.-15%
Qualifications
- Education: High school diploma or general education degree (GED)
- Work Experience: One to three month(s) related experience and/or training; OR equivalent combination of education and experience.
Skills
- Basic Math Skills
- Must be able to read and write standard English language
- Must be able to read and comprehend simple instructions, short correspondence and memos
- Must be able to write simple correspondence
- Must
- each.
Then Qualifications: includes Education, Licensure, Work Experience, Knowledge, etc. Also SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel, etc. Those could be considered Requirements. But we have both Qualifications and Requirements headings allowed. We need to decide which to use. The posting has a "Qualifications" heading with subheadings Education, Licensure, Certification, Etc., Work Experience, Knowledge, etc. Then later there are sections like SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel. Those could be considered Requirements or maybe Skills. But we have Skills heading allowed. However the posting does not have a separate Skills section; the Knowledge section includes skills like basic math, reading, etc. So we could put Knowledge under Skills. But we also have Qualifications section for Education, Experience, Licensure. We could combine Education, Experience, Licensure under Qualifications. Then Knowledge under Skills. Then SCOPE Authority To Act, Budget Responsibility, WORKING CONDITIONS & PHYSICAL DEMANDS, Travel could be under Requirements (maybe as "Requirements").
But we must avoid creating sections with filler text. Ensure each section has real content.
Let's extract:
Qualifications:
- Education: High school diploma or general education degree (GED)
- Licensure, Certification, Etc.: N/A (but N/A is placeholder; we should not include if it's just N/A? The instruction: 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. So we should not include a Licensure subsection if it's just N/A. We could omit that line entirely. Since it's N/A, we can drop it.
- Work Experience: One to three month(s) related experience and/or training; OR equivalent combination of education and experience.
- Knowledge: list of items: Basic Math Skills, Must be able to read and write standard English language, Must be able to read and comprehend simple instructions, short correspondence and memos, Must be able to write simple correspondence, Must be able to effectively present information in one-on-one and small group situations to guests, clients and other employees of the organization, Ability to add and subtract three digit numbers and to multiply and divide with 10’s and 100’s; ability to perform these operations using units of American money, Ability to understand 24 hour and military time systems, Ability to understand rates applicable to time passed.
We could treat Knowledge as Skills.
Then SCOPE Authority To Act: description.
Budget Responsibility: description.
WORKING CONDITIONS & PHYSICAL DEMANDS: includes Physical Requirements, Lifting Requirements, Working Environment, Travel.
Travel: Travel of up to 5% may be required.
We could group WORKING CONDITIONS & PHYSICAL DEMANDS under Requirements (or maybe under a separate section but not allowed). Since we have Requirements heading allowed, we can put all those under Requirements.
Thus sections:
- About the role (summary)
- Responsibilities (essential functions)
- Qualifications (education, work experience)
- Skills (knowledge/abilities)
- Requirements (scope, budget, working conditions, physical demands, travel)
- Benefits
- Pay
- Schedule
We need to ensure we don't create sections with filler text. All have content.
Now we need to format.
We'll output HTML fragment: