The opportunity
Render is looking for a Staff Developer Relations Engineer to grow usage and word of mouth for Render among developers building full-stack and AI applications. You'll be Render's technical face on stage, in workshops, at meetups, and in the developer and AI ecosystems where our users build.
What you'll do
Represent Render at conferences, meetups, hackathons, podcasts, and: livestreams, with talks and live demos on building and running AI agents and full-stack apps.
Design and run hands-on workshops and hackathons, from the curriculum to the technical setup behind them.
Set DevRel's technical direction: pick the communities, ecosystems, and events worth investing in, and define what good looks like for talks, workshops, and demos.
Be the technical counterpart for ecosystem partners such as AI frameworks,: agent tooling, and open source projects: joint workshops, co-hosted events, and the integrations worth building together.
Go deep in technical communities on GitHub, X, Discord, Reddit, and Hacker: News. Answer hard questions, debug real deployments, and show up where Render has a credible voice.
Run the developer feedback loop. Turn what you hear in the field into clear,: prioritized input for Product and Engineering, and follow it through until it ships.
What they're looking for
- + years in developer relations, solutions engineering, or software: engineering, including at least 3 years in a developer-facing role at a developer tools, cloud, or infrastructure company.
- A track record on stage: talks at recognized developer conferences, and workshops you designed and ran yourself.
- Experience setting direction for a developer relations program: choosing where to invest, measuring what worked, and changing course.
- Hands-on fluency with AI agents: tool calling, MCP servers, LLM APIs, and agent frameworks. You can build a working agent app live and explain what it needs to run in production, such as long-running tasks, sandboxed code execution, and retries. The field is young, so we look at what you've done recently. We don't expect years of experience in it.
- The engineering depth to be credible with senior engineers. You can deploy a: multi-service app, read logs, trace a failed deploy, and find the root cause in front of an audience.
- Working knowledge of cloud infrastructure: containers and Docker, networking basics, CI/CD, environment configuration, and infrastructure as code.
- You use coding agents like Claude Code, Codex, or Cursor every day and keep: up with the agent ecosystem as it changes.
- Examples of developer feedback you turned into product changes: what you heard, the case you made, and what shipped.
