RudderStack interview questions

The recruitment process lacked clarity and meaningful feedback. The role was presented as Product Engineer, but the interviews were conducted more like for a Software Engineer position, without clearly defining expectations upfront. Before the final round I was asked to have a drawing tool ready. When I asked whether I should prepare for any specific diagram types (for example UML), I was told that if the discussion goes in that direction, I should know UML. This made it difficult to understand what level and scope of preparation was actually expected. During the final round, communication was very challenging due to strong accents and the long (2-hour) format with 2 engineers at once, which made the discussion more exhausting than productive. The most disappointing part was the feedback. After multiple rounds and several hours invested, I received a generic rejection email sent from a “noreply” address the next day, with no additional explanation. I expected at least brief, constructive feedback after such a time commitment.