> Markdown version of [/jobs/ext/3963820-senior-infrastructure-automation-engineer-compute-platform-eda-infrastructure](https://www.wearedevelopers.com/jobs/ext/3963820-senior-infrastructure-automation-engineer-compute-platform-eda-infrastructure). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Infrastructure Automation Engineer, Compute Platform - EDA Infrastructure - **Company:** NVIDIA Corporation - **Location:** United States - **Experience:** Expert - **Salary:** $184,000 - $287,500 - **Contract:** Permanent contract - **Skills:** Computing Platforms, Configuration Management, Continuous Integration, Python (Programming Language), Ansible, Infrastructure Automation Frameworks, Information Technology, Slurm, Drift Detection, Puppet - **Published:** October 27, 2026 - **Apply:** https://www.careerbuilder.com/job-details/senior-infrastructure-automation-engineer-compute-platform-eda-infrastructure-tx--a1df596a-0e26-4bed-816d-c546519ac730 ## About the Role Automation Engineering, Computer Systems, Schedule Development, Automation Engineering, System Migration, Sales Pipeline, Machine Tool, Computer Science, Configuration Management, Chef (Configuration Management), * BS or MS in Computer Science or equivalent experience. * 6+ years in infrastructure engineering with strong config management depth - Ansible, Salt, Puppet, Chef, or comparable. * Real experience with GitOps practice at scale: review workflow, environment promotion, drift detection, and safe rollback. * Proficiency in Go, Python and shell, and comfort building the tooling rather than only using it. * Experience automating stateful, long-lived infrastructure where you cannot simply destroy and recreate. Ways to stand out from the crowd: * You have brought a manually administered estate under configuration management while it stayed in production. * Familiarity with LSF, Slurm, or another batch scheduler as a configuration target. * CI/CD experience for infrastructure, including test environments that meaningfully resemble production. * Observability instincts - you instrument what you automate.