Check the Meeting Expectations in a Remote Job Offer

A remote job can remove the commute and still consume the entire day in calls. The work location tells you where your laptop sits. It tells you much less about whether you can get an uninterrupted morning, whether dinner is a recurring meeting slot, or whether declining an invitation has career consequences.

“We are pretty async” is a starting point for a conversation. Before accepting an offer, ask what a normal week looks like for someone doing this specific job. Meeting expectations vary with role, team, manager, and the parts of the organization that team depends on.

The goal is to understand the collaboration you are signing up for. Engineering needs conversation, and leadership often requires more of it. Useful meetings can save days of confused work. The problem is accepting a role on the strength of a flexible-work promise when the actual calendar demands something very different.

Ask for a representative week in this role

Start with the hiring manager: “Could you walk me through the recurring meetings for someone in this role, including the meetings with partner teams?” Ask for a description or a sanitized example. You do not need access to anyone's private calendar.

List the meetings you would normally attend:

• Team planning, standups, reviews, and retrospectives.
• Manager and peer one-to-ones.
• Design reviews and technical decision meetings.
• Cross-team coordination and stakeholder updates.
• Department meetings and company all-hands.
• Customer, recruiting, mentoring, or leadership obligations specific to the role.

Then ask what happens outside the recurring schedule. A team can have a light official calendar and spend every afternoon in spontaneous huddles. Another can have a busy planning week followed by several quiet delivery weeks. Ask about a normal period and a recent demanding period so that one unusually calm week does not become your baseline.

“How much meeting time should I expect?” is useful, but the follow-up matters: “What work tends to create additional meetings, and who decides whether I need to attend?” That reveals whether meeting load is an intentional part of the job or an unlimited queue of requests.

Count the shape of the calendar as well as the hours

Ten hours of meetings can mean two concentrated afternoons or small interruptions scattered across five days. The total is the same; the workday is not.

Build a rough weekly estimate. Convert fortnightly and monthly meetings into a weekly average, then separately note where they fall. Averages help compare offers, but they conceal a dense planning week or an early call that occurs only twice a month.

Here is an illustrative inventory for an individual contributor:

Commitment	Weekly average	What to clarify
Four 15-minute team check-ins	1 hour	Required live, or written update accepted?
Weekly planning	1 hour	Is preparation additional?
Two design or project sessions	2 hours	Does everyone attend every discussion?
Manager one-to-one	30 minutes	Is the slot stable?
Fortnightly retrospective	30 minutes	Is it combined with another team session?
Monthly all-hands	About 15 minutes	Can it be watched later?

That is roughly five and a quarter scheduled hours before ad hoc conversations, recruiting, preparation, and follow-up. It is an example of arithmetic, not a recommended ceiling. A manager's or staff engineer's useful collaboration load may be much larger.

Next, sketch those commitments onto days. Look for the longest likely uninterrupted blocks, awkward gaps, and meetings that extend the span between your first and last obligation. A calendar with six hours of calls spread from early morning to late evening may constrain your life more than its total suggests.

Separate core hours from actual meeting reach

An employer's core-hours policy defines expected overlap. Meeting reach describes the earliest and latest calls the job actually requires. Ask about both.

Useful questions include:

• Which time zones contain my closest collaborators and decision makers?
• What are the earliest and latest recurring meetings in my local time?
• Are inconvenient meeting times rotated, or does one location absorb them?
• How often are exceptions expected, and how much notice is normal?
• What happens when daylight-saving changes temporarily shift the overlap?
• If I take an early or late call, can I adjust the rest of that day?

Ask for the recent pattern rather than accepting “occasionally” as a measurable frequency. Once a quarter and three times a week can both be described that way. If the team is growing into another region, ask whether its meeting schedule is expected to change.

Keep ordinary collaboration separate from on-call coverage. Production incidents and planned partner-team meetings create different obligations. A manageable on-call rotation does not explain a standing evening design review, and an accommodating meeting policy does not settle incident-response expectations.

Test what “async” lets you do

Async work becomes useful when people can contribute and keep moving without attending every conversation. A recording by itself does not establish that. Watching an hour of video later can simply move the meeting into another part of your day.

Ask for a recent example: “When someone could not attend a design discussion, how did they provide input, learn the outcome, and challenge a decision?” Look for a written proposal, a response window, accessible notes, and a clear owner. Ask whether absent teammates had a meaningful chance to influence the result before implementation began.

GitLab's published all-remote meeting guidance provides a concrete comparison point. It discusses participant time zones, distinguishing required from optional attendees, agendas, recordings, and time for asynchronous input on decisions. Those are GitLab's documented practices, not universal requirements or evidence that another team follows them. Use the specificity as a model for the conversation.

You can ask a prospective teammate:

• “Which recurring meeting could you skip last month without losing context?”
• “Where would I find the outcome of a meeting I missed?”
• “How quickly are written questions normally answered?”
• “When do you choose a call because writing is no longer helping?”

The last question matters. A team that insists on writing through every misunderstanding can be frustrating too. You want deliberate use of synchronous time and a way to preserve what the conversation resolved.

Find out who protects focus time

A focus block on a calendar is useful only if the team treats it as meaningful. Ask whether people can decline meetings outside their role, request an agenda, or propose a written update. Then ask what happens when a senior stakeholder invites them anyway.

“My manager protects the team's mornings” is a more concrete answer than “you own your calendar,” especially when the job depends on several teams. Ask who helps resolve competing invitations and whether the role carries a standing expectation to be available for interruptions.

For a leadership role, the answer may be that coordination is a substantial part of the work. Evaluate whether that load fits the outcomes you are expected to produce. Supporting a team, hiring, and settling cross-team decisions takes time. An offer that expects all of those activities plus a full individual delivery workload needs a discussion about priorities.

Also ask about camera expectations, lunch breaks, meeting-free periods, and notice for schedule changes where those affect your working day. These details do not need to become a list of demands. They are ordinary operating questions about a job you may hold for years.

Compare answers across the people you meet

Ask the manager and a prospective peer versions of the same question. Different calendars are normal; incompatible descriptions deserve follow-up. A manager may describe the intended system while a teammate describes the current workload.

Keep a short comparison note with four fields: expected recurring hours, earliest/latest obligation, how absent people participate, and who resolves meeting overload. Add the source and whether an answer describes policy, current practice, or a planned improvement.

If something is essential to accepting the job, request a written clarification. “Most meetings fall within these hours” and “this role is required to attend a weekly call at this time” are different statements. A useful final question is: “Have I understood the expected schedule correctly, including the regular exceptions?”

Avoid treating an interviewer's calendar walkthrough as a guarantee that the schedule can never change. Teams reorganize and projects evolve. What you can evaluate is the present expectation, the change process, and whether the manager can explain the tradeoffs honestly.

Decide whether this is a working week you want

There is no single correct meeting budget for remote engineering. A role centered on individual implementation needs different blocks of time from a role centered on technical alignment or supporting managers. Your decision should account for the actual work and the rest of your life.

Before accepting, you should be able to describe a plausible normal week: when collaboration happens, how much of it needs you live, where focused work fits, and what happens when meetings multiply. If you cannot, the remote-work label is doing too much of the selling.

A good remote offer gives you enough information to make that tradeoff deliberately. Ask for the calendar reality with the same care you give the equipment stipend and other written terms. The schedule is part of what you are agreeing to do every week.