Business Systems Tech
Uniti Group Inc. · State College, PA · 1 mo ago
Information TechnologyFull-time
We need to produce HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to parse the posting.
Let's extract sections:
- About The Role: paragraph describing role.
- What You’ll Do: list of duties.
- Do You Have?: list of abilities/requirements.
- Even Better: certifications or training directly related, two-year technical degree, etc.
- Minimum Requirements: associate degree and experience.
- This is a safety sensitive position.
- Benefits: Medical, Dental, Vision Insurance Plans, 401K Plan, Health & Flexible Savings Account, Life and AD&D, Spousal Life, Child Life Insurance Plans, Educational Assistance Plan.
- Pay: "Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience." That's not a specific number; it's vague. According to rules: 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. The pay statement is vague but does state that pay depends on location etc. Is that considered filler? It says "Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience." That's not a specific number or range, but it's still stating something about pay. However the rule says never create Pay section unless posting actually states them. It does state something about pay (that it depends). Is that considered substantive? It's not a specific figure, but it's still info about pay. The rule about filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". This statement is similar to "depends on location and experience". Might be considered vague but not exactly those phrases. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay, albeit vague. I'd lean to include a Pay section with that statement, but we must avoid filler. The statement is not exactly filler like "commensurate with experience". It says actual base pay will depend on location and other factors. That's still somewhat generic but maybe acceptable. However the instruction also says: "Prefer a few substantive sections over many thin ones." So maybe we can combine Pay into Benefits? But Benefits already present. Could we include Pay as a subsection? Probably better to include Pay section with that statement.
Schedule: Not mentioned explicitly. There's mention of "Ability to work assigned schedules and extended hours including day, evening, weekend, and holiday hours. Ability to respond to after hour call-outs." That's about schedule requirements but not a schedule description. There's no explicit schedule like "Full-time, 40 hours per week". So we should not create a Schedule section because no specific schedule is stated. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Schedule, there is no explicit schedule statement, so we should not include Schedule heading.
Now we need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine some.
We have:
- About the role: paragraph.
- Responsibilities: the "What You’ll Do" list.
- Requirements: maybe the "Do You Have?" list (abilities) plus Minimum Requirements? Could split.
- Qualifications: maybe the "Even Better" and Minimum Requirements? Or we could treat Minimum Requirements as Qualifications.
- Skills: maybe the abilities like "Ability to understand CLR/DLR..." etc. Could be considered skills.
We need to avoid too many thin sections. Perhaps we can have:
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings? It says use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to parse the posting.
Let's extract sections:
- About The Role: paragraph describing role.
- What You’ll Do: list of duties.
- Do You Have?: list of abilities/requirements.
- Even Better: certifications or training directly related, two-year technical degree, etc.
- Minimum Requirements: associate degree and experience.
- This is a safety sensitive position.
- Benefits: Medical, Dental, Vision Insurance Plans, 401K Plan, Health & Flexible Savings Account, Life and AD&D, Spousal Life, Child Life Insurance Plans, Educational Assistance Plan.
- Pay: "Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience." That's not a specific number; it's vague. According to rules: 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. The pay statement is vague but does state that pay depends on location etc. Is that considered filler? It says "Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience." That's not a specific number or range, but it's still stating something about pay. However the rule says never create Pay section unless posting actually states them. It does state something about pay (that it depends). Is that considered substantive? It's not a specific figure, but it's still info about pay. The rule about filler includes "commensurate with experience", "not specified", "N/A", "varies", "TBD". This statement is similar to "depends on location and experience". Might be considered vague but not exactly those phrases. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay, albeit vague. I'd lean to include a Pay section with that statement, but we must avoid filler. The statement is not exactly filler like "commensurate with experience". It says actual base pay will depend on location and other factors. That's still somewhat generic but maybe acceptable. However the instruction also says: "Prefer a few substantive sections over many thin ones." So maybe we can combine Pay into Benefits? But Benefits already present. Could we include Pay as a subsection? Probably better to include Pay section with that statement.
Schedule: Not mentioned explicitly. There's mention of "Ability to work assigned schedules and extended hours including day, evening, weekend, and holiday hours. Ability to respond to after hour call-outs." That's about schedule requirements but not a schedule description. There's no explicit schedule like "Full-time, 40 hours per week". So we should not create a Schedule section because no specific schedule is stated. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Schedule, there is no explicit schedule statement, so we should not include Schedule heading.
Now we need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Possibly combine some.
We have:
- About the role: paragraph.
- Responsibilities: the "What You’ll Do" list.
- Requirements: maybe the "Do You Have?" list (abilities) plus Minimum Requirements? Could split.
- Qualifications: maybe the "Even Better" and Minimum Requirements? Or we could treat Minimum Requirements as Qualifications.
- Skills: maybe the abilities like "Ability to understand CLR/DLR..." etc. Could be considered skills.
We need to avoid too many thin sections. Perhaps we can have:
About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Pay
Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience.
We should not include Qualifications or Skills separately if we merged. Check if we lose any substantive info: We need to preserve all substantive information. Let's list all substantive info from posting: - Company description: Kinetic, a business unit of Uniti (NASDAQ: UNIT), premier insurgent provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in across the U.S. Additional info at www.GoKinetic.com - About The Role paragraph: Kinetic's team of Business Systems Technicians are vital team members who represent our leading telecommunications brand that connects homeowners, small business, and carrier partners across the United States. Our team of Technicians care about technology and connecting customers to products they value. Through providing technical expertise and customer support, our Technicians create meaningful connections with customers that create long-term relationships. - What You’ll Do list: * Perform routine installation, maintenance, and repair activities for network systems including voice, data, network, transport, and video equipment * Complete post installation tests for call processing functionality and AMA testing * Coordinate central office/Network equipment, card/SFP insertions, translations, fiber cross-connects and inside wiring activities * Perform OTDR tests and understand results * Fixed Wireless Installation & Maintenance * Safely operate and maintain clean and organized company service vehicle * Work in both inside and outside environments * Complete necessary safety training and follow safety standards and regulations * You will report to the Manager of Local Operations - Do You Have? list: * Ability to understand CLR/DLR and Engineering job packs * Ability to perform OTDR tests and understand results * Basic technology and math skills * Valid driver’s license and safe driving record * Ability to distinguish colors in use of color-coded cable. * Ability to use equipment with maximum load capacity of 275lbs. * Ability to lift up to 50lbs, capable of working aloft. * Ability to successfully complete required safety training. * Ability to work assigned schedules and extended hours including day, evening, weekend, and holiday hours. * Ability to respond to after hour call-outs. * High School Degree or GED equivalent - Even Better: * Certifications or training directly related to the position. * Two-year technical degree in computers or electronics, or the equivalent in work experience - Minimum Requirements: * Associate Degree in a technical discipline and 4-6 years technical/telephony experience with 4+ years directly related to the job; or 6+ years of directly related telephony or network operations experience and/or an equivalent combination of education and directly related experience required. * This is a safety sensitive position. - Benefits: * Medical, Dental, Vision Insurance Plans * 401K Plan * Health & Flexible Savings Account * Life and AD&D, Spousal Life, Child Life Insurance Plans * Educational Assistance Plan - Pay statement: Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience. - Also there is EEO boilerplate etc which we remove. - Also there are notices about non-US citizens, pre-employment screenings etc which we remove as boilerplate/legal. We need to preserve all substantive info; we must not invent or summarize away detail. So we need to include all the above points. Now we need to decide how to structure sections to avoid losing info. Option: Have sections: About the role, Responsibilities, Requirements (including Do You Have?, Even Better, Minimum Requirements), Benefits, Pay. But we need to ensure we don't lose the "Even Better" and "Minimum Requirements" details. If we put them under Requirements, we can list them as list items. We also need to include the company description? The posting starts with a description of Kinetic. Should we include that? It's substantive info about the company. The instructions: "Preserve ALL substantive information". So we should include that somewhere. Where? Could be part of About the role? Or maybe a separate section like "About Kinetic". But we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put company description in About the role paragraph, but that section is about the role, not company. However we could incorporate it into About the role paragraph as a preamble. The instructions: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should stick to those. So we need to fit company description somewhere, maybe in About the role paragraph as an introductory sentence.
Thus About the role paragraph could include: "Kinetic, a business unit of Uniti (NASDAQ: UNIT), is a premier insurgent provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in across the U.S. Additional information about Kinetic is available at www.GoKinetic.com. Kinetic's team of Business Systems Technicians are vital team members..." That preserves company description.
Now Responsibilities: list of What You’ll Do.
Requirements: combine Do You Have?, Even Better, Minimum Requirements, and safety sensitive note.
We need to be careful not to lose any detail: The "Do You Have?" list includes many abilities. The "Even Better" list includes certifications/training and two-year technical degree. The Minimum Requirements includes associate degree + experience or equivalent, and safety sensitive note.
We should include all as list items under Requirements.
Potentially we could split Requirements into two sub-sections: Minimum Requirements and Preferred Qualifications, but we only have headings list; we could use Requirements for mandatory and Qualifications for preferred. But we have Qualifications heading available. So we could do:
- Requirements: Mandatory (Do You Have? + Minimum Requirements)
- Qualifications: Preferred (Even Better)
That would preserve info and use headings appropriately.
Thus sections:
About the role (paragraph with company description + role description)
Responsibilities (ul)
Requirements (ul) - mandatory: Do You Have? list + Minimum Requirements (associate degree/experience, safety sensitive)
Qualifications (ul) - preferred: Even Better (certifications/training, two-year technical degree)
Benefits (ul)
Pay (p)
We should not include Schedule.
Now we need to ensure we don't include any boilerplate like EEO, notices, etc.
Now we need to format as HTML fragment, no or , no markdown fences.
Let's craft.
First, About the role paragraph:
Kinetic, a business unit of Uniti (NASDAQ: UNIT), is a premier insurgent provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in the U.S. Additional information about Kinetic is available at www.GoKinetic.com.