The opportunity
Render’s mission is simple: eliminate the tedious work of building software by providing a cloud platform that just works.
What you'll do
Make a multi-service system legible at a glance. Design the views that let a: developer see how their services connect and depend on each other, instead of stitching the picture together one service at a time. This comprehension gap is where design can make a complicated system feel cohesive and friendly.
Design system-level observability. Aggregated logs, metrics, deploys, and: events across a whole project, filterable by environment and resource — so a developer can answer "what's going on with my system" in one place. This is high-density information design where hierarchy, scanning speed, and progressive disclosure are the whole game.
Design deployment as a coordinated act. When an application has many: services, coordination gets hard. You'll design cross-service deployment and rollback, and a preview model so shipping feels safe at any scale.
Design and consider all product states . You'll own the "unglamorous": moments. Like build errors, failed deploys, and empty states, and turn them into helpful experiences. Since developer tools earn their reputation by how they handle problems, your focus is on guiding the user to success even when things go wrong.
Own a first-run experience worth recommending. The path from signup to first: successful deploy is where trust starts. You'll design it so that a developer's first ten minutes make them want to tell someone.
Contribute to where the platform goes next. Alongside the shipping work,: you'll bring concept explorations and a strong point of view to a design-led discovery track, shaping the platform's future through a weekly critique cadence with the rest of the team.
What they're looking for
- + years of relevant experience. Whether you’ve worked on developer tools,: cloud infrastructure, or another complex, high-stakes product, we care more about your impact than your title.
- Exceptional taste and craft. You have an eye for detail that borders on: obsessive — typography, spacing, motion, density, interaction feedback. You notice when something is 2px off and it bothers you, and you've shipped work other practitioners admire.
- Strong information architecture. You can take a tangle of objects and: relationships and make it feel like one obvious thing.
- You design the whole journey, not a screen at a time. Your portfolio shows a: user carried coherently across every surface a feature touches — entry point to empty state to failure to recovery — not a set of polished screens that don't add up to a system.
