• Job Title: Staff Engineer, Domain Architect PMT
• Company: TMUS Global Solutions
• Employment Type: Full-Time
• Experience Required: 8+ Years
• Location: Hyderabad, India
• Work Mode: Hybrid/Office (Based on Business Requirements)

ABOUT THE ROLE:

The Staff Engineer, Domain Architect PMT is the most senior individual contributor on the India-based PMT operational engineering team. The role provides cross-portfolio architectural leadership across all PMT applications – HR systems (Workday, UKG, Learning, and adjacent platforms), DevOps and platform tooling, and automation/AI initiatives.

This role mirrors T-Mobile’s US-based Staff Domain Architects, providing architectural continuity and partnership across geographies. The Domain Architect partners with the Manager SRE on team direction, with US-based Domain Architects on portfolio-wide patterns, with US-based Software Developers (DevOps) on platform tooling direction, and with all India engineers as a technical mentor and design reviewer.

This is a forward-looking role: as T-Mobile transitions from SaaS-heavy to custom-built platforms over the next several years, the Domain Architect shapes the engineering standards, integration patterns, and reliability frameworks that the team will build against.

WHAT YOU’LL DO:

• Define and evolve architecture standards across the PMT application portfolio – integration patterns, observability conventions, automation frameworks, security posture.
• Review and guide significant technical designs from the SRE, DevOps/Platform, and Automations & AI pods.
• Partner with US Domain Architects on SaaS-to-custom migration patterns; partner with US Software Developers (DevOps) on platform and CI/CD direction.
• Provide hands-on technical mentorship to engineers across all India pods; raise the engineering bar through code review, design review, and pairing.
• Own architectural decision records for cross-portfolio choices (e.g., common observability stack, identity integration patterns, automation framework selection).
• Identify and lead targeted proof-of-concept work that de-risks the broader Phase 2 build direction.
• Represent India engineering perspective in T-Mobile architecture forums and standards discussions.
• Coach engineers on full-stack engineering skills (development, not just operations) as the team’s role evolves.

WHAT YOU’LL BRING:

• 8+ years of software engineering experience with at least 3 years in architecture, technical leadership, or staff-engineer-equivalent roles.
• Deep, hands-on technical experience across multiple domains – at minimum two of: distributed systems, SaaS platform integration, automation frameworks, observability platforms, cloud infrastructure.
• Demonstrated ability to influence engineering direction without direct authority – through design review, written architecture docs, and credible technical leadership.
• Strong code review skills; able to teach as well as critique.
• Experience working across geographies and time zones, particularly with US-based architecture partners.
• Excellent written communication; can author clear architectural decision records and design docs.
• Hands-on experience using AI tools (Claude, GitHub Copilot, or equivalent) in production engineering work, with the ability to architect multi-agent systems and define team standards for how AI agents are built, deployed, and governed across the portfolio.

REQUIRED TECHNICAL SKILLS:

• AI & agent architecture: Proficient in AI coding/automation assistants (Claude, Copilot, or equivalent). Able to architect multi-agent systems; define and enforce team standards for agent design, deployment, observability, and governance across the PMT portfolio; and evaluate AI integrations at the platform level. This role sets the AI engineering bar for the India team.
• Production software development experience in one or more of: Python, Java, Go, Node.js.
• Hands-on familiarity with at least one enterprise SaaS platform (Workday, ServiceNow, Salesforce, or similar) at the integration / extension level.
• Strong cloud architecture skills (AWS, GCP, or Azure) – IAM, networking, observability, cost design.
• API design and integration architecture (REST, event-driven, iPaaS patterns).
• Observability and reliability engineering practice (SLOs, error budgets, incident review).
• CI/CD and infrastructure-as-code (Terraform or similar).