Me postulé en línea. El proceso tomó 5 semanas. Acudí a una entrevista en FieldRoutes
Entrevista
The recruiter was unprofessional and had attitude. I was told we would have a phone screen. One hour before the designed time, I was told that the position was on hold and I now was given a couple of sample tests to gauge my basic comprehension of some of the technologies that would be used in the position. It took a couple days total to do them both.
Afterwards, I was invited to a face-to-face interview at the company, but I lived far away from Texas and didn't want to spend hundreds of dollars on a plane ticket where I could get rejected anyway. I asked if we could do a Skype interview instead, to which she responded they could have one the following week and asked me for my availability.
And that was it. I tried reaching out to her after, to which I had no response. There was an undertone in her communication where it was unreasonable for me to ask for a virtual face-to-face interview. They need to treat their candidates like people and understand that somethings aren't feasible for everyone.
Preguntas de entrevista [1]
Pregunta 1
They asked me to do a simple 30 minute test online. It was easy.
Me postulé en línea. Acudí a una entrevista en FieldRoutes (Reno, NV) en ene 2020
Entrevista
There was an intro call with someone in human resources and then a technical interview was scheduled. The technical interview is 2.5 hours and consists of some intro time, then 1.5 hours of coding, and then a review of your code.
I was iffy when I heard there was no matching 401k. But I went ahead. I learned during the technical interview that PestRoutes operates with no framework, no CI/CD pipelines, and no tests in place. I didn't wait to hear back from them. I emailed them shortly after and thanked them for their time, but let them know I was not interested.
I've seen enough home-brewed architecture to know I don't want that again. Couple that with no CI/CD or tests is a hard no. It could be a great place to work. I have no idea of course and just having those things doesn't make everything perfect. But I'll take my chances elsewhere.
A note if PestRoutes reads this. I think code exercises can be a valuable way to weed out candidates that don't fit your technical criteria. I personally don't find the pressure of doing X in Y time conducive. It's not how most developers code and therefore is not a natural assessment. If it's working for you then certainly keep it. I would go a different route.
Me postulé a través de una recomendación de un empleado. El proceso tomó 1 semana. Acudí a una entrevista en FieldRoutes en may 2019
Entrevista
You will talk directly with CTO and participate in coding challenge. The test can be written in any language of your choice. The test is not too hard but you must cover all cases possible
Preguntas de entrevista [1]
Pregunta 1
Programming challenge about date processing. You can use any language you like, as long as the date fit requirement
