AI Comp by Funding Stage.
AI compensation broken down by company funding stage: seed, Series A, B, C, D+, late, public. Base, equity, signing bonus, total comp. With explicit equity-vs-cash trade-off math.
What it is, and why it exists.
AI compensation does not move linearly with seniority and city alone. It bends sharply with company funding stage. A seed-stage AI company in San Francisco can pay $165K base with a $95K-per-year equity grant for a senior AI engineer. A public AI company pays $268K base with $112K-per-year RSU. The total comp numbers happen to be in the same ballpark for the headline ($260K vs $408K when equity is liquid), but the composition is dramatically different and the risk profile is incompatible.
Without a stage-aware engine, every comp calculation has to assume an average company stage, which makes the answer wrong for both seed and public. The Comp by Stage engine fixes that by treating funding stage as a first-class dimension. Pass company_stage=series-b to /calculateand the response returns the band for that stage specifically. Without it the API uses the role's stage-weighted average and flags the assumption in the response.
We built this engine because every founder, every candidate evaluating multiple offers, every comp consultant building bands for an early-stage portfolio, and every recruiter writing offer narratives needs stage-specific data. The market did not have a clean source for this: Levels.fyi conflates stages within companies; Pave is paywalled and stops at seed-stage detail. Orbyt's engine surfaces the breakdown in every salary response, with sources cited and methodology version visible.
For agents, this engine is the difference between "an AI engineer earns $310K in San Francisco" and "a senior AI engineer at a Series B company in San Francisco earns $225K base + $58K/yr in equity + $15K signing, totaling $298K: versus $408K at a public company in the same city, with the gap explained almost entirely by the equity liquidity profile." The second answer is decision-ready; the first is a rough average that misleads both sides.
Sample: Senior AI Engineer · San Francisco.
Snapshot from May 2026. Equity values use 30-day VWAP for public, most recent priced round for private. Total comp shown at face value: apply your own private-equity liquidity discount for stages before pre-IPO.
Methodology version 2026.2-stage. Sample shown. Full data for every role × stage via GET /api/v1/intelligence/salaries/calculate?company_stage=....
Methodology.
Stage is determined by tracking each company's most recent funding round. Signals come from Crunchbase, PitchBook, SEC filings (Forms 8-K, S-1, DEF 14A), and press announcements. We cross-reference the round size against the company's reported valuation to filter out misclassified rounds (a $50M Series A is sometimes mis-tagged as a Series B; we use the size to align with the round's actual stage).
Compensation is composed of four components: base salary (from H-1B LCA filings + job postings + community submissions), equity grant value (from the most recent priced round or trailing 30-day VWAP for public), vesting schedule (default 4-yr cliff-1 if not disclosed), and signing bonus (from community submissions + job-posting bonus disclosures). The engine returns each component separately so customers can apply their own valuation logic.
For private companies, the equity value is the face value at the most recent round. We never silently apply a liquidity discount: the customer applies their own. Some customers use 30-50% for Series A, 20-40% for Series B, 10-30% for Series C+; the appropriate discount depends on the customer's risk tolerance and the company-specific liquidity profile, neither of which we can know in aggregate.
The stage-specific multiplier on base is fit quarterly with the same mixed-effects model described on the Skill Premiums page. Stage enters the regression as a fixed effect with seven levels; the coefficients on each stage are the stage-specific premium / discount relative to the cross-stage average for the role.
Use cases.
A seed-stage founder pulls the engine's seed-stage band for the role, the city, and the seniority. The band shows the typical equity grant size, the typical base, and the typical signing bonus. The founder calibrates the offer to be defensible against the band, with explicit room above for top candidates and below for those still growing into the level.
The most common multi-offer comparison is seed vs Series C vs public. The engine returns each stage's comp composition, the implied equity-vs-cash trade-off, and a four-year forward projection (base + vested equity) for each. Candidates can apply their own liquidity discount and risk tolerance.
Consultants pull stage-specific bands for every role in a company's leveling framework. The bands inform the company's own pay philosophy: do we want to be at the 50th percentile for our stage, or at the 75th? The engine's output is the input to that decision.
Recruiters at early-stage companies use the engine's output to explain the offer's composition to candidates: "Our base is at the 60th percentile for Series A, our equity grant is at the 80th, and our signing matches market." The narrative is defensible because every number ties back to a Bloomberg-grade source trail.
API integration.
Two integration paths. Both return the same envelope.
Full reference at /orbyt-intelligence/api-docs.
Pricing and access.
Stage-aware compensation queries require the Pro tier and the compensation:read scope. Without these, salary endpoints return the stage-weighted average for the role with a disclosed assumption note. Full pricing at /orbyt-intelligence/pricing.
See also.
Methodology version 2026.2-stage. Last updated May 2026. Stage data refit quarterly. Equity values use 30-day VWAP for public, most recent priced round for private. Apply your own liquidity discount as appropriate.