Hospital Security Technical Specialist – Security Department – Full Time
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings.
We have "About The Job" paragraph describing role. That could be "About the role". Also "About Mu Health Care" could be maybe "About the organization" but not in list; we could treat as part of "About the role"? Probably better to include as separate section? The allowed headings list includes those examples but not limited? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. So we need to map content accordingly.
We have:
- About the role: The paragraph after "About The Job" describing ideal candidate etc.
- Responsibilities: The "Detailed Job Description" bullet list (multiple sentences). Could be responsibilities.
- Requirements: Could include "Required Qualifications" and maybe "Preferred Qualifications" as part of Requirements or Qualifications. The headings list includes Requirements, Qualifications, Skills. We can decide.
We have "Required Qualifications" and "Preferred Qualifications". Could combine into "Qualifications" section.
We have "Employee Benefits" list: health, vision, dental insurance, paid leave, retirement options, tuition assistance, discounts. That's Benefits.
We have Pay: Compensation Base Pay Range.
We have Schedule: Shift Monday-Friday 8-4, Work Arrangement On-Site.
We might also have "Skills": maybe not explicit; we could omit if no specific skills list.
We must not include boilerplate like EEO, etc.
We must preserve all substantive information; not invent or summarize away detail. Must not create sections with filler like "commensurate with experience". Pay section we have actual range, okay.
Schedule: we have specific shift and work arrangement.
Benefits: we have list.
Responsibilities: we have detailed job description paragraphs; we need to turn into - items. The description includes multiple sentences each starting with a verb. We should split each duty into separate
- . Ensure we preserve all details.
Qualifications: we have Required Qualifications and Preferred Qualifications. We'll combine into a
- list.
We also have "PHYSICAL DEMANDS" maybe could be part of Requirements? But not in headings list; but we could include as a separate section? The instruction says prefer a few substantive sections over many thin ones. Physical demands is substantive; we could include under "Requirements" or "Qualifications". But maybe better to include as its own section? Not in the example headings but we could still use
for any heading; they gave examples but not exclusive. However they said use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; but not strictly prohibited to add others? Safer to stick to those.
Physical demands could be placed under "Requirements" as a bullet.
Also "Essentials of Crime Prevention through Environmental Design (CPTED) certification by ASIS International within one (1) year as a condition of continued employment in this job classification." That's a qualification.
"Personal driver license; Missouri class F or higher license within thirty (30) days of Missouri residency." Also qualification.
"OnGuard Certified Associate certification." Preferred.
"Additional license/certification requirements as determined by the hiring department." Preferred? Actually under Preferred Qualifications.
We'll include all.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ...
...
Qualifications
- ...
...
Benefits
- ...
...
Pay
Base Pay Range: $22.00 - $34.74 per hour, based on experience
Schedule
Shift: Monday through Friday 8:00 AM to 4:00 PM; Work Arrangement: On-Site
We must not repeat job title. No mention of Job ID etc.
We need to preserve all substantive information: include department, facility? Those are metadata; maybe we could include them in a short paragraph under About the role? But they said fold minor metadata into a short or drop it. So we could include a short paragraph after About the role maybe: "
Department: Security Department • Facility: University Hospital – 1 Hospital Drive, Columbia, MO
" That preserves info.
Also we have "Learn more about MU Health Care. Learn more about living in mid-Missouri." That's boilerplate? It's promotional but maybe considered part of About Mu Health Care. We could include that as part of About the role? Actually it's about the organization. Could be included in About the role paragraph? But we already have About Mu Health Care paragraph describing culture etc. That is substantive; we should keep it. However the instruction says use headings like About the role, Responsibilities, etc. There's no heading for About the organization. Could we incorporate that content under About the role? Might be okay but we risk losing detail. Better to create a section "About the organization" but not in list. However they said use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we could add another heading like "About MU Health Care". That seems reasonable.
Thus we could have:
About MU Health Care
...
But we already have About the role section. We'll keep both.
Now we need to ensure we don't include boilerplate like "Learn more about MU Health Care. Learn more about living in mid-Missouri." That's maybe navigation/link text; we should drop it. The paragraph about MU Health Care ends with "Learn more about MU Health Care. Learn more about living in mid-Missouri." That's likely boilerplate; we should remove those sentences. Keep the rest.
Now let's extract content.
About The Job paragraph:
"MU Health Care is looking for a highly skilled, solutions-driven professional who thrives at the intersection of technology, security, and innovation. The ideal candidate is a proactive problem solver with a sharp analytical mindset, a passion for continuous improvement, and the ability to confidently navigate complex systems while maintaining exceptional attention to detail. They are a collaborative partner who excels at building relationships across teams, communicates effectively with both technical and non-technical stakeholders, and remains committed to delivering reliable, secure outcomes. Success in this role requires adaptability, accountability, and a strong customer-service focus, especially when responding to critical issues and supporting a fast-paced healthcare environment. If you are energized by emerging technologies, driven to optimize performance, and motivated to make a meaningful impact on safety and security, we encourage you to apply and join our team."
We'll put that in .
About MU Health Care paragraph:
"MU Health Care is proud to be named one of Forbes’ Best-in-State Employers seven years in a row, and that’s largely a result of the incredible culture and team we’ve built. At MU Health Care, we have an inspired, hard-working and collaborative environment driven by our mission to save and improve lives. Here, we believe anything is possible and rally around solutions. We celebrate innovation and offer opportunities to be a part of something bigger — to have a voice and role in the work that is serving our community and changing the field of medicine. Our academic health system — the only in mid-Missouri — is home to seven hospitals, including the region’s only Level 1 Trauma Center and region’s only Children’s Hospital, as well as over 90 specialty clinics. Here you can define your career among our many clinical and nonclinical positions — with growth, opportunity and support every step of the way."
We'll drop the "Learn more about MU Health Care. Learn more about living in mid-Missouri." lines.
Now Responsibilities: Detailed Job Description sentences:
"Provide technical support to resolve day-to- day issues related to various security technology systems, to include programming support for core functions and programming modifications for system performance improvement."
"Provide technical liaison with Information Technology professionals and technology system vendors for server maintenance and proper integration of security systems with overall IT infrastructure, to include compliance with cyber security policies and procedures."
"Monitor system performance and data integrity through the use of regular audits and provide feedback to primary users and integrators."
"Prepares reports for access tracking and access violations."
"Provide training to employees regarding security systems as needed."
"Assist with Planning, Design & Construction."
"Support and oversee the new installation of security technology systems as it relates to ensuring compliance with standards, and support for local system integrators."
"Provide testing of security technology system installations prior to final acceptance."
"Adheres to University of Missouri System, campus, healthcare, and departmental policies and procedures."
"Perform related duties as assigned, which may include duties outside the area of responsibility with oversight."
"Execute emergency responsibilities, including on-call for weekends, holidays, and after hours as designated."
"May complete unit/department-specific duties as outlined in department documents."
We need to preserve all. We'll make each a
- .
Now Qualifications: Required Qualifications bullet list:
"High school diploma, technical certification, or an equivalent combination of education and experience from which comparable knowledge, skills and abilities can be acquired."
"Experience and knowledge of various access control platforms, video management systems and incident management application/software."
"Essentials of Crime Prevention through Environmental Design (CPTED) certification by ASIS International within one (1) year as a condition of continued employment in this job classification."
"Personal driver license; Missouri class F or higher license within thirty (30) days of Missouri residency."
Preferred Qualifications:
"OnGuard Certified Associate certification."
"Additional license/certification requirements as determined by the hiring department."
We'll combine into one list.
Now Benefits list:
"Health, vision and dental insurance coverage starting day one"
"Generous paid leave and paid time off, including ten holidays"
"Multiple retirement options, including 100% matching up to 8% and full vesting in three years"
"Tuition assistance for employees (75%) and immediate family members (50%)"
"Discounts on cell phone plans, rental cars, gyms, hotels and more"
"See a comprehensive list of benefits here." That's a link; maybe drop as boilerplate? It's a reference; we could keep but it's not substantive detail. Probably drop.
Now Pay: "Compensation Base Pay Range: $22.00 - $34.74 per hour, based on experience"
Schedule: "Shift: Monday through Friday 8:00 AM to 4:00 PM Work Arrangement: On-Site"
We'll combine.
Now Department and Facility: we can include a short paragraph after About MU Health Care maybe.
Let's craft HTML.
We need to ensure we don't include any extra text outside HTML.
We'll output:
About
- items. The description includes multiple sentences each starting with a verb. We should split each duty into separate
- . Ensure we preserve all details.
Qualifications: we have Required Qualifications and Preferred Qualifications. We'll combine into a
- list.
We also have "PHYSICAL DEMANDS" maybe could be part of Requirements? But not in headings list; but we could include as a separate section? The instruction says prefer a few substantive sections over many thin ones. Physical demands is substantive; we could include under "Requirements" or "Qualifications". But maybe better to include as its own section? Not in the example headings but we could still use
for any heading; they gave examples but not exclusive. However they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; but not strictly prohibited to add others? Safer to stick to those. Physical demands could be placed under "Requirements" as a bullet. Also "Essentials of Crime Prevention through Environmental Design (CPTED) certification by ASIS International within one (1) year as a condition of continued employment in this job classification." That's a qualification. "Personal driver license; Missouri class F or higher license within thirty (30) days of Missouri residency." Also qualification. "OnGuard Certified Associate certification." Preferred. "Additional license/certification requirements as determined by the hiring department." Preferred? Actually under Preferred Qualifications. We'll include all. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:
About the role
...
Responsibilities
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Base Pay Range: $22.00 - $34.74 per hour, based on experience
Schedule
Shift: Monday through Friday 8:00 AM to 4:00 PM; Work Arrangement: On-Site
We must not repeat job title. No mention of Job ID etc. We need to preserve all substantive information: include department, facility? Those are metadata; maybe we could include them in a short paragraph under About the role? But they said fold minor metadata into a shortor drop it. So we could include a short paragraph after About the role maybe: "
Department: Security Department • Facility: University Hospital – 1 Hospital Drive, Columbia, MO
" That preserves info. Also we have "Learn more about MU Health Care. Learn more about living in mid-Missouri." That's boilerplate? It's promotional but maybe considered part of About Mu Health Care. We could include that as part of About the role? Actually it's about the organization. Could be included in About the role paragraph? But we already have About Mu Health Care paragraph describing culture etc. That is substantive; we should keep it. However the instruction says use headings like About the role, Responsibilities, etc. There's no heading for About the organization. Could we incorporate that content under About the role? Might be okay but we risk losing detail. Better to create a section "About the organization" but not in list. However they said use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we could add another heading like "About MU Health Care". That seems reasonable. Thus we could have:About MU Health Care
...
But we already have About the role section. We'll keep both. Now we need to ensure we don't include boilerplate like "Learn more about MU Health Care. Learn more about living in mid-Missouri." That's maybe navigation/link text; we should drop it. The paragraph about MU Health Care ends with "Learn more about MU Health Care. Learn more about living in mid-Missouri." That's likely boilerplate; we should remove those sentences. Keep the rest. Now let's extract content. About The Job paragraph: "MU Health Care is looking for a highly skilled, solutions-driven professional who thrives at the intersection of technology, security, and innovation. The ideal candidate is a proactive problem solver with a sharp analytical mindset, a passion for continuous improvement, and the ability to confidently navigate complex systems while maintaining exceptional attention to detail. They are a collaborative partner who excels at building relationships across teams, communicates effectively with both technical and non-technical stakeholders, and remains committed to delivering reliable, secure outcomes. Success in this role requires adaptability, accountability, and a strong customer-service focus, especially when responding to critical issues and supporting a fast-paced healthcare environment. If you are energized by emerging technologies, driven to optimize performance, and motivated to make a meaningful impact on safety and security, we encourage you to apply and join our team." We'll put that in. About MU Health Care paragraph: "MU Health Care is proud to be named one of Forbes’ Best-in-State Employers seven years in a row, and that’s largely a result of the incredible culture and team we’ve built. At MU Health Care, we have an inspired, hard-working and collaborative environment driven by our mission to save and improve lives. Here, we believe anything is possible and rally around solutions. We celebrate innovation and offer opportunities to be a part of something bigger — to have a voice and role in the work that is serving our community and changing the field of medicine. Our academic health system — the only in mid-Missouri — is home to seven hospitals, including the region’s only Level 1 Trauma Center and region’s only Children’s Hospital, as well as over 90 specialty clinics. Here you can define your career among our many clinical and nonclinical positions — with growth, opportunity and support every step of the way." We'll drop the "Learn more about MU Health Care. Learn more about living in mid-Missouri." lines. Now Responsibilities: Detailed Job Description sentences: "Provide technical support to resolve day-to- day issues related to various security technology systems, to include programming support for core functions and programming modifications for system performance improvement." "Provide technical liaison with Information Technology professionals and technology system vendors for server maintenance and proper integration of security systems with overall IT infrastructure, to include compliance with cyber security policies and procedures." "Monitor system performance and data integrity through the use of regular audits and provide feedback to primary users and integrators." "Prepares reports for access tracking and access violations." "Provide training to employees regarding security systems as needed." "Assist with Planning, Design & Construction." "Support and oversee the new installation of security technology systems as it relates to ensuring compliance with standards, and support for local system integrators." "Provide testing of security technology system installations prior to final acceptance." "Adheres to University of Missouri System, campus, healthcare, and departmental policies and procedures." "Perform related duties as assigned, which may include duties outside the area of responsibility with oversight." "Execute emergency responsibilities, including on-call for weekends, holidays, and after hours as designated." "May complete unit/department-specific duties as outlined in department documents." We need to preserve all. We'll make each a
- .
Now Qualifications: Required Qualifications bullet list:
"High school diploma, technical certification, or an equivalent combination of education and experience from which comparable knowledge, skills and abilities can be acquired."
"Experience and knowledge of various access control platforms, video management systems and incident management application/software."
"Essentials of Crime Prevention through Environmental Design (CPTED) certification by ASIS International within one (1) year as a condition of continued employment in this job classification."
"Personal driver license; Missouri class F or higher license within thirty (30) days of Missouri residency."
Preferred Qualifications:
"OnGuard Certified Associate certification."
"Additional license/certification requirements as determined by the hiring department."
We'll combine into one list.
Now Benefits list:
"Health, vision and dental insurance coverage starting day one"
"Generous paid leave and paid time off, including ten holidays"
"Multiple retirement options, including 100% matching up to 8% and full vesting in three years"
"Tuition assistance for employees (75%) and immediate family members (50%)"
"Discounts on cell phone plans, rental cars, gyms, hotels and more"
"See a comprehensive list of benefits here." That's a link; maybe drop as boilerplate? It's a reference; we could keep but it's not substantive detail. Probably drop.
Now Pay: "Compensation Base Pay Range: $22.00 - $34.74 per hour, based on experience"
Schedule: "Shift: Monday through Friday 8:00 AM to 4:00 PM Work Arrangement: On-Site"
We'll combine.
Now Department and Facility: we can include a short paragraph after About MU Health Care maybe.
Let's craft HTML.
We need to ensure we don't include any extra text outside HTML.
We'll output:
About
- list.
We also have "PHYSICAL DEMANDS" maybe could be part of Requirements? But not in headings list; but we could include as a separate section? The instruction says prefer a few substantive sections over many thin ones. Physical demands is substantive; we could include under "Requirements" or "Qualifications". But maybe better to include as its own section? Not in the example headings but we could still use