You have the offer. Or you can feel it coming: the hiring manager has stopped selling you on the role and started asking when you could start. That gap between "we want you" and "you have said yes" is the only window in the whole process where you can change how the job actually works. It lasts a few days, sometimes a few hours. Once you accept, remote days stop being a negotiation and become a favour you have to ask for.
This guide is about that window and nothing else. Not finding remote roles, not writing a CV that reads as remote-ready. Just the conversation where a company that has already decided to hire you agrees, in writing, that you will work from home two or three days a week.
The leverage window opens later than you think
Two mistakes sit on either side of it.
The first is raising remote work too early, in the screening call or on the application itself. Before an employer has decided they want you, every requirement you add is a reason to move on to the next profile. You are one of several people on a shortlist, and you have just made yourself the complicated one. Recruiters are not being difficult here, they are filtering, and "wants remote, role is hybrid" is a very easy filter to apply.
The second is accepting first and asking later. People do this because saying yes feels safe, and they tell themselves they will sort out the days once they have proved themselves. It rarely goes that way. The moment you accept, the company has what it wanted. Your leverage was never your talent in the abstract, it was the specific and temporary cost of losing you and restarting a search that has already eaten weeks. That cost disappears the second you sign.
So the order is fixed. Get the offer. Say clearly that you want the job. Then negotiate. Then accept. That middle step is not a tactic, it is what makes the ask land: "I want this role, and I want to talk about how it runs week to week" reads completely differently from a list of conditions arriving by email.
Diagnose what is actually negotiable
Work out which of three situations you are in, because they need different conversations.
A written company policy. The handbook says three days on site, HR enforces it, and your future manager genuinely cannot change it alone. Here you are asking for a documented exception, and you need someone senior enough to grant one.
A team norm. Nothing is written down, but the department drifted into a Tuesday-Wednesday-Thursday rhythm and nobody has questioned it. This is the most negotiable situation there is, and most people never test it.
Manager discretion. The policy says teams decide. Your whole negotiation is with one person, and it holds exactly as long as that person stays in the job. Which is why the written part below matters so much.
You can find out which one you are in before the offer arrives, without signalling anything, by asking the recruiter neutral questions during the process:
- "How does the team currently split the week between office and home?"
- "Is the three-day pattern a company-wide policy or something each team sets?"
- "Is anyone on the team working from another city?"
Then read the language in the ad and the offer pack. "Employees are expected to be on site three days a week" leaves room. "Required", "minimum" and "mandated" leave much less. And look at how the team already behaves. If two people are in another country, the company has already solved the scheduling and meeting-culture problem, which is most of the objection you are about to hear.
Frame it as a performance proposal, not a preference
This is the shift that changes outcomes. A preference invites a yes or no. A proposal invites a discussion about how it would work.
Weak, and very common:
"I have a long commute, so I'd really prefer to work from home three days a week."
Everything there is about you. Your manager has to weigh your comfort against a policy they did not write, in front of a team who all commute too.
Stronger:
"Everything about the role works for me and I want to accept. There is one thing I'd like to build in properly rather than improvise later. The parts of this job I'm strongest at, the deep analysis and the reporting, are the parts I do best in long uninterrupted blocks. I'd like to propose two fixed days at home, Tuesday and Thursday, with the rest of the week on site and full availability on team days. I'd rather agree it now than quietly drift into it."
That version confirms you want the job, names the work rather than the commute, proposes something concrete, and signals that you want clarity rather than a loophole.
Negotiate specifics, not vibes
"Some flexibility" is the phrase that gets clawed back six months later, because it never meant anything. Nail down:
- How many days at home per week, as a number.
- Which days, or an explicit statement that they are yours to choose.
- Core hours you commit to being reachable.
- Who approves it, by name and role, and whether it survives a change of manager.
- A review date if they want one, with what "working" looks like at that review.
- Travel and on-site expectations beyond the normal week: quarterly planning, onboarding weeks, client visits, and who pays for them.
Volunteer the review date yourself. Offering "let's review this after three months against whether the projects landed on time" turns an open-ended concession into something a cautious manager can say yes to.
What you can offer in return
Negotiation is easier when you arrive with something to trade:
- Full on-site presence for the first 90 days. This kills the strongest objection, that new starters learn by being around people. It costs you little and buys the pattern permanently.
- Guaranteed presence on team days. If the department gathers on Wednesdays, be there every Wednesday, including when you would rather not.
- Travel for the moments that matter. Kickoffs, quarterly reviews, client sessions, onboarding new hires.
- A defined trial with a real review against criteria agreed up front.
- Coverage during the office day, handling the in-person escalations when you are in.
Trading remote days against salary
An employer may float this, or you may be tempted to. It can be a good trade and it can be a quiet loss.
It works when what you give up is genuinely smaller than what the arrangement is worth to you, and you have done that arithmetic honestly: commuting costs, hours returned to your week, childcare, whether you could live somewhere cheaper. It works when it is a one-off adjustment at the start.
It costs you when the discount becomes your new baseline. Every future raise, bonus percentage and internal band is calculated from that lower number, and nobody remembers why it was lower. It also costs you if remote days are withdrawn a year later in a policy change and the salary does not come back up.
If you do trade, say the quiet part out loud: "I'm comfortable with that figure on the understanding that the working pattern is part of the package. If the pattern changes, I'd want to revisit the compensation." Then get both halves documented.
Get it in writing
If you take one thing from this guide, take this. Verbal remote agreements die when your manager changes, when a new head of people arrives, or when someone decides the office looks too empty. The person who agreed it is gone, nothing was recorded, and you look like you are inventing a privilege.
Ask for it in the offer letter or the contract. Something as plain as: the role is based at the city office with an agreed pattern of two days per week worked remotely, Tuesday and Thursday unless mutually varied.
If HR says they cannot put it in the contract, do not treat that as a refusal. Standard contracts are often locked. Work down this list:
- A written amendment or side letter attached to the contract.
- An email from the hiring manager, with HR copied in, setting out the agreed pattern before you sign.
- A named exception recorded against the flexible working policy, if a formal request process exists. Ask whether it does, and use it.
- At minimum, your own confirmation email. "Just so we're aligned before I sign: two remote days, Tuesday and Thursday, full presence on Wednesdays, reviewed at three months. Can you confirm that's right?" A written yes is worth far more than a good conversation nobody recorded.
If all four are refused, that itself is information. A company that will not write down something it says it is happy with is telling you how durable it is.
A worked script for the call
Them: "We'd love to have you. Salary as discussed, start date first of next month."
You: "That's great news, thank you. I want to say clearly that I want this job. There's one thing I'd like to settle before I accept, and I'd rather raise it now than let it become a running conversation later."
Them: "Go ahead."
You: "The role is set up as three days on site. I'd like to propose two days at home, Tuesday and Thursday, with Wednesday as my guaranteed team day and full flexibility for client visits and planning weeks. I'd happily do the first three months fully on site so I'm properly embedded before that starts. Is that something you can agree, or does it need to go elsewhere for approval?"
Them: "I'd have to check. Our policy is three days."
You: "Understood, and I'm not asking you to break the policy. If there's a formal route for a flexible working arrangement, I'm happy to go through it. What would help me is knowing whether it's a yes in principle, and if it is, having it written into the offer letter so it doesn't depend on who my manager is next year."
Them: "And if the answer is no?"
You: "Then I'd like to understand the reasoning before I decide. This isn't a demand. It's the one part of the package I want to be clear about, because I'd rather join with it agreed than negotiate it in six months."
That last line is the whole posture: firm, unembarrassed, not threatening.
Handling a no without damaging the start
A no is not automatically a failure, and how you take it is the first impression your manager will keep.
Do not go silent, do not accept with visible resentment, and do not repeat the request in different words. Ask one clarifying question: is this a no for now, or a no permanently? "Is there a version of this that becomes possible after probation?" is completely reasonable, and often produces a softer answer than the first one.
Then decide honestly whether it is a dealbreaker. It probably is if the commute makes the job unsustainable, if you accepted a lower salary partly on the assumption of flexibility, or if you would resent it from week one. It probably is not if the role is a genuine step up, the team already works flexibly in practice, and the policy is under visible review.
If you decline, do it warmly: "The role is genuinely right for me and I'm disappointed, but the on-site requirement doesn't work with my situation. If that ever changes, I'd very much like to talk again." People move companies, and that message gets remembered.
If you accept without it, put a date in your calendar for the conversation and start building the evidence now, so you ask with a track record rather than a preference.
Last thing before you sign: read the offer letter for what it says about location and pattern, not what you remember hearing on a call. If the agreed arrangement isn't there, ask once, politely and in writing. That single email is the cheapest insurance in the process. And if you're holding more than one offer while you do this, the dynamic changes considerably - a companion guide on our blog covers using competing offers as leverage without bluffing or burning either employer.