The message I get out of this post is: &quot;Know what you want, and be uncompromising in your search for it.&quot; If a company is interviewing you wrong, then the company is disqualified from your list of places you&#x27;d like to work. You can draw up a similar list of criteria (e.g. has an open source presence, has a remote-first culture, uses JIRA, doesn&#x27;t use JIRA, has low technical debt, has high unit test coverage) with which you can assess culture&#x2F;role fit.<p>If you find the companies you&#x27;re interviewing with consistently fail your test, then bring your pattern-identifying skills to bear and figure out why. Maybe all of the companies you&#x27;re interviewing at have something in common (they&#x27;re all startups, they&#x27;re all Fortune 500s, the CEO isn&#x27;t technical, the roles are too senior&#x2F;junior). In which case you should break the pattern and apply for work at different types of companies.<p>Or possibly the pattern lies within yourself. Do you consistently fail the same kind of technical tests? Does your answer to a specific question (&quot;Can you show us a large codebase you&#x27;ve worked on? Oh, you can&#x27;t?&quot;) tend to elicit the same negative answer? Then maybe you should focus on strengthening those weaknesses.