About StackGen

StackGen is building the agentic OS for DevOps — an autonomous operations platform purpose-built for the teams responsible for keeping modern infrastructure reliable and fast. We serve engineering organisations across three high-growth segments: infrastructure and platform engineering, AI SRE, and managed open source observability.

Our products — Aiden for Infrastructure, Aiden for SRE, and Aiden for Observability (including ObserveNow) — give platform engineers, SREs, DevOps engineers, and their leaders the autonomous capabilities they need to eliminate toil, reduce mean time to resolution, and scale confidently. We are growing fast, expanding our market presence and product portfolio, and building the team that will take us to the next stage.

The Role

Content is how StackGen reaches the engineers, SREs, platform teams, and technical leaders who need what we build. It’s how they discover us, how they form a view of what we do, and how they decide we’re worth a closer look. As Content Marketing Manager, you own that content engine — from creation through to distribution — across every channel where our potential customers learn, search, and form opinions.

Your job has two halves, and both matter equally. The first is creating content that resonates: posts, articles, scripts, narratives, and short-form pieces that land with technical audiences because they sound like they were written by someone who actually understands the world they’re written for. The second is making sure that content travels — reaching the right people, in the right channels, at the velocity a fast-moving company needs.

To do that at the scale we need, this role owns the AI-powered workflow systems that turn a single piece of source material into the right content for every channel where it should appear. Building, running, and evolving those workflows is a core part of the job, not an add-on.

You’ll work daily with our Product Marketing function, our Technical Marketing Engineers, our executive team, and our engineering and product leadership across all three of our market segments.

What You’ll Own

Content Creation

You’re responsible for the content that StackGen puts into the market — originating it, building on the work happening across the rest of the company, and orchestrating the workflows that make it all possible at the volume we need:

• Originating content — net new content that begins with this role rather than coming from a product launch or a technical deep-dive. This includes broader market-shift pieces where StackGen has a perspective worth sharing (the move toward agentic operations is one current example), and major project-led work. Our State of Reliability 2026 survey — analysing more than 50,000 incidents — is the kind of project this role originates and owns end-to-end
• Channel-native day-to-day content — the LinkedIn posts, newsletter content, social threads, scripts, and short-form video that the constant flow of StackGen presence requires
• Content built on technical and positioning work — taking the deep technical material produced by our Technical Marketing Engineers and the positioning developed by our Product Marketing function and turning it into content that lands across channels and personas
• Executive thought leadership — working with our CEO, CPO, engineering leadership, and other senior voices to turn their expertise into a consistent, credible external presence
• Editorial standards — establishing and maintaining the voice, tone, and quality bar for everything we publish under the StackGen brand

Distribution Across Channels

You make sure StackGen content reaches the people it’s built for, wherever they spend time:

• Social platforms — LinkedIn as the primary surface for both company and individual presence, plus other networks where DevOps and SRE practitioners and leaders gather
• Engineering communities — Discords, Slacks, Reddit, Hacker News, CNCF forums, and other practitioner spaces, with content that earns credibility rather than imposing on it
• Video platforms — YouTube and other video channels where our audience learns and evaluates
• Owned channels — the StackGen website, email and newsletter programmes, and our resource and video library, ensuring content lives somewhere our audience can return to
• Earned media and guest contributions — supporting placements in publications and external blogs that our buyers actually read, and coordinating opportunities for StackGen team members to contribute
• Search and AI discovery — working with the broader marketing team to ensure content is structured for SEO and AEO (AI Engine Optimisation), so it surfaces in both traditional search and AI-assisted discovery

AI-Powered Workflow Systems

Operating across this many channels at the velocity we need is only possible with serious AI leverage. You’ll own the workflow systems that make it work:

• Building and evolving AI-assisted content workflows that turn source material into channel-appropriate content at scale, with human-in-the-loop quality control
• Designing the systems and skill-based prompts that enable consistent voice and quality across formats and channels
• Continuously improving the workflow stack as the team grows and as AI tooling evolves
• Acting as the in-house standard-setter for what good AI-augmented content production looks like — so that AI is a structural advantage, not a productivity experiment

Amplification of StackGen’s People

StackGen’s engineers, product team, and leaders are doing work worth talking about. You make sure that work travels:

• Coaching and supporting team members on building consistent external voices, particularly on LinkedIn
• Helping engineering and product translate what they’re building into stories that resonate externally
• Identifying and building relationships with credible external voices in the DevOps, SRE, and cloud-native space — collaborating on content, joint posts, podcast appearances, and community presence

Contributing Across the Marketing System

Your content and distribution work feeds into and supports the broader marketing function:

• Demand generation — supplying the content that powers paid, outbound, and lifecycle programmes; learning back from performance data to inform what to create next
• Events — producing pre-event, at-event, and post-event content that extends the reach of our field activity
• Analytics — tracking content performance across channels and using that data to direct effort

What We’re Looking For

• Familiarity with the DevOps, SRE, or platform engineering world — enough to know the audiences, the conversations, and what credibility looks like in these communities. You don’t need to have been an engineer; we have Technical Marketing Engineers who provide deep technical expertise. What we need from you is ecosystem fluency
• A strong content instinct — you can tell what will resonate with a technical audience and what won’t, and you can produce content that lands rather than content that just exists
• Multi-channel distribution craft — you understand how content behaves differently on LinkedIn vs. in a community vs. on a blog vs. in an email, and you can make the same source material work across all of them
• Genuine AI fluency at the workflow level — you build and operate AI-assisted systems, not just use AI tools occasionally. You’re comfortable owning a workflow stack that produces content across many formats and channels at velocity
• Hands-on fluency across the tools modern content marketing runs on — for creation, distribution, measurement, and analysis. Our current stack includes HubSpot, Google Analytics, Google Search Console, and Canva on the operational side, and Claude, ChatGPT, Perplexity, AirOps, and others on the AI side. We expect comfort across this kind of toolset and active engagement in evolving it as the space changes
• A reach orientation — you think about where the right people are, what they pay attention to, and what StackGen needs to do to show up there credibly and consistently
• A bias toward data — you track what’s landing, you adjust based on signal, and you make the case for content investment with evidence
• Comfort working at high velocity across many channels and personas, from individual contributors (platform engineers, SREs, DevOps engineers) up to senior technical leaders (VPs of Engineering, CTOs)

A Note on Background

There’s no single path that leads here. Backgrounds in content marketing at a DevOps or infrastructure tooling company, technical content writing, DevRel, or technical community management are all directly relevant. We care about ecosystem fluency, content craft, and AI-native operating style more than any particular job title or year count.