Interview Experience: Angular Developer (Face-to-Face)
I recently attended a face-to-face interview with Speech2Text for an Angular Developer role. I chose to attend primarily to understand and experience startup interview processes differ, as I currently hold offers from Mercedes-Benz and NTT Data.
The interview lasted close to two hours; however, there were no meaningful questions related to Angular, frontend development, or associated technologies. Instead, much of the discussion focused on unrelated areas such as networking concepts (e.g., OSI model) and general topics like LLMs, which did not appear relevant to the role.
At one point, I was asked to “convince them technically.” In the absence of role-aligned questions, it was unclear how to effectively demonstrate frontend expertise. The overall discussion felt unstructured and not aligned with the expectations of a technical evaluation for this position.
It was also concerning that the interviewer, who was in a managerial role, did not appear closely aligned with the frontend technologies required for the position. This created a disconnect between the role expectations and the evaluation process.
During the interview, there were instances where my responses were dismissed with remarks such as “you should go back and clear your basics,” which felt unprofessional in the context of a constructive technical discussion.
Towards the end of the interview, when I was asked if I had any questions, I inquired about the product’s technology stack—specifically whether it was built as a PWA, Electron application, or using another approach. The response I received was simply that “it’s a platform,” which did not clarify the underlying technologies or architecture. This made it difficult to understand the actual technical direction of the product.
During the same discussion, I also asked whether the mobile application was hybrid. The response again was vague, and when I requested clarification, the interaction felt dismissive.
Overall, the interview process lacked structure, role relevance, and clear communication. It did not appear to be a deliberate stress interview, but rather an unstructured and misaligned evaluation.
Suggestion: Candidates should be prepared for a broad and potentially unrelated line of questioning. Those expecting a structured, role-specific technical discussion may find the experience misaligned.
The interview process would benefit from better alignment with the role, more relevant technical questioning, and a more professional and respectful interaction with candidates.
