> Markdown version of [/jobs/ext/3843803-infrastructure-engineer](https://www.wearedevelopers.com/jobs/ext/3843803-infrastructure-engineer). 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). --- # Infrastructure Engineer - **Company:** FRIDAY HARBOUR - **Location:** United States (Remote available) - **Experience:** Expert - **Salary:** $205,000.0 - $225,000.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Microsoft Azure, Linux, Distributed Systems, Python (Programming Language), Key Management, Google Cloud, Delivery Pipeline, Kubernetes, Terraform, Serverless Computing - **Published:** October 20, 2026 - **Apply:** https://www.builtincolorado.com/auth/login?destination=/job/senior-infrastructure-engineer/11753678 ## About the Role ** Candidates must currently live in the US and have work authorization to work for any US employer **, * Deep Kubernetes experience in production. You've operated Kubernetes for substantial workloads and have a strong mental model of scheduling, networking, resource management, scaling, and failure modes. You can reason through what's happening when a deployment or cluster behaves unexpectedly. * Experience designing new infrastructure and migrating existing workloads onto it. You've made architectural decisions with incomplete information, moved beyond deployment patterns a team had outgrown, and carried the work through to production. * Practical engineering judgment. You weigh the value of additional control against the complexity and ongoing work it introduces. You can explain when you chose a managed service versus when you built something yourself. * Strong cloud fundamentals. You're comfortable with modern cloud platforms (AWS preferred, or Azure, Google Cloud etc.), Linux, networking, storage, and infrastructure as code such as Terraform. You understand how these pieces interact when troubleshooting production systems. * The ability to build and automate. You can write software and tooling that removes operational work and makes infrastructure easier for other engineers to use. * Ownership and clear communication. You're comfortable taking an ambiguous problem from investigation through implementation and operation. You explain tradeoffs clearly and bring other people into decisions that affect their work., You don't need to have experience in every area before joining. Strong infrastructure fundamentals and curiosity about these problems are more important to us than the specific technology you've used. ## Description We're looking for a Senior Infrastructure Engineer to work closely with our Lead AI Platform & Infrastructure Engineer on the foundation for our next stage of growth. You'll help decide how our infrastructure evolves, lead the work to get it there, and own the systems you put into production. There's meaningful room to design here, alongside a live product and real customers to support. You'll work with engineers who have infrastructure and platform backgrounds and care deeply about getting these decisions right. We want a strong managed infrastructure foundation, with clear abstractions that let our team build on top of it. That takes someone who understands the underlying systems well enough to know where we need control, where a managed service makes sense, and when the simplest approach will serve us best. What You'll Own: * Evolve our production infrastructure. Help define the architecture and lead incremental migrations toward a more flexible, cloud-native deployment model. Make changes safely, with clear rollout and recovery plans. * Build the foundations for running AI workloads. Work through questions around execution environments, workload isolation, scheduling, orchestration, and resource utilization. Evaluate new approaches against concrete product needs. * Make production understandable and reliable. Build observability that helps us understand system behavior, diagnose failures, and make informed decisions about performance, capacity, and cost. * Improve how engineers ship. Develop infrastructure as code, deployment workflows, and useful defaults that make it easier to build, test, and operate services. * Own the operational follow-through. Participate in on-call, improve recovery procedures, test backups, and turn incidents into lasting improvements. * Build security into everyday engineering. Make access controls, secrets management, patching, and data protection part of how our infrastructure works. * Shape the boundary between infrastructure and platform. Partner with our engineering and biz-ops teams to understand what they need and turn those needs into capabilities they can depend on., We expect this experience will usually come from five or more years in infrastructure, platform, SRE, or a related engineering role. The systems you've owned and the judgment you've developed matter more than an exact number of years. Nice to Have: * Operating AI applications, agentic workloads, or distributed systems. * Building execution environments with strong isolation or working with serverless compute. * Supporting Python services and asynchronous workers. * Working on a small team where you helped establish infrastructure practices. * Operating systems that handle sensitive data or support regulated customers.