Developer Relations

LogRocket is looking for a technical, creative DevRel to be the face and voice of LogRocket for engineers and technical leaders.

You'll inherit one of the strongest developer content platforms in the industry: PodRocket, our podcast that's consistently ranked a top developer show in State of JS and State of CSS surveys; the LogRocket blog, which has been one of the most-trafficked frontend engineering resources on the web for years; and our growing YouTube channel. Your job is to evolve all three for the AI-native era and be the technical face of LogRocket for developers.

You'll create the content that shows engineers what AI-native dev tooling actually looks like in practice, with Galileo AI as your canvas.

This is a Super IC role first. If the thesis works, you'll build a team. You report directly to the VP of Marketing and work closely with our engineering org and technical founders.

This isn't a sales engineering role wearing a DevRel hat. You're building LogRocket's reputation with engineers, not running demos for prospects.

The opportunity

Galileo AI watches every session replay, support ticket, customer call, and product change, then tells engineers what broke, why, and what to do next. It runs via MCP in Claude, Cursor, ChatGPT, and Gemini, in Slack, in Teams, and inside LogRocket itself. None of our competitors can demo this. You'd be the person who shows engineers what it actually means to have an AI agent sitting next to your code that knows what your users are doing.

That's the hook. The broader job is being the technical face of LogRocket for engineers, building on a content platform that already has serious audience and earned authority.

There's a real strategic problem to chew on here too. The classic developer blog model, high-volume SEO content for frontend frameworks, is getting squeezed by AI search and LLM-generated answers. The LogRocket blog has the audience, brand equity, and domain authority. The question is what it becomes next. Opinionated takes, deep technical investigations, content tied to a real product with proprietary data, video, podcast, community. That's part of the job.

📋 Preparation Priorities (Key Areas to Clarify):

• 1. Dismissing front-end complexity or treating UI logging as a solved commodity
• 2. Failing the technical depth check regarding DOM capture performance overhead
• 3. Relying on top-down enterprise sales motions instead of bottom-up developer adoption

✨ Recommended Role Alignment Hook:

I understand that the best developer tools don't just log errors; they instantly reconstruct the user's frustration so engineering teams can ship with absolute empathy.