Infrastructure Engineer at Numeus
New York, NY
$125,000–$200,000from the description
Jul 25, 2026
New York, NY
Jul 26, 2026
What this job asks for AI summary
This role centres on building and running cloud infrastructure for a systematic trading firm, covering production trading systems, low-latency networking, and large-scale research compute clusters across multiple cloud regions. The work spans Kubernetes orchestration, Terraform-driven infrastructure-as-code, Linux administration, and network stack optimisation. It suits an infrastructure engineer with hands-on experience in a buy-side or similarly demanding trading environment.
Senior level · 5+ years · New York-Newark-Jersey City, NY-NJ-PA · Full-time
“or” means any one of them counts — you don't need all of them.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 1,000 people in the New York-Newark-Jersey City, NY-NJ-PA area plausibly meet what this posting asks for (software developers). range 760–1,600
Applicant volume Light — Few people clear these requirements, so an application that does clear them gets looked at. Worth applying to even if you miss a nice-to-have.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $170,499 (middle half $133,523–$210,499). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
The role lists NYC, London, and Zug (Switzerland) as office locations with periodic travel required. NYC is used as the primary CBSA since the salary range is quoted in USD and the posting reads as US-based; however, the role may be based in London or Zug for some candidates.
AWS is listed as the preferred cloud platform ('ideally AWS') but is framed within a hard requirements block alongside production cloud experience — captured as required with Azure/GCP as named alternatives.
FluxCD and ArgoCD are presented as interchangeable GitOps examples ('such as FluxCD or ArgoCD') within a hard requirements block; FluxCD is listed as primary with ArgoCD as the alternative.
Prometheus and Grafana are cited as examples of monitoring frameworks ('such as Prometheus and Grafana') within the requirements block — treated as required given the firm gating language of the section.
Ansible is framed as an example of automation tooling ('such as Ansible') but sits inside the requirements block under a 'passion for automation' gate — captured as required.
The posting explicitly states 'Certifications alone are not enough' for cloud experience, signaling a strong preference for hands-on production background over credentialed knowledge.
UDP and kernel-bypass networking (e.g. DPDK/RDMA) are called out for low-latency trading context but are not named as distinct standalone tools — subsumed under the TCP/IP networking skill.
The role title carries no seniority modifier; seniority is assessed as Senior based on the 5+ years requirement, production ownership scope, and the breadth of infrastructure responsibilities described.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.