Drimva

JPMorgan Chase

Senior Lead Software Engineer- Platform / Linux Engineering

$176K–$260K

New York, NY · Senior · Full-time · Posted Oct 23, 2026

Experience
5+ years applied experience; no alternatives stated.
Education
Formal training or certification on software engineering concepts.

About the job

Leads hands-on engineering of Linux infrastructure platforms for low-latency electronic trading, including system design, performance optimization, automation, and AI-assisted engineering practices.

What you'll do

  • Design, build, operate, and tune Linux compute platforms and next-generation deployment models for electronic trading.
  • Write production code and automation, and optimize performance across hardware, kernel, and network layers.
  • Guide adoption and governance of approved AI-assisted engineering practices; mentor teams and advise stakeholders.

What they ask for

  • Formal training or certification in software engineering concepts and 5+ years of applied experience.
  • Strong programming skills for production-grade tooling and automation; expertise in Linux engineering and low-latency environments.
  • Hands-on kernel-bypass networking experience with Solarflare Onload and configuration management experience such as Chef or Ansible.
  • Experience with enterprise-authorized AI-assisted development, IPv4 networking, CI/CD and infrastructure-as-code, cloud-native/container orchestration, and cross-functional team leadership.

Nice to have

  • Server hardware selection, BIOS/firmware tuning, and bare-metal provisioning experience.
  • Familiarity with observability/telemetry stacks, cryptography, electronic-trading market-data or messaging technologies, or PostgreSQL.

Pay

$175,750.00-$260,000.00 USD base salary

Tools

Linux, Red Hat Enterprise Linux, Python, Go, Bash, Solarflare Onload, Chef, Ansible

AI focus

Use Agentic AI and approved AI-assisted tools to accelerate engineering, automate research and remediation, support code review, testing, troubleshooting, and incident analysis, and establish validation and responsible-use practices.

Model-written summary · the original posting is authoritative

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