Principal Systems Architect Interview Experience - United States
Process
The interview process was straightforward, as I was working for a vendor for one of the applications used in the mobile core network. The interesting thing that would have held me back was that I didn't have a 4-year degree. I was previously in the midst of completing it and let them know. They asked for transcripts and when I was planning to complete it.
Luckily, I worked on the applications and had extensive knowledge of the mobile core network and virtualization. Otherwise, I would not have gotten an offer.
Questions
- What is the Gx application ID value?
- What is the call flow for a call wanting to establish a service but not in the OCS?
- How would you build a mobile core network in the cloud, and detail the messaging?
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the AT&T Principal Systems Architect role in United States.
Success Rate
AT&T's interview process for their Principal Systems Architect roles in the United States is incredibly easy as the vast majority of engineers get an offer after going through it.
Experience Rating
Candidates reported having very good feelings for AT&T's Principal Systems Architect interview process in United States.
AT&T Work Experiences
- 3.0Exciting Tech, Unstable FuturePrincipal Systems Architect • Current EmployeeMission, Kansas, United StatesFebruary 11, 2019Pros: Exciting technology, interesting work, and much opportunity in select areas.Cons: No job guarantee, as they are moving to consolidate around locations.
- 5.0Great Company, Political DepartmentTechnical Architect • Current EmployeeRemoteDecember 20, 2022Pros: I worked as a contractor for AT&T two times. It's a great company to work for.Cons: They are a large organization and sometimes have to deal with other departments at a political level.
- 4.0Supportive, Balanced, But In-officeTDP Software Engineer • Current EmployeeDallas, Texas, United StatesDecember 2, 2025Pros: Really supportive environment. Collaborative. Good work-life balance.Cons: 5 days in-office. Projects may not be high impact, depending on your team.
