AT&T Software Engineer interview typically runs 4 rounds: online assessment, technical interview, behavioral screen, and final behavioral. The process usually takes a few weeks and is fairly structured, though some candidates report long gaps between steps.
$118K
Avg. Base Comp
$153K
Avg. Total Comp
4-5
Typical Rounds
3-8 weeks
Process Length
Our candidates consistently report that AT&T is less interested in one narrow specialty than in whether you can move comfortably across the stack. The strongest signal is breadth with fundamentals: we’ve seen coding questions ranging from easy string work to harder permutation, graph, and dynamic programming problems, but those are often paired with REST, SQL, backend performance, and basic OOP. In other words, the company seems to care less about whether you’ve memorized a single pattern and more about whether you can explain why a solution works and how it fits into a real system.
A recurring theme is that the interviews reward candidates who can talk through practical engineering tradeoffs. Multiple candidates were asked to debug code, reason about a loaded server, or design a simple app or feature, and the follow-up questions often pushed into implementation details like LRU behavior or database choices. We’ve also seen a clear emphasis on communication under ambiguity: several experiences mention oddly phrased prompts, unstructured conversations, or interviewers who wanted candidates to justify decisions clearly rather than just arrive at the right answer. That makes the process feel more like a working session than a whiteboard performance.
The non-obvious make-or-break factor here is consistency. Some candidates found the process friendly and transparent, while others described it as uneven or overly monitored, especially in the assessment. That means polished technical ability alone may not be enough; our candidates who did best were the ones who stayed calm when the prompt was messy, handled follow-ups cleanly, and could connect coding answers back to backend realities and team collaboration.
Synthetized from 6 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the AT&T process.
I got pushed through a pretty mixed process that started with an online exam and then moved into a more project-focused technical round. The first hurdle was a HackerRank-style test with five to six questions, and that part felt the toughest to me because the wording was a little weird and the problems ranged from easy to hard. I remember seeing a permutation-type LeetCode hard question, plus other questions that leaned into DP and generators. It was fair in the sense that the problems were solvable, but I was not ready enough for the format and the pressure definitely got to me.
After that, I had a second round where they asked about my backend assignment and drilled into how I would handle issues in a loaded server. There were also some more straightforward technical questions, like how to compare two strings, and one LRU-based design question where I had to explain how I would implement it. In the TDP-style interview, they also mixed in a few OOP questions, including the four principles and what inheritance is and why it matters, plus a sort of lightweight system design prompt about how I would build an app that lets users post information. That round felt less like pure coding and more like seeing whether I could explain fundamentals clearly and think through practical tradeoffs.
I did not move forward, and the recruiter had assigned me to a location that was already filled, so even after doing well technically there was no next step. Overall, the process felt a bit inconsistent, but the main thing to prepare for is the online assessment format itself, especially harder-than-expected questions and oddly phrased prompts, along with being ready to talk through backend design, OOP basics, and an LRU implementation.
Prep tip from this candidate
Practice HackerRank-style questions with unusual wording, especially DP and permutation problems, and make sure you can explain an LRU cache implementation clearly. Also be ready to talk through backend bottlenecks like a loaded server and basic OOP concepts such as inheritance and the four principles.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at AT&T
How would you determine if high off-peak data usage is fraud or abuse, and what would you do about it?
| Question | |
|---|---|
| Stakeholder Communication | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Prime to N | |
| Merge Sorted Lists | |
| Hurdles In Data Projects | |
| Find the Missing Number | |
| Size of Joins | |
| The Brackets Problem | |
| Address Schema | |
| Employee Project Budgets | |
| Average Quantity | |
| Google Maps Improvement | |
| Find the Index with Equal Left and Right Sum | |
| Sort Strings | |
| P-value to a Layman | |
| Get Top N Frequent Words | |
| Append Frequency | |
| Cyclic Detection | |
| Type-ahead Search | |
| Target Indices | |
| Swapping Nodes | |
| Total Transactions | |
| Total Salary | |
| Swap Variables | |
| Merge N Sorted Lists | |
| String Palindromes | |
| Payments Received | |
| Type I and II Errors |
Synthesized from candidate reports. Individual experiences may vary.
The process may begin with a resume screening before any technical interview is scheduled. In some cases, this stage also includes basic discussion of background and location preferences.
Candidates complete a HackerRank-style assessment with five questions, often mixing LeetCode-style coding problems with REST/API or SQL questions. The difficulty can range from easy to very hard, and some candidates reported needing to keep their camera on throughout.
This round is typically conducted with two current TDP engineers or software engineers and focuses on live coding plus practical engineering fundamentals. Expect LeetCode-style problems, debugging exercises, OOP concepts, backend performance questions, and sometimes light system design or database questions.
A behavioral round is often conducted with a recruiter, TDP manager, or another hiring leader. Questions are scenario-based and focus on teamwork, conflict, communication, learning new systems, and how you handle failures or presentations.
Some candidates had a final behavioral conversation with the hiring manager, associate director, or similar leader. This stage is used to assess fit, communication, and judgment, and it may be the last step before a decision.