How to apply for IT Systems Engineer, Client Platform Engineer, macOS

About Anthropic

Anthropic is a frontier AI research and product company whose stated mission is to create reliable, interpretable, and steerable AI systems. Teams work on alignment, policy, and security. It publishes specific high-impact opportunities rather than recommending all roles at the company, and it points candidates to reading about concerns of doing harm by working at a frontier AI lab.

About the role

This is an Endpoint team (Client Platform Engineering) role owning Anthropic's device fleet as a platform. You run the MDM as a production service, manage device configuration as code shipped through pull requests, CI, a staging environment, and a canary group, and handle patching, software pipelines, and telemetry across a mostly macOS fleet plus some Linux machines and a growing mobile footprint. The work also involves partnering with Security on hardening, compliance controls, and detection and response, and with developer and infrastructure teams so controls do not block their work.

A typical day

The posting does not describe a daily routine, so ask the team how work is split between building the MDM platform, shipping configuration changes through pull requests and CI, and responding to patching, software, and telemetry needs. Ask how much time goes to Security work on hardening, compliance controls, and detection and response, and how much to automation that cuts manual operational work.

Who Anthropic is looking for

• Has run an MDM as a production service, not just used one, and can speak to the infrastructure underneath it as well as the configuration on top.
• Treats device configuration as code: policies, configuration profiles, queries, remediation scripts, and software all shipped via pull requests, CI, staging, and canary before reaching the fleet.
• Has built and maintained patching and software pipelines that keep a large fleet of mostly macOS devices patched and secure, with telemetry that shows what is actually true on each device.
• Can work across Security (hardening, compliance controls, detection and response) and developer and infrastructure teams, and can build automation that reduces manual operational work.

Tips for this application

• Lead with concrete examples of running an MDM as a production service: what you ran, how many devices, and what you owned end to end.
• Show configuration-as-code practice in detail: the pull request, CI, staging, and canary workflow you used, and what you shipped through it (profiles, queries, remediation scripts, software).
• Give numbers on fleet scale and mix: how many macOS devices, any Linux machines, and any mobile footprint you supported.
• Describe patching and software pipelines you built, and the telemetry you used to verify device state and base access decisions on device trust.
• Name the Security and developer or infrastructure teams you worked with and how you kept controls from getting in the way of their work.

What to cover in your cover letter

Ownership of the MDM platform end to end, including the infrastructure underneath and the configuration on top. Experience shipping all device configuration through pull requests, CI, a staging environment, and a canary group. Patching, software pipelines, and telemetry across a large, mostly macOS fleet with some Linux and mobile. Collaboration with Security on hardening, compliance controls, and detection and response, plus working with developer and infrastructure teams so controls do not block them.

Research before applying

• Read Anthropic's stated mission and its published concerns about doing harm by working at a frontier AI lab, referenced in the job posting.
• Read about Anthropic's teams in alignment, policy, and security, since this role works with Security and with developer and infrastructure teams.
• Look at how Anthropic describes its own high-impact roles and why it posts specific opportunities rather than recommending all positions.
• Check what is publicly known about the size and make-up of Anthropic's device fleet, and note what is not stated so you can ask in the interview.

Likely interview topics

Based on the job description, expect questions about:

• How you have run an MDM as a production service, including the infrastructure it depends on and how you kept it reliable.
• How you manage device configuration as code through pull requests, CI, a staging environment, and a canary group before fleet-wide rollout.
• How you built patching and software pipelines for a large fleet, and how you knew they worked.
• How you used telemetry to determine what is actually true on every device, and how that fed access decisions based on device trust.
• How you worked with Security on hardening, compliance controls, and detection and response without blocking developer and infrastructure teams.

Common mistakes to avoid

• Describing MDM use as an end user or administrator without showing ownership of the infrastructure underneath it or the configuration on top.
• Talking about device management in general terms without the pull request, CI, staging, and canary workflow this team uses.
• Claiming fleet experience without specifics on scale, macOS share, Linux machines, mobile footprint, patching, software pipelines, or telemetry.