IT Support Specialist
Waites · Cincinnati, OH · 3 wk ago
Information TechnologyFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description about company, role, responsibilities, requirements, qualifications, culture fit, why Waites (benefits?), but no explicit Pay or Schedule. So we should not include Pay or Schedule sections. Benefits? There's mention of "attractive base salary with a strong history of profit sharing" and "opportunities for professional advancement". That's benefits-ish but not explicit benefits like health insurance. Might be considered benefits? The instruction: include a section ONLY when posting has real, specific content for it. "Attractive base salary with a strong history of profit sharing" is specific enough for Benefits? Could be considered compensation/benefits. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state base salary and profit sharing, which is compensation/benefits. So we could include a Benefits section with that content. But we also have a "Why Waites?" paragraph that includes culture, growth, etc. That could be Benefits or maybe we could put under About the role? Actually About the role could be the initial description: "What we are: Fun, fast-paced...". That's about company culture. Could be About the role. Responsibilities: list of duties (support service desk, device management, onboarding/offboarding, account admin, workplace tech, security ops, applications license admin, continuous improvement). Requirements: list of qualifications (associate degree, 2-4 years experience, hands-on Windows/macOS, familiarity with Google Workspace/M365, networking, ticketing, endpoint security desired, communication, problem solving, judgment, familiarity with ISO-9001, GDPR, SOC II desired, certifications desired). Qualifications: maybe duplicate? The posting has "Requirements Qualifications & Requirements:" then bullet list. Could combine Requirements and Qualifications into one section? But we need to follow headings: we can have Requirements and Qualifications separate if content distinct. The posting lumps them together. Could split: Requirements: experience, education, technical skills. Qualifications: certifications desired? But they also list desired certifications under same bullet. Might be better to have a single "Requirements" section covering all. Then maybe "Skills" section for soft skills: communication, customer service, problem solving, judgment, humility, hungry, smart, innovative, etc. The posting includes "Culture Fit Requirements" with those traits. Could treat as Skills or Culture Fit. Since we don't have a Culture Fit heading, we could put those under Skills. Benefits: base salary + profit sharing + professional advancement. Also maybe mention "attractive base salary". We'll include Benefits.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. At end there is "WST is an Equal Opportunity Employer." Remove.
We need to preserve all substantive information. So we need to include all details from description.
Let's extract sections:
About the role: Could be the introductory paragraph: "What we are: Fun, fast-paced, client-focused, people-centric, inviting, flexible, and rapidly growing. What we are not: Overly structured, uncompromising, disengaged, or disconnected. We are looking for a resourceful, service-minded IT Support Specialist to be the first point of contact for technology support across Waites. This is a hands-on role for someone who can help resolve issues quickly, setting up new team members for success, and keeping the technology our business runs on reliable and secure. You will own the day-to-day support experience for the company, as well as being a key part of strategic projects within the IT organization. If you take pride in responsive service, like variety in your day, and want room to grow your technical skills across infrastructure, security, and modern business applications, we would love to meet you. The work we do is categorically awesome, and we are looking for someone with the curiosity, drive, ownership, and people skills to help keep it running."
That's about role and company.
Company Description: "We are a leading provider of wireless, mesh-networked, “Internet of Things” (IoT) sensors for industrial environments. Our cost effective, plug-and-play products empower plants of all sizes to conduct predictive and preventative maintenance on mission critical and secondary equipment in order to maximize uptime. (I.e. We help with things like getting your Prime packages to you faster!)"
That could be part of About the role or separate? Since we have only About the role heading, we can include both.
Responsibilities: bullet list from "The IT Support Specialist is the primary owner..." through each bullet.
Let's list responsibilities:
- Serve as the first point of contact for technology support requests across the company
- Own the support queue — triage, prioritize, resolve, and communicate status through to closure
- Troubleshoot hardware, software, connectivity, and peripheral issues for end users
- Build and maintain documentation, knowledge base articles, and self-service resources
- Foster a responsive, customer-first support experience
- Device & Asset Management:
- Provision, image, configure, and deploy laptops, desktops, and mobile devices
- Manage device lifecycle from intake through deployment, refresh, retirement, and secure disposal
- Maintain accurate IT asset inventory and records
- Ensure that our devices stay fully compliant with our SOC-2 security initiatives
- Onboarding & Offboarding:
- Execute new hire technology setup including accounts, hardware, access, and orientation to core tools
- Execute offboarding such as account deactivation, access revocation, and device recovery
- Follow established runbooks, document exceptions, and recommend improvements to the process
- Account & Access Administration:
- Administer user accounts and group membership across Google Workspace and business applications, within approved policy
- Process access requests through defined approval workflows
- Administer physical access and badge management for Waites facilities
- Escalate any request that falls outside established policy rather than granting exceptions
- Periodic reviews of our key systems to ensure there are no unintended access gaps
- Workplace & Site Technology:
- Support conference room technology, audio/visual equipment, printers, and shared workplace systems
- Provide first-line support for World HQ on-site network connectivity issues
- Coordinate with vendors and service providers for warranty and project work
- Security Operations Support:
- Monitor and triage endpoint security alerts, escalating in line with defined thresholds
- Verify patch and update compliance across company devices
- Support security awareness activities, including phishing simulation follow-up
- Assist in gathering evidence and documentation for ISO-9001, SOC II, and GDPR audit activity
- Applications & License Administration:
- Perform routine SaaS license administration, reconciliation, and usage reporting
- Support end users across core business applications
- Assist with rollout, enrollment, and first-line questions for approved AI tools
- Continuous Improvement:
- Identify recurring issues and recommend permanent fixes rather than repeat remediation
- Contribute to end-user training, documentation, and technology adoption
- Stay current with relevant tools and support practices
- Carry out additional responsibilities as needed to support business objectives
That's a lot; we can group under
- .
Requirements: bullet list from "Requirements Qualifications & Requirements:" includes:
- Associate’s degree in Computer Science, Information Technology, or related field, or equivalent practical experience
- 2–4 years of experience in technical support, service desk, or desktop support
- Hands-on experience supporting Windows and macOS devices in a business environment
- Familiarity with Google Workspace and/or Microsoft 365 administration
- Working knowledge of core networking concepts and the ability to troubleshoot connectivity issues
- Experience working within a ticketing system and meeting response expectations
- Experience with endpoint security tooling desired
- Excellent communication skills and a strong customer service orientation, including with non- technical colleagues
- Strong problem-solving skills and the ability to prioritize competing requests independently
- Sound judgment about when to resolve and when to escalate
- Familiarity with legal, statutory/regulatory requirements such as: ISO-9001, GDPR and SOC II desired
- CompTIA A+, Network+, or comparable certification desired
Qualifications: maybe same as requirements; but we could treat "Qualifications" as the certifications desired? However the posting lumps them. To avoid duplication, we could have only Requirements section and skip Qualifications. But instruction: use headings only when posting has real specific content. Since they have a heading "Qualifications & Requirements:" we could treat that as Requirements. We'll not create a separate Qualifications heading.
Skills: we can extract from "Culture Fit Requirements" and maybe other soft skills:
- High intellect and strong analytical skills
- Innovative and driven to constantly improve
- Ability to balance strategic vision with operational execution
- Non-bureaucratic, flexible, and able to thrive in a fast-moving environment
- Positive energy and attitude towards people and problem-solving
- Demonstrates a balance of humility, strong work ethic, and interpersonal savvy (“Humble, Hungry, and Smart”) in approach to teamwork and problem-solving
- “Can Do” mentality
Also communication, problem solving already listed; but we can still include.
Benefits: from "Why Waites?" paragraph: "At Waites, we offer an attractive base salary with a strong history of profit sharing. We are intensely customer-focused, with a culture that encourages hard work, fun, and mutual success. As we continue to grow, there will be many opportunities for professional advancement and development."
We can include that as Benefits.
We should not include Pay or Schedule.
Now produce HTML fragment with sections:
About the role
then... combined intro and company description maybe two paragraphs.
ThenResponsibilities
- ... each responsibility as separate li. For sub-bullets we can just include as part of li text; no nested ul needed but could. Simpler: each top-level bullet as li, with sub-points separated by semicolons or line breaks inside li? Probably okay to keep as single li with line breaks using
. But we can keep simple. We'll produce- Serve as the first point of contact for technology support requests across the company etc. For longer responsibilities with subpoints, we can embed
- inside but that's nested list; still okay. But to keep simple, we can just include all as separate li with description.
Let's list each responsibility as separate li, but we need to capture all points. Might be many li; okay.
We'll produce:
Responsibilities
- Serve as the first point of contact for technology support requests across the company
- Own the support queue — triage, prioritize, resolve, and communicate status through to closure
- Troubleshoot hardware, software, connectivity, and peripheral issues for end users
- Build and maintain documentation, knowledge base articles, and self-service resources
- Foster a responsive, customer-first support experience
- Device & Asset Management: Provision, image, configure, and deploy laptops, desktops, and mobile devices; manage device lifecycle from intake through deployment, refresh, retirement, and secure disposal; maintain accurate IT asset inventory and records; ensure devices stay fully compliant with SOC-2 security initiatives
- Onboarding & Offboarding: Execute new hire technology setup including accounts, hardware, access, and orientation to core tools; execute offboarding such as account deactivation, access revocation, and device recovery; follow established runbooks, document exceptions, and recommend improvements to the process
- Account & Access Administration: Administer user accounts and group membership across Google Workspace and business applications within approved policy; process access requests through defined approval workflows; administer physical access and badge management for Waites facilities; escalate requests outside policy; conduct periodic reviews of key systems to ensure no
- ... each responsibility as separate li. For sub-bullets we can just include as part of li text; no nested ul needed but could. Simpler: each top-level bullet as li, with sub-points separated by semicolons or line breaks inside li? Probably okay to keep as single li with line breaks using