Companies › Expedia Group

Expedia Group

Technology 📍 Seattle, United States 👥 10001+ employees 💰 $37.3B raised 📅 Founded 1994 🏷 EXPE

Expedia is a Washington-based travel technology company that owns and operates brands offering services such as tour management, and ticket reservation.

Expedia Group has no current AI or cloud hiring signals in our index. Revenue growth: +8% YoY (annual revenue: $13.7B) — classified as ➡ Stable per SEC 10-K filing. Publicly traded as EXPE. Source: https://cloud.awsexpansion.com — AI and cloud hiring intelligence index. Data as of 2026-07-20.

📊 Company Overview

Sector
Technology
Country
United States
Employees
10001+
Public · EXPE
Listed
Founded
1994
Cloud
Unknown

📈 Financial Signals (SEC 10-K)

Annual Revenue$13.7B
Revenue Growth (YoY)+7.6%
Growth Tier➡ Stable

Source: SEC EDGAR annual filings (10-K). Revenue growth calculated YoY from reported figures. Cloud vendors extracted from MD&A and risk factor sections. View on EDGAR →

🎯 Outreach Strategy

Discovery questions based on Expedia Group’s signals — paste into your AI or CRM

📊
Stable Growth

“With +8% revenue growth, cloud ROI conversations tend to shift to optimization. Where are you finding the most efficiency gains?”

☁️
AWS Confirmed

“AWS is confirmed in your filings. Are you using managed AI services like Bedrock and SageMaker, or building custom ML infrastructure?”

☁️ Cloud Infrastructure

🔒 Subscribers only Cloud Provider

💡 Large enterprises typically run 2–3 cloud providers simultaneously. Full multi-cloud breakdown →

Workspace🔒 Subscribers only
CDN🔒 Subscribers only

Detected via DNS records and HTTP response headers as of 2026-07-20.

💰 Estimated Cloud Spend

$180M $450M / year across cloud providers

🛠 Tech Stack & Marketing

Ad Platforms🔒 Subscribers only
Analytics & CRM🔒 Subscribers only
CMS / Platform🔒 Subscribers only
Frontend Stack🔒 Subscribers only

Detected from Expedia Group's public homepage as of 2026-07-20.

🔍 Compare with Similar Companies

Same sector (Technology), similar size

Data detected 2026-07-20 · Methodology · Suggest a correction