Some video calls to discuss behavior, general experience, and what you're looking for. Then there is a code challenge where you're given a small Phoenix project and you need to make fixes and extend the functionality. You're not given any timeframe or clear scope for the problem. It's up to you how much you want to sink into this step. Unfortunately, if you don't pass you will recieve about a paragraph summary explaining a few things they liked and a few things that were missing (though not explicitly asked for). It seems clear that they either want you to actually have a lot of Elixir experience or be willing to sink your life into this exercise to write a flawless PR. (They probably spend about 20 minutes looking over it compared to your hours invested).
Pay is location-based so if you're from a "low cost of living country" the pay is probably average for your market so the risk-reward of this process is not great.
Why do you want to work at Remote.com?
The following metrics were computed from 2 interview experiences for the Remote Senior Backend Engineer role in Netherlands.
Remote's interview process for their Senior Backend Engineer roles in Netherlands is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Remote's Senior Backend Engineer interview process in Netherlands.