Hm, his GitHub profile starts in 2017, before that according to his LinkedIn profile he was a project manager, and since then works as a DevOps guy. Though he w

Hm, his GitHub profile starts in 2017, before that according to his LinkedIn profile he was a project manager, and since then works as a DevOps guy. Though he was already writing SQL migrations in 2008 (from MySQL to SQL Server 2005). ¯\_(ツ)_/¯ It's not terribly surprising to me that he simply doesn't have experience with coming up with architectures on the spot. Doing interviews is hard, from both sides. No candidate wants to seem arrogant by explaining that why the question/task/problem is bad in the context[0], so the frustration remains and gets vented in blog posts. [0] Because roles (job descriptions) in the tech industry is so vague, and goes through so many hands. (HR, recruiter, engineering managers, job portals, etc...) And by the time the interview happens it's no wonder the parties have a lot of mismatched expectations of each other. And that's just the baseline, what the post describes is just plain old fucking shitty behavior in a shit job market.