Field CTO at PhysicsX
New York, NY
—
Jul 5, 2026
New York, NY
Jul 21, 2026
What this job asks for AI summary
A regional leadership role responsible for deploying a Kubernetes-based AI simulation platform into customer-owned infrastructure across enterprise accounts. The position combines hands-on technical oversight of complex deployments — including air-gapped and regulated environments — with executive-level relationship management at the CIO/CTO level, and direct responsibility for hiring and growing a regional deployment engineering team.
Senior level · National · Full-time
Advertised as Principal, but the requirements read as Senior.
“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
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $178,991 (middle half $141,096–$225,584).
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)
This role is titled 'Field CTO' and is based in the UK (PhysicsX is a UK-registered company; the posting references UK employment and equality legislation, mentions New York delivery leads as a separate location, and describes travel 'within your region'). The US-based flag is set to false accordingly. No specific city or CBSA is determinable.
The title 'Field CTO' implies a Principal-level advertised seniority, but the actual scope — leading a regional deployment team, owning customer relationships, and being the most senior technical person in the region — maps to a Senior band. The role has direct reports and team-building responsibilities, which is why 11-3021 (Computer and Information Systems Managers) is the primary SOC, with 15-1244 as a runner-up given the heavy hands-on infrastructure delivery component.
Cloud infrastructure is listed as a hard requirement ('AWS, Azure, Open Stack, RHOS'). AWS is used as the primary skill name with Azure and OpenStack as alternatives, since the JD treats them as a group of acceptable platforms.
Infrastructure-as-code tooling (Crossplane, Terraform, Helm) and the OCI ecosystem are listed under 'What We're Looking For' as a single requirement. Crossplane, Terraform, and Helm are emitted as separate named skills since they are distinct tools; the JD groups them together as a set rather than as strict alternatives.
Experience in regulated or high-security environments is explicitly called out as 'a must' in the JD. This is a behavioural/domain requirement rather than a named technology, so it is not emitted as a skill per extraction rules.
Experience with on-prem/HPC 'scientific' environments is explicitly called 'a nice to have' in the JD.
No compensation figures are provided in the posting.
This role's work location reads as outside the US — the candidate pool, comp, and contention benchmarks here are US-only (BLS employment, Adzuna/USAJOBS demand, and certified H-1B wages), so treat them as a rough US reference, not a local market.
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.