Meeting cost by company: how FAANG vs startup bands change the bill

Not every "engineering sync" costs the same. A thirty-minute meeting of five mid-level engineers at a mature public tech company can run several times the labor cost of five engineers at an early-stage startup—because Levels.fyi averages for total compensation differ by employer, level taxonomy, and the equity component in each band. Meeterboard encodes those differences by letting you pick a company first, then attach attendees to that employer's cached pay levels.

Why company choice dominates

Compensation is not a single market. Large companies cluster equity grants, refresh cycles, and bonus targets that push headline TC bands upward. Startups trade cash for upside: lower averages on paper until liquidity events re-rate expectations. Consulting and finance-adjacent tech employers show up with different shapes again. If you multiply the same headcount and duration against different annual TC snapshots, you get different per-second burns before anyone changes behavior.

Meeterboard's formula is identical for everyone:

per_second = annual_tc ÷ 7,488,000

Company selection changes annual_tc, not the math.

Illustrative thirty-minute, five-person meetings

The table uses round illustrative TC averages in the spirit of public Levels.fyi bands—not live quotes. Always verify in the calculator with current data.

| Scenario | Avg TC per attendee (illustrative) | 30 min × 5 people |

|----------|-----------------------------------|-------------------|

| Growth-stage startup, mid SWE | ~$180,000 | ~$216 |

| Large public tech, mid level (e.g. L4/L5 band) | ~$280,000 | ~$336 |

| Same employer, senior+ band | ~$420,000 | ~$504 |

| Finance-heavy tech employer, VP band | ~$650,000 | ~$780 |

The jump from startup mid to public senior is not 10%—it is multiples. That is why executive review meetings deserve different design than team standups.

Single-company constraint

Today each Meeterboard meeting prices all attendees from the host company's cached levels. You cannot mix Google L5 with Amazon L6 in one clock. That avoids ambiguous cross-employer level mapping. For acquihire integrations or joint venture teams, run separate clocks or model guests manually outside the tool.

How data enters the product

When you onboard, Meeterboard fetches or reads cached salary pages for your employer slug. First visitor to a rare company may wait while we ingest job families. Popular employers are often pre-seeded. Refresh cadence is seven days. Deep dive: How Meeterboard uses Levels.fyi data.

Strategic takeaways for leaders

Calendar policy should be company-aware. A "no meetings Wednesday" rule at a high-TC employer saves more dollars per hour than the same rule where cash comp is lower—but the latter team may feel cash pressure more acutely. Context matters.

Vendor and partner meetings at HQ with senior hosts look cheap in headcount ("just me and three vendors") until you price the host's band.

Hiring plans interact with meeting cost: adding two senior reviewers to every architecture review multiplies burn without adding story points.

Using the calculator for company comparisons

1. Create a meeting at employer A with five mid-band engineers; note thirty-minute cost.
2. Repeat with employer B at the same nominal level name if it exists.
3. Compare senior vs mid within one employer to see internal spread.

Spectate and leaderboard surface real sessions users run—empirical distribution, not theory.

Caveats

Levels.fyi coverage varies. Averages hide geo pay zones (many employers blend US hubs). Equity marks change. Illustrative table above is pedagogy, not a data feed.

Further reading

• Meeting cost by level — IC vs director multipliers
• True cost of meetings — annualizing recurring slots
• How it works — formula and pause rules

Acquisitions and dual employer slugs

After acquisitions, teams sometimes operate under legacy employer branding while HR integrates comp bands. Meeterboard prices one host company slug per meeting today—acquired teams should pick the slug that matches their cached pay levels, not the parent logo on slide decks. Mis-picked slugs distort dollars.

Public company vs subsidiary labels

Subsidiaries may have thinner Levels.fyi coverage than parent brands. If your search finds only the parent slug, bands may blend geo pay broadly—interpret totals with wider confidence intervals mentally.

Consulting and client-facing meetings

Agencies pricing client workshops should not use internal TC bands as client billing rates without margin and contract terms. Meeterboard is internal labor visibility, not invoicing. Client pass-through fees often 2–3× internal cost when priced professionally.

Benchmarking peers

Comparing meeting cost across companies in articles is pedagogical. Live leaderboard shows what real users run on Meeterboard—empirical distribution, not industry benchmark survey data.

Geo pay and remote hiring

Employers hiring broadly across US time zones sometimes blend geo pay into single national bands on Levels.fyi pages. Meeting cost for a fully remote team may understate cost if your policy pays SF rates universally—verify bands against internal comp spreadsheets for high-stakes audits.

Offer negotiation season

New hire offer meetings cluster senior bands in calibration loops—temporary spike in meeting cost mix. Seasonal planning should use October/November samples, not quiet summer weeks, when modeling leadership calendar load.