There were a few stages. Due to my schedule, it spread out over about a month or so.
Stage 1: A take-home coding challenge done in their tool. This was a fun, basic coding exercise to be done in approximately 30 minutes.
Stage 2: A one-hour Zoom call with an engineer on the team. Again, this was coding live in their tool (works well for interviewing due to multiplayer support).
Stage 3: A virtual "on-site", where you spend a day working on a mini-project with them. The morning was a collaborative design session, and the afternoon was a demo to present your work. This was more fun than many big tech on-sites where you repeat the same interview 4-5 times. It felt more realistic.
Q: Three coding questions of increasing scope, complexity, and length.
The following metrics were computed from 2 interview experiences for the Replit Engineer role in San Francisco, California.
Replit's interview process for their Engineer roles in San Francisco, California is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Replit's Engineer interview process in San Francisco, California.