IT

Senior Technical Account Manager, Telco Vertical – Amazon

Amazon
Dubai Full-time

Applications close Nov 7, 2026

Job Description

This Senior Technical Account Manager role sits inside AWS’s Telco vertical, the part of Amazon Web Services that works with telecommunications operators and carriers across the region as they move workloads onto the cloud. The job exists at the intersection of deep technical knowledge and customer relationship management: the person in this seat becomes the trusted technical advisor for a portfolio of enterprise telco accounts, rather than a generic support contact.

Day to day, the work is a mix of proactive account health reviews, architecture guidance, incident involvement when something goes wrong in production, and translating a customer’s business goals into concrete AWS adoption plans. A Senior TAM is expected to understand a customer’s environment well enough to spot risk before it becomes an outage, and to coordinate internally with AWS service teams, solutions architects and support engineers to close gaps.

Because the portfolio is telco-specific, familiarity with how carriers run networks, handle regulatory and data residency constraints, and plan capacity for high-availability services is a real advantage. The seniority in the title also implies mentoring newer TAMs and taking on the more complex, multi-stakeholder accounts where technical depth and executive-level communication both matter.

It suits someone who has already worked in a cloud operations, infrastructure, or enterprise support role and wants to move into a strategic, customer-facing position without leaving technical work behind entirely — the role still requires reading architecture diagrams, reasoning about failure modes, and engaging with engineering teams on both sides.

Impact of the Job

A Senior Technical Account Manager is one of the few roles that directly shapes whether a major telco customer stays confident in AWS during the moments that matter most — a capacity crunch, an unexpected failure, or a complex migration milestone. Telco customers tend to run services where downtime has immediate, visible consequences for end users, so the quality of technical account management has a disproportionate effect on retention and expansion within that account. Every proactive review that catches a misconfiguration before it causes an incident protects both the customer's uptime and AWS's reputation with that account team. Because telco accounts are typically large, multi-year, multi-service relationships, a TAM who builds genuine technical trust can influence how much of that customer's future workload lands on AWS versus a competitor. The role also feeds real customer pain points back into AWS's product and service teams, which over time shapes how well AWS serves the entire telco vertical, not just one account.

Job Seeker Benefit

Working as a Senior TAM in AWS's telco vertical gives someone genuine breadth: exposure to how some of the largest, most demanding cloud workloads in the region are actually architected and operated, not just how they look on a whiteboard. Because telco customers run environments with strict uptime and regulatory requirements, the technical problem-solving involved tends to be more rigorous than in general-purpose cloud support, which builds a strong foundation in distributed systems thinking, incident management, and capacity planning. The role also develops a skill set that is harder to pick up in a purely technical job: translating deep technical detail into language that resonates with business stakeholders, and managing relationships under pressure during live incidents. That combination of technical credibility and account management experience is highly transferable, and is a common stepping stone into solutions architecture, customer success leadership, or specialist roles within major cloud providers. Being embedded in AWS also means ongoing exposure to new services and features well before most of the market, which keeps the technical knowledge current rather than stagnant. For someone who enjoys both the technical and the relationship side of enterprise technology, it is a role that builds credibility on both fronts simultaneously, which tends to open doors into more senior account, architecture, or leadership tracks over time.

Suggested Resume Keywords

Consider including these terms in your resume for this role:

AWSTechnical Account Managercloud infrastructuretelcoenterprise supportincident managementsolutions architecturecloud migrationcustomer successcapacity planningdistributed systemsstakeholder management

Requirements

  • Several years of experience in a technical account management, cloud operations, infrastructure, or enterprise IT support role
  • Working knowledge of AWS core services (compute, networking, storage, databases) or equivalent cloud platform experience
  • Comfort reading and reasoning about system architecture, including distributed and high-availability designs
  • Experience managing enterprise customer relationships, including escalations and incident communication
  • Understanding of telecommunications industry operations, regulatory considerations, or network environments is an advantage
  • Strong written and verbal communication skills for both technical and executive audiences
  • Ability to coordinate across multiple internal teams (support, solutions architecture, service teams) under time pressure

Interview Questions to Prepare For

Tell me about a time you caught a technical risk in a customer's environment before it caused an outage.

Listen for proactive monitoring habits and a structured approach to risk assessment, not just luck.

How would you explain a complex architecture issue to a non-technical executive stakeholder?

Look for the ability to simplify without losing accuracy, and awareness of audience.

Describe a high-pressure incident you were involved in and your specific role in resolving it.

Check for ownership, calm communication, and clear escalation judgment.

What do you know about the operational pressures telecom companies face when adopting cloud infrastructure?

Gauge genuine industry awareness versus generic cloud knowledge.

How do you prioritize across a portfolio of enterprise accounts with competing urgent needs?

Look for a repeatable prioritization framework, not just reactive firefighting.

Walk me through how you'd structure a quarterly account health review for a large customer.

Assess structure, proactivity, and whether they tie technical findings to business outcomes.

Tell me about a time you had to push back on an internal team to get the right outcome for a customer.

Look for assertiveness balanced with collaboration, not conflict avoidance or steamrolling.

See how this compares to other IT roles in the UAE — browse similar salaries →