I am very glad to hear you liked it :) That's a really good point - I suppose you could rephrase to say "the work that's easiest to discuss achievements in the

I am very glad to hear you liked it :) That's a really good point - I suppose you could rephrase to say "the work that's easiest to discuss achievements in the first round interview is rarely code" Basically, it's hard to explain, even to a technical person, how hard a code problem was, even if your solution was brilliant. But being able to do stuff that isn't code is a really easy way to showing you can 'getting shit done' I actually cover this in my follow-up post, around the difficulty in detecting strong technical proficiency in a short first-round interview.