Drimva

Appian

AI Security Engineer

$100K–$200K

McLean, Virginia +1 · Full-time · Posted Sep 14, 2026

Location
McLean, Virginia
Appian Corporation - US
Experience
At least 2 years developing AI/ML algorithms or technologies with a bachelor’s degree, or at least 1 year with a related master’s degree; at least 2 years programming with a listed language. Preferred: 3 years deploying scalable, responsible cloud AI solutions.
Education
Bachelor’s degree in Computer Science, AI, Electrical Engineering, Computer Engineering, or related fields; OR a master’s degree in a related field.

About the job

Build and secure AI agents and agentic workflows for Appian’s security operations, integrating security data and human analyst oversight.

What you'll do

  • Design, test, and deploy autonomous and semi-autonomous agents integrated with SIEM, EDR, XDR, and threat intelligence feeds.
  • Develop agentic SOC playbooks and production RAG workflows; evaluate and optimize LLM performance.
  • Secure LLM architectures against risks including prompt injection, data poisoning, and tool abuse, and design human-in-the-loop escalations.

What they ask for

  • Bachelor’s degree in a related field plus at least 2 years developing AI/ML algorithms or technologies, OR a related master’s degree plus at least 1 year of that experience.
  • At least 2 years programming with Python, Go, Scala, or Java.
  • Ability to build production-grade asynchronous code and bridge AI development with practical cybersecurity.

Nice to have

  • 3 years deploying scalable, responsible AI on cloud platforms.
  • Experience with security operations or threat intelligence AI services, multi-agent orchestration, vector databases, or containerized cloud AI workloads.

Pay

$100,000 — $200,000 USD (base salary)

Tools

Python, Go, Scala, Java, SIEM, EDR, XDR, LangChain

AI focus

Develop agentic SOC systems, RAG workflows, and human-in-the-loop security operations; benchmark LLMs and defend AI systems against security threats.

Model-written summary · the original posting is authoritative

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