J'ai postulé via une autre source. J'ai passé un entretien chez Scratch Services
Entretien
Found profile through hired.com
1. 1 hour coder pad: Same question used. Look up the company name in leetcode I found it in a discussion thread. The person asking the question was very poor in her interviewing skills. I had to teach her a thing or two regarding time and space complexity.
2. Moved to onsite stage. First HR call highly unprofessional and funny. The person didn't have HR experience since they moved from a product? sales? role to HR role. Mentioned he had no interest in my answers but he had to ask because of process. okay...
3. Technical screen: Not your typical coding interview. They allow google and basically use logic to use time delta (use time library) to charge a person rent every month after due date etc.
4. Design a transaction system with an archaic system. Payments? Something similar. Very junior person asking system design questions which makes it tough for them to understand your solution.
5. Hiring Manager call: Uninterested. Couldn't wait for it to get done.
6. Ghosted after the onsite. No response.
Nice people, but their process is not mature enough.
Run of the mill tech interview process. There were 2 tech screens and 1 basic systems question. They also included a cross functional interview.
Everyone was very nice and I enjoyed meeting the team a lot.
J'ai postulé via une autre source. Le processus a pris plus d'une semaine. J'ai passé un entretien chez Scratch Services (San Francisco, CA) en juill. 2020
Entretien
I was approached through a hiring site (vettery) in the middle of the summer. I was looking for a small company where the challenges are not fully defined and there is more impact. My journey consisted of 3 parts:
* Take home challenge, which I enjoyed and removed the pressure of talking through implementation and feeling judged (gave me a chance to explore new tech as well :D)
* Virtual on-site was great and I appreciated the flexibility. It was broken down into 2 parts: 1) problem solving, and design 2) culture and fit, and deep dive on previous projects. Those were done in 2 separate days, which I loved! It made me realize that they are thinking about the candidates’ state of mind (we are not going on-site, so there is room to have the interviews in different days).
* One extra coding practice (they wanted more data points for problem solving that was not easy to deduce from the take-home challenge)
I learned a lot about the teams’ chemistry during my interviews. I really enjoyed the conversations and they gave me the confidence to go through the interview without feeling judged.