Prepare for AT&T analyst interviews with reported online assessments, behavioral screens, pandas or Excel tests, and case work. Two candidate reports describe different analyst-style tracks.
$101K
Avg. Base Comp
$117K
Avg. Total Comp
5 rounds
Typical Rounds
Not reported
Process Length
AT&T analyst-style interviews appear to combine a practical skills check with several behavioral conversations. The reports behind this guide come from two differently titled analyst tracks, so treat them as separate examples, not one fixed process.
One candidate in a TDP program described five rounds: a HackerRank assignment built around a Jupyter notebook, a phone screen with three mostly behavioral questions, a recruiter round with four or five situational questions, a technical interview on pandas and data manipulation, and a final behavioral conversation. That candidate found the technical round practical, not algorithm-heavy, and was asked about giving a presentation with little preparation. The outcome was no offer.
A candidate for a Strategy Analyst role reported an online assessment with basic math, Excel, and SQL, then a recruiter phone screen, then three online interviews of roughly an hour to ninety minutes. Those included a market-sizing case on pricing an inflight wifi service, an Excel test that felt harder than expected, a second case, and a PowerPoint presentation of findings. That candidate received an offer but described slow, inconsistent communication afterward.
For preparation, practice structured estimation, Excel formulas and data manipulation under time pressure, and basic SQL or pandas work. Prepare short stories about working under pressure and explaining your background. If you are applying to a different analyst track, confirm which assessments apply with your recruiter.
Synthesized from 3 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 went through five rounds total, which was more intensive than I initially expected. The process started with an assignment on HackerRank where I worked through a Jupyter notebook problem to demonstrate basic technical capability. That felt like a natural filter before the heavier lifting began.
The phone screening came next with three questions that were mostly behavioral in nature. Then there was a recruiter round with four or five additional questions, still focused on situational and experience-based topics. I remember one question asking me to describe a time I had to make a presentation without much preparation—they were really testing how I handle pressure and ambiguity.
The technical interview was surprisingly light compared to the earlier rounds. It focused on pandas and data manipulation in Python, nothing too algorithmically intense. They were checking that I could actually work with data, not that I could solve LeetCode problems. The questions felt practical and relevant to what the role would actually involve.
The final round was another behavioral interview, which by that point felt more like a conversation about fit and culture. Overall, the interviewers were accommodating and honest about the role expectations. They didn't sugarcoat what the work would entail, and I appreciated that directness. While I ultimately didn't receive an offer, I felt the process was well-designed to evaluate both technical and soft skills, and the feedback throughout was constructive.
Prep tip from this candidate
Prepare concrete stories for behavioral questions around working under pressure and on short timelines—that theme came up repeatedly. For the technical portion, focus on practical pandas and data manipulation tasks rather than algorithm complexity; be ready to write clean, efficient code for real data scenarios.
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 | |
| Prime to N | |
| Size of Joins | |
| Hurdles In Data Projects | |
| Find the Missing Number | |
| Closed Accounts | |
| Retailer Data Warehouse | |
| Employee Project Budgets | |
| P-value to a Layman | |
| Average Quantity | |
| Google Maps Improvement | |
| Sort Strings | |
| Groups of Anagrams | |
| Get Top N Frequent Words | |
| Cyclic Detection | |
| Over-Budget Projects | |
| Payments Received | |
| Target Indices | |
| Address Schema | |
| Precision and Recall | |
| Testing Price Increase | |
| Success Measurement | |
| 7 Day Streak | |
| Data Pipelines and Aggregation | |
| Out of Stock Inventory |
Synthesized from candidate reports. Individual experiences may vary.
Both analyst-style reports began with an online task. One candidate completed a HackerRank assignment based on a Jupyter notebook. The other reported basic math, Excel, and SQL questions. The format may vary by track, so expect a fundamentals check rather than an advanced test.
Candidates report early conversations focused on behavior and fit. One described a three-question phone screen and a separate recruiter round with four or five situational questions, including presenting with little preparation. The other described a recruiter screen on background and role fit.
The technical content differed by track. The TDP candidate reported a practical pandas and data manipulation interview. The Strategy Analyst candidate reported a market-sizing case on inflight wifi pricing, plus an Excel test that was harder than expected and had a time limit.
The Strategy Analyst candidate reported three online interviews of about 60-90 minutes each. These included a second case and a PowerPoint presentation of findings. Others may encounter a different mix, so confirm the format with your recruiter.
The TDP candidate described a final behavioral round that felt like a fit and culture conversation, and ended with no offer. The Strategy Analyst candidate received an offer, but reported that the promised one-week response slipped and recruiter follow-up was inconsistent.
