Unified Communications Engineer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the long TEKsystems description etc. That's boilerplate. Also the equal opportunity employer statements etc. Should be removed. Also the San Francisco Fair Chance Ordinance etc. Remove.
We need to preserve substantive info: Position Overview, Key Responsibilities, Must-Have Skills, Nice-to-Have, Ideal Candidate, Skills list, Additional Skills & Qualifications, Experience Level, Job Type & Location, Pay And Benefits, Workplace Type, Application Deadline? Probably drop deadline as it's application instruction? Might be considered metadata but not instruction. However instruction says remove application instructions. Deadline could be considered part of application process. Safer to drop.
We also need to include About TEKsystems? That's boilerplate; remove.
Thus final HTML will have sections: About the role (maybe from Position Overview), Responsibilities, Requirements (maybe combine Must-Have Skills, Nice-to-Have, Additional Skills & Qualifications), Benefits, Pay.
We need to ensure we don't create empty sections.
Let's extract content.
Position Overview: "Our client is seeking an experienced Unified Communications Engineer to support an active migration from Avaya to Zoom Phone. This individual will step into the project mid-stream, quickly understand the current state, and independently drive the remaining migration activities through completion."
That's prose.
Key Responsibilities list:
- Support and drive the Avaya to Zoom Phone migration
- Configure and manage enterprise telephony, including call flows, auto attendants, hunt groups, and number porting
- Support SIP/PSTN connectivity and E911
- Coordinate migration activities, testing, and cutovers
- Track outstanding tasks and drive the project toward completion
- Communicate effectively with IT teams, end users, vendors, and leadership
- Troubleshoot and resolve voice/telephony issues throughout the migration
That's a list.
Must-Have Skills list:
- Strong enterprise telephony / voice engineering experience
- Hands-on UCaaS migration experience
- Experience with SIP, PSTN, call routing, number porting, and E911
- Avaya experience
- Ability to independently take ownership of an active migration
- Strong organization and communication skills
Nice-to-Have list:
- Zoom Phone migration experience
- Multi-site enterprise migration experience
- Carrier/vendor coordination
- Cutover planning and post-migration support
- Ability to travel to locations as needed
Ideal Candidate: prose: "A senior-level UC/telephony engineer who can hit the ground running with minimal ramp-up, take ownership of an in-progress migration, and successfully get the organization off Avaya and onto Zoom Phone."
Skills list (maybe duplicate): "enterprise telephony, SIP/STN, call flows, Number porting, E911, UCaaS migration, avaya, avaya certified, Zoom phone, Multi-site enterprise migration, vendor coordination, cut-over planning, strong documentation, Unified communications, Telecom, Troubleshooting, Telephony, Installation"
Additional Skills & Qualifications list:
- Strong troubleshooting and problem-solving skills
- Experience supporting multi-site enterprise environments
- Carrier/vendor coordination experience
- Cutover planning, testing, and post-migration support
- Strong documentation and project tracking skills
- Ability to work independently with minimal supervision
- Comfortable communicating with both technical and non-technical stakeholders
- Flexible to travel to company sites as needed
Experience Level: Intermediate Level
Job Type & Location: "This is a Contract position based out of Saint Paul, MN."
Pay And Benefits: includes pay range and benefits list.
Workplace Type: "This is a fully onsite position in Saint Paul,MN."
We could combine Job Type & Location and Workplace Type maybe into a section about Location/Workplace? But we only have headings for specific categories: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put location under About the role? Or maybe we can create a separate section? Not allowed headings besides those. So we need to fit location info into one of those sections. Perhaps About the role can include location. Or we could put under Requirements? Better to put location in About the role as part of overview.
But we also have Pay and Benefits separate.
We need to ensure we don't create sections with filler. So we will have:
About the role
Our client is seeking an experienced Unified Communications Engineer to support an active migration from Avaya to Zoom Phone. This individual will step into the project mid-stream, quickly understand the current state, and independently drive the remaining migration activities through completion. This is a Contract position based out of Saint Paul, MN and requires fully onsite work.
That combines overview, job type, location, workplace type.
Responsibilities
- Support and drive the Avaya to Zoom Phone migration
- Configure and manage enterprise telephony, including call flows, auto attendants, hunt groups, and number porting
- Support SIP/PSTN connectivity and E911
- Coordinate migration activities, testing, and cutovers
- Track outstanding tasks and drive the project toward completion
- Communicate effectively with IT teams, end users, vendors, and leadership
- Troubleshoot and resolve voice/telephony issues throughout the migration
Requirements
We need to combine Must-Have Skills, Nice-to-Have, Additional Skills & Qualifications, Experience Level maybe. Could split into Must-Have and Nice-to-Have but we only have Requirements heading. Could also have Skills heading. The allowed headings include Skills. So we could have Requirements for must-have and nice-to-have? Or we could have Skills for the skills list. Let's think: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections: Requirements, Qualifications, Skills. We need to decide how to split.
We have Must-Have Skills (mandatory), Nice-to-Have (preferred), Additional Skills & Qualifications (more). Experience Level (Intermediate Level). Could put Experience Level under Requirements or Qualifications.
Better: Requirements = Must-Have Skills. Qualifications = Nice-to-Have + Additional Skills & Qualifications + Experience Level. Skills = maybe the combined skills list (the long list). But that may be redundant.
We need to avoid thin sections. Let's combine Must-Have and Nice-to-Have into Requirements? Or we could have Requirements for Must-Have, Qualifications for Nice-to-Have + Additional Skills, and Skills for the bullet list of skills (the long list). However the long list is basically a repetition of skills; we could omit it to avoid duplication. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The long list is substantive but duplicates many items already listed. If we omit it, we lose some detail like "avaya certified", "strong documentation", "Unified communications", "Telecom", "Installation". Those are not covered elsewhere. So we need to include them somewhere.
We could put them under Skills section as a list.
Thus:
Requirements
(Must-Have Skills)
Qualifications
(Nice-to-Have + Additional Skills & Qualifications + Experience Level)
Skills
(the long skills list)
But we need to ensure we don't create thin sections. Each will have substantive content.
Let's extract Must-Have Skills list items:
- Strong enterprise telephony / voice engineering experience
- Hands-on UCaaS migration experience
- Experience with SIP, PSTN, call routing, number porting, and E911
- Avaya experience
- Ability to independently take ownership of an active migration
- Strong organization and communication skills
Nice-to-Have list:
- Zoom Phone migration experience
- Multi-site enterprise migration experience
- Carrier/vendor coordination
- Cutover planning and post-migration support
- Ability to travel to locations as needed
Additional Skills & Qualifications list:
- Strong troubleshooting and problem-solving skills
- Experience supporting multi-site enterprise environments
- Carrier/vendor coordination experience
- Cutover planning, testing, and post-migration support
- Strong documentation and project tracking skills
- Ability to work independently with minimal supervision
- Comfortable communicating with both technical and non-technical stakeholders
- Flexible to travel to company sites as needed
Experience Level: Intermediate Level (could be a or
- ? Probably a
under Qualifications.)
Now the long Skills list: "enterprise telephony, SIP/STN, call flows, Number porting, E911, UCaaS migration, avaya, avaya certified, Zoom phone, Multi-site enterprise migration, vendor coordination, cut-over planning, strong documentation, Unified communications, Telecom, Troubleshooting, Telephony, Installation"
We need to turn into list items. Could split by commas.
Let's produce list items:
- enterprise telephony
- SIP/STN
- call flows
- Number porting
- E911
- UCaaS migration
- avaya
- avaya certified
- Zoom phone
- Multi-site enterprise migration
- vendor coordination
- cut-over planning
- strong documentation
- Unified communications
- Telecom
- Troubleshooting
- Telephony
- Installation
Now Benefits list: from Pay And Benefits section:
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan
- Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
We need to preserve all. Some items are phrases; we can keep as list items.
Pay section: just the pay range.
We'll output:
About the role
Our client is seeking an experienced Unified Communications Engineer to support an active migration from Avaya to Zoom Phone. This individual will step into the project mid-stream, quickly understand the current state, and independently drive the remaining migration activities through completion. This is a Contract position based out of Saint Paul, MN and requires fully onsite work.
Responsibilities
...
for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the long TEKsystems description etc. That's boilerplate. Also the equal opportunity employer statements etc. Should be removed. Also the San Francisco Fair Chance Ordinance etc. Remove. We need to preserve substantive info: Position Overview, Key Responsibilities, Must-Have Skills, Nice-to-Have, Ideal Candidate, Skills list, Additional Skills & Qualifications, Experience Level, Job Type & Location, Pay And Benefits, Workplace Type, Application Deadline? Probably drop deadline as it's application instruction? Might be considered metadata but not instruction. However instruction says remove application instructions. Deadline could be considered part of application process. Safer to drop. We also need to include About TEKsystems? That's boilerplate; remove. Thus final HTML will have sections: About the role (maybe from Position Overview), Responsibilities, Requirements (maybe combine Must-Have Skills, Nice-to-Have, Additional Skills & Qualifications), Benefits, Pay. We need to ensure we don't create empty sections. Let's extract content. Position Overview: "Our client is seeking an experienced Unified Communications Engineer to support an active migration from Avaya to Zoom Phone. This individual will step into the project mid-stream, quickly understand the current state, and independently drive the remaining migration activities through completion." That's prose. Key Responsibilities list: - Support and drive the Avaya to Zoom Phone migration - Configure and manage enterprise telephony, including call flows, auto attendants, hunt groups, and number porting - Support SIP/PSTN connectivity and E911 - Coordinate migration activities, testing, and cutovers - Track outstanding tasks and drive the project toward completion - Communicate effectively with IT teams, end users, vendors, and leadership - Troubleshoot and resolve voice/telephony issues throughout the migration That's a list. Must-Have Skills list: - Strong enterprise telephony / voice engineering experience - Hands-on UCaaS migration experience - Experience with SIP, PSTN, call routing, number porting, and E911 - Avaya experience - Ability to independently take ownership of an active migration - Strong organization and communication skills Nice-to-Have list: - Zoom Phone migration experience - Multi-site enterprise migration experience - Carrier/vendor coordination - Cutover planning and post-migration support - Ability to travel to locations as needed Ideal Candidate: prose: "A senior-level UC/telephony engineer who can hit the ground running with minimal ramp-up, take ownership of an in-progress migration, and successfully get the organization off Avaya and onto Zoom Phone." Skills list (maybe duplicate): "enterprise telephony, SIP/STN, call flows, Number porting, E911, UCaaS migration, avaya, avaya certified, Zoom phone, Multi-site enterprise migration, vendor coordination, cut-over planning, strong documentation, Unified communications, Telecom, Troubleshooting, Telephony, Installation" Additional Skills & Qualifications list: - Strong troubleshooting and problem-solving skills - Experience supporting multi-site enterprise environments - Carrier/vendor coordination experience - Cutover planning, testing, and post-migration support - Strong documentation and project tracking skills - Ability to work independently with minimal supervision - Comfortable communicating with both technical and non-technical stakeholders - Flexible to travel to company sites as needed Experience Level: Intermediate Level Job Type & Location: "This is a Contract position based out of Saint Paul, MN." Pay And Benefits: includes pay range and benefits list. Workplace Type: "This is a fully onsite position in Saint Paul,MN." We could combine Job Type & Location and Workplace Type maybe into a section about Location/Workplace? But we only have headings for specific categories: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put location under About the role? Or maybe we can create a separate section? Not allowed headings besides those. So we need to fit location info into one of those sections. Perhaps About the role can include location. Or we could put under Requirements? Better to put location in About the role as part of overview. But we also have Pay and Benefits separate. We need to ensure we don't create sections with filler. So we will have:
About the role
Our client is seeking an experienced Unified Communications Engineer to support an active migration from Avaya to Zoom Phone. This individual will step into the project mid-stream, quickly understand the current state, and independently drive the remaining migration activities through completion. This is a Contract position based out of Saint Paul, MN and requires fully onsite work.
That combines overview, job type, location, workplace type.Responsibilities
- Support and drive the Avaya to Zoom Phone migration
- Configure and manage enterprise telephony, including call flows, auto attendants, hunt groups, and number porting
- Support SIP/PSTN connectivity and E911
- Coordinate migration activities, testing, and cutovers
- Track outstanding tasks and drive the project toward completion
- Communicate effectively with IT teams, end users, vendors, and leadership
- Troubleshoot and resolve voice/telephony issues throughout the migration
Requirements
We need to combine Must-Have Skills, Nice-to-Have, Additional Skills & Qualifications, Experience Level maybe. Could split into Must-Have and Nice-to-Have but we only have Requirements heading. Could also have Skills heading. The allowed headings include Skills. So we could have Requirements for must-have and nice-to-have? Or we could have Skills for the skills list. Let's think: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections: Requirements, Qualifications, Skills. We need to decide how to split. We have Must-Have Skills (mandatory), Nice-to-Have (preferred), Additional Skills & Qualifications (more). Experience Level (Intermediate Level). Could put Experience Level under Requirements or Qualifications. Better: Requirements = Must-Have Skills. Qualifications = Nice-to-Have + Additional Skills & Qualifications + Experience Level. Skills = maybe the combined skills list (the long list). But that may be redundant. We need to avoid thin sections. Let's combine Must-Have and Nice-to-Have into Requirements? Or we could have Requirements for Must-Have, Qualifications for Nice-to-Have + Additional Skills, and Skills for the bullet list of skills (the long list). However the long list is basically a repetition of skills; we could omit it to avoid duplication. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The long list is substantive but duplicates many items already listed. If we omit it, we lose some detail like "avaya certified", "strong documentation", "Unified communications", "Telecom", "Installation". Those are not covered elsewhere. So we need to include them somewhere. We could put them under Skills section as a list. Thus:Requirements
- (Must-Have Skills)
Qualifications
- (Nice-to-Have + Additional Skills & Qualifications + Experience Level)
Skills
- (the long skills list)
or
under Qualifications.) Now the long Skills list: "enterprise telephony, SIP/STN, call flows, Number porting, E911, UCaaS migration, avaya, avaya certified, Zoom phone, Multi-site enterprise migration, vendor coordination, cut-over planning, strong documentation, Unified communications, Telecom, Troubleshooting, Telephony, Installation" We need to turn into list items. Could split by commas. Let's produce list items: - enterprise telephony - SIP/STN - call flows - Number porting - E911 - UCaaS migration - avaya - avaya certified - Zoom phone - Multi-site enterprise migration - vendor coordination - cut-over planning - strong documentation - Unified communications - Telecom - Troubleshooting - Telephony - Installation Now Benefits list: from Pay And Benefits section: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan - Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) We need to preserve all. Some items are phrases; we can keep as list items. Pay section: just the pay range. We'll output:
About the role
Our client is seeking an experienced Unified Communications Engineer to support an active migration from Avaya to Zoom Phone. This individual will step into the project mid-stream, quickly understand the current state, and independently drive the remaining migration activities through completion. This is a Contract position based out of Saint Paul, MN and requires fully onsite work.
Responsibilities
- ...