J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez VSCO (California, PA) en avr. 2025
Entretien
The process was completed in two stages: first, an interview with the manager to discuss experience, background, and expectations, followed by a technical interview that included a live coding exercise to evaluate problem-solving skills, coding quality, and technical knowledge in real time.
Questions d'entretien [1]
Question 1
Can you describe a challenging system you worked on and how you handled scalability and architectural decisions?
J'ai postulé en ligne. J'ai passé un entretien chez VSCO en oct. 2022
Entretien
The initial stages of the interview process at VSCO were quite promising. It began with a well-conducted phone screen by a recruiter, followed by a comprehensive technical interview with the hiring manager. I was particularly impressed by the hiring manager's depth of knowledge across various technologies, which lent a level of credibility and earnestness to the process. The plan was for the process to proceed with a take-home project and a subsequent review in another technical interview. Leaving the conversation, I was optimistic and had been informed to anticipate 'next steps' from the recruiter. However, this is where the process faltered. Despite my proactive follow-up, there was a noticeable lack of communication. A week later, I received a temple-ted rejection email devoid of any feedback. While the beginning of the interview process showcased professionalism and seemed encouraging, the abrupt and unexplained end was not only disappointing but also damaging to the company's brand perception. Such an approach leaves candidates feeling dismissed, with long-term implications that extend to customer relations. As a case in point, I've become disinclined to use or endorse VSCO's products based on this experience, especially given the highly competitive nature of VSCO's niche. A more thoughtful and communicative approach to the candidate experience could benefit all parties involved. This is a problem with the general tech industry and not unique to VSCO, however it's worth noting that VSCO perpetuates this dumb business practice.