J'ai postulé en ligne. J'ai passé un entretien chez Color en janv. 2021
Entretien
The process included a phone screen with a recruiter, one initial interview, and a four hour "onsite." I was really happy with the speed of the interview process, and the quick response times from the recruiting team to get updates on my application. The whole process took around a month (with two weeks of holiday break in between), and I received an offer within a few days of the final round.
I enjoyed the interview process at Color, all my interviewers were professional, friendly, good listeners, and enthusiastic about the company. The questions were not necessarily algorithmically difficult, but I did feel some time pressure after realizing that they were meant to be two-part - i.e. an initial and then a final step. I thought they were pretty reflective of a typical day at work, especially with some collaborating with the interviewer to talk through the process. Everyone seemed passionate about the work they were doing too, and helping their community.
A side note - as a woman in engineering coming from a company who has issues with retaining female engineers, it was refreshing to see a relatively even split in the gender ratio.
Screening call with a recruiter follow by a technical interview.
The question was the same paint question that others have posted about. The interview seemed to go well, and I solved the problem, and all of the interviewer's test cases. However, I received a rejection e-mail a few hours later.
Overall, seemed to be a waste of time. Seems odd to have just one person be the gate-keeper instead of having a hiring panel like most companies.
Questions d'entretien [1]
Question 1
Create a Painter class. The same question that others have posted about.
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Color (Burlingame, CA)
Entretien
The process consisted of 2 coding interviews, 1 system design interview, and 1 behavioral interview with manager. The interviewers were all friendly and patient. We didn't even compile the code I wrote, we just talked through it.
Questions d'entretien [1]
Question 1
Rest APIs, basic coding (any language was fine), OOP patterns
The interview process started with an informal HR call and then a phone screen. The phone screen was scheduled with a senior engineer but instead someone else joined in with no clue on how to interview. I was not given time for introduction and the interview jumped right into the coding question. They were using Codility platform and I was unfamiliar with the platform. The link to the shared pad was given on the spot so I had no time to get comfortable with the platform. The interviewer offered NO HELP whatsoever even when I explicitly asked "How do I run this?" They said - I'm not sure. So I had to spend time figuring it out by myself and after going through my code and testing it, they mentioned a use case that I missed for which I had to restructure my entire code. I kept asking if I was going in the right direction but no helpful response or hints. The interviewer was just staring at me the whole time.
At the end of the call, I got to know that the interviewer has been been in the company for 6 months so I got no insight whatsoever into the company culture, the team responsibilities, etc.
Overall a very bad experience, I won't be engaging with this company again.
Questions d'entretien [1]
Question 1
MS Paint Question:
Given a canvas (list of lists of str)
1. Paint(x, y, color): do canvas[x][y] = color, keep track of all actions performed here for the undo() & redo()
2. Undo(): undo the last performed action (this can be done multiple times and go as far as the first action)
3. Redo(): redo the last undo action (this can be done multiple times and go as far as the first undo)