Join a small, high-ownership team to build agent-facing infrastructure for Cloudinary's media experience platform.
Posted by employer 2 months ago
First seen on Joblaze 1 week ago
Last verified on the company career page 1 day ago
AI in the day-to-day
The developer calling our APIs isn't a person — it's an agent: an LLM, a coding assistant, an autonomous pipeline acting on a human's behalf.
Not disclosed in this posting: compensation, years of experience, work arrangement, visa sponsorship.
Joblaze summary
In this role, the Staff Backend Engineer focuses on enhancing Cloudinary's platform to optimize it for agent-driven interactions, ensuring seamless workflows for automated systems. Key skills include backend development, API design, and experience with SDKs, as the engineer will work on both new infrastructure and refining existing tools for machine users. This position is ideal for a senior engineer with a strong background in backend systems and a passion for innovative technology. The team operates in a dynamic environment, emphasizing ownership and collaboration.
From the original posting
Cloudinary is the media experience platform trusted by millions of developers and thousands of companies — from fast-growing startups to the world's largest brands — to power the images and video behind their digital experiences.
Something fundamental is changing about who uses that platform. Increasingly, the "developer" calling our APIs isn't a person — it's an agent: an LLM, a coding assistant, an autonomous pipeline acting on a human's behalf.
Our Agent Experience (AX) R&D team exists to make Cloudinary the default media layer those agents run on. Our guiding principle is simple: make agentic workflows work flawlessly with no friction.
We're a small, fast, high-ownership team, and we're looking for a Senior Backend Engineer to make Cloudinary work for agents — both by building new agent-facing infrastructure and by reshaping our existing platform for a world where the caller is a machine. Some of this is greenfield. Much of it is taking APIs, auth, and SDKs and making them ergonomic, legible, and reliable for agents.
It’s a problem the whole industry is still figuring out. You’ll help define what great API design looks like when the caller is not a human developer, but an agent acting on their behalf.