Candidates report NBCUniversal software engineering interviews that start with a recruiter screen. They then move to conversational team rounds, and in one case an architecture discussion and a live coding exercise.
$130K
Avg. Base Comp
$155K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Reports on NBCUniversal engineering interviews are mixed, and the roles vary, so treat the details below as individual experiences rather than a fixed format.
The recruiter screen is the one step candidates describe in common. One senior-level candidate says the call centered on the tech stack, the role, salary range, location and why you want to work at NBCUniversal. Prepare a specific answer to that last question and know your salary and location preferences before the call.
The only Software Engineer report that goes past the screen describes an architecture interview and a coding round. The candidate felt the architecture discussion went well. In the coding round they were asked to build a service that returns top movies for a chosen genre using a movie database API, in a shared online sandbox with screen sharing and video. Laggy equipment ate most of the session, and the candidate was rejected. If you get a similar format, test your setup beforehand and practice calling an external API and shaping the response into a small service.
A candidate who got an offer for a Systems Engineer role describes four rounds. They say the conversations leaned behavioral and culture-fit, with questions about how their background fit the new position, and that interviewers were open about the team's day-to-day work. Intern candidates likewise describe friendly, project-focused conversations. One of them reported a wait of a few months for a decision, so allow for slow communication.
Synthesized from 6 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 Nbcuniversal process.
This was a short phone screen with a recruiter, and it felt more like a logistics and fit check than a technical interview. We spent most of the call on the technology stack used at the company and the details of the role, which gave me a decent picture of what the work would look like. The recruiter then moved into standard screening questions covering my tech experience, my salary range, and my location. The one question I remember clearly was why I wanted to work at NBCUniversal, so I would come in with a specific answer rather than a generic one about the company. I didn't move forward after this call, so I can't speak to what later rounds involve.
Prep tip from this candidate
Have a concrete answer for why NBCUniversal specifically, and go in with a clear salary range and location preference, since the recruiter screen covered all three directly.
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 Nbcuniversal
How would you negotiate and resolve disagreements when a client rejects your proposed solution?
| Question | |
|---|---|
| Why Do You Want to Work With Us | |
| Justify a Neural Network | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| P-value to a Layman | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Raining in Seattle | |
| Employee Salaries (ETL Error) | |
| Find the Missing Number | |
| Hurdles In Data Projects | |
| Google Maps Improvement | |
| Address Schema | |
| Retailer Data Warehouse | |
| Permutation Palindrome | |
| Integer to Roman | |
| Liked Pages | |
| Session Difference | |
| One Element Removed | |
| Size of Joins | |
| Basic Regex | |
| The Brackets Problem | |
| String Subsequence | |
| Flatten N-Dimensional Array to 1D Array |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a short recruiter call covering the technology stack, the role, their tech experience, salary range and location. One senior-level candidate remembers being asked why they wanted to work at NBCUniversal, so a specific answer is worth preparing.
A candidate in a systems engineering role reports four rounds that leaned behavioral. Interviewers asked how their background aligned with the position and were open to questions about the team and daily work. Other candidates describe a similarly conversational tone.
One Software Engineer candidate reports an architectural interview that went well, centered on system design and explaining their thought process. Other candidates did not describe this stage, so it may not apply to every team or level.
The same candidate reports a coding round in a shared online sandbox, with video and screen sharing on. The task was to build a service returning top movies by genre from a movie database API. Setup problems consumed much of the session, so checking your equipment in advance may help.
Reported outcomes range from a rejection shortly after a coding round to an offer after a four-round process. Candidates also mention slipping timelines, including a recruiter follow-up that took about two weeks, so it may help to plan for delays.
