Backend Infrastructure Engineer at Vinci4d
Palo Alto, CA
$165,000–$180,000
Jul 15, 2026
Palo Alto, CA
Jul 21, 2026
What this job asks for AI summary
A senior backend and infrastructure engineering role at an early-stage startup building a physics simulation and inference platform for semiconductor and hardware customers. The work centers on owning infrastructure-as-code, CI/CD pipelines, and build systems across large Python and C++ codebases, and on moving research prototypes into reliable production environments. The role suits an experienced engineer comfortable operating across cloud infrastructure, multi-language codebases, and scientific or ML workloads.
Senior level · 8+ years · Remote · 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 5,600 people nationally plausibly meet what this posting asks for (software developers). range 3,400–8,500
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
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 $138,970 (middle half $107,524–$175,762).
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 (9)
The role sits at the boundary between software development and infrastructure/DevOps. It is classified as Software Developers (15-1252) because the JD emphasises building and owning backend services, CI/CD pipelines, and platform components — shipping code — rather than purely operating existing systems. Network/Systems Administrators (15-1244) is noted as a runner-up given the heavy infrastructure-as-code and cloud-provisioning emphasis.
Cloud platform is required as a hard gate ('production work on at least one major cloud') with GCP, AWS, and Azure listed as interchangeable options; GCP is named first and is the primary alternative listed.
Jenkins is listed as the primary CI example with 'or equivalent' — well-known substitutes are captured in alternatives.
pip and uv are listed together as Python packaging tooling; uv is captured as an alternative since either satisfies the same requirement.
C++ is listed under required qualifications as 'working familiarity', which is softer language than Python's 'proficient', but both appear in the same hard-requirements block, so both are treated as required.
Docker, Kubernetes, observability tooling, PyTorch, NumPy, CUDA, and GPU infrastructure all appear under the 'We're very excited to talk with you if you have' section — a clearly secondary, preferred block.
No compensation figures are stated beyond 'competitive salary'; compensation fields are left unpopulated.
No degree requirement is stated anywhere in the posting.
Caller marked this a fully-remote role — scored against the national candidate pool.
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.