> Markdown version of [/jobs/ext/1508143-infrastructure-engineers](https://www.wearedevelopers.com/jobs/ext/1508143-infrastructure-engineers). 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 Engineers - **Company:** Buffer Inc. - **Location:** United States (Remote available) - **Experience:** Expert - **Salary:** $165,000.0 - $213,000.0 - **Contract:** Permanent contract - **Skills:** PHP (Programming Language), Artificial Intelligence, Amazon Web Services, Amazon Elastic Compute Cloud, Amazon S3, BigQuery, Continuous Integration, Software Debugging, DevOps, Programming Tools, Domain Name System (DNS), Identity and Access Management, Python (Programming Language), Node.Js, Open Source Technology, Zero Trust Network Access, TypeScript, Software Vulnerability Management, Datadog, Kubernetes Helm Charts, Build Management, Kubernetes, Sentry, Cloudflare, Amazon Simple Queue Service (SQS), Terraform - **Published:** July 30, 2026 - **Apply:** https://jobs.ashbyhq.com/buffer/1ee8b707-48a0-40cc-a319-3fb7c665a1e8 ## About the Role * You've worked as an Infrastructure Engineer, SRE, "DevOps" engineer, or adjacent role for long enough to be considered senior. * You have hands-on experience operating production Kubernetes at scale on a managed offering (GKE, EKS, AKS), including authoring and maintaining Helm charts, and you're fluent with autoscaling primitives driving KEDA and the cluster auto scaler. * You have AWS depth across IAM, EC2, S3, SQS, ECR, and ALBs. You may have also used Cloudflare (WAF, Workers, etc.) and GCP (BigQuery). * You have strong Terraform skills. You default to modules for structure, and keep the code adaptable, readable, and self-contained. Bonus points if you contributed an OSS module. * You've operated production CI/CD with GitHub Actions (or equivalent) and GitOps via ArgoCD (or similar). You've authored ArgoCD pipelines and Helm configuration yourself, including canary or progressive delivery systems you'd trust to roll back safely. * You've built internal developer tools (CLIs, dev environments, per-PR environments) and you think about them as products with users, not scripts. * You have a track record of pragmatic build-vs-buy decisions on infrastructure tooling. You can defend a choice and revisit it when conditions change. * You've worked with DataDog, Sentry, or similar observability stacks, and you design logs and metrics with cost in mind. You know observability and cloud spend can grow faster than the company if no one is watching. * You're comfortable with the Cloudflare across Workers, Zero Trust, DNS, and the rest of their platform. * You read and modify TypeScript or Node services well enough to upgrade runtimes and unblock teams (legacy PHP and Python show up too). * You're fluent with modern AI tools. You use them to debug, document, and reduce toil, not just to generate code, and you bring those patterns into how infra runs. * You're proactive and you follow through. You spot what needs doing before you're asked, and you close the loop without being chased. * You turn ambiguity into proofs of concept. You take fuzzy asks, ship something rough teammates can react to, and iterate with them until it lands. * You thrive in remote, asynchronous environments. You're clear in your thinking, generous with context. ## Description As Buffer's next Senior Infrastructure Engineer, you'll join two seasoned Infrastructure Engineers on a small, deliberate, high-leverage team. Together, you'll run the platform that lets every Buffer engineer ship, and that indirectly lets millions of creators publish, grow, and earn a living on the social web. When our infrastructure is fast and reliable, creators get features sooner and outages less often. You'll own a meaningful slice of three shifts the team is making. * Keeping the lights on at a higher bar. You'll make our CI/CD pipelines faster and even more anti-fragile, ship boring deploys, and turn each incident into a new lesson rather than a repeat. * Modernizing the foundation. Buffer is not new, but our Infra is in continuous improvement. From deploying KEDA and Argo Rollouts to improving our signal-to-noise ratio in monitoring, there is plenty to do. One cannot talk about modernization without mentioning AI. We're already leaning on it for investigations and boilerplate, and want to bring it deeper into our day-to-day. * Treating engineers across Buffer as customers. You'll evolve the developer tooling that makes the inner loop fast, with documentation that holds up at 2am or when consumed by an agent. We're remote-first with a preference for at least 4 hours of overlap with EMEA time zones, but we're open to strong candidates anywhere in the world. It's an exciting time to join. Buffer is a profitable, 15-year-old company innovating at the edge of AI-assisted development, and there's lots of impactful work to do. Who you'll work with: In this role, you'll report to Miguel, the Infrastructure Engineering Manager. Day-to-day you'll work closely with Peter and Steven, who have helped build the infrastructure we run on since the beginning of Buffer. We're looking to round out the team with someone who sits between infra and developer experience: deep infra expertise paired with an infra-as-a-product mindset. You'll also work daily with all of EPD (Buffer's unified Engineering, Product, and Design team). EPD are the internal customers of the platform you maintain, and they contribute to it too. What you'll be working on * Own the day-to-day reliability of our production platform. Keep EKS, ArgoCD, and the AWS surface area boring, tune autoscaling so the system adjusts well under load, and approach incident response in a way that each incident teaches us something new instead of repeating itself. (On-call is distributed across all engineers at Buffer, a week-long shift roughly once a quarter.) * Build progressive delivery into something the rest of engineering trusts. Implement Argo Rollouts with clean rollback paths, so the time between "this deploy is bad" and "this deploy is reverted" measures in seconds to minutes. * Build developer tools as products, instead of loose scripts. Evolve our in-house local development environment, BIBEs (Buffer Isolated Build Environments, per-PR full-stack staging deployments), and our CLI tooling so the inner loop is fast, frictionless, and parallel-friendly for AI agents. Measure adoption, talk to your users, iterate. * Reduce operational toil with AI. Automate low-risk workflows end-to-end so the team spends its time on the hard problems, not the repeat ones. AI doesn't touch infrastructure directly, it speeds up the humans who do. * Keep the stack current. Drive lifecycle upgrades: application runtimes (Node.js, Python), Kubernetes, EKS, Helm versions, and the Terraform-managed surface area. Own infra-side security vulnerabilities. * Improve the economics of our platform. Lead visibility work on Datadog, AWS rightsizing, and log filters so observability and cloud spend grow slower than the company does. * Partner with EPD on the platform they build on. Raise the documentation bar with the team, carry your share of weekly security work (dependency and vulnerability management is everyone's job), and help the infra team grow toward shared ownership and fewer single-person dependencies., + When submitting your application and resume, take your time. This is your chance to make a strong first impression. + While we have a couple of engineering roles open, we recommend applying to only one role. If during our review or interviews we think you'd be great for a different position, we'll re-route your application internally. + Response times can take a few days to weeks. We're a small team reviewing every application carefully. 2. Hiring manager interview. Chat with the hiring manager for your role (Miguel, Engineering Manager) and another Engineering Leader to understand what it takes to work at Buffer. This is an opportunity for both sides to get to know each other and determine whether our expectations align. 3. Take-home exercise. We'll send you a two-page max asynchronous assignment to review a system or scenario to help us understand how you think about systems, assumptions and communication of technical ideas. 4. Technical interview. Interview with two Infrastructure Engineers from Buffer (Peter and Steven) focusing on your technical experience and approach. 5. Leadership interview. A conversation with one or two Engineering Leaders to discuss your approach to leadership, how we drive value and impact in a cross-functional company, and to really get into how you think about approaching work and collaboration. 6. Final interview. You will have the opportunity to meet with our Executive Leadership team. This is a great chance for you to gain a deeper understanding of Buffer's strategy, values, and work processes. 7. Collaboration period. This is a stage where you would work with us on a real project over two days (fully paid). The goal is to see how it feels to work in the team, both for us and for you. You'll meet a few Bufferoos, we'll kick off the project, invite you to a Slack channel, and you'll collaborate with the team on it. 8. Offer. We wrap it up with an offer and discuss the final details. We would align on the last bits before we make you part of the Buffer team ## Related Videos - [Debugging in the Dark](https://www.wearedevelopers.com/videos/1658-debugging-in-the-dark) - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [From Doubt to Confidence: How Sentry Uses Verdaccio to Bulletproof SDK Releases](https://www.wearedevelopers.com/videos/739-from-doubt-to-confidence-how-sentry-uses-verdaccio-to-bulletproof-sdk-releases) - [From DevOps to Scaled DevOps: How We’re Rebuilding Continuous Delivery as a Platform](https://www.wearedevelopers.com/videos/100018-from-devops-to-scaled-devops-how-we-re-rebuilding-continuous-delivery-as-a-platform) - [Stop configuring infrastructure, start coding it!](https://www.wearedevelopers.com/videos/464-stop-configuring-infrastructure-start-coding-it) - [DevOps Maturity Check – a way to balance autonomy and alignment](https://www.wearedevelopers.com/videos/58-devops-maturity-check-a-way-to-balance-autonomy-and-alignment) ## Related Articles - [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Why Upskilling And Reskilling is Important For Developers](https://www.wearedevelopers.com/magazine/428-why-upskilling-and-reskilling-is-important-for-developers) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [How to Answer the Interview Question: “Why Do You Want to Be a Software Engineer?”](https://www.wearedevelopers.com/magazine/392-how-to-answer-the-interview-question-why-do-you-want-to-be-a-software-engineer) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai)