Information Technology Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. The posting doesn't have explicit "Responsibilities" but "What You'll Own" is responsibilities. "What We're Looking For" could be Skills/Qualifications. Required Qualifications and Preferred Qualifications can be under Requirements or Qualifications. Benefits and Pay: Compensation & Benefits includes base salary and benefits. So we need sections: About the role? Could be "About the role" summarizing The Opportunity. But we must not repeat job title as heading. We can use "About the role" heading and put the opportunity description. Then "Responsibilities" for What You'll Own. Then "Requirements" for Required Qualifications. Then "Skills" maybe for What We're Looking For? Or combine. Then "Benefits" and "Pay" maybe separate? They said include a section ONLY when posting has real specific content. Compensation & Benefits includes base salary range and benefits list. So we can have "Pay" with salary range, and "Benefits" with list. Or combine into one "Compensation & Benefits" but they only listed example headings; we can still use Benefits and Pay. We'll include both if content exists. We must not include boilerplate like EEO, etc. Remove that. We must not include duplicated lines. We must preserve all substantive information. We need to output only HTML fragment, no html/body tags, no markdown fences. Let's extract content: About Clinically AI: description of company. Could be placed under "About the role"? Actually "About the role" should describe the role, not company. But we could put company description under "About the role" maybe not ideal. However rules: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't forbid other headings? They said use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings. So we should map content to those headings. "About the role" could include the opportunity description and maybe company context. We'll include the opportunity paragraph. Responsibilities: "What You'll Own" list. Requirements: Could be "Required Qualifications". We'll put that under Requirements. Skills: Could be "What We're Looking For" (skills/competencies). We'll put under Skills. Benefits: list from Compensation & Benefits: healthcare coverage (medical, dental, vision), unlimited PTO, 401(k) with company match plus Roth option. Pay: Base salary: $85,000-$120,000 + equity. Also note actual compensation depends on experience. We should not include "equity" maybe as part of pay. We should not include "Actual compensation will depend on experience, scope, and overall alignment with the role." That's substantive; include in Pay section maybe as a note. We should not include Preferred Qualifications? Could be under Requirements or Skills as additional. But we have to preserve all substantive information. We could include Preferred Qualifications under Requirements as a sub-list or under Skills. Since we have Requirements and Skills sections, we could put Required Qualifications under Requirements, and Preferred Qualifications under Skills (or maybe under Requirements as well). But we need to not invent headings; we can put Preferred Qualifications under Skills as additional skills. Or we could add another section "Qualifications" but they said we can use Qualifications as heading. Actually they listed Qualifications as an example heading. So we could have a Qualifications section that includes both required and preferred. But they also have Requirements and Skills. To avoid duplication, we could use Requirements for required, Skills for preferred, and maybe Qualifications not needed. But we need to preserve preferred qualifications info. Let's put them under Skills as well (since they are skills/experience). Or we could have a separate "Qualifications" section with both required and preferred. But they said prefer a few substantive sections over many thin ones. So maybe combine required and preferred into Requirements? But then we lose distinction. However we can still include both under Requirements with subheadings? But we cannot add extra headings beyond h3? We could use
to note "Preferred qualifications:" inside Requirements. That's okay. Simplify: Use sections: About the role, Responsibilities, Requirements, Benefits, Pay. Under Requirements, we list required qualifications and also mention preferred qualifications as a note. Under Benefits, list benefits. Under Pay, list salary and equity note. Let's extract details: About the role: The Opportunity paragraph: "We are seeking an IT Manager to own the day-to-day operation of our workforce technology and systems, keeping our employees securely provisioned, our devices compliant, and our IT infrastructure running smoothly as we scale at high velocity. This is a critical role for someone who can manage our Google Workspace environment, administer our device management (MDM) program, and own the full employee technology lifecycle — from onboarding to offboarding. You will work closely with engineering, security/compliance, and executive leadership to keep the company's systems secure, accessible, and audit-ready as we grow. This is not a purely administrative, ticket-routing role. You should be comfortable owning issues from detection to resolution, operating with high rigor, and driving problems to closure yourself rather than just flagging them, in a fast-moving startup environment.We believe a successful IT function is defined not by simply keeping the lights on, but by proactive systems hygiene, strong access controls, and a seamless technology experience for every employee." We could also include company description from About Clinically AI, but maybe not needed. However we must preserve ALL substantive information. The About Clinically AI paragraph is substantive about company. Should we include it? It's not under any of the headings but we could include it under About the role as well. The instructions: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid adding other content under those headings. So we can put company description under About the role as well. That would preserve it. Thus About the role will contain both company description and opportunity. Now Responsibilities: list from What You'll Own: - Administer Google Workspace, including user lifecycle management (onboarding/offboarding), group and access management, security settings, 2FA/SSO enforcement, and audit log reviews. - Manage our MDM to ensure all endpoints are enrolled, encrypted, patched, and compliant with policy — remediating device-level issues directly. - Run periodic access reviews across SaaS applications, ensuring least-privilege access and timely de-provisioning. - Own new-hire IT provisioning and departure de-provisioning — accounts, devices, and application access. - Manage vendor security reviews, DPAs/BAAs, and due diligence for new third-party tools. - Maintain documentation for IT systems, access policies, and provisioning procedures, ensuring they reflect actual practice. - Partner with security/compliance on remediation for identity and access-related control gaps. - Support employees with day-to-day IT needs and troubleshooting as the team scales. We need to put each as
- .
Now Requirements: Required Qualifications list:
- 3+ years of experience in IT administration, systems administration, or a similar role.
- Experience administering Google Workspace in a business environment (user lifecycle, security settings, access controls).
- Experience managing an MDM solution (e.g., Kandji, Jamf, Mosyle, or similar) for endpoint compliance.
- Experience with identity and access tooling (SSO/SAML, Google Cloud Identity, Okta, or similar).
- Strong organizational and follow-through skills — comfortable owning issues from detection to closure.
- Ability to write, maintain, and operationalize IT systems documentation and procedures.
Preferred Qualifications (we can include as a note):
- Experience in healthcare, healthtech, or another regulated data environment.
- Experience supporting enterprise customer security reviews or vendor due diligence processes.
- Working knowledge of cloud environments (GCP preferred).
- Experience partnering with a security/compliance function on shared control ownership.
- Certifications such as CompTIA A+/Network+/Security+, Google Workspace Administrator, or equivalent practical experience.
We'll include them maybe as a sub-list under a note "Preferred qualifications:" inside Requirements.
Now Benefits: list:
- healthcare coverage (medical, dental, vision)
- unlimited PTO
- 401(k) with company match plus Roth option
Also maybe "competitive compensation, equity participation" but that's more pay.
Now Pay:
- Base salary: $85,000-$120,000 + equity
- Actual compensation will depend on experience, scope, and overall alignment with the role.
We'll put that.
Now ensure we don't include boilerplate: EEO, etc.
Now output HTML fragment:
- Administer Google Workspace, including user lifecycle management (onboarding/offboarding), group and access management, security settings, 2FA/SSO enforcement, and audit log reviews.
- Manage our MDM to ensure all endpoints are enrolled, encrypted, patched, and compliant with policy — remediating device-level issues directly.
- Run periodic access reviews across SaaS applications, ensuring least-privilege access and timely de-provisioning.
- Own new-hire IT provisioning and departure de-provisioning — accounts, devices, and application access.
- Manage vendor security reviews, DPAs/BAAs, and due diligence for new third-party tools.
- Maintain documentation for IT systems, access policies, and provisioning procedures, ensuring they reflect actual practice.
- Partner with security/compliance on remediation for identity and access-related control gaps.
- Support employees with day-to-day IT needs and troubleshooting as the team scales.
- 3+ years of experience in IT administration, systems administration, or a similar role.
- Experience administering Google Workspace in
About the role
Clinically AI is a rapidly scaling healthcare AI company transforming how behavioral health and healthcare organizations manage clinical documentation, compliance workflows, chart auditing, and operational efficiency through artificial intelligence. Our platform helps clinicians, compliance teams, administrators, and healthcare organizations reduce administrative burden, improve documentation quality, strengthen audit readiness, and operate more efficiently. We operate at the intersection of AI, healthcare operations, workflow design, and real-world clinical execution, where adoption, trust, usability, and measurable outcomes matter.
We are seeking an IT Manager to own the day-to-day operation of our workforce technology and systems, keeping our employees securely provisioned, our devices compliant, and our IT infrastructure running smoothly as we scale at high velocity. This is a critical role for someone who can manage our Google Workspace environment, administer our device management (MDM) program, and own the full employee technology lifecycle — from onboarding to offboarding. You will work closely with engineering, security/compliance, and executive leadership to keep the company's systems secure, accessible, and audit-ready as we grow. This is not a purely administrative, ticket-routing role. You should be comfortable owning issues from detection to resolution, operating with high rigor, and driving problems to closure yourself rather than just flagging them, in a fast-moving startup environment. We believe a successful IT function is defined not by simply keeping the lights on, but by proactive systems hygiene, strong access controls, and a seamless technology experience for every employee.