cswork / libraryOpen practice workspace

Interview guides · CNN

CNN Software Engineer Interview Guide

CNN Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at CNN, you sit at the intersection of world-class journalism, mass-scale digital distribution, and cutting-edge technology. You build and scale the digital platforms that deliver breaking news, rich multimedia experiences, and AI-powered features to millions of global users every single day. Whether you are developing low-latency backend systems, optimizing modern frontend architectures, or engineering AI-driven content understanding tools, your work directly shapes how the world consumes news. The engineering challenges here combine massive web-scale distribution with high-velocity newsroom demands. You will partner closely with machine learning engineers, product managers, and editorial stakeholders to ship reliable, high-availability systems that power consumer-facing apps, ad targeting, and internal productivity workflows.

This guide is scoped to a Software Engineer candidate at CNN.

Focus areas

  • Data Structures & Algorithms (DSA)
  • JavaScript
  • React

The CNN interview process

CNN candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Recruiter Call

Initial conversation with a technical recruiter to discuss your background, interest in media technology, and basic qualifications.

What to demonstrate

  • Initial conversation with a technical recruiter to discuss your background, interest in media technology, and basic qualifications
  • Depth in Data Structures & Algorithms (DSA)

How to prepare

  • Be able to walk your CV end to end in two minutes, and say why this company specifically.
  • Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.

Technical Assessment

Online coding challenges or a live technical interview focusing on data structures, algorithms, and core language proficiency.

What to demonstrate

  • Online coding challenges or a live technical interview focusing on data structures, algorithms, and core language proficiency
  • Depth in Data Structures & Algorithms (DSA)

How to prepare

  • Answer aloud and timed: Explain the difference between mutable and immutable data structures in your primary programming language.
  • Answer aloud and timed: How do you approach debugging a memory leak in a high-throughput backend service?

Multi-Round Loop

In-depth conversations with engineering managers, staff engineers, and peers covering system design, code quality, and behavioral alignment.

What to demonstrate

  • In-depth conversations with engineering managers, staff engineers, and peers covering system design, code quality, and behavioral alignment
  • Depth in Data Structures & Algorithms (DSA)

How to prepare

  • Answer aloud and timed: Explain JavaScript concepts such as closures, asynchronous programming patterns, and the event loop.
  • Answer aloud and timed: How do you manage state and component lifecycles effectively in modern frontend frameworks like React?

Senior Role Discussions

Additional discussions with leadership regarding architectural ownership, project management, and cross-functional collaboration.

What to demonstrate

  • Additional discussions with leadership regarding architectural ownership, project management, and cross-functional collaboration
  • Depth in Data Structures & Algorithms (DSA)

How to prepare

  • Answer aloud and timed: What are the performance implications of unoptimized re-renders in a large-scale web application?
  • Answer aloud and timed: Walk through how you would structure reusable CSS and modular component styles.

Where candidates lose points

Communicate your thought process clearly

Interviewers at CNN value collaboration and want to understand how you break down problems. Never code in silence; verbalize your assumptions, trade-offs, and alternative approaches as you work through technical challenges.

Brush up on modern web architecture

Because digital media relies heavily on fast content delivery and high availability, ensure you are comfortable discussing caching strategies, CDN usage, and horizontal scaling in system design rounds.

Prepare for behavioral alignment

Expect questions about how you handle pressure, tight deadlines, and cross-functional disagreements. Use the STAR method to structure stories that highlight your accountability and teamwork in fast-paced environments.

Review your past projects thoroughly

Interviewers frequently deep-dive into your resume and past technical work. Be ready to discuss the architecture, bottlenecks, and key learnings from systems you have built and operated in production.

Questions & practice

Solve standard algorithmic problems covering arrays, strings, trees, and graphs.

Medium · Technical & Core Programming

Approach

  1. Restate the input: its shape, its size, and what is guaranteed about it.
  2. Name the brute-force solution and its complexity before improving on it.
  3. Choose the data structure from the access pattern, not from familiarity.
  4. State the target complexity and say which constraint rules the naive version out.

Follow-up

  • How does this change if the input no longer fits in memory?
  • What is the worst case, and how likely is it on real data?

Explain the difference between mutable and immutable data structures in your primary programming language.

Medium · Technical & Core Programming

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

Explain JavaScript concepts such as closures, asynchronous programming patterns, and the event loop.

Medium · JavaScript & Frontend Engineering

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. Distinguish a value from a reference to it, and say which one you handed out.

Follow-up

  • What happens if two callers reach this at the same time?
  • Where could this allocate more than you expect?

Discuss strategies for schema design, indexing, and query optimization in relational versus NoSQL databases.

Medium · Backend & Systems Architecture

Approach

  1. Name the grain you start from and join outward from it.
  2. Check whether any join is one-to-many before aggregating, or the sums inflate.
  3. Say which index the query would use, and what makes it unusable.
  4. Handle the rows that do not match: that is usually the actual question.

Follow-up

  • How does the query change if that join becomes one-to-many?
  • What happens to this when the table is ten times larger?

Denormalise tenant onto revisions and backfill it live

Hard · denormalisation · online migration · backfill

resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.

