> Markdown version of [/jobs/ext/2352117-engineer-platform-infrastructure](https://www.wearedevelopers.com/jobs/ext/2352117-engineer-platform-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). --- # Engineer, Platform Infrastructure - **Company:** Lever, Inc. - **Location:** San Diego, CA, United States - **Experience:** Expert - **Salary:** $120,000.0 - $180,000.0 - **Contract:** Temporary contract - **Skills:** Automation of Tests, Continuous Delivery, Linux, Distributed Systems, Key Management, Networking Basics, Pair Programming, Public Key Infrastructure, Ansible, Software Deployment, Software Engineering, Trunk-based Development, SSL Certificate Management, Test-Driven Development (TDD), Delivery Pipeline, Git, Gitlab-ci, Kubernetes, Extreme Programming, Terraform - **Published:** August 4, 2026 - **Apply:** https://jobs.lever.co/shieldai/b3927595-1e5a-455e-b831-721674088249/apply ## About the Role If humans perform the same task repeatedly, the system probably needs improvement., You should be comfortable working across most of these areas: * Kubernetes * Linux * Networking fundamentals * Git and trunk-based development * GitLab CI * Infrastructure as Code * Ansible * Terraform * Helm * Zarf * Containers * PKI and certificate management * Secrets management * Observability * Infrastructure testing * Troubleshooting distributed systems ## Description We build and operate the platform that our engineers and our customers rely on. The platform isn't a product that's ever "finished." It's something we improve continuously. Every deployment, outage, bug, and annoying manual task is an opportunity to make the system better. An L3 Platform Engineer is a fully contributing member of that effort. This isn't a ticket factory. We expect engineers to think critically, collaborate closely, and continuously improve both the platform and the way we build it. How We Work: Our engineering culture is built on Extreme Programming and Continuous Delivery. That means: * Pair programming is our default way of developing software. * We work in small batches. * We integrate continuously. * We automate repetitive work. * We test first whenever practical. * We optimize for learning and feedback instead of individual velocity. * The team owns the outcome. If you're looking for a role where you're handed tickets, disappear for a week, and come back with a pull request, this isn't it. What You'll Do: * Build and improve the platform that deploys and operates customer environments. * Develop infrastructure as code using Ansible, Terraform, Helm, Zarf, Big Bang, Packer, and related tooling. * Improve Kubernetes platforms and the systems around them. * Build deployment automation that reduces risk and removes manual work. * Pair with other engineers to design, implement, and troubleshoot platform capabilities. * Write automated tests for infrastructure and deployment workflows. * Improve observability, reliability, security, and recoverability. * Write documentation that explains why something exists-not just how to type commands. * Leave every part of the system better than you found it., Successful L3 engineers consistently help the team: * Deploy more frequently. * Deploy more safely. * Recover from failures faster. * Remove manual work. * Reduce operational complexity. * Improve documentation. * Increase confidence through testing. * Deliver changes in small, reversible increments. * Make the platform easier to operate and easier to evolve. ## Related Videos - [Enabling automated 1-click customer deployments with built-in quality and security](https://www.wearedevelopers.com/videos/83-enabling-automated-1-click-customer-deployments-with-built-in-quality-and-security) - [Dev & Test in the Cloud? Deploy your cloud environments with Ansible & Terraform](https://www.wearedevelopers.com/videos/1607-dev-test-in-the-cloud-deploy-your-cloud-environments-with-ansible-terraform) - [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Eclipse Che for Infrastructure Automation](https://www.wearedevelopers.com/videos/1611-eclipse-che-for-infrastructure-automation) - [#90DaysOfDevOps - The DevOps Learning Journey](https://www.wearedevelopers.com/videos/548-90daysofdevops-the-devops-learning-journey) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [The Best X (Twitter) Accounts for Developers](https://www.wearedevelopers.com/magazine/294-the-best-x-twitter-accounts-for-developers) - [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development) - [The Best Software Developer Blogs to Read](https://www.wearedevelopers.com/magazine/156-the-best-software-developer-blogs-to-read) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)