Candidates describe a Comcast Data Analyst interview built around SQL, with Tableau or Python in some cases, plus behavioral questions about past projects and why you want Comcast. Reports cover three to four rounds.
$103K
Avg. Base Comp
$115K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Comcast Data Analyst interview as SQL-heavy, with a behavioral layer that can include why you want to work at Comcast. Every technical account mentions SQL, and the reported level ranges from basic to intermediate.
One candidate who received an offer described a Tableau and SQL round followed by a SQL-only round. That SQL round also tested business judgment, not just syntax. Another offer recipient reported three technical rounds plus a final manager conversation, with questions on IN versus EXISTS, finding the max salary in a department, query optimization and window functions. That candidate put the whole process at roughly two to three weeks.
Behavioral questions appear in several accounts. They include a challenge at work, a time you could not get your way, and why you want to work at Comcast. One candidate said the hiring manager pushed back when their answer focused on personal career goals instead of the company. A candidate for an internship-level role also reported a HireVue video screen and a JOIN versus INNER JOIN question before a rejection.
Role scope can vary. One candidate described a Philadelphia-based opening focused on auditing data across product and channel streams and helping shape an audit framework, with Python and SQL rounds. Ask the recruiter early whether the work leans toward dashboards, reporting or auditing. Reports are few and mixed, so treat the details as signals rather than a fixed format.
Synthesized from 4 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 Comcast process.
I went through three technical rounds plus a final manager conversation. The first round was online and covered SQL basics — they asked about the difference between IN and EXISTS clauses, then moved into more complex queries like finding the max salary in a department. I had to think through query optimization and window functions as well. The second round was face-to-face and felt like a continuation of the same technical focus, drilling deeper into SQL and how I'd approach real-world problems. By the third round, I was on a call with the US team and the questions were similar in nature but the conversation felt less like an interrogation and more like they were genuinely assessing how I'd work with their actual systems. The final round with my soon-to-be manager was more conversational — less about drilling specific SQL syntax and more about how I'd fit into the team and what I was looking to accomplish in the next few years. Overall, the process moved pretty smoothly. The interviewers seemed to have done their homework on my background, and I never felt rushed or blindsided. Turnaround was reasonable, maybe two to three weeks from start to offer. The main takeaway is that they're serious about SQL fundamentals here — it's worth spending time on query optimization and window functions specifically, not just basic SELECT statements.
Prep tip from this candidate
Focus heavily on SQL optimization, window functions, and the semantic differences between IN and EXISTS — these came up repeatedly. Practice writing queries that handle max values in groups and be ready to discuss trade-offs in query performance.
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 | |
| Improve Search Results | |
| Address Schema | |
| Hurdles In Data Projects | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Prime to N | |
| Employee Salaries (ETL Error) | |
| Monthly Customer Report | |
| Paired Products | |
| Top 3 Users | |
| Size of Joins | |
| Decreasing Comments | |
| Get Top N Frequent Words | |
| Google Maps Improvement | |
| Button AB Test | |
| P-value to a Layman | |
| Raining in Seattle | |
| Over-Budget Projects | |
| Bagging vs Boosting | |
| Youtube Recommendations | |
| Bank Fraud Model | |
| Closed Accounts | |
| Duplicate Rows | |
| Liked Pages | |
| Identifying User Sessions |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an opening conversation with a recruiter, a hiring manager or a HireVue video. Questions included a work challenge and why you want to work at Comcast. Prepare a Comcast-specific motivation answer, since one candidate was pressed on this.
Candidates describe technical rounds centered on SQL, with Tableau in one account and Python in another. Reported topics include IN versus EXISTS, JOIN differences, max values within groups, window functions and query optimization. Difficulty is typically described as moderate.
One candidate reported a SQL-focused round that also tested business knowledge and how analysis would be applied. Another described a face-to-face round and a call with the US team that continued the SQL focus. Be ready to explain your reasoning aloud, not just write queries.
One candidate reported behavioral conversations about past projects, communication and teamwork, including a time they could not get their way. One offer recipient had a final manager conversation about team fit and goals over the next few years. Prepare concrete project examples.
