Influence Without Authority and Hard Conversations
How TAMs get things done without owning the people or systems: prioritizing across customers, advocating with service teams through feature requests, delivering bad news, disagreeing with customers, and handling an angry executive.
You Own Almost Nothing
A TAM doesn’t own the customer’s engineers, the customer’s systems, the AWS support engineers, or the AWS service teams. Yet the TAM is accountable for outcomes that need all of them. That’s influence without authority, and interviewers will probe it directly: “Tell me about a time you got someone to do something they didn’t have to do.”
Influence comes from three things:
- Credibility: you’re technically right, and you’ve been right before
- Data: you bring evidence, not opinions
- Relationships: people help you because you’ve helped them and you’re easy to work with
Advocating Inside AWS
TAMs are the customer’s voice inside AWS. When a customer needs something AWS doesn’t do, the TAM files a product feature request (PFR) with the service team. Strong PFRs:
- Describe the customer problem, not just the requested feature
- Quantify impact: revenue at risk, workload size, how many customers ask for it
- Include the current workaround and why it hurts
- Get aggregated with other customers’ requests, since service teams prioritize by demand
Be honest with the customer: a PFR is not a promise. Set expectations, offer the best workaround now, and follow up.
Prioritizing Across Customers
TAMs often support several customers, and everything feels urgent. A simple order:
- Active business-critical impact (outage, security event)
- Time-bound risk (a launch next week, an end-of-life deadline)
- High-value proactive work (the review that prevents the next Sev-1)
- Everything else, scheduled and communicated
When you can’t do something, say so early, explain why, and offer an alternative or another person. Customers forgive “not this week, here’s when.” They don’t forgive silence.
Hard Conversations
- 1 Listen
Let them finish; acknowledge impact
- 2 Facts
What happened, with data
- 3 Own it
What AWS or you got wrong
- 4 Options
Paths forward + trade-offs
- 5 Agree
Owners, dates, next check-in
- 6 Follow through
Do exactly what you said
The angry executive after an AWS-side event
Don’t get defensive and don’t minimize. Acknowledge the business impact in their terms. Share what you know, and commit to a detailed explanation by a specific time. Then turn it into resilience: “Here’s how we can make sure a similar event in one AZ doesn’t affect you next time.”
Telling a customer their architecture is risky
They may have built it themselves and be proud of it. Lead with their goal (“you told me checkout uptime is your top metric”), show the risk with data, offer options, and respect their decision. If they accept the risk, document it. That’s Have Backbone; Disagree and Commit.
Saying no to the customer
Sometimes the customer asks for something a TAM can’t or shouldn’t do: write their code, guarantee a feature date, bypass a security control. Say no clearly, explain why, and offer what you can do. A clear no keeps trust. A vague maybe destroys it.
Common mistake: “I told the customer AWS support was terrible and I’d personally make sure it got fixed.”
Advocating for the customer doesn’t mean trashing your colleagues. Own the problem (“We didn’t meet the bar here”), fix it through the right channels, and keep both relationships intact. Interviewers listen for this balance.
Key Takeaway
A TAM drives outcomes through credibility, data, and relationships, not authority. Advocate inside AWS with quantified feature requests, prioritize by business impact and deadlines, and handle hard conversations by listening, stating facts, owning mistakes, offering options, and following through. Say no clearly, and disagree with respect.
Have a friend play the customer’s CTO, or write out both sides:
“Your Region had a networking event yesterday. Our app was down for 47 minutes during our biggest sales day of the year. I’m paying for Enterprise Support. Why didn’t you warn us? Why should we stay on AWS?”
Respond in under 3 minutes. Check: Did you acknowledge the impact before explaining? Did you avoid making promises you can’t keep? Did you end with a specific next step and time?
1. What makes a product feature request most likely to be prioritized?
Service teams prioritize by problem clarity and demand, so quantify and aggregate.
2. A customer accepts a risk you advised against. What should you do?
Have Backbone; Disagree and Commit: state your case clearly, then commit once the owner decides.
3. During a hard conversation with an upset executive, what should come first?
Acknowledging impact first lowers defensiveness and builds trust for what follows.
4. Two customers need you at once: one has a launch in 3 weeks, the other has an active production outage. What comes first?
Active business-critical impact comes first; communicate clearly with the other customer.