You think the rejections are about your country.
So you start thinking about hiding it. A European city on the CV that isn’t yours. “Remote (Europe)” where the address should be. A country dropdown filled in with wishful thinking.
Don’t.
Lying about where you live is the fastest way to lose an offer you already won. It surfaces at contract stage, when payroll needs a tax residency, a bank account, and an address matching your ID. That is the worst possible moment to be caught. You don’t just lose the job. You lose the reference, and the recruiter who was one week away from introducing you to three other companies.
There is no version of this where the lie holds.
But your instinct isn’t stupid. You noticed something real. Your location does change the conversation.
It just doesn’t change it the way you think.
The variable isn’t secrecy. It’s order.
At a company that already hires remotely, your location is rarely a disqualifier. It’s an input.
The question is what it’s an input to.
Named early, before anyone has a view on your work, your country is a pricing input. It’s the first fact in the file. Everything after it gets read through it.
Named later, after two people have already argued you’re the strongest candidate, it’s a logistics detail. Someone has to sort out contracting and hours. Mildly annoying. Entirely solvable. Not a discount.
Same fact. Same honesty. Completely different job.
You aren’t hiding anything. You’re deciding what goes first.
What your country does to the number
Negotiation researchers have measured this for decades.
A meta-analysis by Orr and Guthrie found a correlation of roughly .50 between the opening offer and the final agreed number. In one widely cited experiment by Galinsky and Mussweiler, the correlation between the first offer and the settlement price reached .85 — reported in a review of first-offer and anchoring research in Negotiation and Conflict Management Research.
Read that again. The first number in the room drags the last number toward it.
Your country is a number wearing a disguise.
That’s because of how remote pay actually gets set. Ravio, a European compensation data platform, lays out three models companies pick from: fully location-based pay benchmarked to each local market, geographic differentials that apply a multiplier to an HQ baseline, and location-agnostic pay that pays one rate everywhere.
Two of those three convert your address into a multiplier.
That’s the machine. Not prejudice. A spreadsheet.
And the spreadsheet is moving. Buffer published its own numbers when it cut from four cost-of-living bands to two: salaries went up for 55 of 85 team members, by an average of $10,265, with a stated intention to remove the cost-of-living factor entirely. One company. But it’s the direction you’re arguing in, and it isn’t a fantasy.
The multiplier itself is a separate fight, and I’ve written it up in /we-pay-local-rates/. This post is about the step before that fight: not handing them the multiplier before they’ve decided they want you.
The rules on who asks what are shifting
Something else moved in your favour.
The EU Pay Transparency Directive (2023/970) says applicants have the right to information about the initial pay or its range for the role, given “in a published job vacancy notice, prior to the job interview or otherwise.” The same article states: “An employer shall not ask applicants about their pay history during their current or previous employment relationships.” That’s Article 5, verbatim.
The company names the range first. Your history is off the table.
Now the honest part, because overstating this helps nobody. The transposition deadline was 7 June 2026, and most member states missed it. Law firm Littler reported the day after that only Slovakia, Malta and Italy had fully transposed, with Germany and Austria yet to publish implementing legislation — and noted that until a member state writes it into national law, workers can’t bring claims based on the Directive itself.
So this isn’t a card you play. It’s a norm you stand on. The same norm has been spreading elsewhere for years: HR Dive tracks 22 statewide and 24 local US bans on pay history questions.
None of that is legal advice. It’s weather.
What you do with it is simple. A recruiter asks what you currently earn. You ask for their range instead. That isn’t evasion. That’s the direction the entire market is walking.
Give this. Hold that.
Give: your country. Your city, if asked. Your time zone. Your overlap hours. How you can legally be engaged — contractor, employer of record, your own registered entity. Whether you’ve done this before.
Hold: nothing.
You hold nothing back. You just don’t lead with it.
There’s a real difference between a fact you’ll answer instantly and honestly, and a fact you volunteer in the first line of your CV summary. One is integrity. The other is bad sequencing.
And there’s one thing you never say. Ever.
Never tell them you’re cheaper.
Not “cost-effective.” Not “competitive rates for the region.” The second you sell the discount, the discount becomes the product. You’ve told them the best thing about you is your address, and every conversation after that is about how much less. You also stop competing on the thing that wins — which is exactly the mistake I break down in /competition-isnt-berlin-its-krakow/.
Your skills are underpriced by geography. That’s a mispricing to correct, not a feature to advertise.
The moments it comes up — and the exact words
One pattern runs through all of these: answer fully, give one piece of evidence, redirect to the work.
Never evasive. Never apologetic. No “unfortunately.”
On your CV
Country in the header. One line. No apology, no explanation.
[Your name] — Senior Product Manager Manila, Philippines (UTC+8) · 4–6 hours daily overlap with CET · fully remote for 5 years
Your country is right there. And it’s immediately followed by the thing that answers the real question. Because the reader isn’t asking where you are. They’re asking whether this works.
You answered both in one line, then moved on.
Keep it out of your summary paragraph. That space is for what you’ve delivered.
The first recruiter call
They’ll ask. Usually inside the first four minutes. Answer it like it’s the weather.
“I’m in Ho Chi Minh City, UTC+7. I work 2pm to 10pm local, which gives me a full overlap with the Berlin team through their whole afternoon. I did the same for two years at my last company — my manager was in Munich and we never had a scheduling problem. Where’s the biggest gap on the team right now?”
Three moves. Full answer. One piece of evidence. A question back about the work.
That last question does the heavy lifting. It closes the location topic and hands them something better to think about. If you want the longer version of that evidence, it’s in /timezone-is-not-a-problem/.
The “just curious, where are you based?” aside
Mid-interview. Casual tone. Dropped between two technical questions.
It isn’t an ambush. It’s small talk. Treat it that way.
“Kuala Lumpur. Eight hours ahead of you — I’m usually online until your mid-afternoon. Anyway, on that migration question…”
Short. Warm. Back to the work in one breath.
The length of your answer teaches them how big a deal it is. A forty-second answer with three caveats says there’s a problem here. A nine-second answer says there isn’t.
After the offer arrives
Now location is a contracting question. Now it’s safe, because they’ve already decided.
“Great — and I want to make this easy on your side. I can be engaged through an employer of record, or as a contractor with my own registered entity, whichever your finance team prefers. I’ve worked both ways. On the number: the range you shared sits below where this role benchmarks in your market, and my output isn’t discounted by my postcode. Can we talk about [number]?”
You solved their problem before raising yours. That’s the whole trick. The full negotiation sequence lives in /negotiate-european-salary-from-southeast-asia/.
When the form makes location mandatory
Sometimes there’s nothing to sequence. The application form has a required country field and a red asterisk.
You fill it in truthfully. Every time.
That doesn’t break the strategy. It compresses it.
A form isn’t a conversation. Nobody negotiates with a dropdown. That field goes into a database, and the pricing discussion happens weeks later, with a human who has read your work by then. What you’re protecting is different: your voice, naming your country first, in a live discussion, before anything else about you has landed. A form field isn’t your voice.
So fill it in. Then put your evidence next to it. If there’s a cover letter box, spend exactly one line:
“I’m based in Jakarta (UTC+7) and work a CET-aligned schedule — my last two roles were fully remote with European teams. The rest of this is about the platform migration you mentioned in the ad.”
One line. Then never again in the document.
If a form demands your current salary and won’t take a blank, give your target range labelled as a target, or the smallest true figure the field accepts. Don’t inflate a number. A fabricated salary is the same category of error as a fabricated address — it’s a claim you’ll be asked to back up with a document.
And yes, some forms screen you out by country outright. That happens. It’s usually about payroll entities and data rules rather than you. That’s a filter, not a verdict. The fix is to spend your applications where hiring outside the EU is already normal: companies with an employer-of-record setup, or an existing distributed team on three continents.
What actually happens in the room
I sit on the hiring side at a European tech company, so here’s how location shows up in a shortlist conversation.
It comes up once, and it comes up as feasibility. Can this person be employed here? Do the hours work? Who handles the contract? Thirty seconds, and then the discussion goes back to the work.
The pricing conversation is a different meeting. Often different people. And it happens after the shortlist is already set.
Candidates who lead with their location drag the pricing question into the feasibility meeting. Now one conversation is doing two jobs at once — and when that happens, the cheapest answer wins by default.
That’s the real cost of bad sequencing. Not rejection. Compression.
The short version
Never lie about where you live. It gets found, and it gets found at the worst moment.
Put your country on your CV, with your overlap hours right beside it.
Fill mandatory fields truthfully.
Answer the question fast, once, with evidence, then redirect to the work.
Never sell yourself as the cheap option.
And keep the money conversation until after they’ve decided they want you.
Ten years in Southeast Asia. Three remote jobs. Three promotions. I have never sat in the same office as my boss, and my pay more than doubled across that run.
Not one of those companies hired me because of where I live.
A couple of them nearly priced me by it. What stopped them was when they found out.