Drimva

JPMorgan Chase

Lead Software Engineer - ML Engineer for Agent Platform

$157K–$215K

Jersey City, NJ +3 · Full-time · Posted Jul 20, 2026

Location
Jersey City, NJ
Tampa, FL
Plano, TX
Austin, TX
Experience
5+ years of applied experience.
Education
Formal training or certification on software engineering concepts.

About the job

Leads hands-on engineering of NEO, a secure and scalable agent runtime platform for Payments Technology, including execution, communication, memory, retrieval, and evaluation components.

What you'll do

  • Builds and operates runtime components, including agent sandboxing, A2A and MCP integrations, memory, retrieval, and evaluation harnesses.
  • Implements secure, permission-aware agent execution and promotes validated AI-assisted engineering practices.
  • Leads technical evaluations and engineering communities, and mentors senior and Lead engineers.

What they ask for

  • Formal training or certification in software engineering concepts and 5+ years of applied experience.
  • Strong Python skills and advanced proficiency in one or more programming languages.
  • Hands-on delivery experience across system design, application development, testing, and operational stability; production Kubernetes experience expected.
  • Experience building LLM-powered or agentic systems, including tracing, evaluations, and guardrails; knowledge of responsible AI use and financial services IT systems.

Nice to have

  • Exposure to LLMs, RAG, vector databases, embedding-based retrieval, or Graph RAG; experience with A2A, MCP, or multi-agent orchestration.
  • Experience with secure code-execution sandboxes, agent memory, LLM/agent evaluations, Terraform, Docker, or data observability tools.

Pay

USD 156,750.00-$215,000.00 base salary

Tools

Python, Kubernetes, A2A, MCP, Firecracker, Kata, gVisor, Terraform

AI focus

Builds agent runtime capabilities and LLM-powered or agentic systems, and leads safe, validated use of AI-assisted software engineering tools.

Model-written summary · the original posting is authoritative

First seen Oct 28, 2026 · Last verified Nov 5, 2026 (UTC)