Comcast Behavioural Interview: 6 Competencies to Nail
Six competencies that large media and technology employers like Comcast commonly probe in behavioural interviews, plus a worked STAR answer and a prep checklist you can use this week.
What a Comcast behavioural interview is really testing
A behavioural interview asks you to describe real situations from your past rather than hypothetical ones. The reasoning is simple: how you acted before is the best available predictor of how you will act in the job. Expect prompts such as 'Tell me about a time when…' or 'Give me an example of…'.
Comcast is a large media, connectivity and technology company, and its roles range from customer-facing and field positions to engineering, sales, marketing and corporate functions. The exact format varies by role, location and team, and we can't tell you the specific questions you will get. What we can say is that the competencies below are the ones large, customer-facing, fast-changing organisations commonly assess. Check the job description and Comcast's careers pages for the values and behaviours they state publicly, and mirror that language where it is honest to do so.
Depending on the role, you may meet a recruiter screen, a one-way video interview, a hiring-manager conversation or a panel. Behavioural questions can appear in any of them, so one set of well-built stories will serve you throughout.
Six competencies commonly assessed (and what interviewers listen for)
You don't need a different story for every question. Prepare six to eight strong examples and map each to one or two of these themes.
- Customer focus: Did you understand what the customer or internal stakeholder actually needed, and go beyond the minimum? Listen-for: you identified the real problem, not just the stated request.
- Ownership and accountability: Did you take responsibility, follow through and own mistakes? Listen-for: 'I' language, clear decisions, and honesty about what went wrong.
- Collaboration: Did you work effectively across teams or with people you disagreed with? Listen-for: how you built trust and shared credit.
- Adaptability and handling change: How did you respond when priorities, tools or plans shifted? Listen-for: calm, quick learning and a practical response rather than complaints.
- Problem solving and use of data: Did you break a problem down, weigh options and use evidence? Listen-for: your reasoning, not just the outcome.
- Communication and influence: Could you explain something complex simply or bring someone round to your view? Listen-for: tailoring your message to the audience.
Structure every answer with the STAR method
STAR keeps answers focused and complete. Situation: the context in one or two sentences. Task: your specific responsibility or goal. Action: what you did, step by step, which should take most of your time. Result: the outcome, ideally quantified, plus what you learned.
The most common mistake is spending 60% of the answer on the situation. Aim for roughly 15% Situation and Task combined, 60% Action, and 25% Result and reflection.
Here is an example for a customer-focus question: 'Tell me about a time you went beyond what a customer asked for.' It is an illustrative answer to adapt with your own facts, not a script.
- Situation: 'In my role on a retail support desk, a customer called for the third time about the same intermittent connection fault. Previous contacts had each been closed as resolved.'
- Task: 'I was responsible for resolving the call, but I could see that closing it again wouldn't fix the underlying problem.'
- Action: 'I read the notes from the earlier contacts and noticed the faults all happened in the evening. I asked the customer when it occurred and how many devices were in use, then arranged a technician visit in a slot that suited them. I also wrote up the pattern for my team lead so the next agent wouldn't start from scratch.'
- Result: 'The technician found a faulty splitter and the customer had no further contacts over the next month. My team lead adopted the note format for repeat-fault cases. I learned to check the history before the script.'
Reading about it isn't the same as doing it on camera.
Run a free timed mock interview →Do and don't: the difference between average and strong answers
Small phrasing choices change how your answer lands. Compare these approaches.
- Don't say 'We decided to…' throughout. Do say 'I proposed… and the team agreed' so your contribution is clear.
- Don't pick a story with no stakes. Do choose one where something was genuinely at risk: time, money, a relationship or a deadline.
- Don't claim a perfect outcome every time. Do include one story where things went partly wrong and explain what you changed.
- Don't finish with 'and it went well'. Do finish with a measurable or observable result: time saved, error rate down, a customer retained, feedback received.
- Don't recite jargon from the job advert. Do use plain language and let your actions demonstrate the competency.
Handling a one-way video format
If your interview is recorded, you will typically see the question on screen, get a short preparation window and then answer to camera within a time limit. There is no interviewer to react to you, so structure carries more weight. Make sure you can deliver a full STAR answer in 90 seconds to two minutes, and check the exact limits in your invitation.
Look at the lens rather than the screen, sit with good front lighting, and test your audio beforehand. Use the preparation time to jot down only keywords, such as the story you'll use and your result, rather than a script. Reading sounds stilted on video.
Practising out loud matters more than most candidates expect. A tool like ScreenReady lets you rehearse timed, on-camera answers and get AI feedback on structure and delivery, which is useful for spotting rambling or a missing Result before the real thing.
A practical preparation checklist
Work through this in the week before your interview.
- Read the job description and highlight the three or four behaviours it stresses most.
- Write six to eight stories in STAR bullet form, covering the six competencies above.
- Add a number or concrete outcome to each Result, being careful to stay accurate.
- Prepare one failure or mistake story that shows learning and accountability.
- Time yourself: each answer should land between 90 seconds and two minutes.
- Practise aloud on camera, then review for filler words, pace and eye contact.
- Prepare two thoughtful questions about the team, customers or how success is measured.
Frequently asked questions
What kinds of questions are asked in a Comcast behavioural interview?
They vary by role, and we can't know the specific questions. In general, expect 'tell me about a time…' prompts on customer focus, teamwork, handling change, problem solving, ownership and communication. Preparing flexible STAR stories is more reliable than trying to guess exact questions.
How long should my STAR answers be?
Aim for about 90 seconds to two minutes when speaking. That is long enough to give real detail on your actions and result, and short enough to hold attention. For recorded interviews, check the time limit given per question and stay comfortably inside it.
What if I don't have work experience relevant to the question?
Use examples from university, volunteering, part-time jobs, sports or community projects. Interviewers care about the behaviour you demonstrate, such as taking ownership or helping someone, more than the setting. Just make sure your own role in the story is clear.
Can I reuse the same story for different questions?
Yes, within reason. A single story about a difficult project can show problem solving in one answer and collaboration in another, if you emphasise different actions. Avoid repeating the same story within one interview, though, so have enough distinct examples ready.
Practise for these companies
Put this into practice
ScreenReady builds a realistic, timed mock interview around your target role, records your answers on camera, and gives AI feedback on structure, evidence and delivery.
Start a free mock interview →