Candidatei-me online. Fiz uma entrevista na empresa SciTec.
Entrevista
There are three phases to the interview process. The first is a 30 minute phone screen with a manager, then a coding challenge to be completed in C++ or Python, then a final interview with a few employees.
Overall I was told the process would take two weeks. It actually took a little under 2 months. I had to reach out to the HR person rather than them reaching out to me for scheduling, the team interview was a mess (some people just didn't show up for it), and I had to wait a month after the final interview to hear that I didn't get the job despite being told it would take no more than 2 weeks to get a final answer.
Everyone I interviewed with was very friendly and made it sound like a great place to work. It's possible they are just having a hard time dealing with COVID, but this interview experience and total lack of communication left an impression that they do not respect their candidates' time or effort.
Perguntas de entrevista [1]
Pergunta 1
Explain your work history and how it relates to this role
Candidatei-me online. O processo levou 2 semanas. Fui entrevistado pela SciTec em ago. de 2024
Entrevista
Did phone interview and got the coding homework with a week long deadline. Spent a few days on the coding test. After submitting the work, they came back with, sorry, we don’t have a matching position for you. This company does not value your time and who knows what it would be like when you work for them. Steer clear.
Candidatei-me online. O processo levou 1 semana. Fui entrevistado pela SciTec (Boulder, CO) em jul. de 2024
Entrevista
Quick discussion with a recruiter followed by take home coding challenge. I declined the take home challenge because I didn't realize why the salary was so low. I guess they bid really low on the contract and can't offer better salaries.
- Behavioral phone call with hiring manager
- Take home code problem
- In person behavioral / technical that cover take home problem and go over typical interview questions with two onspot OOP challenges.