Working across time zones from Egypt

I work from Egypt, using Africa/Cairo for scheduling. Availability and meeting times are agreed directly with each team. Cairo's seasonal clock changes are handled by the timezone, rather than a fixed UTC offset.

01 · Agree the working arrangement

A useful remote arrangement states when meetings happen, which work can proceed asynchronously and how decisions are recorded. I do not publish a fixed EU or US coverage promise. Teams should agree the overlap they actually need.

02 · Review the work, including its stage

My portfolio includes owned products, delivered client systems and public developer tools. MedPrüf is an own product. Harmonia is client work. RetailOS and Bridge are paused own projects as of October 2026. Abokamar is collaborative client work: Wael at WO! Studio led design and handoff; I built the CMS, backend and deployment. Public launch is pending.

Those distinctions matter when reviewing fit. A deployed endpoint does not establish current adoption, paid customers or a commercial outcome.

03 · Set scope around a workflow

Start with the operating problem, the information available and a small acceptance boundary. Interfaces, data, integrations and deployment belong in that conversation alongside AI. My current service prices and scope are listed on the work-together page; this article does not compare salaries or promise a geographic discount.

04 · Keep the handoff usable

A remote system needs a clear release path, documented configuration and an operator who can use it. A strong working arrangement makes those responsibilities explicit and records decisions where the next person can find them.