AT&T Data Scientist interview typically runs 3 rounds: HR, technical live coding, behavioral. Timeline is usually fast, with responses within hours, but office logistics can be disorganized.
$144K
Avg. Base Comp
$200K
Avg. Total Comp
3
Typical Rounds
1-2 weeks
Process Length
Our candidates report that AT&T’s data scientist interviews are less about exotic technical depth and more about whether you can stay crisp under very ordinary pressure. The technical bar in the experience we saw was intentionally accessible — basic SQL and Python on the spot — but that simplicity is deceptive, because the company seems to use it as a filter for composure and clean thinking rather than cleverness. Even the one technical concept called out, bagging vs. boosting, points to a preference for fundamentals over flash.
What stands out more is the behavioral side. Multiple prompts centered on ambiguity, mistakes, leadership style, and how someone would explain a new idea to a senior manager, which tells us AT&T is looking for people who can operate in a structured corporate environment without getting rattled when plans change. Our candidates report that the interviewers wanted concrete examples, not polished narratives, and that fit questions like “what can you bring to AT&T?” were treated seriously, not as filler.
A recurring theme is that the process can feel administratively uneven even when the questions themselves are straightforward. One candidate described being moved between offices without warning, and heard of others experiencing the same thing. That suggests the non-obvious test here is not just technical readiness, but whether you can remain professional and adaptable when the company’s own logistics are messy.
Synthesized from 1 candidate report 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.
The process was pretty straightforward on paper, but the office logistics were messy enough that it became the most memorable part for me. I had an initial HR round, then a technical round that was live coding with super easy SQL and Python, and after that a behavioral round with a program manager. I heard back from the first two rounds within a few hours, which made the turnaround feel fast, but between the technical and behavioral rounds they moved me from office A to B without telling me. I only found out after I asked the manager, and they said office A was full. That part felt disorganized, especially because I later heard of someone else being shifted between offices for the same role right before the final round too.
The technical round was not hard if you’re comfortable writing basic SQL and Python on the spot. The behavioral round was more structured around how I handle ambiguity and leadership. I was asked about something unexpected that interrupted a project, a mistake I made, my leadership style, a time I had to deviate from the original plan, an area for improvement and what I did about it, and how I would present a new creative idea to a senior manager. They also asked what I could bring to AT&T, so it was clearly about fit as much as experience. Overall the questions were pretty standard, but they wanted concrete examples and not just polished answers. I didn’t get an offer, and the main takeaway for me was to be ready for very basic coding plus a lot of behavioral depth, while also not assuming the office assignment is settled until the end.
Prep tip from this candidate
Brush up on basic live-coding SQL and Python, since that round was described as very easy but still on the spot. For the behavioral round, prepare concise examples for project interruptions, mistakes, leadership style, adapting plans, and pitching ideas to senior management.
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 | |
|---|---|
| Revenue Leakage Signals | |
| Unlimited Plan Abuse | |
| Stakeholder Communication | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Prime to N | |
| Average Quantity | |
| Over-Budget Projects | |
| Hurdles In Data Projects | |
| Find the Missing Number | |
| Size of Joins | |
| Closed Accounts | |
| Retailer Data Warehouse | |
| Employee Project Budgets | |
| The Brackets Problem | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Find the Index with Equal Left and Right Sum | |
| Sort Strings | |
| String Subsequence | |
| Cyclic Detection | |
| Get Top N Frequent Words | |
| Total Salary | |
| Total Transactions | |
| Append Frequency | |
| Groups of Anagrams | |
| Random Forest Explanation | |
| Swapping Nodes |
Synthesized from candidate reports. Individual experiences may vary.
An initial HR conversation to review your background, interest in the Data Scientist role, and basic fit. In this experience, the candidate heard back quickly after this round, suggesting a fast-moving process.
A live coding round focused on very basic SQL and Python. The questions were described as straightforward for someone comfortable writing code on the spot, with emphasis on practical execution rather than difficult algorithms.
A structured behavioral discussion centered on ambiguity, leadership, and fit for AT&T. The interviewer asked for concrete examples about unexpected project interruptions, mistakes, leadership style, deviating from a plan, areas for improvement, and how the candidate would pitch a creative idea to a senior manager.
