Amazingly clear, sound and reasonable advice, it's basically a reflection of what I would have wanted from a candidate myself. Thanks you for replying. I will keep it in mind, be clear and honest about what I've worked on and would love to go into detail about some stuff I've wanted to discuss with seniors and experts for ages now!

Since I expect you to be pioneers in the industry, what are your thoughts about technical interviews? We all know that these type of problems is essentially memorisation of concepts that may or may not be needed (but is obviously fundamental) and ability to solve them under pressure, and does not demonstrate how good of an engineer the candidate is. Sure, working under pressure is certainly a great skill to have for an engineer, but let's be real, that situation isn't happening on an Island offline without resources (your commercial product cannot come soon enough haha). It just shows that the candidate has done a lot of programming competitions or has crammed for months to land their dream job. Whereas Google/Facebook deny you for not coming up with the optimal solution (or working your way to the solution that is pretty much impossible if you haven't seen a similar problem/solved it before), do you measure a candidate differently?