Telecomm Specialist I
for the introductory paragraph about community values and location? The instruction: Use
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.
We have content: Job location, opening worker subtype, time type, scheduled weekly hours, department, work shift, compensation range. That's metadata could be folded into a short
. We should not create separate sections for Pay/Schedule/Benefits unless posting actually states them. It does state compensation range and scheduled weekly hours (40). So we could include a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation range and scheduled weekly hours, so we could include a Pay section (maybe also Schedule). But we should prefer few substantive sections over many thin ones. Could combine Pay and Schedule into one section? But headings are prescribed: we can use
for Pay and Schedule separately if we have content. However we might avoid creating many thin sections. Perhaps we can include a single Compensation and Schedule
but that's not in the list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? Likely we should stick to those headings. So we could have Pay and Schedule sections separately. But that would be two thin sections. However we have actual content for both: compensation range and scheduled weekly hours (40). So we could include both.
We also have Responsibilities (detailed list). That's a section.
We have Minimum Education & Experience (requirements). That could be Requirements or Qualifications. We'll use Requirements.
We have Knowledge, Skills And Abilities (skills). That's Skills.
We have LICENSES AND CERTIFICATIONS (maybe Qualifications or Requirements). Could be part of Requirements.
We have the introductory paragraph about community values and location etc. That could be About the role? Or we could just put in a
before sections. The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have About the role section with the introductory paragraph.
We must not repeat the job title as a heading. No job title given explicitly, but we can ignore.
We must remove boilerplate: EEO statement at end (the long paragraph about non-discrimination). Remove that.
Also remove duplicated lines: there are some duplicated responsibilities lines (some repeated). We need to preserve all substantive information but not duplicate lines. We should deduplicate.
Let's extract substantive content:
Intro: "As a community, the University of Rochester is defined by a deep commitment to Meliora - Ever Better. Embedded in that ideal are the values we share: equity, leadership, integrity, openness, respect, and accountability. Together, we will set the highest standards for how we treat each other to ensure our community is welcoming to all and is a place where all can thrive."
Job Location: "Job Location (Full Address): 300 Science Pkwy, Rochester, New York, United States of America, 14620"
Opening Worker Subtype: "Regular"
Time Type: "Full time"
Scheduled Weekly Hours: "40"
Department: "100110 University IT / CTS"
Work Shift: "UR - Day (United States of America)"
Range: "UR URG 109 H"
Compensation Range: "$27.16 - $38.03" with description.
Responsibilities: many bullet-like sentences. We need to convert to - . We'll need to parse responsibilities list.
Let's copy responsibilities paragraph:
"Responsibilities Leads the technical support that ensures stable and continuous service for faculty, staff, students and clinicians whose business functions rely on voice, data or video services in a 24x7 environment. Maintains expertise in and mentors others on current telephony and network technologies. Analyzes, triages, designs, installs, upgrades, monitors, tests and repairs telephone, data and video systems, as well as manages cable plant, switch rooms and CER's. Oversees contractors, vendors and other technicians. Programs telephone system features and functionality. Produces and updates voice and data system and process documentation. Diagnoses and resolves complex voice and data issues. Provides training to other technicians. Assists with developing strategies and implements process changes to support new voice, data and video technologies and infrastructure. Builds out new and upgrades existing telephone system infrastructure. Manages vendors to ensure appropriate planning, scheduling and acceptance testing."
Then "Essential Functions" repeats many items. We need to combine and deduplicate.
Essential Functions list:
"Programs telephone system features and functionality.
Produces and updates voice and data system and process documentation.
Develops and maintains network and cable design documentation and databases.
Coordinates activities including tag, test, splice and move.
Updates cable plant infrastructure and ensures integrity of the databases.
Manages daily dig requests with various departments.
Rotates through positions providing triage, project leadership, warehouse management, critical team support and on-call responsibilities.
Monitors user-generated service and trouble tickets.
Monitors and evaluates normal and critical workloads and allocates and/or reallocates resources as needed.
Follows escalation procedures and demonstrates exemplary communication skills.
Interacts with a cross-section of teams to support daily activities.
Trains and mentors technicians in telephone system software programming.
Advocates for customers and recommends process changes as appropriate.
Diagnoses and resolves complex voice and data issues and provides training to other technicians.
Reviews daily alarm logs and resolves first and second level system problems.
Updates technical documentation.
Completes preventive maintenance routines, such as voicemail maintenance, power system diagnostics, and battery plant.
Maintains spare parts inventories with input from engineers.
Serves as escalation for service interruptions associated with voice services, voicemail, paging, cellular and computer network.
Handles high visibility situations and critical customers using effective negotiating and exemplary customer service skills.
Develops strategies and implements process changes to support new voice, data and video technologies and infrastructure.
Builds out new and upgrades existing telephone system infrastructure.
Manages vendors to ensure appropriate planning, scheduling and acceptance testing.
Works closely with engineering and cable plant to ensure proper procedures and processes are executed.
Completes monthly voicemail maintenance and reports daily on system health.
Resolves voice and voicemail system emergencies and serves as escalation to technical resources working after hours in on-call rotations.
Participates in the on-call rotation.
Completes billing information and coordinates with peers to manage and procure inventory levels.
Maintains cable plant documentation.
Follows identification standards for cable connections including CER line card documentation.
Keeps abreast of current telephony, network and LAN technologies through continuing education, journal review, web searches, on the job training and formal seminar opportunities.
Other duties as assigned."
We need to deduplicate overlapping items with earlier responsibilities list. Many items repeat. We'll create a unified list of unique responsibilities.
Let's compile unique items:
- Leads the technical support that ensures stable and continuous service for faculty, staff, students and clinicians whose business functions rely on voice, data or video services in a 24x7 environment.
- Maintains expertise in and mentors others on current telephony and network technologies.
- Analyzes, triages, designs, installs, upgrades, monitors, tests and repairs telephone, data and video systems, as well as manages cable plant, switch rooms and CER's.
- Oversees contractors, vendors and other technicians.
- Programs telephone system features and functionality.
- Produces and updates voice and data system and process documentation.
- Diagnoses and resolves complex voice and data issues.
- Provides training to other technicians.
- Assists with developing strategies and implements process changes to support new voice, data and video technologies and infrastructure.
- Builds out new and upgrades existing telephone system infrastructure.
- Manages vendors to ensure appropriate planning, scheduling and acceptance testing.
- Develops and maintains network and cable design documentation and databases.
- Coordinates activities including tag, test, splice and move.
- Updates cable plant infrastructure and ensures integrity of the databases.
- Manages daily dig requests with various departments.
- Rotates through positions providing triage, project leadership, warehouse management, critical team support and on-call responsibilities.
- Monitors user-generated service and trouble tickets.
- Monitors and evaluates normal and critical workloads and allocates and/or reallocates resources as needed.
- Follows escalation procedures and demonstrates exemplary communication skills.
- Interacts with a cross-section of teams to support daily activities.
- Trains and mentors technicians in telephone system software programming.
- Advocates for customers and recommends process changes as appropriate.
- Reviews daily alarm logs and resolves first and second level system problems.
- Updates technical documentation.
- Completes preventive maintenance routines, such as voicemail maintenance, power system diagnostics, and battery plant.
- Maintains spare parts inventories with input from engineers.
- Serves as escalation for service interruptions associated with voice services, voicemail, paging, cellular and computer network.
- Handles high visibility situations and critical customers using effective negotiating and exemplary customer service skills.
- Works closely with engineering and cable plant to ensure proper procedures and processes are executed.
- Completes monthly voicemail maintenance and reports daily on system health.
- Resolves voice and voicemail system emergencies and serves as escalation to technical resources working after hours in on-call rotations.
- Participates in the on-call rotation.
- Completes billing information and coordinates with peers to manage and procure inventory levels.
- Maintains cable plant documentation.
- Follows identification standards for cable connections including CER line card documentation.
- Keeps abreast of current telephony, network and LAN technologies through continuing education, journal review, web searches, on the job training and formal seminar opportunities.
- Other duties as assigned.
Now Minimum Education & Experience:
"High School diploma or equivalent and 5 years of practical experience, including previous technical experience, required
Associate's degree preferred
Or equivalent combination of education and experience"
Knowledge, Skills And Abilities:
"Safe use of hand tools and test equipment required
Ability to work in confined spaces, such as closets, ceilings, crawl spaces, pipe chases and mechanical rooms required
Exceptional customer service skills, including outstanding verbal and written communications skills and ability to diffuse difficult situations required
MA 4000, NEAX 2400, 9300 and 9500 Installation & Maintenance preferred
ACD-MAT preferred
UM8700 (voicemail) Administration & Maintenance preferred
Advanced problem solving techniques, including ability to troubleshoot telephony and network issues remotely preferred
Demonstrated project management skills preferred"
LICENSES AND CERTIFICATIONS:
"Valid New York State driver's license required
Telemanagement system certification or equivalent training upon hire preferred
Cable management system certification or equivalent training upon hire preferred"
Now we need to decide sections.
We have About the role (intro + location etc). Could include location, worker subtype, time
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. We have content: Job location, opening worker subtype, time type, scheduled weekly hours, department, work shift, compensation range. That's metadata could be folded into a short
. We should not create separate sections for Pay/Schedule/Benefits unless posting actually states them. It does state compensation range and scheduled weekly hours (40). So we could include a Pay section? The instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation range and scheduled weekly hours, so we could include a Pay section (maybe also Schedule). But we should prefer few substantive sections over many thin ones. Could combine Pay and Schedule into one section? But headings are prescribed: we can use
for Pay and Schedule separately if we have content. However we might avoid creating many thin sections. Perhaps we can include a single Compensation and Schedule
but that's not in the list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? Likely we should stick to those headings. So we could have Pay and Schedule sections separately. But that would be two thin sections. However we have actual content for both: compensation range and scheduled weekly hours (40). So we could include both.
We also have Responsibilities (detailed list). That's a section.
We have Minimum Education & Experience (requirements). That could be Requirements or Qualifications. We'll use Requirements.
We have Knowledge, Skills And Abilities (skills). That's Skills.
We have LICENSES AND CERTIFICATIONS (maybe Qualifications or Requirements). Could be part of Requirements.
We have the introductory paragraph about community values and location etc. That could be About the role? Or we could just put in a
before sections. The instruction: Use