Render’s mission is simple: eliminate the tedious work of building software by providing a cloud platform that just works
We’re evolving from the go-to platform for solo developers into the backbone for fast-scaling teams. As our users’ apps grow from a single service into complex, multi-service architectures, our biggest challenge is keeping it all feeling simple. We need a Product Designer to take that "pile of parts" and turn it into a cohesive system that actually makes sense
This is a craft-focused IC role, and it's web UI at its most demanding. You'll own the surfaces developers depend on when the clock is ticking and things are breaking. Designing for infrastructure is unique: your screens see the most traffic when the user is most stressed, and "failure" is a first-class state, not an edge case. We’re looking for someone who finds that responsibility energizing
You’ll join a design team that takes its craft seriously, with weekly critiques and deep cross-functional collaboration. You’ll thrive here if you love untangling complex, messy problems and turning them into accessible, beautiful experiences
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