IT Specialist
About the role
. Then responsibilities list. Then qualifications: we have Required Qualifications and Additional Qualifications; we can combine into Requirements or Qualifications. UseRequirements
maybe. Benefits: they mention "Eligible to participate in HiveWatch Equity Incentive Plan" which is a benefit. Also maybe other benefits not listed. So we can include Benefits section with that. Pay: they have base salary range $120,000 - $140,000 USD per year. So include Pay. Schedule: not mentioned, so omit Schedule. Skills: not explicitly separate; maybe we can omit Skills if not distinct. Could include Skills under Requirements but not required. We must use- for any list of duties/requirements/benefits. For prose use
. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Us: Could be considered part of About the role? Might be separate but not required heading. Might be okay to include as a paragraph under About the role? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "Use
for section headings (e.g ...)". Likely they expect only those headings. So we should not include About Us heading; we could incorporate About Us into a paragraph under About the role or maybe as a separate
before the role heading? But they said "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." About Us is not minor metadata; it's substantive. But they didn't list About Us as a heading to use. Could we still include it as a
without heading? Probably yes. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot have other headings, but they gave examples. Safer to follow: only those headings. So we will not output About Us heading; we can include About Us content as a paragraph under About the role or maybe as a separate
before the role heading. But they said "Prefer a few substantive sections over many thin ones." So maybe combine About Us into About the role section as introductory paragraph. Thus structure:
About the role
[About Us text + About The Role text combined?] We need to preserve all substantive information. So we can include About Us paragraph then the About The Role paragraph. But we must not duplicate content. Let's combine: About Us: HiveWatch is a tech-forward, inclusive organization fostering the evolution of the physical security industry. We are a diverse team of forward thinkers who empower each other to find creative and collaborative solutions in an industry ripe for modernization. We are passionate about the problems we're solving for our customers and equally passionate about the company we're building. HiveWatch is here to help security teams pivot from chasing threats to preventing them. We protect organizations, people, and property through the intelligent orchestration of physical security programs. With better communication, more insights, and less "noise", we are modernizing what it means for businesses and their employees to truly feel safe. About The Role: As our IT Specialist, you will be the backbone of our employees' day-to-day technology experience, treating every person across the organization as a valued customer and holding yourself to a high standard of responsiveness and resolution. You'll own the full IT function end-to-end, from managing our systems and tools to ensuring every new hire has a seamless first day and every departure is handled securely and completely. This role is as much about service excellence as it is about technical skill - you'll be the first point of contact when something breaks, the person who sets up the new account before someone's first morning, and the one who makes sure nothing falls through the cracks when someone leaves. If you take pride in making technology invisible to the people who depend on it, this role is built for you. We can put both in
elements, maybe separate paragraphs. Then Responsibilities: list items. We need to capture all responsibilities bullet points. Let's extract responsibilities from "Key Responsibilities:" section. It has Core, hands-on (the majority of your time): then a list of items each starting with a dash? Actually they are sentences separated by line breaks. Let's list them: - Personally own the full support lifecycle as the sole IT resource — intake, triage, and hands-on resolution for all employee requests — escalating to vendors only where appropriate, while keeping stakeholders informed - Manage employee IT onboarding and offboarding — accounts, hardware, access provisioning and de-provisioning, identify efficiencies as it relates to the onboarding/offboarding process as HiveWatch scales - Own endpoint management end-to-end via MDM — provision and deploy laptops & workstations; manage device policy across the fleet; run hardware lifecycle from procurement to retirement - Administer and set policy for business productivity software (Google Workspace, Microsoft 365) — user lifecycle, access, configuration standards, and license governance - Own and run the corporate network hands-on — firewalls, switching, wireless, VPN, and DNS — including configuration, monitoring, segmentation, and capacity planning - Own internet connectivity and uptime — manage ISP relationships, circuits, and failover so the office and business-critical services stay online - Own engineering tooling provisioning and licensing governance (GitHub, SaaS access) - Ownership, periodic or shared: Balance reactive support with proactive improvements as the company scales - Manage the IT vendor and MSP ecosystem — selection, onboarding, SLAs, performance reviews, renewals, and escalations — holding partners accountable to outcomes - Oversee cloud IAM (AWS, GCP) for non-production access — provisioning standards, group management, and access reviews - Own documentation standards for configuration, process, and best practices - Own the HQ technology stack (conference rooms, presentation and phone systems, printers), coordinating vendors for installation and maintenance - Coordinate office build-outs, moves, and low-voltage/cabling projects through vendors We need to preserve all. Use
- for each. Then Required Qualifications and Additional Qualifications. We can combine into Requirements section. Let's extract Required Qualifications: - 5+ years in IT with demonstrated progression into ownership of corporate IT for a growing organization; direct experience managing IT vendors and/or MSP relationships - Hands-on experience working at a start-up (early to mid stages) - Strong hands-on experience administering Google Workspace (or Microsoft 365) and managing endpoints via MDM, including laptop/workstation provisioning and hardware lifecycle - Comfort operating as a team of one — self-directed, able to prioritize and personally resolve support requests - A strong technical foundation across endpoint management, IAM/SSO, networking, and cloud — deep enough to build and operate directly, and to set standards and hold vendors accountable - Proven track record managing SaaS licensing and vendor contracts, SLAs, and renewals - Experience with one or more IAM tools and strong understanding of SSO, provisioning, and application/group management - Strong MacOS background and experience overseeing Windows environments - Excellent communication and stakeholder management skills, with the ability to translate technical concepts for various audiences and negotiate with vendors - Strong organizational, written, and verbal skills Additional Qualifications: - SaaS experience - Experience supporting a GSOC or SOC environment - Experience managing office build-outs, moves, or low-voltage/cabling projects through vendors We can list all as
- under Requirements.
Benefits: "Eligible to participate in HiveWatch Equity Incentive Plan". That's a benefit. Possibly also other benefits not mentioned. We'll just include that.
Pay: "Base salary range for this position is $120,000 - $140,000 USD per year". We'll put in
. Schedule: none, omit. We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none. Now output HTML. We need to ensure we don't include any extra text outside HTML. Let's craft:
About the role
HiveWatch is a tech-forward, inclusive organization fostering the evolution of the physical security industry. We are a diverse team of forward thinkers who empower each other to find creative and collaborative solutions in an industry ripe for modernization. We are passionate about the problems we're solving for our customers and equally passionate about the company we're building. HiveWatch is here to help security teams pivot from chasing threats to preventing them. We protect organizations, people, and property through the intelligent orchestration of physical security programs. With better communication, more insights, and less "noise", we are modernizing what it means for businesses and their employees to truly feel safe.
As our IT Specialist, you will be the backbone of our employees' day-to-day technology experience, treating every person across the organization as a valued customer and holding yourself to a high standard of responsiveness and resolution. You'll own the full IT function end-to-end, from managing our systems and tools to ensuring every new hire has a seamless first day and every departure is handled securely and completely. This role is as much about service excellence as it is about technical skill - you'll be the first point of contact when something breaks, the person who sets up the new account before someone's first morning, and the one who makes sure nothing falls through the cracks when someone leaves. If you take pride in making technology invisible to the people who depend on it, this role is built for you.
Responsibilities
- Personally own the full support lifecycle as the sole IT resource — intake, triage, and hands-on resolution for all employee requests — escalating to vendors only where appropriate, while keeping stakeholders informed
- Manage employee IT onboarding and offboarding — accounts, hardware, access provisioning and de-provisioning, identify efficiencies as it relates to the onboarding/offboarding process as HiveWatch scales
- Own endpoint management end-to-end via MDM — provision and deploy laptops & workstations; manage device policy across the fleet; run hardware lifecycle from procurement to retirement
- Administer and set policy for business productivity software (Google Workspace, Microsoft 365) — user lifecycle, access, configuration standards, and license governance
- Own and run the corporate network hands-on — firewalls, switching, wireless, VPN, and DNS — including configuration, monitoring, segmentation, and capacity planning
- Own internet connectivity and uptime — manage ISP relationships, circuits, and failover so the office and business-critical services stay online
- Own engineering tooling provisioning and licensing governance (GitHub, SaaS access)
- Balance