Tips on working a remote corporate job while cruising

Remote work from a moving sailboat isn't an aspiration anymore. It's infrastructure. And the infrastructure fails.

TLDR

• Satellite internet has changed what's possible, but bandwidth throttling, power consumption, and complete signal blackouts remain real operational constraints
• Your corporate workflow must assume intermittent connectivity and rebuild around store-and-forward protocols, not live collaboration
• Time zone drift and the cognitive load of passage making will wreck your performance if you don't design deliberate separation between ship operations and screen time

I know a sailor who quit a six-figure consulting gig three weeks into a transatlantic crossing. Not because the Starlink failed. Because it worked just well enough to keep him tethered to Slack channels and Zoom standups while he was trying to reef the main at 1300 in a building sea. The technology worked. The human collapsed.

The promotional materials show someone typing on a laptop in a cockpit with a sunset behind them. That photo was taken at anchor. You will not be working while underway on a passage longer than an overnight coastal hop. Your job is to sail the boat. If your employer expects you to be responsive during a delivery from Bermuda to the Azores, you have the wrong employer or the wrong plan.

The Satellite Reality

Starlink for maritime works. It also costs $160 per month for the residential roaming plan that most cruisers use, plus the hardware. The flat high-performance dish draws 50-65 watts continuous. On a 400Ah house bank running an inverter, that's 4-5 amps at 12V before conversion losses. If you're motoring or have solar gain in the tropics, fine. If you're reaching across the Atlantic under sail in November, you're choosing between refrigeration and connectivity.

The service throttles. Starlink's acceptable use policy may deprioritize maritime and roaming users during network congestion. In practice, this means you get full speed at 0600 local and degraded performance during U.S. East Coast business hours if you're sharing a beam with hundreds of other users. Video calls become impossible. Large file uploads time out.

The beam drops entirely in certain conditions. Heavy weather that forces you to take the dish down. Geographic obstructions in fjords or close coastal passes. Satellite handoff zones where coverage cells overlap poorly. You will lose signal. Your contingency is not "wait for it to come back." Your contingency is a workflow that doesn't require it.

The Workflow Inversion

Corporate remote work assumes persistent low-latency connectivity. Conference calls. Shared documents with live collaboration. Messaging apps that show you online. None of that maps to a vessel making a passage or sitting in a remote anchorage with marginal signal.

You need to invert the workflow. Batch communications. Download everything you need in the morning during your best connectivity window. Work offline. Upload deliverables in a single session. Use email, not Slack. Record video updates instead of attending live meetings. If your role requires real-time presence for more than two scheduled hours per day, it is not compatible with offshore cruising. Period.

Some roles adapt better than others. Software development, technical writing, financial analysis, and design work can all be done in batches with delayed submission. Customer-facing support, live trading, and anything requiring instant response cannot. Know which kind of work you do before you assume you can do it from 400 miles offshore.

Time Zone Destruction

You will cross time zones. If you're working for a U.S. employer and sailing east into the Caribbean, you gain an hour. Keep sailing to the Mediterranean and you're five or six hours ahead. Your 0900 standup is now at 1500 local. You're eating lunch during their morning. You're trying to sleep when they're sending urgent requests.

The worst scenario is the mid-ocean passage where you're standing watch in three-hour rotations and your work calendar expects you to be coherent at arbitrary times. You cannot maintain both a watch schedule and a corporate schedule simultaneously. One will fail, and it's usually your sleep.

Set boundaries before you leave. Establish core hours when you will be reachable and make it clear that those hours will shift as you move. If your employer cannot accept that, you are being paid for availability, not output, and this will not work.

The Power Budget

Your laptop, satellite terminal, phone, and any external monitors are parasitic loads on a system designed to run navigation instruments, refrigeration, and autopilot. A 15-inch MacBook pulls 60 watts under load. The Starlink dish pulls another 60. An external monitor adds 30. You're now drawing 150 watts, or roughly 13 amps at 12V, for the duration of your workday.

Run that for six hours and you've pulled 78Ah from your house bank. Add in the inefficiency of your inverter and you're closer to 90Ah. That's more than your refrigeration load on most boats. If you don't have solar or aren't running the engine, you've just committed to motoring for two hours to recover what you used sitting in front of a screen.

You need to account for this in your electrical budget before you leave. Add capacity or reduce load. There is no third option.

The Cognitive Cost

The hardest part is not technical. It's the constant toggle between two completely different mental states. Sailor brain is threat-aware, weather-focused, and attuned to small changes in motion, sound, and systems. Corporate brain is abstract, deadline-driven, and requires sustained focus on problems that have nothing to do with the wind direction.

You cannot do both at once. If you try, you will do both badly. The person who fell overboard in calm conditions was probably distracted. The deliverable that got submitted late with errors was written while worrying about an approaching squall line.

You need separation. Physical if possible. Work at anchor, not underway. Work in port, not on passage. If you must work underway, keep it to administrative tasks that don't require deep thought. Save anything requiring real cognitive load for when the boat is stationary and safe.

The infrastructure exists. The question is whether you can build the discipline to use it correctly.

By Nora Halstead