Build and scale high-performance, low-latency backend systems for Polymarket's core exchange infrastructure using C/C++ or similar systems languages. Requires 4-7+ years experience in distributed systems, concurrency, and production debugging.
Salary not listed
On-site4+ YOEBackend Engineering
About the role
Responsibilities
Build the exchange backend: Design and implement scalable, low-latency backend services that power Polymarket’s exchange, using C/C++ or other performance-oriented systems languages (Go, Rust, Java).
Optimize for performance & scale: Profile, tune, and debug systems with a focus on latency, throughput, memory usage, and correctness in production.
Design distributed systems: Build and operate robust APIs, data pipelines, and event-driven systems using messaging and streaming platforms (Kafka, Pulsar, RabbitMQ).
Own reliability & operations: Reinforce security, availability, performance, and scalability across backend systems, and participate in diagnosing and resolving production issues.
Collaborate cross-functionally: Work closely with engineers across product, infra, and data to ensure tight integration between the exchange and the broader platform.
Contribute to code quality: Participate in code reviews, design discussions, and architectural decisions to maintain a high bar for engineering excellence.
Requirements
4–7+ years of professional backend development experience, with strong proficiency in C/C++ (preferred) or another systems language (Go, Rust, Java).
Solid understanding of algorithms, data structures, concurrency, memory management, and experience building low-latency, high-throughput systems.
Comfortable working on complex systems end-to-end, debugging production issues on Linux, and taking responsibility for correctness and performance.
Nice-to-haves
Experience in trading systems, HFT, gaming, telecom, or other latency-sensitive domains.
Production experience with Kafka, Pulsar, or similar streaming platforms at scale.
Familiarity with gRPC, Protobuf, ZeroMQ, or similar technologies.
Experience deploying systems in cloud environments (AWS/GCP) and using containers.
Benefits
Competitive salary & equity.
Unlimited PTO, Health, Vision, & Dental coverage.
401k match.
Hardware setup — new MacBook Pro, big display, & accessories.
Founding backend engineer building end-to-end cloud partner integrations for ClickHouse. Own architecture, auth/identity, multi-tenancy, and production systems across external platforms with significant ambiguity. 5+ years experience, strong systems instincts, and comfort with auth federation and partner constraints required.
141k – 238k/yr
Remote5+ YOEBackend Engineering
Senior Software Engineer, Backend
PayabliMiami, FL
Senior backend engineer building scalable C#/.NET services for payment routing, connector management, and high-volume transaction processing in a fintech payments infrastructure platform. Requires 5+ years production backend experience, strong payments/fintech background, and technical leadership skills.
Salary not listed
Remote5+ YOEBackend Engineering
Senior Backend Engineer
AurelianSeattle, WA
Senior Backend Engineer building core voice AI and automation platform for 911 centers. Architect scalable systems, optimize realtime AI pipelines and audio latency, build analytics and integrations. Requires 4+ years software engineering experience with strong fundamentals.
160k – 220k/yr
On-site4+ YOEBackend Engineering
Senior Software Engineer, Backend
Vector LegalUnited States
Senior Backend Engineer building scalable distributed systems for freight and field service automation platform. Requires significant enterprise software development experience and distributed systems expertise; Java ecosystem preferred.
180k – 200k/yr
Remote5+ YOEBackend Engineering
Software Engineer, Backend
MercorSan Francisco, CA
Own and define the shared backend architecture, core services, data models, and APIs that power Mercor's rapidly scaling talent network and AI training products. Requires 8+ years backend engineering experience with a track record of organization-wide architectural ownership and complex migrations.