Envié una solicitud electrónica. Acudí a una entrevista en InVision
Entrevista
I received a request for an interview after around 5 weeks of the application. I provided my availability to the recruiter, but it took 6 days to receive a response (after chasing a couple of times), so I then had to provide further availability.
After some discussion, I discovered that although InVision claim employees can work remotely 'from anywhere', they actually expect the successful candidate for this role to work at least 6 hours between 10am-6pm EST. This would be the equivalent of working night shifts for me.
Ultimately, I was very disappointed with InVision for what felt like a waste of my time. They need to disclose the core hours required on their job site - it is completely unfair to waste the time of applicants.
11
Otras opiniones sobre las entrevistas para el puesto de Lead Software Engineer en InVision
Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en InVision en jun 2021
Entrevista
The interview process consisted of 4 steps. All were interviews with various representatives from the hierarchy of the company. There was a coding exercise and a couple of discussions with team members.
Preguntas de entrevista [1]
Pregunta 1
What were the most interesting projects you worked on?
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en InVision en oct 2018
Entrevista
Applied online in October 2018. The whole process took about 2 weeks.
First had an initial 30 - 45 min recruiter interview. After that we scheduled a 1-hour technical interview with another technical lead. We discussed my experience, the role, and walked through an implementation of a simple SaaS service. The interview ended up lasting 1.5 hours as I had a lot of questions about InVision. After this I was scheduled 2 back-to-back "behavioral" interviews with 2 managers. I thought the first one went very well, and the 2nd went OK. Both asked about dealing with difficult situations and working through issues in the past experience. After this I was scheduled a final 45-minute interview with a director of engineering. It was similar to the manager interviews and I thought this went OK.
Everyone was nice and the recruiter I dealt with ensured a smooth process and was prompt with replies and requests for information on benefits, etc...
The 2 back-to-back manager interviews were pretty similar in structure and content so it's kind of tiring to do repetitive questions and answers twice in a row over a two hour period.
After 5 lengthy interviews where by all indication and from some initial feedback I received during the interviews everything was going well; and as I progressed through it all the way to the final interview I was expecting an offer or at least a discussion about one, compensation and possible role within the company. But in the end I received a generic "no" rejection email without any kind of reasoning or feedback as to why the decision was made.
One weird thing was that near the end of the process they had removed almost all of their engineering positions on their careers page. Since then, a couple of weeks later, they added a bunch of new ones but all of them are more "generic" position descriptions, rather than specific team & role positions they had earlier.
Preguntas de entrevista [1]
Pregunta 1
We walked through an implementation of a SaaS product.
I was asked to give an example of a good manager I had in the past and why I thought they were a good manager, and similarly an example of a bad manager I had in the past and describe why I thought they were a poor manager.
