Drimva

Apple

Machine Learning Engineer, Information Security

$142K–$278K

Seattle, Washington +1 · Full-time · Posted Feb 6, 2026

Location
Seattle, Washington
Sunnyvale, California
Education
BSc or Master's degree in a relevant field; Ph.D. preferred.

About the job

Designs, deploys, and operates machine-learning systems that detect and prevent security threats and improve security processes.

What you'll do

  • Translate research into production-ready ML models for security use cases, from data exploration and development through evaluation, deployment, and monitoring.
  • Use generative AI, statistical modeling, reinforcement learning, and data science to address security challenges.
  • Collaborate with security teams, software engineers, and researchers to prototype and scale AI/ML security solutions.

What they ask for

  • BSc or Master's degree in Machine Learning, Data Science, Computer Science, Information Security, Mathematics, Statistics, or a related field.
  • Strong Python and Scala skills, with experience using ML libraries such as TensorFlow, PyTorch, HuggingFace, and Scikit-learn.
  • Hands-on experience with the full ML model lifecycle, production services in cloud-native environments, and deploying models on CUDA devices.
  • Solid understanding of security fundamentals, plus proven experience building generative AI applications for real-world use cases.

Nice to have

  • Ph.D. in a technical field; in-depth knowledge of ML algorithms and large language models.
  • Experience deploying ML or generative AI in cybersecurity; familiarity with AWS, GCP, Apache Spark, security tools, C++ or Swift, or open-source and conference contributions.

Pay

$142,300 and $263,300 (base salary); $150,400 and $277,600 (base salary)

Tools

Python, Scala, TensorFlow, PyTorch, HuggingFace, Scikit-learn, CUDA, AWS

AI focus

Develop and deploy production-ready AI/ML security systems, including generative AI applications, to proactively detect and defend against threats.

Model-written summary · the original posting is authoritative

First seen Oct 15, 2026 · Last verified Nov 4, 2026 (UTC)