I applied online in Fall 2017 for the Software Dev Intern position in San Ramon, CA. The interview process began with a coding challenge that I received by email. There were three questions, much easier than any other coding challenge that I had ever done before, even easier than the "easy" questions on HackerRank or similar websites. If you have ever done any programming or taken an introductory programming class, this should be simple.
I then received an email from a recruiter requesting a phone screen. It began by giving me a description of the overall intern program and then asking if I had any questions. After I had asked my questions, the recruiter went over my resume and talked about my past internship experience and technologies I had used there. At the end of the interview, the recruiter said she would recommend me to the next step of the interview process, which was a behavioral and technical portion.
The behavioral interview went great. The guy on the other end was a senior manager who I really hit it off with. We discussed my past experience and a few standard behavioral questions about how I dealt with leadership and conflicts within a group project I was leading. He also asked a few unorthodox questions about:
The technical portion was a bit more challenging than I initially expected. I was asked to discuss the 4 pillars of OOP, the difference between primary and foreign keys in SQL, the difference between an interface and an abstract class, and when to use recursive vs. iterative approaches.
The second portion of the technical interview had us go to one of those code collaboration websites where I shared my screen. First, he pasted some Java code and asked for the output of the code. The code was on inheritance principles and inheriting by reference. I messed up a bit since I had not done Java since the beginning of the year. The next two questions I could do in any language. He asked me a question on finding palindromes and an iterative approach to calculating the Fibonacci sequence. I solved both quite easily, and the interviewer was pleased. I received an email stating that I had moved to the third round the next day.
The last interview was with a senior manager. It was somewhat similar to the first behavioral interview, though I didn't quite hit it off as well as I had last time. There were more orthodox behavioral questions on my past experiences and internship, as well as plans for the future. He also asked about any other offers/opportunities I was considering.
I received a call next week about an offer. I did not negotiate since they had offered a pay that was much higher than I expected, as well as a hefty signing bonus.
All questions that I was asked and I can remember are in the description.
The following metrics were computed from 1 interview experience for the AT&T Software Development role in Seattle, Washington.
AT&T's interview process for their Software Development roles in Seattle, Washington is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for AT&T's Software Development interview process in Seattle, Washington.