You keep applying to US remote roles that match your stack and your years of experience, and the applications just disappear. No feedback, no interview, nothing. After enough of that you start to wonder whether the problem is your skills or whether something is going wrong long before anyone opens your GitHub.
Most of the time it has nothing to do with how you write code. The CV is what stops you. Developers outside the US usually write their CVs for the local market or for general international applications, and US hiring managers read with a different set of filters than the ones those CVs were built for.
Local conventions create friction in the first second. A photo, a date of birth, a marital status line, or a long personal summary at the top tells a US reader the document was not prepared for their process. They do not need any of it, and seeing it there often reads as a sign that the candidate has not worked out how US companies actually evaluate people.
Task lists make it worse. When the top half of the page is a description of responsibilities rather than what you shipped and what changed because of it, the reader moves on. US screeners are trained to look for concrete impact on the first pass, and when the impact is missing from the page they tend to assume it was missing from the work too.
