IT Systems Engineer, Mobile Client Platform Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe Qualifications, Skills), Benefits, Pay, Schedule. Must include only sections with real specific content. The posting includes: About Anthropic (mission) but we should not repeat job title as heading. The "About The Role" is a section heading; we can use

About The Role

. Then responsibilities list. Then qualifications: "You may be a good fit if you ..." and "Strong candidates may also ..." and "Technical Skills". Those can be combined into Requirements/Qualifications/Skills. We need to decide sections: maybe "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay". The posting includes compensation range: Annual Salary $285,000—$325,000 USD. Also mentions benefits: "We offer competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, and a lovely office space". Also "Visa sponsorship: We do sponsor visas!". 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 info. So we can have Benefits section with those details. Pay section with salary range. Schedule section with hybrid policy. Also maybe "About the role" includes description. We'll output sections: About the role (maybe not needed? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include About the role heading. Then Responsibilities. Then Qualifications (or Requirements). Then Skills. Then Benefits. Then Pay. Then Schedule. Ensure we only include sections with real content. All have content. We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate like EEO, scam warning, etc. Also remove navigation, cookie, legal. Also remove "How We're Different", "Guidance on Candidates' AI Usage", "Come work with us!" maybe those are not required sections; but they contain substantive info about culture; but not fitting into defined sections; we could omit as they are not requested sections. The instruction: "Prefer a few substantive sections over many thin ones." But we must include sections only when posting has real specific content for it. The sections we have are defined; we can include them if content exists. The "How We're Different" etc could be omitted as not part of requested headings. It's okay. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, qualifications, skills, benefits, pay, schedule. Must not lose any detail. Let's extract: About the role paragraph: "The Endpoint team (Client Platform Engineering) manages the laptops and handsets every Anthropic employee works on, plus the infrastructure underneath them. We treat the fleet as a distributed platform, not a collection of devices, and every piece of configuration ships as code through pull requests, CI, staging, and a canary group. Today the mobile side of the fleet is BYOD. This role exists to change that. You will design and implement a corporate-issued mobile device program (managed company phones and managed Apple accounts) in every region Anthropic operates in, and take it from early design to production. The team is deliberately lean and runs with high autonomy. You’ll define what a corporate mobile program looks like at Anthropic and own the platform decisions that get it there." That's the About the role content. Responsibilities list: bullet points (each line starting with a verb). We need to put them in

