Senior Content Engineer

ABOUT THE ROLE

Developers increasingly pick their tools through AI assistants and coding agents. When someone asks ChatGPT, Claude, or a coding agent where to deploy their app, we want Render to be the answer. That depends on content that exists, is accurate, and stays current.

As Render’s Senior Content Engineer, you’ll own the strategy and the system behind that content. You’ll find the gaps in our content catalog based on how Render shows up in LLM and answer-engine results, decide which gaps matter most, and build and run the content factory that fills them. The role sits close to DX Engineering and is fully focused on content. You’ll work directly with the Head of Developer Experience, the DX team, Render’s docs owners, and external content partners.

The primary audience for this content is coding agents and LLMs. You’ll ship focused, technically grounded pieces that help them answer developer questions and cite Render: use-case articles, stack-specific guides, comparisons, and docs. The field is still taking shape, so you’ll test what works and help write the playbook.

This is a remote role within the US, with the option to work out of our headquarters in San Francisco.

WHAT YOU'LL DO

- Own Render’s content gap analysis. Use AEO benchmarks, citation tracking, and AI agent traffic data to find where Render is missing, wrong, or out-cited in LLM answers, and turn noisy signals into clear priorities.

- Turn that analysis into a prioritized backlog across articles, guides, and docs, with clear reasoning for what ships first.

- Build and improve Render’s content factory: the AI-assisted pipelines, built on Render Workflows, that research, draft, fact-check, and assist us in publishing technical content. Test changes with evals and keep the system reliable as output grows.

- Own the review loop. Make expert review faster and cheaper, track factual accuracy, and keep the quality bar high at higher volume.

- Run the refresh cycle for existing content so pages stay accurate as the product changes.

- Manage day-to-day work with external content partners: briefs, feedback, quality, and output.

- Partner with docs owners to expand docs coverage where it drives citations.

- Define and report the metrics that show whether content moves Render’s visibility and signups. Volume published is one input among several.

WHAT SUCCESS LOOKS LIKE

- The content factory is reliable, well maintained, and keeps up as our content needs grow.

- Render shows up more often in agent and LLM answers for the topics the content plan targets.

- Content stays technically accurate, and expert review takes less time per piece as output grows.

- The content plan responds to gaps in our catalog and to what we learn about Render’s visibility in agent and LLM answers.

- We have a plan and a workflow to keep the catalog up to date as the product changes.

WHAT WE'RE LOOKING FOR

- 5+ years in technical content, developer education, content engineering, or software engineering with a strong content focus, ideally at a developer tools or infrastructure company.

- A working understanding of AEO or generative engine optimization (GEO) and how answer engines choose sources. The field is new, so we care about what you’ve built and measured, and how fast you learn.

- Strong working knowledge of AI agents. You use coding agents like Claude Code, Codex, or Cursor every day, and you know agent workloads (long-running tasks, tool calls, sandboxed code execution) well enough to judge whether content about them is correct.

- A builder’s approach to AI. You’ve built content systems in code (scripts, pipelines, LLM and agent workflows) and use evals to understand what a change affects. Comfortable with Python or TypeScript, Git, and APIs.

- Strong technical judgment. You can read a docs page or code sample and tell whether it’s correct.

- Sharp editorial taste. You catch weak structure, generic AI-generated prose, and factual errors fast.

- Comfort owning a system end to end and holding external partners to a quality bar.

NICE-TO-HAVES

- Experience running SEO or programmatic content at scale, especially for developer audiences.

- Experience with LLM benchmarking or answer-engine measurement.

- Experience building agents or MCP servers.

- Familiarity with cloud hosting, deployment, or infrastructure products.

- You’ve used Render before, professionally or on side projects.

PROJECTS YOU MIGHT WORK ON

- Sizing the long tail of developer questions where Render should be cited and isn’t, then building the plan to cover it.

- Adding an automated fact-check stage to the content pipeline that verifies claims against live Render docs.

- Building a refresh system that flags stale content when the product changes.

- Running a recurring survey of LLM answers to measure where Render appears and who gets cited instead.