Code and Theory Interview Questions
& Process

The interview process was good and went well. Everyone was nice. There were 6 rounds in total. They asked questions about my experience, and about market and product trends. It was mostly behavioral questions. It's a great company with good employees and good HR. Everything was fine.

The interview process spanned 4 weeks and included 5 distinct interviews. I found it confusing because the role's responsibilities were described differently in each interview. After completing all the interviews, no feedback was given on why I wasn't offered the position.

The interview process included a recruiter call, followed by a conversation with the manager, and then a final round with the head of engineering. The discussions were mainly about the team's working process, and while they might ask a specific question related to your profession, it won't be overly difficult.

The interview process was efficient and well-organized, consisting of multiple rounds. First, I had an introductory call with HR, which mainly focused on my experience and alignment with the company's culture and goals. This was followed by a technical interview where I was asked relevant questions about CRM, project management, and leadership scenarios—areas aligned with my experience in the technology industry. The interviewers were friendly, and the questions were more conversational than intimidating. It felt like they were more interested in how I would approach challenges rather than testing only technical skills. The final round was with senior leadership, where we discussed the company’s direction and how my role would fit into that vision. Overall, the process was transparent, and while I appreciated the follow-ups from HR, I believe the communication could be more proactive. Sending updates on the application status regularly, rather than only in response to inquiries, would provide applicants with clearer expectations and reduce uncertainty during the process.