We look at hundreds of CVs from devs applying to remote positions at Howdy, and the pattern repeats: React, Node, Docker, Kubernetes, AWS, 6 years of experience. That CV is indistinguishable from 40 other candidates with the same stack. The problem isn't the experience, it's that a list of tools says nothing about whether you can work without someone reviewing every single decision you make, which is exactly what a US team needs from a senior remote dev.
A hiring manager filling a remote role isn't looking for your stack, they're looking for a signal that you can operate with real autonomy: making a technical call in the face of ambiguity and owning the outcome without anyone looking over your shoulder. That signal isn't in your list of technologies. It's in how you tell the story of what you did.
The difference between listing tasks and showing judgment
Compare these two ways of describing the same thing. Version one: "Developed REST APIs with Node.js and Express, worked with PostgreSQL databases, participated in code reviews." Version two: "Designed the migration from a monolith to three microservices after the team determined weekly deploys were generating too much risk; split off the payments service first because it was causing the most incidents, and cut deploy time from 40 minutes to 6."
The second version doesn't mention any more technologies than the first. It mentions a decision, the reason behind that decision, and a measurable result. That's what a US remote team reads as "this person can operate without me having to explain what to do every step of the way."
Tell decisions, not responsibilities
For every job you list on your CV, ask yourself: what decision did I make here that someone with less judgment wouldn't have made the same way? If you built a feature by following a ticket with step-by-step instructions, that's not the story worth telling. If you had to choose between two possible architectures, justify why you picked one, and own it when things didn't go as expected, that is.
You don't need to have been a tech lead to have these stories. A mid-level developer who decided how to structure a module, or who identified and fixed a performance bottleneck without anyone asking them to, already has material. The key is naming the decision explicitly, not burying it inside a generic task description.
Numbers that matter (and the ones that don't)
Years of experience matter a lot less to a remote team than the size of the problem you solved. "8 years of experience" is a demographic fact. "Cut load time on a 200,000-active-user app from 4.2 to 1.1 seconds by fixing N+1 queries" is evidence. If you can quantify the impact of what you did, users affected, time saved, incidents avoided, cost reduced, do it. If you don't have the exact number, an honest estimate beats leaving it out.
Watch out for the opposite extreme: padding your CV with inflated metrics is easy to spot in a technical interview, the moment someone asks you to explain how you got to that number. One well-explained example carries more weight than five bullet points of achievements you can't back up in a ten-minute conversation.
What a US team needs to see before the interview
Before investing 45 minutes in a technical interview, a remote hiring manager wants to reduce the risk that async communication and the lack of direct supervision will become a problem. That means your CV should answer, even if only implicitly, three questions: have you worked on a distributed team or across time zones before, did you make technical decisions without someone validating them in real time, and is your written English clear enough to avoid friction in a Slack thread?
If you have previous remote experience, even if it was partial or freelance, prioritize it. If you don't, look through your in-office experience for moments when you collaborated asynchronously with another office, coordinated with a distributed team, or solved a technical problem without direct supervision, and tell that story with the same level of detail you'd use for a technical achievement.
Format: scannable in 15 seconds, not impressive
Your CV's design matters less than you think, but it's not irrelevant. ATS (Applicant Tracking Systems) filter it before a human ever sees it, so you need a simple structure: clear sections, no nested tables or graphics the parser can't read, and the job's keywords worked naturally into your experience descriptions, not tacked on at the end in a separate list.
Once you clear the automated filter, you get somewhere between 15 and 30 seconds of real attention from the person reading it. Put your GitHub or portfolio link at the top, not the bottom. If your repo has recent commits and a clear README, that's worth more than any certification you could add to your CV.
The mistake that ruins the most senior CVs: misplaced humility
We've seen dozens of CVs from devs with seven or eight years of experience describing their work with the same timid language someone would use in their first job: "collaborated on the development of," "took part in the implementation of," "helped improve." That language hides exactly the information a remote team needs: who decided what.
It's not about exaggerating your role either, just being precise about your actual responsibility. If you led the decision, say so: I decided, I designed, I implemented. If you contributed to someone else's decision, be specific about what your contribution was. Vagueness doesn't make you look modest, it makes you look interchangeable.
A CV that lists tools puts you in the same pile as hundreds of candidates with a similar stack. A CV that shows decisions, context, and results pulls you out of that pile, because it gives the recruiter the one signal that actually matters for a remote position: that you can operate with your own judgment without anyone needing to review your work line by line.
