Guide

Australian engineers on a US startup team: what founders asked and what works

The Sydney morning overlaps the US West Coast afternoon. That's the easy part. These are the practical questions US founders asked us, and how teams handle them.

By the Lyra Capital team · · 3 min read

The overlap, briefly

Sydney is 17 to 19 hours ahead of San Francisco, and a standard workday overlaps for one to three hours: the Sydney morning and the San Francisco afternoon. The full table by season is in how much Sydney and San Francisco overlap.

The upside is the handoff. Work you hand over in your afternoon is ready for review when your day starts.

What US founders asked

Seven of the 37 calls with recorded questions raised time zones or remote work. The questions, lightly edited:

  • How will the time difference affect management?
  • Can the engineer be reached outside standard hours?
  • How will urgent issues be handled across time zones?
  • Can remote engineers work with a team that works in person?
  • Is an onsite visit possible at the start?
  • Which locations can we hire from under our customers' security rules?

The daily rhythm that works

  1. End of the Sydney day: a short written update with what shipped, what is in progress, what is blocked and any questions.
  2. Your morning: review, answer the questions, merge.
  3. The overlap: a live sync every day or two for decisions and anything ambiguous.
  4. Urgent issues: one agreed channel, often a text or call, for production problems only.
  5. Before your weekend: raise anything you need by Thursday afternoon US time, because your Friday afternoon is Sydney's Saturday.

Lyra engineers join your Slack, codebase and standups, so this runs in the tools you already use.

When remote doesn't fit

Be honest about this one. A team optimizing for in-person cohesion, where decisions happen at a whiteboard and never get written down, will find remote engineers frustrating whatever the time zone. Some founders asked about an onsite week at the start for discovery. It helps with context, but it won't change a culture that needs everyone in one room.

Products that change direction several times a day carry a coordination cost too: the overnight handoff turns into rework. Tighten the daily priority list first, or keep that work local.

Security and allowed locations

Founders selling into security-sensitive customers asked where they were allowed to hire. Check your customer contracts before hiring outside your own country, write down which locations are allowed, and agree which systems and data the engineer can reach. Customers may ask during a security review, and it's easier to answer when it's already written.

Questions founders ask

Can Australian engineers work US hours?

Partly. The Sydney morning overlaps the US West Coast afternoon for one to three hours. Most of the value is the handoff: work done overnight is ready when your day starts.

How do you handle urgent issues across time zones?

Agree one urgent channel, usually a text or call, for production issues, and keep everything else in written async updates.

Do remote engineers work for in-person teams?

Only if decisions get written down. If the team relies on being in one room to decide things, remote engineers will struggle whatever the time zone.

Based on Granola notes from 46 calls Nam Dao and the Lyra team held with founders about hiring engineers, 6 July to 7 November 2026. Names, companies and figures are left out. AI helped pull the questions from the notes, and each one was checked against its note. Facts about Lyra engineers are as published on lyratechnologies.com.au.