There are enough threads comparing the OP and john mentioned in the article. I'll not get into details on that. OPs experience does echo a few of my colleagues,

There are enough threads comparing the OP and john mentioned in the article. I'll not get into details on that. OPs experience does echo a few of my colleagues, who kinda got screwed in the end. A few things I have learnt from other peoples mishaps is that 1. Always be Coding. Keep solving interview / LeetCode problems if you want to pursue SE role. You never know, when shit hits the fan and you're asked to leave. Not being prepared to give interview in a short notice will hurt a lot in the future. 2. Spend the first 90 days understanding team dynamics, culture, execution. I rather observer the first few days and play dumb as apposed to show off my skills, even though I know I could do a hell of a better job that the other guy. 3. If I dont like things going smoothly in first 90 days you should gtfo. I was in teams before, where there were soo many gaming types folks (I personally dont play video games that much) and barely a culture of reading or discussing tech papers. I pretty much realized its not my place and I need to gtfo.