The process took almost one month, and after the second manager interview I got rejected because, as they said, they had doubts about my motivation. The technical interviewers seemed very unmotivated.

At first there was the phone screen. Nothing special. The usual questions. There were 2 home assignments with specified timeframes. * React related questions without using external resources. (45 minutes). *Autocomplete React + typescript component fetching data from async remote server. (90 minutes) Requirements were that it should use React hooks, no external libraries. The input text should be highlighted on the options. Basic CSS, nothing fancy + Bonus for loading external data from a real API. Oh AND a "perfect user experience" - without specifying what that means. Obviously this poor description will mean trying to mind read & interpret the author and will take more than 90 minutes if working from scratch. Be certain other applicants will use external resources to answer questions & use existing code for the AutoComplete & may invest extra time - There is no way for them to enforce those demands. So it's more like a filtering method than actually checking for skills. Apparently there is a lot of “competition” for the position, so there are many applicants (Allegedly). The home assignment was checked 1 full week after I sent it back and I received no confirmation of them even receiving it. I thought at first they had simply ghosted me. I believe they have forgotten about me or ghosted me because they only replied back after I checked with them after a while and admitted to having done nothing. The feedback I got left an impression they barely checked the exercise other than a short glance. According to what I understand some of the perfect user experience includes: - Controllable status of the component - You should ask which they prefer. - Loading external API data may not actually be a good thing. I’m not sure. Perhaps you need mock data and then add an option to use a real API? - Debounce & sanitize user input + fetch - Allow keyboard to move through options and alter options menu scrollbar accordingly - Error handling for failure to fetch data. - Hide options after selection or when leaving component focus - Contrast strongly between background and text colors. - Style & CSS should probably be more than just basic. - Show message to user when data fetch brought no results The reviews regarding the company were not very good, especially regarding their work practices and work life balance so I only wrote a simple basic implementation and didn’t spend more time than the specified timeframe. I didn’t think spending extra time was worth it. I also had a suspicion, especially after their above mentioned "forgetfulness" / near ghosting, that they are so disorganized that each developer evaluates the code differently from the next developer so it could also be a question of luck. I wouldn’t be surprised if 1 developer would evaluate you poorly for a controlled component while another would praise you for it. So you should ask a lot of questions before you implement or use an existing solution. Better yet ask them for an existing example of a "perfect" component to emulate instead of guessing. I also came to realize later that I actually know a guy who now works there in a technical management position who could possibly have had something to do with the review process. The review was negative and my relationship with that other person was also negative. I wonder if that person was involved somehow. But anyway, as long as he’s there I’m definitely not going to have anything to do with Deel and I wouldn’t recommend it to my friends to be working with that person. (If I had known that manager started working there I would not have applied, So I hope others can gain something from this review). It's likewise possible the technical requirements for the coding assignment "perfect" user experience were skewed due to external influence and thus very open to interpretations so a different person might encounter different results.