Envié una solicitud electrónica. El proceso duró 2 meses. Acudí a una entrevista en Crowdbotics en may 2021
Entrevista
I applied for this position and shortly afterwards scheduled a call with HR. The call was brief and was used to schedule a further two interviews. These interviews went well and they seemed very enthusiastic. This took place on a Friday and I was told "we will be in touch on Monday". I didn't hear anything back for over two weeks, even after I had sent an email asking for an update. This was the first red flag but I decided to continue anyway.
The next step was a take-home coding test where you had to make a simple Django application using their system. Again for the demo, the team seemed enthusiastic. They asked me for feedback on their application and what I would improve. Again I was told, "We will get back to you on Monday". I was ghosted after this. My experience seems to mirror another review on this company.
Here is my theory, they ask you to do a coding test. Once you have the coding test completed they ask you for feedback on their product. They use this feedback to find bugs or improve features and then ghost you after. It is my opinion that they are using job hunters as free testers for their mediocre software.
Steer clear and look somewhere else.
Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Crowdbotics en ene 2023
Entrevista
I was contacted by one of their HR members on LinkedIn. They gave me 2 options, between completing a homework based on their system (badly done by the way, very slow with plenty of bugs), or share something I've already done in the past. I obviously opted for the second option. I've checked their LinkedIn page and seems that there are many fake profiles in their company and curiously most of them are from Asia (India, Pakistan, Nepal etc….), a very strong red flag that the compensation wouldn't be attractive. Looks like they are not interested to hire someone, they just want to show their system and taking feedbacks.
Preguntas de entrevista [1]
Pregunta 1
Is that recommended using the approach you have used in this project. Instead of spreading the payload in different model, why don't you just stored everything in one model field?
