Take-Home Test: The process starts with a take-home test, which is extremely demanding. You are expected to build a production-ready application with thorough documentation just to advance to the next stage.
First Technical Interview: If you pass the take-home test, the first interview focuses on your submitted project. You will be asked about your approach and may be asked to make small changes to your code.
On-Site Interviews: There are five interviews scheduled in a single day. The first is with the hiring manager, followed by a coding interview, a frontend system design interview, an interview with a product design team member, and then another session with the hiring manager.
I went through all the stages, and I found the take-home test to be particularly demanding. I spent over a week building the project, and just meeting the minimum requirements won’t be enough to pass—you have to go above and beyond.
During the system design interview, the interviewers seemed unprepared and asked vague, open-ended questions. If your answers don’t align with what they have in mind, you may be rejected, even if you're technically strong. At one point, the interviewer was even Googling questions during the interview. Lastly, the hiring manager was not very engaging—he barely asked any questions and seemed to expect me to drive the conversation.
PS: if you have a lot of time to spend on take home test even before speaking to someone then apply to this company
Preguntas de entrevista [1]
Pregunta 1
Leetcode style questions -> debugging and performance optimization questions -> few behavioral questions
They sent me a take home assessment which is a program to write and take about 4 hours to finish, then followed up with a interview go over your assessment
Preguntas de entrevista [1]
Pregunta 1
Finish this assessment and turn in through greenhouse
You have to do a take-home exam. It is a simple API in Go that does some processing. Be careful, they will give you an option to provide a private repo as a submission but then you will receive a rejection email saying that your repo was private and team couldn't review it. This was after I had told the recruiter that I am happy to give the team/reviewer access. Just poor communication in general.
Preguntas de entrevista [1]
Pregunta 1
Write a simple reciept processing API in go. It is super simple if you know how to use hashmaps.
Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Fetch
Entrevista
1st step in the interview process is having a takehome. No interview or call with HR.
You have a generous amount of time to complete it. They perform 'tests' that take up to 48 hours for them to tell you your results.
However, I believe that they completely disregard the takehome results and just choose the best resume.
Given that they are citing 'compliance' reasons for not discussing what could be better, instead of doing the correct thing and wanting engineers to improve, you should avoid doing this company's interviews.