AT&T Software Engineer interviews typically start with a timed HackerRank-style assessment covering coding, SQL, and REST questions, followed by one or two technical rounds and behavioral conversations; timelines vary, and some candidates report long gaps between steps.
$119K
Avg. Base Comp
$161K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Across both the general Software Engineer track and the Technology Development Program (TDP), candidates consistently describe an online assessment as the first real hurdle. It's usually a timed HackerRank-style test, often around three hours with four to six questions. It mixes LeetCode-style data structures and algorithms problems with SQL and REST/HTTP API questions. Several candidates note the difficulty swings from easy to genuinely hard, with dynamic programming or permutation problems showing up alongside simpler list and string questions. Because of that spread, treating the OA as a serious coding screen rather than a light new-grad warm-up is the most consistent advice in these accounts.
After the OA, most candidates move into one or two technical interviews, frequently with current TDP engineers. These combine live coding (commonly LeetCode easy-to-medium) with debugging exercises, OOP fundamentals like inheritance and polymorphism, and a lightweight system or feature-design discussion. Some candidates were also asked how they would debug a backend performance issue, handle a loaded server, or implement an LRU cache, so practical engineering judgment matters as much as raw coding speed.
Behavioral rounds, typically with a recruiter or hiring manager, lean on STAR-style prompts. Candidates report questions about presenting without preparation, resolving conflict with teammates, failure, and learning a new system. A number of candidates also mention slow or inconsistent communication between steps, including multi-week or even multi-month gaps. Following up proactively with your recruiter may help you manage expectations.
Synthesized from 20 candidate 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
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Unlimited Plan Abuse | |
| Stakeholder Communication | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Prime to N | |
| Merge Sorted Lists | |
| Over-Budget Projects | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Find the Missing Number | |
| Address Schema | |
| Retailer Data Warehouse | |
| Employee Project Budgets | |
| The Brackets Problem | |
| Find the First Non-Repeating Character in a String | |
| P-value to a Layman | |
| Average Quantity | |
| Find the Index with Equal Left and Right Sum | |
| Google Maps Improvement | |
| Sort Strings | |
| Groups of Anagrams | |
| Real-Time Transaction Streaming | |
| String Subsequence | |
| Get Top N Frequent Words | |
| Cyclic Detection | |
| Skyscanner Partner ETL | |
| Append Frequency | |
| Find Duplicate Numbers in a List | |
| Type-ahead Search |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a timed HackerRank online assessment, frequently around three hours with four to six questions. It mixes LeetCode-style data structures and algorithms problems with SQL and, in many cases, a REST/HTTP API question. Difficulty is typically uneven: some report mostly easy-to-medium problems, while others describe one or two notably hard questions involving dynamic programming or permutations.
Many candidates describe a recruiter or behavioral screening conversation covering background, location preferences, and standard behavioral prompts. Examples include how you handle conflict, your greatest technical strength, how you prepare a pitch, or a time you had to learn a new system. This round is generally lighter than the technical stages and focuses on communication and fit.
Candidates typically have one or two technical rounds, often with two current TDP engineers; one candidate described the round as about an hour. These rounds commonly combine live coding (LeetCode easy-to-medium, sometimes a debugging exercise with planted logical errors) with OOP fundamentals like inheritance and polymorphism and a lightweight system or feature-design question. Some candidates were also asked about debugging backend performance issues, handling a loaded server, implementing an LRU cache, or choosing database types for a web app.
The closing round is usually behavioral, with a hiring manager, TDP manager, or associate director, and is described as running about an hour. Candidates report STAR-style prompts about teamwork, failure, cooperation, and presenting without preparation. One candidate noted this round also covered how they would define and apply automation.
