← Back to Directory

AT&T interview notes, page 6 of 6

Large Enterprises

Most of these AT&T write-ups come from Software Engineers (56), then Data Scientists (1). The most reported rounds are the technical phone screen (15), the hiring manager screen (14), the system design round (7) and the multi-round onsite (6).

57 interview notes · updated Oct 2026

AT&T·Software Engineer·Hiring Manager Screen

Sep 2026
Applied internally for a Supply Chain Manager role with 7 years of SCM experience but no bachelor's degree, got a recruiter screen and then a Zoom call with the hiring manager that ran way over the scheduled 30 minutes. The hiring manager was friendly and talked a lot, asked three questions I'm pretty sure I fumbled, and closed with the classic 'we'll be in touch.' Trying to read the tea leaves here.
  • Walk me through your background and experience in supply chain management.
  • How have you handled a situation where your team or process wasn't meeting expectations?
  • How do you prioritize competing demands or tasks when managing supply chain operations?

“I thought I had this one.”

View Post

AT&T·Software Engineer·Onsite - Multi Round

Sep 2026
Seven rounds over four months, including a full onsite in Dallas where they flew me out, put me up in a hotel, and had me talk to five different people. Then they rejected me with feedback so vague it was basically useless.
  • Why do you want to leave your current position, and what specifically draws you to this company?

“This is apparently what tanked me, which is wild because I was straightforward about it from day one.”

View Post

AT&T·Software Engineer·Recruiter / HR Screen

Sep 2026
Went in for a recruiter screen after getting fired, tried to spin the situation as gracefully as possible, and now I'm stuck waiting two weeks for an answer that's probably already a no.
  • Are you currently employed, and if not, what happened at your last position?

“Said something like 'I concluded my time there a few weeks ago and I'm looking for the next opportunity.' Which, sure, technically true.”

View Post

AT&T·Software Engineer·Recruiter / HR Screen

Sep 2026
Recruiter screen that ended with a project deep-dive question shoehorned into the last five minutes. Left feeling like the answer didn't land, mostly because I'm still not sure what they were actually looking for.
  • Tell me about a project you've worked on.

“Five minutes left on the clock and this is what they ask.”

View Post

AT&T·Software Engineer·Hiring Manager Screen

Sep 2026
Went for a permanent IT developer role after 13 years contracting, figured it was worth a look. The hiring manager asked exactly one question, lost it when I didn't spit out a number immediately, declared himself an 'expert at interviewing', and hung up. Whole thing lasted maybe six minutes.
  • What salary are you looking for?

“I said something reasonable: coming from contracting, salary alone doesn't tell the whole story, and I'd need to understand the role better before throwing out a number.”

View Post

AT&T·Software Engineer·Recruiter / HR Screen

Sep 2026
Did an AI-conducted behavioral interview for an IT internship and it did not go well. Four questions total, two were fine, two completely derailed me. I kept asking to restart mid-answer and now I'm sitting here wondering if I should just email the recruiter or pretend it never happened.
  • Describe a situation where you had to adapt to an unexpected challenge or change.
  • Tell me about a time you worked through a conflict with a teammate or colleague.
  • Walk me through a time you successfully completed a technical or work-related task under pressure.
  • Describe an experience where you had to collaborate with others to achieve a goal.

“This was one of the two that wrecked me.”

View Post

AT&T·Software Engineer·Technical Phone Screen

Oct 2026
Technical interview that started well on the experience and systems side, then fell apart when it came to actually writing the code. Could talk through the solution fine but completely blanked when they asked me to implement it.
  • Walk us through a system you've worked on and what changes or improvements you would make to it.
  • Implement the solution you just described in code.

“This part actually went fine.”

View Post