Go-to-market strategy for Azure HPC to win energy companies away from AWS
Company: Google
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
Azure sells high-performance computing (HPC) capacity and wants energy companies to use far more of it. The stated ambition is that every energy-sector client runs its HPC work on Azure rather than on AWS. What strategy would you put in place to get there?
```hint Follow the switching costs
Ask what keeps an energy company on its current platform today. A plan that only competes on price per core-hour misses most of the reasons clients stay where they are.
```
### Clarifying Questions
- Does the energy sector here mean oil and gas exploration only, or also utilities, renewables developers and other energy research?
- Are the target clients running HPC on AWS today, on their own on-premises clusters, or a mix of both?
- Should success be judged by HPC consumption, by revenue, or by the number of clients that commit to Azure?
- Is "every client" the literal target, or is the real aim to win the largest share of energy HPC work?
### What a Strong Answer Covers
- Segmentation of energy clients by HPC workload and current setup, with a justified first segment
- A diagnosis of what makes clients choose or stay with AWS, and where Azure has a credible edge
- Strategy pillars spanning product, partner software, commercial offers and the sales motion, in priority order
- Success metrics with guardrails such as margin and available HPC capacity
- Risks, including clients that deliberately use more than one cloud and how AWS is likely to respond
### Follow-up Questions
- A large client keeps years of seismic survey data in AWS storage. How do you make moving it worthwhile for them?
- If AWS matches your pricing within a quarter, which parts of your strategy still hold?
- How would you decide which energy accounts are not worth pursuing?
Overview: A product strategy question about growing Azure's high-performance computing business with energy companies that could otherwise run their workloads on AWS. It tests customer segmentation, understanding of switching costs such as data volume and simulation software licensing, competitive positioning, go-to-market planning and success metrics.