Reported Comcast Software Engineer interviews combine project discussion, coding fundamentals, REST API and SQL questions, plus a pen-and-paper subsequence exercise.
$138K
Avg. Base Comp
$180K
Avg. Total Comp
Not reported
Typical Rounds
2-4 weeks
Process Length
Comcast Software Engineer preparation should cover both project depth and practical coding fundamentals. A directly matching report described a recorded video interview, a recruiter phone screen, an at-home coding assignment, and technical conversations. The live discussion spent substantial time on a previous project, including its technical details, the decisions made, and the resulting impact. Prepare a clear account of work you owned, with enough detail to explain tradeoffs instead of relying on a high-level overview.
Technical discussion in the report included RESTful API practices, SQL query order of operations, DSA, and OOP concepts. The candidate also encountered a medium subsequence problem on paper. Practice structuring an approach aloud: clarify the problem, describe the algorithm, call out edge cases, and explain complexity before writing code. That habit is especially useful when you cannot run a solution or use test cases.
The reported process was practical rather than purely algorithmic. Bring a concise project narrative, refresh API and SQL basics, and rehearse a medium coding problem without an editor. Be ready to connect implementation choices to the goals and constraints of your past work, since communication and technical judgment were both central to the account.
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 Comcast process.
The hardest part of my Comcast interview was actually the format, not the difficulty of the questions. My process was pretty short: it started with a recorded video interview, and then I had a 30-minute live interview where we spent most of the time talking through a project I had worked on before. The live round felt more like a technical discussion than a formal grilling. They asked me to explain the technical details of the project, the decisions I made, and the overall impact, so I had to be ready to go deep on my own work rather than just recite buzzwords.
There was also a technical recruiter phone screen in the process, and after that I had an at-home coding assignment before meeting the technical team on Teams. In that technical conversation, they asked about RESTful API practices, and in another round I was asked a SQL question about the order of operations in a query. One interview also included DSA and OOP concepts, and the questions were framed around how well I understood the breadth of the project I was working on. The most unusual round was a pen-and-paper coding test with a medium-level subsequence problem, which was a little awkward because I couldn’t rely on a computer or test cases. Overall, the process felt practical and project-heavy, with enough coding to confirm fundamentals but a lot of emphasis on explaining real engineering choices. I ended up getting an offer and not moving forward in another, so it seemed like being clear, structured, and confident about your past work really mattered.
Prep tip from this candidate
Be ready to explain one of your past projects in depth, including the technical decisions you made and the impact it had. Also review RESTful API basics, SQL order of operations, and be comfortable solving a medium subsequence-style DSA problem without a computer.
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 | |
|---|---|
| Address Schema | |
| String Subsequence | |
| Type-ahead Search | |
| Hurdles In Data Projects | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Monthly Customer Report | |
| Prime to N | |
| Rolling Bank Transactions | |
| P-value to a Layman | |
| Retailer Data Warehouse | |
| Top 3 Users | |
| Raining in Seattle | |
| Google Maps Improvement | |
| Over-Budget Projects | |
| The Brackets Problem | |
| Size of Joins | |
| Bagging vs Boosting | |
| Employee Project Budgets | |
| Permutation Palindrome | |
| Integer to Roman | |
| Liked Pages | |
| One Element Removed | |
| Sort Strings | |
| Basic Regex | |
| Cyclic Detection |
Synthesized from candidate reports. Individual experiences may vary.
The Software Engineer report said the process began with a recorded video interview. No specific prompts were provided, so prepare concise spoken explanations of your background, engineering experience, and the projects most relevant to the role.
A technical recruiter phone screen was also reported. The account does not specify its questions or order relative to every other stage, but candidates can prepare a focused overview of their experience and the work they want to discuss in depth.
The candidate reported completing an at-home coding assignment. Its subject and evaluation criteria were not described. Practice delivering a clear, maintainable solution and be prepared to explain the reasoning behind important implementation choices.
In a reported 30-minute live interview, most of the conversation focused on a past project. Questions covered technical details, decisions, and impact. Prepare one project story with clear ownership, constraints, tradeoffs, and outcomes.
Reported technical topics included RESTful API practices, SQL order of operations, DSA, and OOP concepts. The candidate also described a pen-and-paper medium subsequence problem. Rehearse explaining an algorithm, edge cases, and complexity without relying on a computer.
