This is not a night shift
Our clients are in the United Kingdom, and what an engagement needs is roughly four hours of overlap with their working day. It does not need your whole day aligned to theirs.
For most of the locations we work with, that overlap sits inside ordinary working hours. If you are far enough ahead that the overlap would fall late in your evening, we would rather tell you before you apply than place you into something that quietly wears you down.
What the overlap is for
It exists so that decisions do not wait a day. A question asked at the wrong moment in a distributed team can cost twenty-four hours, and three of those in a row is a week gone.
In practice that means being reachable for their morning and early afternoon: the stand-up, the quick call when a decision is genuinely faster spoken than written, and the window where you can unblock someone or be unblocked yourself.
The habits that make it work
Write more than feels necessary. In a room, a shrug carries information. Remotely, it carries none, so the thinking has to be on the page.
Say when something is going to be late as soon as you know, not when it is due. Nobody minds a moved date; people mind discovering it on the day.
Ask early. Engineers who are new to remote work often burn a day proving they can solve something alone. On a client engagement, a half-hour question is almost always cheaper than a day of independence.
The engineers who do best here are not the ones who are never stuck. They are the ones who are visibly stuck early.
You work for yourself, not for a manager
You are engaged as an independent contractor to deliver an outcome. Nobody tracks your hours, nobody watches your screen, and there is no timesheet.
That is a genuine freedom and it carries a genuine expectation. You decide how the work gets done; what is agreed is that it does get done, and that the people depending on it can see it moving.