Customer Engineer, Public Sector

Google Google · Big Tech · Mexico City, CDMX, Mexico

Customer Engineer for Google Cloud Public Sector, focusing on architecting and managing LLM deployments, including on-premises and cloud environments. Responsibilities include auditing multi-agent orchestration, agent construction, vector databases, orchestrating inference and training with Docker/Kubernetes, securing model weights and data, and mitigating AI-specific threats. Requires extensive experience in AI/ML development, infrastructure, and containerization, with a strong security clearance.

What you'd actually do

  1. Architect and manage Large Language Model (LLM) deployments across on-premises (NVIDIA/AMD) and cloud (cloud computing platform, Google Cloud platform (GCP) environments. Audit multi-agent orchestration, agent construction, and vector databases to map data flows and enforce privilege boundaries.
  2. Use Docker and Kubernetes to orchestrate scalable inference and training environments, optimizing Graphics Processing Unit (GPU) utilization and resource isolation.
  3. Protect model weights, secure data ingestion, and harden inference endpoints across the Machine Learning operations (MLOps) lifecycle. Investigate and mitigate AI-specific threats (e.g., prompt injection, jailbreaking, data poisoning). Map testing findings to MITRE ATLAS, OWASP for LLMs, and STRIDE models.
  4. Bridge local high-compute clusters and cloud AI services while maintaining a consistent security posture.

Skills

Required

  • AI/ML development
  • AI infrastructure engineering
  • software development
  • containerization (Docker)
  • orchestration (Kubernetes)
  • Python
  • PyTorch
  • TensorFlow
  • Hugging Face Transformers
  • Top Secret/SCI security clearance with current polygraph

Nice to have

  • AI/ML research
  • LLM deployment frameworks (vLLM, NVIDIA Triton, Ollama)
  • agent development
  • OWASP for LLMs
  • cloud-native AI services (Vertex AI)
  • deploying AI models on air-gapped or on-premises HPC systems

What the JD emphasized

  • Must possess an active Top Secret/SCI security clearance with current polygraph.

Other signals

  • LLM deployments
  • AI infrastructure engineering
  • MLOps lifecycle
  • AI-specific threats