Constructor Interview Questions
& Process

First step was an HR screening. Then I met with someone from the AI team. The 3rd step was meeting with a Data team member or Lead. I was forced to do an A/B test with python and data analysis live coding. Completely unnecessary and backwards approach to ask to live code it. This is something which I solved always in my work easily using python and LLM whenever I was forgetting something. Completely no need to force it to live code. I knew all the concepts and answered how to do, just because of few mistakes couldn't implement the code. Very backwards I am a great Data analyst overall solving any problem in work, it wasn't mandatory to ask this.

The whole thing took about a month, with one interview a week. It had four stages plus a trial task. First, I did a case study presentation. Then there was a whiteboard exercise. After that, I interviewed with the PM lead and dev lead. The last interview was with the VP of Product. I liked the people I talked to, they were professional and seemed genuinely interested in discussing things. I got to ask my questions and learn about the team and how they work. It was cool that so many people were involved. They were clear about what to expect at the start, but communication totally dropped off before the final interview. I asked about the format for the last interview and never heard back. So, I was surprised when they asked me to present a project I'm proud of and explain why, and I had very little time. The interview itself was only 30 minutes, so no real chance to present myself well, ask questions, or have a good discussion. After all that, I got a generic rejection email with no feedback, which felt really dismissive after investing so much time over the weeks. I asked for more info, and it took three days to get a response. It's super frustrating to go through so many stages over weeks just to get rejected at the end with hardly any communication. From my side, it was a big time and effort commitment that didn't feel valued.

There were eight interview rounds spanning different departments. The quality of interviews was inconsistent; some interviewers were very professional and organized, while others seemed less prepared and didn't follow best practices for their field. Candidate experience was also an issue, with interviewers being late in about 60% of the meetings, showing low engagement, and usually leaving little to no time for candidate questions. The overall hiring process feels too long and poorly managed compared to industry leaders, which reportedly leaves some positions open for over six months. On the bright side, the team has strong professionals and significant potential; improving operations could help realize it. A COO or Head of People Ops could help address these gaps.

I had two interviews for the Javascript Engineer role. The first was a screening interview where we discussed the company, the role, and my background. The second interview was a one-hour pair programming session with two engineers. They gave me a coding task to complete within a time limit, allowing me to use Google for syntax and ask questions. After the task, we discussed my solution approach and if I'd change anything. Both interviews included time for my questions. The whole process was well-organized, and the interviewers were friendly and supportive, guiding me through and offering help when I needed it.