← Back to Directory

AT&T interview notes, page 2 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·Technical Phone Screen

May 2026
Technical phone screen for a software engineer role, just one coding question around text search and indexing. Pretty focused session, no behavioral stuff at all.
  • Given a dictionary mapping integer indices to sentence strings and a single query word, return a sorted list of the indices where that word appears. Matching should be case-insensitive and word-boundary aware.

“My first instinct was just to loop through every sentence and split on whitespace, which works fine for one query.”

View Post

AT&T·Software Engineer·Onsite - Cross-functional / Panel

May 2026
Research presentation round for a Seismic Imaging Analyst role that went sideways pretty fast. Two interviewers kept questioning why I even applied, since my research background didn't line up with the job scope at all. To be fair, I hadn't applied directly, so that was a fun dynamic to navigate for an hour.
  • Why did you apply for this role given that your research background seems quite distant from what we do here?

“This came up almost immediately and I had no clean answer because I genuinely hadn't applied directly.”

View Post

AT&T·Software Engineer·Technical Phone Screen

May 2026
Coding interview that went sideways not because the problem was hard, but because the bar was apparently 'solve it perfectly with zero hints in record time.' Failed despite getting the right answer eventually.
  • Solve a coding problem and then iteratively optimize your solution toward the best possible time complexity.
  • Identify all edge cases and test cases for your solution.

“Got the initial solution fast, maybe five minutes.”

View Post

AT&T·Software Engineer·Hiring Manager Screen

May 2026
First real SWE interview after finishing a CS degree, coming from an automotive engineering background. The screen went reasonably well covering projects and general CS concepts, but the interviewer flagged concerns about raw coding ability and gave a heads-up that the next round would be algorithm-heavy.
  • Walk me through your capstone project.
  • How do you approach debugging a problem in your code?
  • Can you explain object-oriented programming concepts?
  • How do databases work, and what experience do you have with them?
  • What do you know about APIs and how have you worked with them?
  • How would you approach designing a simple system from scratch?

“This was the comfortable part.”

View Post

AT&T·Software Engineer·Technical Phone Screen

May 2026
Short technical screen for a data engineer role, basically just one SQL question and that was it. Pretty low-key, nothing fancy.
  • You have two tables: one containing streamer information and one containing streaming session records. Write a query to compute the total view count for each streaming session, grouped by streamer.

“Pretty standard join question.”

View Post

AT&T·Software Engineer·Technical Phone Screen

May 2026
Thirty-minute technical screen for a senior full stack role that went really well until the last question blindsided me completely. Fifteen years of React and framework-based frontend work, and I got tripped up by vanilla JS state management with no libraries allowed.
  • How would you manage state across components in React?
  • How would you handle state management if you had no framework and no third-party libraries available?

“This was the easy warmup and I actually nailed it.”

View Post

AT&T·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round focused on building an LLM-based log parsing pipeline. The problem was more open-ended than I expected and required thinking through schema variability across log types, which I hadn't really prepped for.
  • Design an LLM-based workflow that can parse and extract structured fields from log messages, where different log types (e.g. access logs vs. error logs) have completely different schemas.

“The tricky part isn't the LLM call itself, it's the schema variability.”

View Post

AT&T·Software Engineer·Hiring Manager Screen

Jun 2026
Hiring manager interview that went fine until the very end, when the guy asked what I currently make and got weirdly cold when I declined to answer.
  • What are your salary expectations?

“I gave my usual deflection, something like I'm open to whatever range you have in mind.”

View Post

AT&T·Software Engineer·Online Assessment (OA)

Jun 2026
Got recruited for an FDE role and was told the Codesignal assessment was just a formality. It was not a formality. Ended up with a 350/600 on what turned out to be a Machine Learning Core Assessment, which felt completely mismatched for a job that's mostly client-facing and data engineering work.
  • Implement a machine learning algorithm from scratch in code, without using any ML libraries or AI tools.
  • Implement a second machine learning concept from scratch in a timed, proctored coding environment.
  • Solve a general (non-ML) coding problem as part of the assessment.

“This is where things fell apart.”

View Post

AT&T·Software Engineer·Technical Phone Screen

Jun 2026
Failed a technical phone screen after making some syntax and naming convention mistakes that the interviewer counted against me, even though I nailed the complexity analysis. Still not sure if I agree with the feedback, but here we are.
  • Solve an algorithmic problem and analyze its time and space complexity.

“Got the right approach and explained the complexity fine at the end, which felt good.”

View Post