At Render, we’re building the modern cloud platform for developers creating AI-native, full-stack, multi-service applications. Our mission is to eliminate the tradeoff between the power of hyperscalers and the simplicity of developer-friendly platforms—so teams can ship fast, scale reliably, and focus on their product, not infrastructure. Unlike complex hyperscalers or ephemeral edge/serverless solutions, Render offers a developer-first experience with persistent compute, dynamic autoscaling, built-in orchestration, and observability, allowing teams to launch, scale, and manage real-world applications without writing infrastructure code or managing servers. Whether you're building LLM-powered applications, scalable SaaS products, or async processing pipelines, Render empowers teams to move fast and scale confidently from MVP to millions of users. Our platform is trusted by over 7 million developers worldwide and continues to grow rapidly. In February 2026, we raised an additional $100M in Series C financing, bringing our total funding to $260M, to accelerate our vision of making cloud infrastructure both powerful and intuitive—designed for the speed of modern AI development. We’re a diverse and talented team that values craft, velocity, and user experience. If you’re excited to help shape the future of the intelligent cloud and empower developers everywhere, we’d love to hear from you. APPLYING TO RENDER We're seeking candidates who possess high integrity, humility, and an insatiable drive to learn. Through reasoned discussions and continuous feedback, we strive to improve both individually and collectively. We foster an environment of mutual trust and respect, empowering effective debate to achieve the best outcomes for our customers and team. We especially encourage members of underrepresented groups in the tech community to apply and understand that not all successful candidates will meet each requirement listed. Our interview process is unique to each role, and we value the candidate experience just as much as our customer experience. We hope your conversations with us reflect a thoughtful process that is illuminative, enjoyable, and respectful of your time. Render's mission is to eliminate the undifferentiated work that goes into building software products by offering an easy-to-use, powerful cloud platform for developer teams of all sizes. As we grow into the place to deploy AI-native apps and agents, we design for two users at once — developers and the agents working on their behalf. We treat the agent as a first-class customer, not an afterthought: every primitive should feel as considered for an agent as it does for a developer. We're hiring a Staff Product Designer to own Agent Experience (AX) end to end — the whole programmatic surface and the whole loop: an agent deploys, a human reviews what happened, the agent hits an error and recovers, the human grants it exactly the access it needs. Every hop crosses an interface boundary, and today those boundaries show seams. Your job is to design the loop as one product. That takes real craft across every surface an agent touches — the CLI, the API, MCP, SDKs, Blueprints and Skills, and the documentation that teaches an agent how to operate — plus real craft in web UI, because half the loop is a human deciding whether to trust what an agent just did. Most designers are strong on one side of that line; we want someone strong on both. This isn't design following the company's strongest bet; it's design leading it. We think about agent-native design in three areas: the interfaces agents need to operate, the human ↔ agent handoff where a person supervises and trusts agent work, and trust, safety, and governance — how access is granted, scoped, and revoked. This role owns all three. The first two are where the product is moving fastest today, but all three are in scope from day one — the whole point is to design them as one coherent experience rather than three disconnected efforts. You'll inherit real signal to build on: an AX audit and scoring framework, a developer community that already trusts the product, and a design team treating agent experience as a first-class discipline. YOU WILL: - Design the full programmatic interface, not just the CLI. The agent operates Render through many doors — the CLI, the API, MCP, SDKs, Blueprints, and Skills — and they should feel like one coherent product, not a set of independently evolved tools. You'll own the interaction model and the error language across all of them, so an agent can run deploy → verify → debug → iterate without a human in the loop. A one-command path from empty directory to running app matters, but so does an API call an agent can reason about and an MCP surface it can operate reliably. An error message an agent can't parse and recover from is a broken feature, and you'll treat it that way — on every surface. - Design documentation as an agent-facing product. Docs aren't just for humans anymore; they're how an agent learns to operate the platform. You'll design Blueprints, Skills, and reference material that teach an agent to use Render correctly — treating docs-as-experience as a first-class programmatic surface, with the same rigor as any command or endpoint. - Close the human-operated gap in onboarding. Today the default first-deploy path runs service-by-service through the UI — the one thing an agent fundamentally can't operate. You'll design a configuration-first path where the whole system is described in code (Blueprints) and deployed in one motion, so the programmatic loop doesn't break at step one. - Design the dashboard surfaces where agent work becomes visible to humans. When an agent deploys, retries, or fails on someone's behalf, a person needs to see what happened, why, and whether to trust it. You'll design the review, supervision, and activity surfaces for agent-driven work — web UI held to the same rigor as any flagship flow, because this is where confidence in the whole agent story is won or lost. - Design agent auth and access. Consent, scoping, and token management — so a developer can grant an agent or third-party app exactly the access it needs, see what that access is being used for, and revoke it without fear. Least-privilege should feel legible and safe rather than all-or-nothing. This is half policy design, half interface design, and it's where "can I trust this?" gets answered. - Design one model, expressed everywhere. The core objects of the platform — applications, services, environments — should mean the same thing whether you meet them in the dashboard, the CLI, the API, an SDK, MCP, or a Blueprint. You'll design that model once and hold every surface to it, so a human and an agent are always looking at the same product. - Surface the agent-operable paths at moments of intent. Copy-a-prompt CTAs, post-signup CLI install, post-error tooling suggestions. The programmatic paths already exist but aren't discovered — you'll place them where developer intent is highest. WE'RE LOOKING FOR: - 7+ years of product design experience, ideally on developer tools, infrastructure, APIs, or another technical, credibility-driven product. You may have worked as a product designer, a designer who codes, or something harder to label — the title matters less than the work. At this level, we expect someone who has owned a major surface or product area end to end and set the direction others built against. - Craft that spans GUI and non-GUI surfaces. You have an eye for detail that borders on obsessive — the wording of an error, the shape of a command, the structure of an API response, the spacing of a dashboard — and you're as rigorous about a CLI message or an SDK method as you are about a screen. Your portfolio shows strong web UI work alongside text-first thinking: command design, API ergonomics, MCP/SDK design, docs-as-experience, or conversational interfaces. - You design the whole…