AT&T Software Engineer interview questions

15 Software Engineers have shared notes from their AT&T interviews, with the questions they were asked in each round. That is 94% of the 16 AT&T interview notes on Screna AI.

15 Software Engineer interview notes

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

Jun 2026
System design round with a principal engineer for a software engineer role. Felt like a decent environment to work in, though I left unsure whether I'd actually clicked with the interviewer.
  • Design a system for recording meetings and analyzing customer data.

“Meaty prompt.”

View Post

AT&T·Software Engineer·Technical Phone Screen

Jun 2026
Coding screen for a software engineer role, just one problem but it had enough moving parts to trip you up if you weren't careful. The inverted index angle wasn't immediately obvious to me and I spent a minute or two going down a brute-force path before catching myself.
  • Given a mapping of sentence indices to sentence strings, a list of query words, and an integer N, score each sentence by the total number of times any query word appears in it, then return the indices of the top N sentences in descending score order, breaking ties by ascending index.

“My first instinct was to just loop over every sentence for every query word, which works but feels gross once you think about doing it repeatedly.”

View Post

AT&T·Software Engineer·Technical Phone Screen

Jun 2026
Technical phone screen for a software engineer role, just one coding question but it had a complexity discussion attached which I was not fully expecting. Pretty standard stuff but the inverted index angle made it feel slightly more interesting than a typical string problem.
  • Given a mapping from sentence index to sentence text, return a mapping from each word to the sorted list of sentence indices where that word appears. Matching should be case-insensitive, treat whitespace-separated tokens as words, and strip punctuation. Also discuss the time complexity of your solution.

“Basically an inverted index builder.”

View Post

AT&T·Software Engineer·Technical Phone Screen

Jun 2026
Phone screen for a software engineer role, just one coding question with a follow-up variant. Pretty straightforward, nothing that should trip you up if you've done any interval-type problems before.
  • Given a list of entries each containing a timestamp and an intensity value, plus a threshold, return all contiguous time periods where the intensity exceeds that threshold.

“Not a hard problem once you see it as a simple scan and merge intervals thing.”

View Post

AT&T·Software Engineer·Technical Phone Screen

Jun 2026
Technical phone screen for a software engineer role, one coding question about building a rate limiter from scratch. Pretty implementation-heavy, more about getting the details right than any clever algorithm.
  • Implement a token bucket rate limiter class with a method that takes a number of required tokens and a timeout in seconds. The bucket starts full at 1000 tokens, refills continuously at 10 tokens per second up to the max capacity, and each call should block up to the given timeout waiting for enough tokens before returning false.

“The core state is just two fields: current token count and the last refill timestamp.”

View Post

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

May 2026
System design round for a software engineer role, focused entirely on a flight ticket booking system. Pretty deep dive, went from schema design all the way down to B-tree internals and concurrency problems.
  • Design the database schema for a flight ticket booking system. What tables would you create and how would they relate to each other?
  • What indexes would you build on these tables, and why?
  • Can you explain how a B-tree index works internally?
  • Walk through the full UX flow and the backend queries involved when a user books a flight.
  • How would you prevent double booking when two users try to book the same seat at the same time?

“Went with Flight, Passenger, and Flight_ticket tables which felt pretty natural.”

View Post

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

May 2026
System design round for a software engineer role, one question about building an agent-facing support tool with some awkward constraints baked in. Not the most straightforward setup I've seen.
  • Design a support ticket system for agents, where the ticket data is only accessible via a browser (no API), and user data is available through an API that can be used to generate chat responses.

“The no-API constraint on the ticket system is what tripped me up at first.”

View Post

AT&T·Software Engineer·Technical Phone Screen

May 2026
Technical phone screen for a Software Engineer role, one coding problem, rejection came the same afternoon. The problem looked like a standard LRU cache variant until it wasn't.
  • Design and implement an in-memory cache in C++ with bounded capacity, per-entry TTL, and LRU eviction. Expired entries must never be returned. When evicting, prefer removing expired entries before evicting valid LRU entries. Target O(1) average for get and put.

“I knew the standard LRU cache with a doubly linked list and hashmap cold.”

View Post

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

May 2026
System design round for a software engineer role, focused on a counting/rate-limiting type problem. The interviewers got visibly impatient during clarification questions, which threw me off and made the whole thing feel pretty rough.
  • Design a system for counting, rate limiting, or tracking usage statistics at scale.

“The clarification phase went badly.”

View Post

AT&T·Software Engineer·Technical Phone Screen

Apr 2026
Coding round where they asked me to implement a deque from scratch, resize logic included. Pretty standard data structures interview but the resize part tripped me up more than I expected.
  • Implement a deque (double-ended queue) that automatically resizes when it reaches capacity.

“I got the basic push/pop from both ends working fine but the resize logic is where I fumbled.”

View Post