There was an initial interview with the senior developer, a coding challenge, and an interview with the team.
The senior dev interview is informal and a general gauge on you as a person.
The coding challenge is easy; just make sure to follow the directions.
It was an unfortunate case where I didn't appease one out of the three interviewers, so they gave me a pass without any feedback.
One interviewer in particular was hard to deal with and would have been someone who I'd be working closely with.
Amusingly, one interviewer sort of implied he was hard to work with, which is interesting. In other words, I dodged a bullet.
Overall, they were looking for someone who checked all the boxes, and with Comcast, they'll have no problem finding that person.
I sort of sensed they weren't really trying to sell me the company and that the name would carry on its own.
It sounded like a typical tech job.
Why are you pursuing other opportunities? What is a cron job? What is an Elasticsearch shard?
They'll ask you about the coding assessment. We spotted X in the coding assessment which isn't right. How would you address this? What is your approach to code comments?
The following metrics were computed from 60 interview experiences for the Comcast Software Engineer role in United States.
Comcast's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Comcast's Software Engineer interview process in United States.