Quick Facts
- Category: Education & Careers
- Published: 2026-05-20 00:47:27
- 7 Things You Need to Know About .NET MAUI's Move to CoreCLR in .NET 11
- Navigating the Path to Zero: A Practical How-To Guide for Maritime Decarbonization
- Googlebook: The Premium Android-Powered Laptop Challenging Apple and Microsoft
- How to Protect Your macOS or Linux ASP.NET Core Server from the Critical CVE-2026-40372 Vulnerability
- How Massachusetts Locked in Cheaper Offshore Wind Power and Saved $1.4 Billion
Artificial intelligence is revolutionizing how we manage cloud infrastructure. Our company is developing an agentic operating system for DevOps—autonomous AI agents that self-build, self-heal, and self-optimize cloud environments. This innovation requires a unique professional: a DevOps/SRE engineer who also excels at creating technical content. If you've spent years provisioning infrastructure, responding to incidents, and somewhere along the way started documenting your experiences, this role might be your perfect next step. Below are seven essential insights into this position, covering everything from daily responsibilities to the ideal candidate profile.
1. The Role: DevOps/SRE Engineer Plus Technical Content Creator
This isn’t a typical DevOps role—it’s a hybrid position that blends deep engineering expertise with content creation. You’ll still work hands-on with infrastructure, but you’ll also produce tutorials, blog posts, and demo videos that showcase real-world applications. The goal is to bridge the gap between complex technical concepts and the broader DevOps community. You’re not just building systems; you’re teaching others how to use them effectively. Learn more about the mission.

2. Your Mission: Build the Agentic Operating System for DevOps
Our core product is an agentic OS that makes cloud environments self-building, self-healing, and self-optimizing. As a Content Engineer, you’ll translate this advanced AI-driven capabilities into practical guides and demos. You’ll create examples that show how our agents automate provisioning, incident response, and performance tuning. Your content will help engineers understand the value proposition and how to integrate these agents into their existing workflows. See what your day-to-day looks like.
3. Day-to-Day: From Writing Tutorials to Building Proof-of-Concepts
Your typical week will involve writing technical blog posts and tutorials based on real hands-on experience. You’ll also create demo videos and screencasts that walk through realistic product scenarios. Beyond content creation, you’ll build proof-of-concepts, sandbox environments, and reference architectures that validate our platform’s capabilities. Engaging with DevOps and SRE communities—answering questions, sharing insights—is also key. You’ll collaborate closely with Marketing, Product, and Engineering teams to ensure your content aligns with what matters most to users. Find out who we're looking for.
4. Who We're Looking For: The Perfect Blend of Hands-On Experience and Storytelling
We need someone who has lived the day-to-day reality of DevOps for at least 3–5 years. You should have deep experience with Terraform, Kubernetes, Docker, and major cloud platforms like AWS, GCP, or Azure. Familiarity with monitoring tools such as Prometheus, Grafana, or OpenTelemetry is essential. But technical skills alone aren’t enough—you must have created technical content before, whether it’s blog posts, conference talks, videos, or GitHub repositories. Excellent written and verbal English is required. This role is open to candidates based in LATAM. See the must-have skills in detail.

5. Must-Have Skills: Terraform, Kubernetes, Docker, and Cloud Proficiency
On the engineering side, you need proven, hands-on expertise with infrastructure-as-code tools like Terraform, container orchestration with Kubernetes, and containerization with Docker. Cloud experience should include at least one major provider: AWS, GCP, or Azure. For observability, you should be comfortable with Prometheus, Grafana, or OpenTelemetry. On the content side, you’ve already produced technical materials—perhaps a popular blog or a series of screencasts. Your English—both written and spoken—must be excellent to communicate complex ideas clearly. Explore nice-to-have differentiators.
6. Nice-to-Have Differentiators: Video Editing, Community Presence, Public Speaking
While not required, certain extras will make your application stand out. Experience with video editing tools helps you produce polished demos and tutorials. An active presence in developer communities—whether on Dev.to, GitHub, Discord, or local meetups—shows you’re already engaging with the audience. Public speaking experience indicates you can present ideas confidently in webinars or conferences. If you have any of these, be sure to highlight them. Check out what we offer.
7. What We Offer: Fully Remote, Flexible, Competitive Compensation
This is a full-time, 100% remote position. You’ll have flexible work arrangements—set your own schedule as long as you deliver great content. Compensation is competitive and commensurate with experience. You’ll be part of a forward-thinking team building the future of AI-driven DevOps. If this sounds like you, we’d love to hear from you.
Interested? Apply here: DevOps Content Engineer Application