Technical Support
under maybe "About the role"? But that's not accurate. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So only those headings allowed. We must not add other headings. So we need to fit content into those sections.
We have:
- About the role: could include description of the role: troubleshooting proprietary software via phone/chat, typing 60 WPM, 100% remote, 1 year experience, contract position based out of Lehi, UT, great opportunity with local software company. Also note contradictory onsite vs remote; we keep both.
- Responsibilities: could list troubleshooting proprietary software via phone calls and chat. Possibly also typing requirement? That's more a requirement. Responsibilities: troubleshooting via phone/chat.
- Requirements: at least 1 year experience doing technical support of any kind; typing 60 WPM; work 100% remote (though contradictory). Also maybe contract position based out of Lehi, UT? That's more job type/location.
- Qualifications: maybe same as requirements? Could separate: qualifications could be experience, typing speed, remote work ability.
- Skills: maybe technical support, troubleshooting, phone/chat communication, typing.
- Benefits: list as given.
- Pay: pay range $20.00 - $23.00/hr.
- Schedule: not explicitly given; we have workplace type (fully onsite) but not schedule like full-time/part-time, hours. Not given. So we should not create Schedule section unless posting actually states them. It does not state schedule. So omit Schedule.
We must not include headings with filler text. So we will include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We need to use for each section heading. Then content: use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
Let's extract details:
About the role prose: "TEKsystems is looking for a technical support representative for one of your clients. You will be troubleshooting a proprietary software via phone calls and chat. You must be able to type at least 60 WPM and work 100% remote. We are looking for people with at least 1 years of experience doing technical support of any kind. This is a great opportunity with a local software company. Job Type & Location This is a Contract position based out of Lehi, UT."
We could split: About the role includes the description; Job Type & Location maybe part of About the role or Requirements. We'll keep as prose.
Responsibilities: "Troubleshooting a proprietary software via phone calls and chat."
Requirements: list: "At least 1 year of experience doing technical support of any kind", "Ability to type at least 60 WPM", "Ability to work 100% remote". Also maybe "Contract position based out of Lehi, UT" but that's job type/location; could be in Requirements or About the role. We'll keep it in About the role.
Qualifications: maybe same as requirements? To avoid duplication, we could treat Qualifications as "Experience in technical support, typing speed, remote work capability". But that duplicates. Better to separate: Requirements = mandatory experience; Qualifications = preferred or additional qualifications? Not given. Could combine. But we need to avoid filler. If we put Qualifications with same content as Requirements, it's duplicate but still substantive. Might be okay but could be considered duplication. The instruction: remove duplicated lines. So we should avoid duplicating same info across sections. So we need to split info logically.
Let's assign:
- About the role: general description: TEKsystems looking for technical support rep for a client; troubleshooting proprietary software via phone/chat; great opportunity with local software company; contract position based out of Lehi, UT.
- Responsibilities: troubleshooting proprietary software via phone calls and chat.
- Requirements: at least 1 year experience doing technical support of any kind; ability to type at least 60 WPM; ability to work 100% remote.
- Qualifications: maybe none distinct; but we could include "Experience with proprietary software troubleshooting" but that's same as responsibilities. Could leave Qualifications section out if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we don't have distinct qualifications, we should omit Qualifications.
- Skills: maybe "Technical support, troubleshooting, phone/chat communication, typing (60 WPM)". That's derived but could be considered summarizing. However we can list skills as bullet points: "Technical support experience", "Troubleshooting proprietary software", "Phone and chat communication", "Typing proficiency (≥60 WPM)". That's not invented; it's derived from responsibilities and requirements. Might be okay.
- Benefits: list as given.
- Pay: pay range $20.00 - $23.00/hr.
We must not include Schedule.
Now we need to ensure we preserve all substantive information: we have included:
- Troubleshooting proprietary software via phone/chat (in Responsibilities)
- Typing 60 WPM (in Requirements and Skills)
- 100% remote (in Requirements)
- 1 year experience (in Requirements)
- Contract position based out of Lehi, UT (in About the role)
- Great opportunity with local software company (in About the role)
- Benefits list (in Benefits)
- Pay range (in Pay)
We omitted mention of "Workplace Type: This is a fully onsite position in Lehi,UT." That's contradictory to remote. This is substantive information; we must preserve it. Where to put? Could be in About the role or Requirements. Since it's about workplace type, we could add to About the role: "Note: The position is described as fully onsite in Lehi, UT (contrary to remote requirement)." But we must not invent; we just state the fact: "This is a fully onsite position in Lehi, UT." We'll include that in About the role.
Thus About the role will contain both remote and onsite statements; we preserve both.
Now we need to format.
HTML fragment:
About the role
TEKsystems is looking for a technical support representative for one of its clients. You will be troubleshooting a proprietary software via phone calls and chat. This is a great opportunity with a local software company. The position is a contract role based out of Lehi, UT. Note: the posting also indicates the role is a fully onsite position in Lehi, UT.
But we need to preserve the exact wording? Not required to quote exactly, but preserve all substantive information. We can paraphrase but must not lose detail. Safer to keep close to original.
Let's copy sentences:
"TEKsystems is looking for a technical support representative for one of your clients. You will be troubleshooting a proprietary software via phone calls and chat. You must be able to type at least 60 WPM and work 100% remote. We are looking for people with at least 1 years of experience doing technical support of any kind. This is a great opportunity with a local software company. Job Type & Location This is a Contract position based out of Lehi, UT. Workplace Type This is a fully onsite position in Lehi,UT."
We can keep that as a paragraph.
But we need to split into sections; we already placed typing and remote in Requirements, experience in Requirements. So About the role can exclude those to avoid duplication. However we must preserve all info; if we remove them from About the role, they are still present in Requirements, so overall preserved. That's fine.
Thus About the role: "TEKsystems is looking for a technical support representative for one of your clients. You will be troubleshooting a proprietary software via phone calls and chat. This is a great opportunity with a local software company. Job Type & Location This is a Contract position based out of Lehi, UT. Workplace Type This is a fully onsite position in Lehi,UT."
Now Responsibilities: "Troubleshooting a proprietary software via phone calls and chat."
Requirements: list: "At least 1 year of experience doing technical support of any kind", "Ability to type at least 60 WPM", "Ability to work 100% remote".
Qualifications: we may omit.
Skills: list: "Technical support experience", "Troubleshooting proprietary software", "Phone and chat communication", "Typing proficiency (≥60 WPM)". But typing proficiency already in Requirements; duplication across sections maybe okay but could be considered duplicated lines. The instruction: remove duplicated lines. So we should avoid repeating same exact line. However "Typing proficiency (≥60 WPM)" is similar to "Ability to type at least 60 WPM". Not identical but same meaning. Might be considered duplication. Better to avoid Skills section if it just repeats. Could we have Skills with other skills not covered? Not given. So maybe omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay.
Check
- for any list of duties/requirements/benefits, and
for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details: About the role prose: "TEKsystems is looking for a technical support representative for one of your clients. You will be troubleshooting a proprietary software via phone calls and chat. You must be able to type at least 60 WPM and work 100% remote. We are looking for people with at least 1 years of experience doing technical support of any kind. This is a great opportunity with a local software company. Job Type & Location This is a Contract position based out of Lehi, UT." We could split: About the role includes the description; Job Type & Location maybe part of About the role or Requirements. We'll keep as prose. Responsibilities: "Troubleshooting a proprietary software via phone calls and chat." Requirements: list: "At least 1 year of experience doing technical support of any kind", "Ability to type at least 60 WPM", "Ability to work 100% remote". Also maybe "Contract position based out of Lehi, UT" but that's job type/location; could be in Requirements or About the role. We'll keep it in About the role. Qualifications: maybe same as requirements? To avoid duplication, we could treat Qualifications as "Experience in technical support, typing speed, remote work capability". But that duplicates. Better to separate: Requirements = mandatory experience; Qualifications = preferred or additional qualifications? Not given. Could combine. But we need to avoid filler. If we put Qualifications with same content as Requirements, it's duplicate but still substantive. Might be okay but could be considered duplication. The instruction: remove duplicated lines. So we should avoid duplicating same info across sections. So we need to split info logically. Let's assign: - About the role: general description: TEKsystems looking for technical support rep for a client; troubleshooting proprietary software via phone/chat; great opportunity with local software company; contract position based out of Lehi, UT. - Responsibilities: troubleshooting proprietary software via phone calls and chat. - Requirements: at least 1 year experience doing technical support of any kind; ability to type at least 60 WPM; ability to work 100% remote. - Qualifications: maybe none distinct; but we could include "Experience with proprietary software troubleshooting" but that's same as responsibilities. Could leave Qualifications section out if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So if we don't have distinct qualifications, we should omit Qualifications. - Skills: maybe "Technical support, troubleshooting, phone/chat communication, typing (60 WPM)". That's derived but could be considered summarizing. However we can list skills as bullet points: "Technical support experience", "Troubleshooting proprietary software", "Phone and chat communication", "Typing proficiency (≥60 WPM)". That's not invented; it's derived from responsibilities and requirements. Might be okay. - Benefits: list as given. - Pay: pay range $20.00 - $23.00/hr. We must not include Schedule. Now we need to ensure we preserve all substantive information: we have included: - Troubleshooting proprietary software via phone/chat (in Responsibilities) - Typing 60 WPM (in Requirements and Skills) - 100% remote (in Requirements) - 1 year experience (in Requirements) - Contract position based out of Lehi, UT (in About the role) - Great opportunity with local software company (in About the role) - Benefits list (in Benefits) - Pay range (in Pay) We omitted mention of "Workplace Type: This is a fully onsite position in Lehi,UT." That's contradictory to remote. This is substantive information; we must preserve it. Where to put? Could be in About the role or Requirements. Since it's about workplace type, we could add to About the role: "Note: The position is described as fully onsite in Lehi, UT (contrary to remote requirement)." But we must not invent; we just state the fact: "This is a fully onsite position in Lehi, UT." We'll include that in About the role. Thus About the role will contain both remote and onsite statements; we preserve both. Now we need to format. HTML fragment:
About the role
TEKsystems is looking for a technical support representative for one of its clients. You will be troubleshooting a proprietary software via phone calls and chat. This is a great opportunity with a local software company. The position is a contract role based out of Lehi, UT. Note: the posting also indicates the role is a fully onsite position in Lehi, UT.
But we need to preserve the exact wording? Not required to quote exactly, but preserve all substantive information. We can paraphrase but must not lose detail. Safer to keep close to original. Let's copy sentences: "TEKsystems is looking for a technical support representative for one of your clients. You will be troubleshooting a proprietary software via phone calls and chat. You must be able to type at least 60 WPM and work 100% remote. We are looking for people with at least 1 years of experience doing technical support of any kind. This is a great opportunity with a local software company. Job Type & Location This is a Contract position based out of Lehi, UT. Workplace Type This is a fully onsite position in Lehi,UT." We can keep that as a paragraph. But we need to split into sections; we already placed typing and remote in Requirements, experience in Requirements. So About the role can exclude those to avoid duplication. However we must preserve all info; if we remove them from About the role, they are still present in Requirements, so overall preserved. That's fine. Thus About the role: "TEKsystems is looking for a technical support representative for one of your clients. You will be troubleshooting a proprietary software via phone calls and chat. This is a great opportunity with a local software company. Job Type & Location This is a Contract position based out of Lehi, UT. Workplace Type This is a fully onsite position in Lehi,UT." Now Responsibilities: "Troubleshooting a proprietary software via phone calls and chat." Requirements: list: "At least 1 year of experience doing technical support of any kind", "Ability to type at least 60 WPM", "Ability to work 100% remote". Qualifications: we may omit. Skills: list: "Technical support experience", "Troubleshooting proprietary software", "Phone and chat communication", "Typing proficiency (≥60 WPM)". But typing proficiency already in Requirements; duplication across sections maybe okay but could be considered duplicated lines. The instruction: remove duplicated lines. So we should avoid repeating same exact line. However "Typing proficiency (≥60 WPM)" is similar to "Ability to type at least 60 WPM". Not identical but same meaning. Might be considered duplication. Better to avoid Skills section if it just repeats. Could we have Skills with other skills not covered? Not given. So maybe omit Skills. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Check