Business Analyst IV Job Plano area,Texas USA,IT/Tech

1. Core Skills (T-Mobile Baseline Expectations)
A. Control Testing (How We're Judged)
At T-Mobile, operational effectiveness means the control works every day, not just on audit day.
You must be strong in:

Design vs. Operating Effectiveness testing
End-to-end control walkthroughs across teams
Sampling at scale (automated + manual)
Re-performance of technical controls
Evidence quality assessment (system-generated > screenshots > attestations)
Control failure pattern identification
Compensating controls in legacy environments
Issue severity tied to regulatory exposure, not theoretical risk

B. Telecom-Specific Risk & Controls (Critical Differentiator)
This is where generic auditors fail.
You must understand:

CPNI requirements and enforcement expectations
Network data sensitivity vs. traditional PII
Call Detail Records (CDRs)
Location data risks
Lawful intercept and access governance
SIM, IMSI, IMEI data handling
Vendor access to network systems
Roaming partner data exchange risks

C. Identity, Access & Privileged Controls (High-Risk Area)
IAM failures are regulatory accelerants.

Required skills:

Role-based vs. entitlement-based access models
Joiner/Mover/Leaver (JML) lifecycle testing
Privileged Access Management (Cyber Ark-centric)
Break-glass access testing
Service account governance
Emergency access logging and review
Access reviews (manual vs. automated)
Segregation of Duties (SoD) conflicts

D. Cloud & Hybrid Environment Testing
T-Mobile is not greenfield-and never will be.
You must test:

AWS and Azure shared responsibility controls
Cloud IAM (AWS IAM, Azure Entra )
Logging & monitoring effectiveness (Cloud Trail, Azure Monitor)
Infrastructure-as-Code control evidence
Hybrid data flows (on-prem ? cloud ? vendor)
Cloud vendor assurance reports (SOC 2, ISO)

Design vs. Operating Effectiveness testing
End-to-end control walkthroughs across teams


Increase/decrease your Search Radius (miles)



Job Posting Language