Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en Filevine en ene 2024
Entrevista
Started with an initial screen with the recruitment team, then followed up with a technical screen with engineering. Third round was with engineering leadership, and finally a conversation with the CTO. Everyone involved was very friendly and conversational, you could tell they believed in Filevine and probably would have made great coworkers.
Preguntas de entrevista [1]
Pregunta 1
Coding problem - collaborative with engineer. Not terribly difficult, but did test some problem solving ability.
Pretty lame experience. I had an interview scheduled at 3:30. The recruiter emailed me 5 minutes before and told me to reschedule since he had a “meeting he could not miss”.
Massive disrespect for my time with no remorse. Job hunting is already a bad experience and recruiters like this make it worse.
Me postulé a través de una recomendación de un empleado. El proceso tomó 4 días. Acudí a una entrevista en Filevine
Entrevista
Started with an online technical screening with some development leadership. This included technical questions as well as a programming exercise.
Then went to another technical/cultural screening with the potential team. This included technical questions and team-fit type questions.
Lastly, a cultural screening with the CTO. This was more of a back and forth interview to get to know the company mission, value alignment, and more cultural fit.
Preguntas de entrevista [1]
Pregunta 1
In an event-driven architecture, how do you prevent infinite update loops?
Me postulé en línea. El proceso tomó 3 días. Acudí a una entrevista en Filevine (Salt Lake City, UT) en sep 2025
Entrevista
Applied online. Interview with HR. Then coding test. I did fine but not perfect so they did not call me back. All LINQ solvable problems. Weak way to test knowledge really.