IT Support Engineer, Application Administrator

for section headings. We could have

Responsibilities

with
• items each being a duty. Might be many; we can break into multiple
  maybe but okay. - Requirements/Qualifications/Skills: The "You may be a good fit if you" list and "Strong candidates may also". That's qualifications/skills. So we can have

  Requirements

  (or Qualifications). Use
  • . - Benefits: The posting mentions "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space". Also earlier: "Anthropic is a public benefit corporation...". So we have benefits: competitive compensation, optional equity donation matching, generous vacation and parental leave, flexible working hours, lovely office space. Also maybe remote role? Location: remote role with travel required. That's more about schedule/location. Pay: Annual Salary $230,000—$265,000 USD. So we have Pay section. - Schedule: Not explicitly given besides location: remote role, travel to SF office required, occasional travel to other offices. Also "Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time." That's schedule/hybrid expectation. So we can include Schedule section with that info. We must not include sections with filler like "commensurate with experience". Not present. We must not repeat job title as heading. Not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO etc. The posting includes a lot of boilerplate at end about safety, scams, etc. We must remove those. Also remove "How We're Different", "Guidance on Candidates' AI Usage", etc. Those are not required sections; we can drop them as they are not part of required headings (they are not Benefits, Pay, Schedule, etc). However we need to preserve ALL substantive information; but those sections are not required headings; they are extra info about company culture, research, etc. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." But also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "How We're Different" etc might be considered boilerplate? Not exactly legal/EEO, but it's more about company culture. The instruction says to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company culture paragraphs. However earlier: "Prefer a few substantive sections over many thin ones." And we should only include sections when posting has real specific content for it — never emit a heading followed by filler/placeholder text. The "How We're Different" etc is substantive but not fitting into our defined headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Could we incorporate some of that into About the role? Possibly but it's about the company mission, research directions. The posting already had an "About Anthropic" section at start describing mission. That could be considered part of About the role? But we already have About The Role heading. The "About Anthropic" is separate; we could treat that as part of About the role? The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can use those headings; we could also have an "About the company" heading? Not listed. Probably we should stick to the allowed headings. The "About Anthropic" could be considered part of About the role? Might be okay to include as a paragraph under About the role? But the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings not listed, but the examples are given. Safer to only use those headings. So we will omit the "About Anthropic" paragraph? But that would lose substantive info about mission. However the "About The Role" already includes some description of team. The mission might be considered boilerplate? It's about the company mission; maybe it's okay to drop as it's not directly about the role. The instruction says preserve ALL substantive information; but also we must not invent or summarize away detail. Dropping the mission might be summarizing away detail. However the mission is not specific to the role; it's generic company info. Might be considered boilerplate? Not sure. Given the typical tasks, they likely expect to keep the "About Anthropic" as part of "About the role" maybe as a paragraph. But the heading "About the role" is already used for the role description. Could we have two

    sections: "About the role" and "About the company"? Not in list but maybe allowed. However they said "e.g." meaning examples, not exhaustive. So we could add other headings if needed. But they said "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for those sections; other headings maybe not needed. I'd include "About the role" covering both the role description and maybe a brief about company mission? Could incorporate mission into that paragraph. Let's extract substantive content for each section: About the role: The paragraph under "About The Role": "The IT Operations team keeps Anthropic running. We make sure every employee can do their best work without friction. We're hiring IT Operations Engineers to own SaaS Operations, the service-operator layer for Anthropic's SaaS catalog: app administration, license and seat operations, renewals, audit evidence, app health and update coordination, Google Groups, and Google Calendar resources. You'll be a directly responsible individual for the SaaS Admin lane, owning its intake, execution, and runbook end to end, and you'll partner with IT Eng often: they own platform-level configuration, SSO/SCIM, integrations, and new-app intake, and you'll operate inside systems as they're configured, bringing platform-level work to them." That's good. Responsibilities: list items: - SaaS Administration - Perform admin actions inside configured apps: role grants, settings changes the app already supports, and user troubleshooting at admin level, across the catalog's heaviest apps such as Gong, 1Password, MongoDB, and Vanta - Own intake and execution for tickets escalated from the Support queue into the SaaS lane, and write the runbook as you go - Identify repetitive work across the lane and automate it: license workflows, seat reporting, evidence pulls, and anything the queue keeps handing you - Build automations with the tools at hand (scripts, app-native workflows, AI tools) and partner with IT Engineering when an automation needs platform-level access - Monitor application health, usage, and performance at the app level, and route platform or infrastructure issues to IT Engineering - Coordinate vendor-driven app updates and feature rollouts: track release notes, schedule changes inside the apps, and communicate user-facing impacts - Assign and reclaim licenses across the catalog - Produce seat utilization reporting and run the monthly utilization review - Renewals & Vendor Operations - Own the renewal calendar and prepare true-ups - Act as the day-to-day contact for vendor customer success managers (contract negotiation and spend approval stay with Procurement and Finance) - Audit & Compliance Operations - Pull SOC2 evidence, support access-review execution, and package audit responses on the audit calendar (audit scope and policy stay with Security and Compliance) - Google Workspace - Administer Google Calendar resources: rooms, equipment, and resource hygiene - Administer Google Groups: membership and access changes, troubleshooting, and keeping a heavily nested group structure understandable and clean - Slack Support - Slack app installs in partnership with CorpSec for scope review - Workspace compartmentalization through Grid Auditing and rotating Slack apps credentials in partnership with developers We could flatten all into a single

    with each bullet as
    • . That would be long but okay. Requirements/Skills: from "You may be a good fit if you" list: - Have 6+ years of hands-on experience administering a portfolio of SaaS applications at the admin level, ideally in a fast-paced or high-growth environment - Have owned license and seat management: assignment, reclamation, and utilization reporting - Have supported renewals or true-ups and worked directly with vendor account or CSM contacts - Have pulled audit evidence or executed access reviews (SOC2 or a similar framework) - Are an excellent communicator who genuinely enjoys helping people solve problems - Write things down: runbooks, how-to guides, and knowledge base articles - Are organized enough to run calendar-driven work (renewals, audits, access reviews) alongside a ticket queue without things falling through the cracks - Recognize when a request crosses from operating a system into changing it, and route platform-level work to the owning team - Take ownership of problems and follow through until they're resolved - Look for manual work that repeats and automate it Strong candidates may also: - Have basic scripting experience (Bash or Python) for automating license or reporting tasks - Have Google Workspace administration experience, especially with Google Groups - Have worked a full SOC2 or similar audit cycle on the evidence side - Have experience with a SaaS management or license management platform - Have experience using AI tools to improve personal or team productivity We can combine into one list under Requirements. Benefits: from later: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space in which to collaborate with colleagues." Also maybe "Anthropic is a public benefit corporation headquartered in San Francisco." That's more about company. We'll list benefits: competitive compensation, optional equity donation matching, generous vacation and parental leave, flexible working hours, lovely office space. Pay: Annual Salary $230,000—$265,000 USD. Schedule/Location: "This is a remote role. Travel to our San Francisco office is required, along with occasional travel to other Anthropic offices." Also "Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices." We can combine into Schedule section: remote role, required travel to SF office, occasional travel to other offices, expected office presence at least 25% of time. We must not include boilerplate like "Deadline to apply: None. Applications will be received on a rolling basis." That's application instructions; remove. Also remove "Logistics Minimum education: Bachelor’s degree..." That's actually a qualification (education). Should we include under Requirements? Yes, it's a requirement. So we need to incorporate education requirements: Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience. Required field of study