• . Let's list them: - Design the corporate-issued mobile device program: device standards, what we issue to whom, and how the program grows from a first region to everywhere Anthropic operates - Own the global logistics of issuing hardware: procurement partners, regional coverage, spares, and refresh cycles - Bring mobile configuration into the team’s config-as-code pipeline so mobile policies are reviewed, tested, and progressively rolled out like the rest of the fleet - Build zero-touch enrollment: Apple Business Manager and ADE with managed Apple accounts on iOS, the zero-touch equivalent on Android, so a new phone works the first time without hands-on setup - Own policy, compliance, and device lifecycle for the corporate fleet, from issue to wipe - Build telemetry on the corporate fleet: which devices are checking in, OS and patch state, drift between reported and actual state - Own managed app distribution for mobile, from app approval through update rollout - Partner with Corporate Security on device posture, device trust signals, and travel devices for international trips - Decide how corporate-issued and BYOD coexist, and own that boundary as the program rolls out That's all. Qualifications/Requirements: "You may be a good fit if you" bullet list: - Have owned a global or multi-region mobile device program end to end, with 8+ years managing corporate fleets at thousands-of-devices scale - Go deep on iOS device management: enrollment flows, Apple Business Manager and ADE, APNs and certificate lifecycle, declarative device management - Have worked with Android device management and can hold your own in a mixed fleet - Treat device configuration as code and have moved past clicking in consoles - Have run the infrastructure under an MDM, not just administered a SaaS console: a self-hosted MDM server, AWS, Terraform, and configuration that ships as code - Have built or launched a corporate device program, not just operated one, and can decide how it coexists with BYOD - Excel at ambiguous problems that touch several teams at once - Communicate technical concepts clearly to any audience - View IT Engineering as requiring product engineering rigor - Write clear documentation as a natural part of your workflow Strong candidates may also: - Have managed ChromeOS devices alongside a mobile fleet - Have run a device program across multiple regions and dealt with the logistics that come with it - Have built automated, progressive rollout systems with promotion gated on telemetry - Bring proficiency in Swift for building device tooling - Have used LLMs to automate operational work, or are excited to make Claude a teammate Technical Skills: - Python and shell scripting - iOS and Android platform internals (depth on iOS, working knowledge of Android) - Modern MDM or UEM platforms (Jamf, Intune, Workspace ONE, or equivalent) - Running the infrastructure under an MDM (self-hosted servers, AWS GCP, Terraform) - Querying live device state at fleet scale - Mobile device lifecycle automation (enrollment, policy, patching, app distribution) - GitOps and CI for configuration management - Endpoint security fundamentals We could combine Qualifications and Skills into sections: maybe "Qualifications" for the "You may be a good fit if you" and "Strong candidates may also". Then "Skills" for Technical Skills. Benefits: from "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 "Visa sponsorship: We do sponsor visas! However, we aren't able to successfully sponsor visas for every role and every candidate. But if we make you an offer, we will make every reasonable effort to get you a visa, and we retain an immigration lawyer to help with this." Also maybe "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." That's schedule but could be benefits? We'll put schedule separate. Pay: "Annual Salary $285,000—$325,000 USD". Also note about deadline: None. Applications will be received on a rolling basis. That's not pay but maybe we could include in a short paragraph but not required section. The instruction: do not include filler like "Deadline to apply: None." That's minor metadata; we could fold into a short p or drop. Probably drop. Schedule: "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 also have "Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience", "Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience", "Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position". Those are qualifications but maybe we can include in Qualifications section as bullet points. They are specific. We should include them. Also "Visa sponsorship" is benefit. Now we need to output HTML fragment only, no markdown fences. We'll structure:

  About the role

  ... paragraph ...

  Responsibilities

  • ... each ...

  Qualifications

  • ... from "You may be a good fit if you" ...
  • ... from "Strong candidates may also" ...
  • Minimum education: Bachelor’s degree or an equivalent combination of education, training, and/or experience
  • Required field of study: A field relevant to the role as demonstrated through coursework, training, or professional experience
  • Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position

  Skills

  • ... technical skills list ...

  Benefits

  • Competitive compensation and benefits
  • Optional equity donation matching
  • Generous vacation and parental leave
  • Flexible working hours
  • Lovely office space for collaboration
  • Visa sponsorship (reasonable effort to obtain visa, immigration lawyer retained)

  Pay

  Annual Salary $285,000—$325,000 USD

  Schedule

  Location-based hybrid policy: Expected to be in one of our offices at least 25% of the time; some roles may require more office time.

  We must ensure we preserve all substantive information. Let's verify we didn't lose any details. From About the role: we captured all. Responsibilities: captured all bullet points. Qualifications: we captured the "You may be a good fit if you" bullets (10 items). Also "Strong candidates may also" (5 items). Also minimum education, field of study, min years experience. Skills: captured all 8 items. Benefits: we captured competitive compensation and benefits, optional equity donation matching, generous vacation and parental leave, flexible working hours, lovely office space, visa sponsorship details. Did we miss anything else? The posting also mentions "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." That's covered. Also "We think AI systems like the ones we're building have enormous social and ethical implications." That's not a benefit; it's mission statement maybe not needed. Also "Your safety matters to us." That's scam warning; we drop. Also "We encourage you to apply even if you do not believe you meet every single qualification." That's encouragement; could be considered boilerplate; we can drop as not specific benefit. Also "We think AI systems like the ones we're building have enormous social and ethical implications. We think this makes representation even more important, and we strive to include a range of diverse perspectives on our team." That's EEO/diversity; we drop as boilerplate. Also "Research shows that people who identify as being from underrepresented groups are more prone to experiencing imposter syndrome..." drop. Also "We