Developer Relations / Content Engineer (Growth Engineer)
Fully remote · Full-time · US hours preferred up to $84k · B2B contract preferred The company
This seed-stage startup (based in San Francisco ) builds the infrastructure AI agents use to read the live web. Its API lets agents search for sources, crawl websites, and turn what they find into structured data they can use in their next step. That means developers can build agents that research companies, compare prices, or monitor changes across thousands of pages without maintaining their own browser and scraping infrastructure.
The company has reached $2M+ in annual recurring revenue, and its API already powers the default web-access feature inside an AI automation platform. Users can search and extract data directly in their workflows, with the platform handling API access and billing.
The ambition is to make live web access a built-in capability wherever developers build AI agents. You’ll help decide which platforms to work with and build the integrations that put the API directly into developers’ hands.
The role
You'll build things that make developers stop and think: "I didn't know I could build that."
This is a hybrid role at the intersection of software engineering, technical content, and developer growth .
You'll build real applications using the company's infrastructure, explain how they work, and turn them into videos, tutorials, and technical content that developers actually want to watch, read, and share.
This isn't traditional developer marketing. We don't want throwaway demos, generic AI tutorials, or content written by someone who doesn't understand the code.
You'll own the entire process: from technical idea to working software, compelling explanation, and distribution.
The technical challenge A good demo shows that an API works. A great one shows developers something they didn't realize was possible.
Think research agents that gather and synthesize information across hundreds of sources, monitors that track changes across websites, or automated workflows that turn unstructured web pages into useful data.
The challenge is twofold: build something technically credible,
then explain it so clearly that other developers want to try it themselves.
Your work should hold up beyond a polished video. The code should work, the technical choices should make sense, and the explanation should teach something useful.
What you'll own
- Build real projects: Create agents, research pipelines, monitors, and other applications using the API, SDKs, MCP server, and CLI. Build things developers can actually reproduce and extend.
- Technical video production: Script, record, and edit everything from short product demos to deep technical walkthroughs and launch videos.
- Technical writing: Publish tutorials, implementation guides, and opinionated technical posts grounded in projects you've built and problems you've investigated.
- Developer education: Explain not just how to use an endpoint, but why a particular architecture works, where it breaks, and what tradeoffs matter.
- Developer distribution: Share your work on X, LinkedIn, YouTube, and developer communities. Participate in hackathons and technical conversations, not just promotional campaigns.
- Product feedback: Work closely with engineering. Identify friction in APIs, SDKs, tooling, and documentation, and help turn developer feedback into product improvements.
Who this is for
You're likely a solid fit if you:
- Can build software independently. You're comfortable working with APIs, reading documentation, debugging integrations, and shipping working projects. Previous professional software engineering experience is a strong plus.
- Understand modern AI tooling. You've worked with LLM APIs, agents, tool calling, MCP, or related frameworks, and you're curious about how these systems work internally.
- Can produce excellent technical videos. You can script, record,
and edit content that is both technically accurate and engaging. Being comfortable on camera is a plus.
- Have public proof of work. You've made things and explained them through videos, technical posts, GitHub projects, open-source contributions, or talks.
- Have strong technical taste. You care about clean implementations, useful abstractions, and explaining why you chose one approach over another.
- Know how to communicate with developers. You can make complicated engineering ideas accessible without stripping away the details that make them interesting.
We care more about what you've built and explained than your degree, previous job title, or years of experience.
Why now
AI agents are moving from isolated demos to applications that need reliable access to real-world information.
The infrastructure is still taking shape, and developers are figuring out which workflows, tools, and architectures actually work.
You'll join early enough to shape how developers discover, understand, and build with the product , with direct access to the engineers building it.
For someone who enjoys both writing code and explaining it, this is an opportunity to do both as a core part of the job.
This role is not for you if
- You want to focus exclusively on content creation without writing or understanding code.
- You prefer producing high volumes of generic content over building fewer, technically substantial projects.
- You enjoy building software but have little interest in explaining it, recording videos, or engaging with developer communities.
- You need detailed instructions rather than independently identifying interesting projects and executing them.
Compensation and logistics
- Compensation: up to $84k
- Location: Fully remote. The company is based in San Francisco.
- Language: Fluent English required.
- Role type: Full-time. B2B contract preferred.
About Aurora
Aurora helps exceptional engineers find the right roles at some of the most ambitious startups worldwide.
We work with teams that value technical excellence, high ownership, and the ability to build things that matter.
📌 Developer Relations Engineer (India)
🏢 AURORA
📍 India