Senior IT Systems Administrator
UserTesting · United States · 3 wk ago
RemoteRemoteInformation TechnologyFull-time
We need to output HTML fragment with sections using for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions, accommodations, etc? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove sections like "Application Process", "Accommodations", EEO statements, etc. Also remove "Job Description" maybe? It's a heading but not in list; we can treat as prose? Probably we can keep content but not as heading unless matches allowed headings. The allowed headings are those listed. So we need to map content to those sections.
We have content: Overview paragraph about UserTesting mission etc. That could be "About the role"? Actually "About the role" is a typical heading. The overview about company and mission could go there.
Then "Senior IT Systems Administrator - AI Overview" is like role title but we shouldn't repeat job title as heading. So we can skip that.
Then "We are seeking a highly skilled..." that's role description; could go under About the role.
Then "Key Responsibilities" with bullet list. That maps to Responsibilities.
Then "System Administration and Maintenance" also part of responsibilities; could be merged.
Then "Support & Collaboration" also responsibilities.
Then "Job Description" paragraph about IT team; could be part of About the role or Responsibilities? Probably About the role.
Then "Role Requirements" with bullet list; that maps to Requirements (maybe also Qualifications, Skills). The list includes: Able to work Monday through Friday in US Eastern or Central time zones. 5+ years experience... etc. Also certifications etc. We need to separate into Requirements, Qualifications, Skills? The instruction says use headings for those categories if content exists. We have to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = preferred? Skills = technical skills. But we can just put all under Requirements if we don't have clear distinction. However we should try to split if possible.
Let's parse Role Requirements bullet list:
- Able to work Monday through Friday in the US Eastern or Central time zones.
- 5+ years of experience with enterprise IT systems in a system administrator capacity.
- 5+ Experience with Okta Workflows, Google Workspace Administration, MDM platforms (Jamf / Intune)
- Hands-on experience with MCP server setup and management, AI agent deployment, AI feature configuration within enterprise SaaS tools.
- Familiarity with scripting & automation technologies in Python and/or Bash, with working knowledge of Git for version control and JSON/YAML for config and API work.
- Familiarity with API-based integrations — managing keys, scoping permissions, reading docs, and troubleshooting connectivity issues.
- Ability to work in a Kanban-style environment, managing due dates, new tasks, and tech debt effectively.
- Ability to train and mentor IT Support staff on ITSM practices as they apply to your role and function.
- Certifications in AI platforms are a plus (e.g., AWS, Google Cloud, Anthropic), but demonstrated hands-on experience is valued more highly, be prepared to explain this experience with real world examples.
- Ability to learn in a constantly shifting environment. We will do our best to manage processes, but the field of AI is new and growing. Change is unavoidable. Don’t meet every single requirement but excited about the role? We encourage you to apply. Research shows that some candidates are less likely to apply unless they meet 100% of the qualifications—but you may be exactly who we’re looking for. Diverse perspectives drive innovation, and we’re committed to building a team with a wide range of backgrounds, experiences, and skills.
The last part is more about encouragement and diversity; that's boilerplate EEO-ish; we should remove that as per instruction (remove EEO/equal-opportunity boilerplate). So we should cut that.
Thus we have requirements list.
We also have "Skills" maybe we can extract technical skills: MCP server setup, AI agent deployment, AI feature configuration, scripting Python/Bash, Git, JSON/YAML, API integrations, Okta Workflows, Google Workspace, MDM (Jamf/Intune), Kanban, training/mentoring.
We could put those under Skills.
Qualifications maybe include 5+ years experience, time zone availability, ability to learn, etc.
But we need to avoid filler like "commensurate with experience". Not present.
We need to include Pay, Schedule, Benefits only if posting states them. The posting does not mention pay, benefits, schedule. So we should NOT include those sections.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills (maybe). But we need to ensure we don't create thin sections. Could combine Qualifications and Requirements? But we have distinct content.
Let's decide:
- About the role: company mission overview and role summary (first paragraphs).
- Responsibilities: combine Key Responsibilities, System Administration and Maintenance, Support & Collaboration into bullet list.
- Requirements: mandatory items like time zone, 5+ years experience, experience with Okta etc, MCP, AI agent deployment, scripting, API integrations, Kanban, ability to train/mentor.
- Qualifications: maybe certifications plus? But we have "Certifications in AI platforms are a plus..." that's more preferred. Could put under Qualifications.
- Skills: technical skills list (maybe overlapping). Could also put under Skills.
But we need to avoid duplication. Let's extract distinct bullet points.
From Responsibilities bullets:
- Support the deployment and lifecycle management of AI solutions.
- Heavy importance on project/process management and communication skills for scoping calls, stakeholder meetings, and demo-style calls.
- Set up, configure, and maintain MCP (Model Context Protocol) servers that connect AI systems to internal tools and data sources, including scoping access, managing credentials, and troubleshooting integrations.
- Enable and manage AI features within existing SaaS platforms (e.g., Atlassian Rovo, Slack AI, Okta AI, ChatGPT, Google Gemini), working with vendors and internal stakeholders to configure, roll out, and govern usage.
- Provision and support AI agent infrastructure: service accounts, API key management, permissions scoping, rate limit monitoring, and access auditing for agents operating across internal systems.
- Maintain documentation for all AI integrations, including architecture diagrams, access maps, runbooks, and troubleshooting guides.
- Stay current on the AI tooling ecosystem and proactively identify tools or integrations that could benefit the IT team or the broader organization.
- Support the administration of UserTesting’s IT systems and SaaS toolset across the organization.
- Become a subject matter expert for AI-enabled platforms, integrations, and supporting infrastructure.
- Maintain assigned platforms through onboarding, offboarding, access management, feature rollouts, system cleanups, and lifecycle reviews.
- Identify, prioritize, and address technical debt across IT systems, workflows, and integrations.
- Partner with other IT System Administrators to improve reliability, automation, documentation, and supportability.
- Act as an escalation point for complex ITSM issues for the IT support team.
- Collaborate with cross-functional teams (Security, People Ops, Engineering, etc) to improve onboarding/offboarding, lifecycle processes, and AI tool adoption.
- Document procedures, system changes, and troubleshooting workflows.
That's a lot; we can keep as bullet list under Responsibilities.
Now Requirements bullet list (mandatory):
- Able to work Monday through Friday in the US Eastern or Central time zones.
- 5+ years of experience with enterprise IT systems in a system administrator capacity.
- 5+ Experience with Okta Workflows, Google Workspace Administration, MDM platforms (Jamf / Intune)
- Hands-on experience with MCP server setup and management, AI agent deployment, AI feature configuration within enterprise SaaS tools.
- Familiarity with scripting & automation technologies in Python and/or Bash, with working knowledge of Git for version control and JSON/YAML for config and API work.
- Familiarity with API-based integrations — managing keys, scoping permissions, reading docs, and troubleshooting connectivity issues.
- Ability to work in a Kanban-style environment, managing due dates, new tasks, and tech debt effectively.
- Ability to train and mentor IT Support staff on ITSM practices as they apply to your role and function.
That's 8 items.
Qualifications: maybe "Certifications in AI platforms are a plus (e.g., AWS, Google Cloud, Anthropic), but demonstrated hands-on experience is valued more highly, be prepared to explain this experience with real world examples." plus ability to learn in constantly shifting environment. Also maybe "Ability to learn in a constantly shifting environment." That could be qualification.
Thus Qualifications:
- Ability to learn in a constantly shifting environment.
- Certifications in AI platforms (e.g., AWS, Google Cloud, Anthropic) are a plus; hands-on experience valued.
We could combine.
Skills: maybe we can list specific technical skills: MCP server setup, AI agent deployment, AI feature configuration, scripting Python/Bash, Git, JSON/YAML, API integrations, Okta Workflows, Google Workspace, MDM (Jamf/Intune), Kanban, ITSM practices.
But that overlaps with Requirements. To avoid duplication, we could put Skills as a summary of technical proficiencies: MCP server setup, AI agent deployment, AI feature configuration, scripting (Python/Bash), Git, JSON/YAML, API integration, Okta Workflows, Google Workspace, MDM (Jamf/Intune), Kanban, ITSM.
But that may be repetitive. However instruction says preserve ALL substantive information; we can keep it in Requirements and not duplicate in Skills. If we create Skills section, we must not repeat same content verbatim? It didn't forbid duplication but said preserve ALL substantive information; we can include in multiple sections as long as we don't invent or summarize away detail. Duplication is okay if it's present in source? The source doesn't have a separate Skills section; it's embedded in Requirements. Creating a Skills section would be summarizing/inventing? It would be extracting from the same bullets; that's okay as it's not inventing new info, just reorganizing. But we risk creating thin sections. Better to not create Skills if we already have Requirements covering them. However we need to decide if we need Skills heading at all. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating Skills if it's thin. We could combine Requirements and Qualifications into one section? But we have distinct content.
Maybe we can have About the role, Responsibilities, Requirements (including qualifications and skills). That's three sections. That seems good.
Thus we will output:
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions, accommodations, etc? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove sections like "Application Process", "Accommodations", EEO statements, etc. Also remove "Job Description" maybe? It's a heading but not in list; we can treat as prose? Probably we can keep content but not as heading unless matches allowed headings. The allowed headings are those listed. So we need to map content to those sections.
We have content: Overview paragraph about UserTesting mission etc. That could be "About the role"? Actually "About the role" is a typical heading. The overview about company and mission could go there.
Then "Senior IT Systems Administrator - AI Overview" is like role title but we shouldn't repeat job title as heading. So we can skip that.
Then "We are seeking a highly skilled..." that's role description; could go under About the role.
Then "Key Responsibilities" with bullet list. That maps to Responsibilities.
Then "System Administration and Maintenance" also part of responsibilities; could be merged.
Then "Support & Collaboration" also responsibilities.
Then "Job Description" paragraph about IT team; could be part of About the role or Responsibilities? Probably About the role.
Then "Role Requirements" with bullet list; that maps to Requirements (maybe also Qualifications, Skills). The list includes: Able to work Monday through Friday in US Eastern or Central time zones. 5+ years experience... etc. Also certifications etc. We need to separate into Requirements, Qualifications, Skills? The instruction says use headings for those categories if content exists. We have to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = preferred? Skills = technical skills. But we can just put all under Requirements if we don't have clear distinction. However we should try to split if possible.
Let's parse Role Requirements bullet list:
- Able to work Monday through Friday in the US Eastern or Central time zones.
- 5+ years of experience with enterprise IT systems in a system administrator capacity.
- 5+ Experience with Okta Workflows, Google Workspace Administration, MDM platforms (Jamf / Intune)
- Hands-on experience with MCP server setup and management, AI agent deployment, AI feature configuration within enterprise SaaS tools.
- Familiarity with scripting & automation technologies in Python and/or Bash, with working knowledge of Git for version control and JSON/YAML for config and API work.
- Familiarity with API-based integrations — managing keys, scoping permissions, reading docs, and troubleshooting connectivity issues.
- Ability to work in a Kanban-style environment, managing due dates, new tasks, and tech debt effectively.
- Ability to train and mentor IT Support staff on ITSM practices as they apply to your role and function.
- Certifications in AI platforms are a plus (e.g., AWS, Google Cloud, Anthropic), but demonstrated hands-on experience is valued more highly, be prepared to explain this experience with real world examples.
- Ability to learn in a constantly shifting environment. We will do our best to manage processes, but the field of AI is new and growing. Change is unavoidable. Don’t meet every single requirement but excited about the role? We encourage you to apply. Research shows that some candidates are less likely to apply unless they meet 100% of the qualifications—but you may be exactly who we’re looking for. Diverse perspectives drive innovation, and we’re committed to building a team with a wide range of backgrounds, experiences, and skills.
The last part is more about encouragement and diversity; that's boilerplate EEO-ish; we should remove that as per instruction (remove EEO/equal-opportunity boilerplate). So we should cut that.
Thus we have requirements list.
We also have "Skills" maybe we can extract technical skills: MCP server setup, AI agent deployment, AI feature configuration, scripting Python/Bash, Git, JSON/YAML, API integrations, Okta Workflows, Google Workspace, MDM (Jamf/Intune), Kanban, training/mentoring.
We could put those under Skills.
Qualifications maybe include 5+ years experience, time zone availability, ability to learn, etc.
But we need to avoid filler like "commensurate with experience". Not present.
We need to include Pay, Schedule, Benefits only if posting states them. The posting does not mention pay, benefits, schedule. So we should NOT include those sections.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills (maybe). But we need to ensure we don't create thin sections. Could combine Qualifications and Requirements? But we have distinct content.
Let's decide:
- About the role: company mission overview and role summary (first paragraphs).
- Responsibilities: combine Key Responsibilities, System Administration and Maintenance, Support & Collaboration into bullet list.
- Requirements: mandatory items like time zone, 5+ years experience, experience with Okta etc, MCP, AI agent deployment, scripting, API integrations, Kanban, ability to train/mentor.
- Qualifications: maybe certifications plus? But we have "Certifications in AI platforms are a plus..." that's more preferred. Could put under Qualifications.
- Skills: technical skills list (maybe overlapping). Could also put under Skills.
But we need to avoid duplication. Let's extract distinct bullet points.
From Responsibilities bullets:
- Support the deployment and lifecycle management of AI solutions.
- Heavy importance on project/process management and communication skills for scoping calls, stakeholder meetings, and demo-style calls.
- Set up, configure, and maintain MCP (Model Context Protocol) servers that connect AI systems to internal tools and data sources, including scoping access, managing credentials, and troubleshooting integrations.
- Enable and manage AI features within existing SaaS platforms (e.g., Atlassian Rovo, Slack AI, Okta AI, ChatGPT, Google Gemini), working with vendors and internal stakeholders to configure, roll out, and govern usage.
- Provision and support AI agent infrastructure: service accounts, API key management, permissions scoping, rate limit monitoring, and access auditing for agents operating across internal systems.
- Maintain documentation for all AI integrations, including architecture diagrams, access maps, runbooks, and troubleshooting guides.
- Stay current on the AI tooling ecosystem and proactively identify tools or integrations that could benefit the IT team or the broader organization.
- Support the administration of UserTesting’s IT systems and SaaS toolset across the organization.
- Become a subject matter expert for AI-enabled platforms, integrations, and supporting infrastructure.
- Maintain assigned platforms through onboarding, offboarding, access management, feature rollouts, system cleanups, and lifecycle reviews.
- Identify, prioritize, and address technical debt across IT systems, workflows, and integrations.
- Partner with other IT System Administrators to improve reliability, automation, documentation, and supportability.
- Act as an escalation point for complex ITSM issues for the IT support team.
- Collaborate with cross-functional teams (Security, People Ops, Engineering, etc) to improve onboarding/offboarding, lifecycle processes, and AI tool adoption.
- Document procedures, system changes, and troubleshooting workflows.
That's a lot; we can keep as bullet list under Responsibilities.
Now Requirements bullet list (mandatory):
- Able to work Monday through Friday in the US Eastern or Central time zones.
- 5+ years of experience with enterprise IT systems in a system administrator capacity.
- 5+ Experience with Okta Workflows, Google Workspace Administration, MDM platforms (Jamf / Intune)
- Hands-on experience with MCP server setup and management, AI agent deployment, AI feature configuration within enterprise SaaS tools.
- Familiarity with scripting & automation technologies in Python and/or Bash, with working knowledge of Git for version control and JSON/YAML for config and API work.
- Familiarity with API-based integrations — managing keys, scoping permissions, reading docs, and troubleshooting connectivity issues.
- Ability to work in a Kanban-style environment, managing due dates, new tasks, and tech debt effectively.
- Ability to train and mentor IT Support staff on ITSM practices as they apply to your role and function.
That's 8 items.
Qualifications: maybe "Certifications in AI platforms are a plus (e.g., AWS, Google Cloud, Anthropic), but demonstrated hands-on experience is valued more highly, be prepared to explain this experience with real world examples." plus ability to learn in constantly shifting environment. Also maybe "Ability to learn in a constantly shifting environment." That could be qualification.
Thus Qualifications:
- Ability to learn in a constantly shifting environment.
- Certifications in AI platforms (e.g., AWS, Google Cloud, Anthropic) are a plus; hands-on experience valued.
We could combine.
Skills: maybe we can list specific technical skills: MCP server setup, AI agent deployment, AI feature configuration, scripting Python/Bash, Git, JSON/YAML, API integrations, Okta Workflows, Google Workspace, MDM (Jamf/Intune), Kanban, ITSM practices.
But that overlaps with Requirements. To avoid duplication, we could put Skills as a summary of technical proficiencies: MCP server setup, AI agent deployment, AI feature configuration, scripting (Python/Bash), Git, JSON/YAML, API integration, Okta Workflows, Google Workspace, MDM (Jamf/Intune), Kanban, ITSM.
But that may be repetitive. However instruction says preserve ALL substantive information; we can keep it in Requirements and not duplicate in Skills. If we create Skills section, we must not repeat same content verbatim? It didn't forbid duplication but said preserve ALL substantive information; we can include in multiple sections as long as we don't invent or summarize away detail. Duplication is okay if it's present in source? The source doesn't have a separate Skills section; it's embedded in Requirements. Creating a Skills section would be summarizing/inventing? It would be extracting from the same bullets; that's okay as it's not inventing new info, just reorganizing. But we risk creating thin sections. Better to not create Skills if we already have Requirements covering them. However we need to decide if we need Skills heading at all. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating Skills if it's thin. We could combine Requirements and Qualifications into one section? But we have distinct content.
Maybe we can have About the role, Responsibilities, Requirements (including qualifications and skills). That's three sections. That seems good.
Thus we will output:
About the role
... (company mission and role summary)
Responsibilities
- ... each bullet
Requirements
- ... each bullet