Approach

  1. Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
  2. Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
  3. Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
  4. Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.

Follow-up

  • The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
  • How do you verify the backfill actually finished, given rows are still being inserted while it runs?

Write a few lines of code to open a file, parse data, and handle exceptions.

Medium · Technical & Core Programming

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

How do you manage state and component lifecycles effectively in modern frontend frameworks like React?

Medium · JavaScript & Frontend Engineering

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What are the performance implications of unoptimized re-renders in a large-scale web application?

Medium · JavaScript & Frontend Engineering

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

Walk through how you would structure reusable CSS and modular component styles.

Medium · JavaScript & Frontend Engineering

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

How do you design a RESTful API or event-driven service using Node.js or Python?

Medium · Backend & Systems Architecture

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

How would you design a caching layer to reduce database load during traffic spikes from breaking news events?

Medium · Backend & Systems Architecture

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

Walk through a system design for a high-availability content delivery pipeline.

Medium · Backend & Systems Architecture

Approach

  1. Fix the scope first: who calls this, how often, and what they do when it fails.
  2. Name the read and write paths separately; they rarely have the same bottleneck.
  3. Choose a partition key and say what query it makes expensive.
  4. State the consistency you need, and where you are willing to be stale.

Follow-up

  • What breaks first when traffic grows ten times?
  • How does this behave when that dependency is down for an hour?

How do you approach reviewing and improving purposely flawed code for separation of concerns and maintainabili

Medium · DevOps & Code Quality

How do you approach reviewing and improving purposely flawed code for separation of concerns and maintainability?

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

What practices do you implement to ensure robust CI/CD pipelines and automated testing?

Medium · DevOps & Code Quality

Approach

  1. Clarify what is being asked and what a complete answer contains.
  2. State your assumptions explicitly before working the problem.
  3. Say what you would check first and why it is the highest-information step.
  4. Work from the requirement backwards to the design.

Follow-up

  • What assumption would you test first?
  • How would you know your answer was wrong?

How do you approach debugging a memory leak in a high-throughput backend service?

Medium · Technical & Core Programming

Approach

  1. Establish what changed and when, before forming any theory.
  2. Pick a bisection that eliminates candidates whichever way it turns out.
  3. Check the instrumentation before believing the symptom.
  4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

  • What would you look at first, and what would it rule out?
  • How would you tell a cause from a coincidence here?

Suggested practice checklist

Built from the rounds and topics CNN candidates report.

Day 1 — Map the CNN loop

  • Write out the reported sequence: Recruiter Call, Technical Assessment, Multi-Round Loop, Senior Role Discussions.
  • For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.

Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.

Day 2 — Work Data Structures & Algorithms (DSA)

  • Spend the session on Data Structures & Algorithms (DSA), which CNN candidates report being tested on.
  • Write one worked example in Data Structures & Algorithms (DSA) and time yourself on it.

Deliverable: One timed worked example in Data Structures & Algorithms (DSA).

Day 3 — Work JavaScript

  • Spend the session on JavaScript, which CNN candidates report being tested on.
  • Write one worked example in JavaScript and time yourself on it.

Deliverable: One timed worked example in JavaScript.

Day 4 — Work React

  • Spend the session on React, which CNN candidates report being tested on.
  • Write one worked example in React and time yourself on it.

Deliverable: One timed worked example in React.

Day 5 — Answer out loud: Technical & Core Programming

  • Answer aloud, timed: Solve standard algorithmic problems covering arrays, strings, trees, and graphs.
  • Answer aloud, timed: Write a few lines of code to open a file, parse data, and handle exceptions.

Deliverable: Spoken answers to 2 reported Technical & Core Programming question(s), under time.

Day 6 — Answer out loud: JavaScript & Frontend Engineering

  • Answer aloud, timed: Explain JavaScript concepts such as closures, asynchronous programming patterns, and the event loop.
  • Answer aloud, timed: How do you manage state and component lifecycles effectively in modern frontend frameworks like React?

Deliverable: Spoken answers to 2 reported JavaScript & Frontend Engineering question(s), under time.

Day 7 — Answer out loud: Backend & Systems Architecture

  • Answer aloud, timed: How do you design a RESTful API or event-driven service using Node.js or Python?
  • Answer aloud, timed: Discuss strategies for schema design, indexing, and query optimization in relational versus NoSQL databases.

Deliverable: Spoken answers to 2 reported Backend & Systems Architecture question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

How do you handle configuration management and infrastructure as code in cloud environments?

Medium · DevOps & Code Quality

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Walk through a challenging technical project from your past and how you drove it to completion.

Medium · Behavioral & Background

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

How do you handle disagreements with product managers or editorial stakeholders regarding technical scope?

Medium · Behavioral & Background

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?

Describe a time when a production system failed and how you troubleshot and resolved the issue under pressure.

Medium · Behavioral & Background

Approach

  1. Pick a story where you made the decision, not one where you watched it.
  2. State the situation in two sentences and spend the rest on the reasoning.
  3. Give the blast radius: what could have broken, and what you measured.
  4. Name the disagreement and how you resolved it with evidence.

Follow-up

  • What would you do differently if you ran that again?
  • How did you know your change caused the improvement?