I was interviewed by a single person who took no notes, the Vice President of Engineering, Richard Hill, for the post of Senior Python Engineer. He did a reasonable job of explaining what the company does and asked a handful of questions relevant to the role being applied for but appeared to be completely out of his depth and unprepared for any questions in return. He was cagey giving answers to even for the most basic questions like: how is the company funded, what makes it robust enough that it would survive should a competitor in the legal documents business decide to enter their document analysis market, and how are they preparing to scale. Although questions were invited, several times my questions were rebuffed with attempts to accuse me of not having read the job description - of course I did - I'm sorry but a good potential employee will enquire about the long term viability of a company and especially one that presents what appears to be a weak USP and below-market salaries. He was also keen to stress he had no understanding or trust of the existing technical stack. An odd position for someone who is responsible for looking after it. It was clear that he hadn't read my CV. I would suggest the interviewer actually reads applicants' CVs ahead of the interview instead of wasting time floundering and avoiding simple but apparently unwelcome questions back.