First stage phone interview - 30 minutes - most clueless team you could meet... Second stage phone interview - 30 minutes - most clueless team you could meet. They use a triplestore that doesn't require any inference - like what is the point of using a triplestore then? You can then literally use any graph store. They have an ontologist - so what is the point of hiring a knowledge engineer then? They have a data scientist - so what is the point of hiring a knowledge engineer then? Made me wonder if the entire organization hires technically clueless people. Also, 30 minutes is a very short time for interviews. Oddest bit is the number of times I had to repeat myself, they couldn't even be bothered to read the CV, I had to explain everything that I had stated in interview again in an email....the architect was even more clueless just kept passing silly assumptions? why interview if you want to spend the time making assumptions about the candidate? In fact, they have multiple other teams doing the same types of work, but can't be bothered to reuse/share. After the interview, it felt like the organization is disorganized and badly managed. And, teams are technically clueless at best with a lot of internal politics and red tape.