Set Pricing Tiers and a Billing Unit for Google's Machine-Translation API
Company: Google
Role: Product Manager
Category: Product / Decision Making
Difficulty: medium
Interview Round: Other
You are the product manager responsible for pricing Google's machine-translation API, the service developers and businesses call from their own software to translate text. How would you price it? Explain what customers are billed for, how you arrive at the price levels, and how pricing differs across customer types.
```hint Unit before number
Settle what a customer is charged for before choosing an amount. Then ask what sets the lowest price you could accept, what sets the highest a customer would pay, and how usage differs between a hobby project and a global platform.
```
### Clarifying Questions
- Is this a first launch or a change to an API already on sale, and do rival APIs already set customers' price expectations?
- What should pricing optimize: winning share quickly, maximizing margin, or drawing customers onto the wider cloud platform?
- Which buyers matter most: hobbyist developers, growing software companies, or large enterprises translating billions of characters?
- Does the offering go beyond plain text, for example document translation that preserves formatting, models customized to a customer's terminology, or speech?
### What a Strong Answer Covers
- A billing unit, justified by both serving cost and how customers think about value.
- Price bounds from cost, competitor references and customer value, with every figure labeled as an assumption.
- A tier structure matched to segments: free allowance, pay-as-you-go, volume discounts, premium features and enterprise commitments.
- A plan to validate and adjust prices after launch, with metrics.
- Risks such as price wars, free-tier abuse, cheaper substitutes and the cost of raising prices later.
### Follow-up Questions
- A competitor halves its price. Do you follow, and for which customers?
- Text in Chinese or Japanese packs more meaning into each character than English does. How should that affect the billing unit you chose?
- How would you price a custom model that a customer trains on its own documents?
Overview: A pricing question asking a product manager to set prices for Google's machine-translation API. It tests choosing a billing unit, using cost, competitor and customer-value bounds, designing tiers from hobby developers to enterprises, and planning how to validate prices and manage risks.