Design Engineer

You live in the browser, in code, in the space between "it functions" and "it feels inevitable." You build the interactions, the transitions, the animations, and the components that make Rho feel like the most considered product our customers use all day. Then you write the libraries that let the rest of the team hit that bar without you in the room.

This is not a product design role. You're not writing PRDs, running discovery, or owning a roadmap. You're the person who takes something that works and makes it sing, and who builds the systems that make singing the default.

If you've ever reimplemented an animation three times because the first two were 40ms too slow and felt cheap, you already understand the job.