Tier 1 Helpdesk Support Technician @ MSP
qnectU IT Services Utah · Sandy, UT · 1 mo ago
On-siteInformation Technology$18–$24/hrFull-time
We need to output 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 need to parse the posting.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we should drop "Ready to Join Our Team? Click the APPLY button..." and "Equal Opportunity Employer..." etc.
We need to preserve all substantive information.
Let's extract sections:
- About the role: The initial paragraph describing role: "You Don’t Need to Know Everything About IT Yet. You do need to be the kind of person who wants to. qnectU is looking for an in-office Tier 1 Support Technician who likes people, likes solving problems, and is genuinely curious about how technology works." Then bullet list of qualities: Friendly and comfortable talking to people, Curious enough to dig into a problem..., Able to explain things..., Organized enough..., Humble enough..., Motivated enough..., Excited about developing a real career in IT.
That could be "About the role" or maybe "Qualifications"? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections we have content for.
We have:
- About the role: description of role and what they look for (personality traits). Could be "About the role".
- Responsibilities: list under "What You’ll Actually Be Doing" and "What You’ll Be Responsible For:" (the bullet list). So we can combine.
- Requirements/Qualifications/Skills: The posting has "What We’re Looking For" bullet list of traits and also technical experience helpful but not required. Could be under "Qualifications" or "Skills". We need to decide. Since they ask for sections only when posting has real specific content. We have content for both "Qualifications" (maybe technical experience helpful) and "Skills" (people skills, curiosity). Could combine into one "Qualifications" section.
- Benefits: "Compensation & Benefits:" includes pay range, medical/dental insurance, holiday pay & PTO, hours, location, driver's license requirement. So we have Benefits and Pay and Schedule maybe.
Pay: "$18-24 per hour, depending on experience, certifications, and what you bring to the role."
Schedule: "Hours: 8:00 am – 5:00 pm, Mon-Fri"
Benefits: "Medical/dental insurance· Holiday pay & PTO· This position works primarily from the qnectU headquarters in Sandy, UT.· Must have a valid driver's license and clean driving record."
We could separate Pay, Benefits, Schedule as separate headings if they have specific content. According to instruction: "Prefer a few substantive sections over many thin ones." But we need to include a section ONLY when posting has real specific content for it. We have content for Pay, Benefits, Schedule. Could combine Pay and Benefits into one "Compensation & Benefits" but headings list includes Benefits and Pay separate. We could make a Benefits section that includes medical/dental, holiday pay & PTO, location, driver's license. Pay section separate with pay range. Schedule section separate with hours.
We must not include placeholder text like "commensurate with experience" etc. We have actual numbers.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we should drop "Ready to Join Our Team? Click the APPLY button..." and "Equal Opportunity Employer..." etc.
We need to preserve all substantive information.
Let's extract sections:
- About the role: The initial paragraph describing role: "You Don’t Need to Know Everything About IT Yet. You do need to be the kind of person who wants to. qnectU is looking for an in-office Tier 1 Support Technician who likes people, likes solving problems, and is genuinely curious about how technology works." Then bullet list of qualities: Friendly and comfortable talking to people, Curious enough to dig into a problem..., Able to explain things..., Organized enough..., Humble enough..., Motivated enough..., Excited about developing a real career in IT.
That could be "About the role" or maybe "Qualifications"? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections we have content for.
We have:
- About the role: description of role and what they look for (personality traits). Could be "About the role".
- Responsibilities: list under "What You’ll Actually Be Doing" and "What You’ll Be Responsible For:" (the bullet list). So we can combine.
- Requirements/Qualifications/Skills: The posting has "What We’re Looking For" bullet list of traits and also technical experience helpful but not required. Could be under "Qualifications" or "Skills". We need to decide. Since they ask for sections only when posting has real specific content. We have content for both "Qualifications" (maybe technical experience helpful) and "Skills" (people skills, curiosity). Could combine into one "Qualifications" section.
- Benefits: "Compensation & Benefits:" includes pay range, medical/dental insurance, holiday pay & PTO, hours, location, driver's license requirement. So we have Benefits and Pay and Schedule maybe.
Pay: "$18-24 per hour, depending on experience, certifications, and what you bring to the role."
Schedule: "Hours: 8:00 am – 5:00 pm, Mon-Fri"
Benefits: "Medical/dental insurance· Holiday pay & PTO· This position works primarily from the qnectU headquarters in Sandy, UT.· Must have a valid driver's license and clean driving record."
We could separate Pay, Benefits, Schedule as separate headings if they have specific content. According to instruction: "Prefer a few substantive sections over many thin ones." But we need to include a section ONLY when posting has real specific content for it. We have content for Pay, Benefits, Schedule. Could combine Pay and Benefits into one "Compensation & Benefits" but headings list includes Benefits and Pay separate. We could make a Benefits section that includes medical/dental, holiday pay & PTO, location, driver's license. Pay section separate with pay range. Schedule section separate with hours.
We must not include placeholder text like "commensurate with experience" etc. We have actual numbers.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll produce something like:
About the role
...
Responsibilities
- ... ...
Qualifications
- ... ...
Pay
$18-24 per hour, depending on experience, certifications, and what you bring to the role.
Benefits
- Medical/dental insurance
- Holiday pay & PTO
- Position works primarily from the qnectU headquarters in Sandy, UT
- Must have a valid driver's license and clean driving record
Schedule
Hours: 8:00 am – 5:00 pm, Mon-Fri
We need to ensure we preserve all substantive information from the posting. Let's extract the exact text. About the role paragraph: "You Don’t Need to Know Everything About IT Yet. You do need to be the kind of person who wants to. qnectU is looking for an in-office Tier 1 Support Technician who likes people, likes solving problems, and is genuinely curious about how technology works. Maybe you have some IT experience. Maybe you’ve been the unofficial “computer person” everywhere you’ve worked. Maybe you’ve built your own PC, helped your family fix their Wi-Fi, or spent way too much time figuring out why something wasn’t working simply because you needed to know. That gets our attention." Then bullet list of qualities: "· Friendly and comfortable talking to people.· Curious enough to dig into a problem instead of immediately giving up.· Able to explain things without making someone feel dumb for asking.· Organized enough to keep track of what they are working on.· Humble enough to ask for help.· Motivated enough to actually learn from the answer.· Excited about developing a real career in IT." We need to preserve bullet points as- . The bullet list uses middle dot. We'll convert.
Now Responsibilities: There's "What You’ll Actually Be Doing" paragraph: "You’ll be one of the first people our clients interact with when technology decides not to cooperate.· A password stops working.· Outlook is doing something weird.· A printer has apparently chosen violence.· Someone can’t connect to the VPN.· A new employee needs their computer set up before Monday morning.· A workstation suddenly thinks Wi-Fi is optional."
Then paragraph: "You’ll work with users to understand what is happening, troubleshoot the issue, fix what you can, and make sure anything you cannot resolve gets to the right person with useful information. Some days you’ll spend most of your time helping people remotely from our office. Other days you may be preparing computers, configuring equipment, helping with hardware, or heading to a client location when something needs hands-on attention. You will see a lot of different technology, a lot of different businesses, and a lot of different IT problems. You will not be bored, but you definitely need to have people skills. Our clients might be frustrated, stressed, confused, busy, or convinced that their computer is out to get them. You need to be able to meet them where they are. That means:· Listening before jumping to conclusions.· Asking good questions.· Communicating clearly.· Staying patient when someone does not understand the technology.· Explaining what is happening in normal human language.· Keeping people updated.· Making sure they feel like somebody actually owns their problem."
Then paragraph: "You can be technically brilliant and still be terrible at IT support. We want someone who can become great at both. When you run into something unfamiliar, your first instinct should not be:“I don’t know. Someone else can handle it.”There is nothing wrong with escalating something you do not yet know how to solve. There is a problem if you encounter the same issue five times and never learn how it was fixed. That’s why you’ll work alongside more experienced technicians and learn from real problems—not just training videos. As you grow, we expect the problems you can solve independently to grow too."
Then "What You’ll Be Responsible For:" bullet list: "· Providing frontline technical support to client users.· Troubleshooting common hardware, software, Microsoft 365, connectivity, and workstation issues.· Working assigned service tickets from initial review through resolution or appropriate escalation.· Communicating with clients throughout the support process.· Maintaining accurate ticket notes and time entries.· Following qnectU technical standards, procedures, and documentation.· Reviewing existing documentation before performing unfamiliar procedures.· Updating or creating documentation when information is missing or outdated.· Escalating issues with useful troubleshooting information.· Reviewing escalated resolutions to improve your own technical knowledge.· Preparing and configuring workstations and other equipment.· Assisting with user onboarding and offboarding.· Supporting workstation replacements and equipment deployments.· Providing appropriate onsite support when required.· Maintaining accurate asset and configuration information.· Following security and identity-verification procedures.· Participating in training, coaching, and team meetings.· Continually developing your technical skills."
We need to include all that.
Now Qualifications/Skills: The "What We’re Looking For" bullet list: "· Genuinely enjoy helping people.· Communicate easily with different personalities.· Are naturally curious.· Like figuring out why something is not working.· Can stay calm when someone else is frustrated.· Take ownership instead of waiting for someone to chase you.· Pay attention to details.· Are comfortable admitting when you do not know something.· Actually remember what you were taught.· Take feedback well.· Enjoy learning.· Can work independently but also know when to involve the team.· Want to build your technical skills instead of staying comfortable forever.· Help friends and family fix their computers so often that they have basically turned you into unpaid tech support.· Spend your own time learning how technology works just because you find it interesting."
Also preceding paragraph: "Technical experience is helpful, but for this role we care just as much—if not more—about the person behind it. You’ll probably do well here if you:" then bullet list.
Also paragraph: "We care less about whether you learned something in a classroom, at a previous job, or at 1:00 AM because you refused to let a computer win. We care whether you are curious, capable of learning, and willing to put in the effort."
We could include that as part of Qualifications.
Now Pay: "$18-24 per hour, depending on experience, certifications, and what you bring to the role."
Benefits: "Medical/dental insurance· Holiday pay & PTO· Hours: 8:00 am – 5:00 pm, Mon-Fri· This position works primarily from the qnectU headquarters in Sandy, UT.· Must have a valid driver's license and clean driving record."
But we separated Hours into Schedule. So Benefits will have medical/dental insurance, holiday pay & PTO, location, driver's license.
Schedule: "Hours: 8:00 am – 5:00 pm, Mon-Fri"
Now we need to ensure we don't duplicate content. The Hours appears also in Benefits line but we moving to Schedule. We'll keep only in Schedule.
Now we need to output HTML.
We'll need to escape any special characters? Not needed.
We'll produce:
About the role
You Don’t Need to Know Everything About IT Yet. You do need to be the kind of person who wants to. qnectU is looking for an in-office Tier 1 Support Technician who likes people, likes solving problems, and is genuinely curious about how technology works. Maybe you have some IT experience. Maybe you’ve been the unofficial “computer person” everywhere you’ve worked. Maybe you’ve built your own PC, helped your family fix their Wi-Fi, or spent way too much time figuring out why something wasn’t working simply because you needed to know. That gets our attention.
- Friendly and comfortable talking to people.
- Curious enough to dig into a problem instead of immediately giving up.
- Able to explain things without making someone feel dumb for asking.
- Organized enough to keep track of what they are working on.
- Humble enough to ask for help.
- Motivated enough to actually learn from the answer.
- Excited about developing a real career in IT.
Res