Ambulance Operator Coordinator
for each section heading. 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 — fold minor metadata into 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 job posting.
Let's extract substantive content:
- Opening: "The Position OPEN EXAMINATION- ONE-YEAR PROBATIONARY PERIOD Job Description: Under general supervision, this non-sworn mid-management position plans, coordinates, monitors, and evaluates the effectiveness of the Basic Life Support (BLS) ambulance transport component of the Glendale Fire Department's Emergency Medical Services Program. The position manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources."
- Classification Code: 2762 (metadata, can be short p or drop)
- Reporting Relationships: "This position reports to the EMS/Fire Battalion Chief."
- Common Responsibilities: list of items: Customer Service, Ethics, Performance, Work hours, Safety, Teamwork, Communications, Equipment, Cyber Security. Each with description.
- Minimum Requirements: includes Education, Experience, Certifications/Licenses.
- Also "Background Investigation" etc (but that's part of selection process, maybe not needed as separate section? Could be part of Requirements? But we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
"About the role": could be the initial description (job description). So we can put that under
About the role
with a .
"Responsibilities": we have Common Responsibilities list (Customer Service etc). Could also include the duties described earlier (manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources). So we can combine.
"Requirements": Minimum Requirements (Education, Experience, Certifications/Licenses). Could also include Classification Code? Not needed.
"Qualifications": maybe similar to Requirements? Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they are separate headings allowed. However we should only include sections if there is real specific content. We have content for Requirements (education, experience, certifications). We also have content for Skills (maybe the Common Responsibilities includes skills like Customer Service, Ethics, etc). Could treat those as Skills section.
"Benefits": The posting mentions: "The City of Glendale offers a comprehensive benefit package including vacation, holiday, and sick leave as well as medical, dental, vision, life, and long-term disability insurance. The above listed benefits apply to full-time, salaried positions only." That's specific benefits. So we can include Benefits section.
"Pay": Not mentioned; no salary range given. So we should NOT include Pay section.
"Schedule": Not mentioned; no schedule info. So we should NOT include Schedule section.
Thus sections: About the role, Responsibilities, Skills, Requirements (or Qualifications), Benefits.
We need to decide naming: The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use any of those. We need to avoid duplication. Perhaps we can have About the role, Responsibilities, Skills, Requirements, Benefits. That seems fine.
Now we need to format content.
For About the role: a paragraph summarizing the job description: "Under general supervision, this non-sworn mid-management position plans, coordinates, monitors, and evaluates the effectiveness of the Basic Life Support (BLS) ambulance transport component of the Glendale Fire Department's Emergency Medical Services Program. The position manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources."
We could also include classification code and reporting relationships as minor metadata; maybe include in a short p after About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include classification code and reporting relationships in a short p under About the role or separate small p. Probably better to include them in About the role paragraph or a separate p.
Let's include: After the description, a short p: "Classification Code: 2762. Reports to the EMS/Fire Battalion Chief."
Now Responsibilities: we have the list of Common Responsibilities with descriptions. Also the earlier duties (manages etc) could be considered responsibilities but already in About the role. To avoid duplication, we can keep the Common Responsibilities list as Responsibilities.
We need to output
- for each duty/requirement/benefit. For Responsibilities, each item is a heading (Customer Service, Ethics, etc) with description. Should we make each
- contain the heading and description? Probably yes:
- Customer Service: Provide exceptional customer service to all employees, customers, vendors and other City departments.
etc.
Similarly for Skills: maybe we can treat the same list as Skills? But we already used them for Responsibilities. Could split: Responsibilities = the operational duties (manages Ambulance Operator personnel etc). Skills = the list of common responsibilities (Customer Service, Ethics, etc). However the instruction says prefer few substantive sections over many thin ones. Might be better to combine them into one Responsibilities section that includes both operational duties and the common responsibilities. But we need to use - for any list of duties/requirements/benefits. So we can have a single Responsibilities section with a list that includes both the operational duties and the common responsibilities items.
Let's think: The operational duties: manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources. That's a list.
The common responsibilities: Customer Service, Ethics, Performance, Work hours, Safety, Teamwork, Communications, Equipment, Cyber Security. That's also a list.
We could combine them into one list under Responsibilities. That would be substantive.
Then we could have a Skills section maybe empty? Better to avoid empty sections. So we could omit Skills section entirely and just have About the role, Responsibilities, Requirements, Benefits.
But the allowed headings include Skills; we don't have to use it if no content. So we can omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
Now Requirements: we need to list Education, Experience, Certifications/Licenses. Also maybe mention "An equivalent combination of experience and education sufficient to perform the essential job functions and provide the required knowledge and abilities is qualifying." That's prose.
We can format as a list: Education: Associate of Arts or Associate of Science Degree in a related field required; Bachelor desirable; Completion of Registered Nursing Program or Paramedic Training Program required. Experience: Five years recent experience in delivery of emergency medical care required, one year supervisory; Experience in delivery of skills training and education highly desirable. Certifications/Licenses: Valid California Registered Nursing License or valid California State Paramedic License required; Valid California Class C Driver's License required.
We could also include "Background Investigation" etc but that's part of selection process, not requirements. Might be considered under Requirements? But it's more about selection. Could be omitted or placed in a separate section? Not needed.
Now Benefits: list: vacation, holiday, sick leave; medical, dental, vision, life, long-term disability insurance. Note applies to full-time salaried positions only.
We'll output as
- each.
Now we need to ensure we don't include boilerplate like "Click here to view the complete class specification", "Selection Process", "APPLICATION", etc. Remove those.
Also remove duplicated lines like "Background Investigation" repeated; we can ignore.
Now produce HTML fragment.
Structure:
About the role
Under general supervision, this non-sworn mid-management position plans, coordinates, monitors, and evaluates the effectiveness of the Basic Life Support (BLS) ambulance transport component of the Glendale Fire Department's Emergency Medical Services Program. The position manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources. Classification Code: 2762. Reports to the EMS/Fire Battalion Chief.
Responsibilities
- Manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources.
- Customer Service: Provide exceptional customer service to all employees, customers, vendors and other City departments.
- Ethics: Model and practice the highest standards of ethical conduct.
- Performance: Develop necessary skills from on-the-job training and meet standards of performance for the classification by the end of the probationary period; work the necessary hours and times, including overtime as authorized for non-management staff, to complete goals, tasks, and objectives.
- Safety: Ensure the duties of the position are performed in a safe and efficient manner; assume responsibility for maintaining a safe working environment.
- Teamwork: Foster a teamwork environment; establish and maintain effective working relationships.
- Communications: Give and receive direction in English; communicate effectively in English, both orally and in writing.
- Equipment: Operate or use all position-related software, equipment and tools effectively and safely.
- Cyber Security: Actively participate in maintaining a secure computing environment by adhering to and implementing City cybersecurity policies, procedures, and best practices; includes understanding common cyber threats such as phishing and malware and promptly reporting suspicious activities.
Requirements
An equivalent combination of experience and education sufficient to perform the essential job functions and provide the required knowledge and abilities is qualifying.
- Education: Associate of Arts or Associate of Science Degree in a related field required; Bachelor of Arts or Bachelor of Science Degree desirable; completion of either a Registered Nursing Program or a Paramedic Training Program required.
- Experience: Five years of recent experience in the delivery of emergency medical care required, with at least one year in a supervisory capacity; experience in delivery of skills training and education highly desirable.
- Certifications/Licenses: Possession of a valid California Registered Nursing License or a valid California State Paramedic License required; valid California Class C Driver's License required.
Benefits
- Vacation, holiday, and sick leave.
- Medical, dental, vision, life, and long-term disability insurance.
- Note: Benefits apply to full-time, salaried positions only.
Check for any leftover boilerplate: We removed "Click here to view the complete class specification", "Background Investigation" repeated, "Exceptional Customer Service Policy", "Selection Process", "ORAL INTERVIEW", etc. Good.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings — fold minor metadata into 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 job posting. Let's extract substantive content: - Opening: "The Position OPEN EXAMINATION- ONE-YEAR PROBATIONARY PERIOD Job Description: Under general supervision, this non-sworn mid-management position plans, coordinates, monitors, and evaluates the effectiveness of the Basic Life Support (BLS) ambulance transport component of the Glendale Fire Department's Emergency Medical Services Program. The position manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources." - Classification Code: 2762 (metadata, can be short p or drop) - Reporting Relationships: "This position reports to the EMS/Fire Battalion Chief." - Common Responsibilities: list of items: Customer Service, Ethics, Performance, Work hours, Safety, Teamwork, Communications, Equipment, Cyber Security. Each with description. - Minimum Requirements: includes Education, Experience, Certifications/Licenses. - Also "Background Investigation" etc (but that's part of selection process, maybe not needed as separate section? Could be part of Requirements? But we have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. "About the role": could be the initial description (job description). So we can put that under
About the role
with a. "Responsibilities": we have Common Responsibilities list (Customer Service etc). Could also include the duties described earlier (manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources). So we can combine. "Requirements": Minimum Requirements (Education, Experience, Certifications/Licenses). Could also include Classification Code? Not needed. "Qualifications": maybe similar to Requirements? Might be redundant. The instruction says prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one? But they are separate headings allowed. However we should only include sections if there is real specific content. We have content for Requirements (education, experience, certifications). We also have content for Skills (maybe the Common Responsibilities includes skills like Customer Service, Ethics, etc). Could treat those as Skills section. "Benefits": The posting mentions: "The City of Glendale offers a comprehensive benefit package including vacation, holiday, and sick leave as well as medical, dental, vision, life, and long-term disability insurance. The above listed benefits apply to full-time, salaried positions only." That's specific benefits. So we can include Benefits section. "Pay": Not mentioned; no salary range given. So we should NOT include Pay section. "Schedule": Not mentioned; no schedule info. So we should NOT include Schedule section. Thus sections: About the role, Responsibilities, Skills, Requirements (or Qualifications), Benefits. We need to decide naming: The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use any of those. We need to avoid duplication. Perhaps we can have About the role, Responsibilities, Skills, Requirements, Benefits. That seems fine. Now we need to format content. For About the role: a paragraph summarizing the job description: "Under general supervision, this non-sworn mid-management position plans, coordinates, monitors, and evaluates the effectiveness of the Basic Life Support (BLS) ambulance transport component of the Glendale Fire Department's Emergency Medical Services Program. The position manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources." We could also include classification code and reporting relationships as minor metadata; maybe include in a short p after About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include classification code and reporting relationships in a short p under About the role or separate small p. Probably better to include them in About the role paragraph or a separate p. Let's include: After the description, a short p: "Classification Code: 2762. Reports to the EMS/Fire Battalion Chief." Now Responsibilities: we have the list of Common Responsibilities with descriptions. Also the earlier duties (manages etc) could be considered responsibilities but already in About the role. To avoid duplication, we can keep the Common Responsibilities list as Responsibilities. We need to output
- for each duty/requirement/benefit. For Responsibilities, each item is a heading (Customer Service, Ethics, etc) with description. Should we make each
- contain the heading and description? Probably yes:
- Customer Service: Provide exceptional customer service to all employees, customers, vendors and other City departments. etc. Similarly for Skills: maybe we can treat the same list as Skills? But we already used them for Responsibilities. Could split: Responsibilities = the operational duties (manages Ambulance Operator personnel etc). Skills = the list of common responsibilities (Customer Service, Ethics, etc). However the instruction says prefer few substantive sections over many thin ones. Might be better to combine them into one Responsibilities section that includes both operational duties and the common responsibilities. But we need to use
- for any list of duties/requirements/benefits. So we can have a single Responsibilities section with a list that includes both the operational duties and the common responsibilities items.
Let's think: The operational duties: manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources. That's a list.
The common responsibilities: Customer Service, Ethics, Performance, Work hours, Safety, Teamwork, Communications, Equipment, Cyber Security. That's also a list.
We could combine them into one list under Responsibilities. That would be substantive.
Then we could have a Skills section maybe empty? Better to avoid empty sections. So we could omit Skills section entirely and just have About the role, Responsibilities, Requirements, Benefits.
But the allowed headings include Skills; we don't have to use it if no content. So we can omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
Now Requirements: we need to list Education, Experience, Certifications/Licenses. Also maybe mention "An equivalent combination of experience and education sufficient to perform the essential job functions and provide the required knowledge and abilities is qualifying." That's prose.
We can format as a list: Education: Associate of Arts or Associate of Science Degree in a related field required; Bachelor desirable; Completion of Registered Nursing Program or Paramedic Training Program required. Experience: Five years recent experience in delivery of emergency medical care required, one year supervisory; Experience in delivery of skills training and education highly desirable. Certifications/Licenses: Valid California Registered Nursing License or valid California State Paramedic License required; Valid California Class C Driver's License required.
We could also include "Background Investigation" etc but that's part of selection process, not requirements. Might be considered under Requirements? But it's more about selection. Could be omitted or placed in a separate section? Not needed.
Now Benefits: list: vacation, holiday, sick leave; medical, dental, vision, life, long-term disability insurance. Note applies to full-time salaried positions only.
We'll output as
- each.
Now we need to ensure we don't include boilerplate like "Click here to view the complete class specification", "Selection Process", "APPLICATION", etc. Remove those.
Also remove duplicated lines like "Background Investigation" repeated; we can ignore.
Now produce HTML fragment.
Structure:
About the role
Under general supervision, this non-sworn mid-management position plans, coordinates, monitors, and evaluates the effectiveness of the Basic Life Support (BLS) ambulance transport component of the Glendale Fire Department's Emergency Medical Services Program. The position manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources. Classification Code: 2762. Reports to the EMS/Fire Battalion Chief.
Responsibilities
- Manages Ambulance Operator personnel, staffing, recruitment, onboarding, training, regulatory compliance, quality improvement, operational readiness, and assigned program resources.
- Customer Service: Provide exceptional customer service to all employees, customers, vendors and other City departments.
- Ethics: Model and practice the highest standards of ethical conduct.
- Performance: Develop necessary skills from on-the-job training and meet standards of performance for the classification by the end of the probationary period; work the necessary hours and times, including overtime as authorized for non-management staff, to complete goals, tasks, and objectives.
- Safety: Ensure the duties of the position are performed in a safe and efficient manner; assume responsibility for maintaining a safe working environment.
- Teamwork: Foster a teamwork environment; establish and maintain effective working relationships.
- Communications: Give and receive direction in English; communicate effectively in English, both orally and in writing.
- Equipment: Operate or use all position-related software, equipment and tools effectively and safely.
- Cyber Security: Actively participate in maintaining a secure computing environment by adhering to and implementing City cybersecurity policies, procedures, and best practices; includes understanding common cyber threats such as phishing and malware and promptly reporting suspicious activities.
Requirements
An equivalent combination of experience and education sufficient to perform the essential job functions and provide the required knowledge and abilities is qualifying.
- Education: Associate of Arts or Associate of Science Degree in a related field required; Bachelor of Arts or Bachelor of Science Degree desirable; completion of either a Registered Nursing Program or a Paramedic Training Program required.
- Experience: Five years of recent experience in the delivery of emergency medical care required, with at least one year in a supervisory capacity; experience in delivery of skills training and education highly desirable.
- Certifications/Licenses: Possession of a valid California Registered Nursing License or a valid California State Paramedic License required; valid California Class C Driver's License required.
Benefits
- Vacation, holiday, and sick leave.
- Medical, dental, vision, life, and long-term disability insurance.
- Note: Benefits apply to full-time, salaried positions only.
- each.
Now we need to ensure we don't include boilerplate like "Click here to view the complete class specification", "Selection Process", "APPLICATION", etc. Remove those.
Also remove duplicated lines like "Background Investigation" repeated; we can ignore.
Now produce HTML fragment.
Structure: