J'ai postulé en ligne. Le processus a pris 6 semaines. J'ai passé un entretien chez Remote (Seattle, WA) en août 2023
Entretien
Very long and drawn out, it took weeks. Two soft interviews one with a recruiter, one with an engineering manager, and then what I thought was going to be a technical interview The soft interviews were what you expect, just an informal ~40 min conversation getting to know the other person a little better. These went extremely well. The supposed technical interview was were things went wrong. In business there is a saying that A people hire A people, and B people hire C people. They sent their B people to the interview and I could tell because they were confused by a lot of basic concepts in server side engineering and didn't seem like they had ever really conducted a technical interview before. I don't feel bad about not getting an offer if anything I feel great about not having to work with these people and waste a lot of time teaching them basic stuff like how to not put your cache in memory on your node so that you don't have reliability or performance problems that negatively impact your user experience every time you deploy. I really wish the the company the best of luck and hope that there are people in the organization making good technical decisions for the benefit of the company.
Questions d'entretien [1]
Question 1
There wasn't really a challenging interview question anywhere to be seen in the entire process. The technical interview was very soft and the interviewers didn't seem very confident in asking questions or having a technical discussion. It was a lot like being interviewed by a bunch of junior engineers. What it really boiled down to is that there was no personal chemistry between myself and the interviewers. They didn't like my style, and I really didn't much care for theirs either. The problem for the management of the company is that this kind of filtration and selection process might produce a group of people who can get along in an elevator, but it is not going to secure you the kind of engineering talent you need for when things get hard.
We appreciate your candid feedback and will take it into consideration to improve our interview process.
Candidature
J'ai postulé en ligne. J'ai passé un entretien chez Remote
Entretien
1. HR interview, 2. Manager interview, 3. Take-home assignment, 4. Team interview about the assignment, 5. Head of engineering interview.
I got up to the team interview stage, after which I received a rejection. I went above and beyond to complete the take-home with many extras, only to be rejected on a single botched requirement. I find that to be disproportional relative to the expectations and quality level of the entire assignment, and I feel that my time has been wasted.
My advice to candidates is to make sure you hand in a flawless assignment, if you really want to work there.
Questions d'entretien [1]
Question 1
Build an Elixir-Phoenix application to show what you know.
We're sorry to hear that you had a negative experience. We aim to provide all candidates with a positive and meaningful experience, and we apologize if this was not the case. We will be taking your feedback on board and making changes to ensure that all candidates feel valued and engaged in the future. Thank you for your honesty and for helping us improve.
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.
Thanks for your review. We're sorry to hear that our rejection feedback wasn't as helpful as it could have been. We strive to provide valuable feedback to all candidates, and we'll use your input to improve our process. We appreciate your honesty and wish you the best in your future endeavors.
J'ai postulé en ligne. Le processus a pris 2 mois. J'ai passé un entretien chez Remote en sept. 2024
Entretien
Pros:
- Excellent product offering
- Friendly and competent interviewers
Cons:
While the product and culture at Remote.com are commendable, there are significant issues with how the company plans and budgets its hiring processes. As an HR-focused organization, it’s disappointing to see interviews being dropped or frozen after candidates have invested two months and reached the final stage. This lack of consideration for candidates’ time reflects poorly on the company’s planning and communication.
Additionally, during the interviews, it was mentioned that the company is dealing with a substantial amount of tech debt, which appears to be causing challenges now. While this might hint at broader financial issues, it’s worth noting that the product and overall culture remain strong. However, I hope Remote will prioritize more efficient hiring processes and greater respect for candidates in the future.
Thank you for your review. We're sorry to hear that your experience with our recruitment team was not up to our usual high standards. We are always looking to improve candidate experience at Remote so we appreciate you bringing this to our attention.