Comcast Data Analyst interview typically runs 3 rounds: screening, Tableau, SQL. It usually takes a few weeks and is uneven, with later rounds more role-relevant.
$85K
Avg. Base Comp
$97K
Avg. Total Comp
3
Typical Rounds
2-4 weeks
Process Length
Our candidates report that Comcast is looking for analysts who can connect the dots between tools and business context, not just recite syntax. In one experience, the early conversation felt generic and light on follow-up, but the later discussions quickly shifted into hands-on Tableau and SQL work. That pattern tells us the company is less interested in polished storytelling than in whether you can actually navigate data, explain your choices, and translate results into something useful for the business.
A recurring theme is that Comcast seems to value practical fluency over deep theory. The SQL questions were described as basic to intermediate, but they weren’t purely technical; they also tested how the candidate would apply analysis to real scenarios. That’s an important signal for this role: we’ve seen that candidates do best when they can show they understand the why behind a query or dashboard decision, not just the mechanics. The bar appears to be centered on clear analytical judgment and comfort with common reporting tools.
We also noticed that the process can feel uneven at first, which means first impressions may not fully reflect the eventual evaluation. One candidate said the initial interviewer seemed disengaged, yet the later rounds were much more relevant and ultimately led to an offer. For us, that suggests Comcast may use the earlier conversation as a broad filter, but the real decision hinges on whether you can handle the day-to-day realities of the role: practical analysis, business-aware interpretation, and solid Tableau/SQL execution.
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 Comcast process.
The process felt pretty uneven at first, mostly because the interviewer in the first conversation seemed disengaged and the questions were very generic. That round was more of a routine screening than a real discussion about my background. I was asked a standard behavioral question about a time I faced a challenge at work and how I handled it, but there wasn’t much follow-up, so it didn’t feel like they were digging into my actual experience or skills.
The later rounds were much more relevant to the Data Analyst role. Round 1 had a lot of Tableau and SQL questions, and Round 2 was focused entirely on SQL. The SQL portion wasn’t just syntax; it also tested business knowledge and how I’d apply analysis to real problems. The questions covered basic and intermediate Tableau and SQL, so I’d say the difficulty was moderate rather than deeply technical, but you still needed to be comfortable explaining your thinking clearly. Overall, the process went better than I expected, and I did get an offer. My main takeaway is that this interview leaned heavily on practical Tableau and SQL fundamentals, so it’s worth being ready for both tool-specific questions and business-oriented analytical scenarios.
Prep tip from this candidate
Brush up on basic and intermediate Tableau and SQL, and practice explaining how you’d apply those skills to business problems. Also be ready for a simple behavioral question about handling a challenge at work, since that came up too.
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 Comcast
Find the missing integer from a array of consequtive integers
| Question | |
|---|---|
| Type-ahead Search | |
| Address Schema | |
| Hurdles In Data Projects | |
| Improve Search Results | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Monthly Customer Report | |
| Prime to N | |
| Compute Deviation | |
| Button AB Test | |
| P-value to a Layman | |
| Paired Products | |
| Top 3 Users | |
| Raining in Seattle | |
| Over-Budget Projects | |
| Size of Joins | |
| Bagging vs Boosting | |
| Decreasing Comments | |
| Google Maps Improvement | |
| Bank Fraud Model | |
| Closed Accounts | |
| Identifying User Sessions | |
| Liked Pages | |
| Revenue Retention | |
| Sort Strings | |
| Digital Library Borrowing Metrics |
Synthesized from candidate reports. Individual experiences may vary.
An initial screening conversation that felt fairly routine and generic. The interviewer asked a standard behavioral question about handling a challenge at work, but there was little follow-up and limited digging into the candidate’s background.
A more role-relevant interview focused on practical Tableau and SQL fundamentals. The discussion included basic to intermediate questions and required the candidate to explain their thinking clearly.
A second technical interview centered entirely on SQL. Beyond syntax, the questions tested business understanding and how the candidate would apply analysis to real-world problems.
