went through Comcast's coding process for a mid-level frontend role in early 2026. sharing because the OA format is a little different from what most guides describe.
Online assessment: HackerRank platform, 90 minutes, 3 problems. this is the screening step before any live interview.
the difficulty breakdown in my session: one easy, one medium, one medium-hard. they were NOT raw leetcode problems. they had a Comcast-ish flavor. i got one about processing a log stream from a network device (string parsing + frequency counting), one about scheduling jobs with dependencies (basically topological sort but described in business terms), and one that was a modified interval problem.
i did not get any DP-heavy problems. the one i struggled with was more about getting the algorithm right AND writing clean readable code. there were explicit test cases you could see and some hidden ones. i passed 8/10 test cases on the hard one and still moved forward.
Live coding round (after OA): one 45-minute session with a Comcast engineer. they gave me a problem on a shared editor (CoderPad). it was a medium-difficulty array problem. they cared more about how i talked through it than whether i got the optimal solution immediately. the interviewer asked me to refactor after i got a brute force working, which felt like a good sign.
what to prep: trees + graphs: at least BFS/DFS cold, these came up in multiple people's reports string manipulation: showed up more than i expected don't skip the runtime/space complexity conversation. they asked me to walk through Big O on both rounds.
if you're applying for frontend specifically: there's also a 30-min JS/React round that's separate from the algo coding. that one was more practical (what does useEffect cleanup do, how does event delegation work, build a small component). not a gotcha session, but you should know your hooks.