I applied online.
Intro calls, then a coding technical, which was a pretty good experience. I was presented with a simple, yet realistic, problem and got to solve it "open-book" style. No Google-style brain teasers, and not the sort of thing you can study for. Finally, a discussion interview in which I was asked to explain the most complex project I'd worked on in the past. The questions were mostly behavioral. I was rejected at this stage for technical skill reasons. They likely intend this stage to screen for good communication skills and problem-solving experience, but I suspect it also screens for very-recent experience with super-hairy FAANG-scale problems. I recommend that you pick an experience which is fresh in your mind.
Be prepared to talk about it at every level of detail, with elaborate anecdotes from every angle you can think of - design, technical, process, decision-making, outcomes, maintenance, etc. Overall, the process felt reasonable and not onerous. I rate my experience as negative only because I didn't feel they made their expectations for the discussion interview clear.
Describe, at length, the most complex project you worked on.
The following metrics were computed from 1 interview experience for the Render Backend Engineer role.
Render's interview process for their Backend Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Render's Backend Engineer interview process.