cswork / libraryOpen practice workspace

Interview guides · U.S. News & World Report

U.S. News & World Report Software Engineer Interview Guide

U.S. News & World Report Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at U.S. News & World Report, you play a pivotal role in shaping the digital landscape of one of the most trusted sources of news and information in the United States. This position is critical for developing and maintaining the technology that powers our extensive suite of online products, including rankings, reviews, and analysis that helps millions of users make informed decisions across various sectors such as education, health, and finance. Your work will directly impact how users interact with our content, enhancing their experience and engagement. The position is not just about writing code; it involves collaborating with cross-functional teams to address complex challenges and deliver scalable solutions. You will work on projects that require a deep understanding of user needs, data analytics, and innovative technologies.

This guide is scoped to a Software Engineer candidate at U.S. News & World Report.

Focus areas

  • Coding assessments
  • System design (high-level application design)
  • JavaScript

The U.S. News & World Report interview process

U.S. News & World Report candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

HR Interaction

Initial interaction with an HR representative to gauge interest and explain company culture.

What to demonstrate

  • Initial interaction with an HR representative to gauge interest and explain company culture
  • Depth in Coding assessments

How to prepare

  • Answer aloud and timed: Explain the difference between synchronous and asynchronous programming.
  • Answer aloud and timed: How would you optimize a SQL query for performance?

Coding Assessment

A coding assessment that tests your ability to solve problems relevant to the role.

What to demonstrate

  • A coding assessment that tests your ability to solve problems relevant to the role
  • Depth in Coding assessments

How to prepare

  • Answer aloud and timed: Describe your experience with RESTful API design and implementation.
  • Answer aloud and timed: What are some common security vulnerabilities in web applications?

Technical Phone Interview

Engage in discussions about past experiences and technical challenges in a collaborative format.

What to demonstrate

  • Engage in discussions about past experiences and technical challenges in a collaborative format
  • Depth in Coding assessments

How to prepare

  • Answer aloud and timed: Can you discuss a challenging technical problem you faced and how you resolved it?
  • Answer aloud and timed: Describe a time when you had to manage conflicting priorities in a project.

In-Person Interview

Meet various team members to discuss the technical and strategic direction of projects.

What to demonstrate

  • Meet various team members to discuss the technical and strategic direction of projects
  • Depth in Coding assessments

How to prepare

  • Answer aloud and timed: How do you approach feedback and criticism from peers or supervisors?
  • Answer aloud and timed: Share an experience where you had to adapt to significant changes in project requirements.

Where candidates lose points

Understand the company mission

Familiarize yourself with U.S. News & World Report's values and mission to demonstrate alignment during interviews.

Prepare for coding assessments

Practice common coding challenges and familiarize yourself with the tools used for assessments, such as HackerRank.

Be ready for behavioral questions

Prepare examples from your past experiences that highlight your problem-solving and teamwork skills.

Ask insightful questions

Show your interest by preparing thoughtful questions about the team dynamics, projects, and the company’s technology stack.

Questions & practice

Explain the difference between synchronous and asynchronous programming.

Medium · Technical / Domain Questions

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?

Write a function to reverse a linked list.

Medium · Coding / Algorithms

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?

Solve a sample coding challenge on a platform like HackerRank or LeetCode.

Medium · Coding / Algorithms

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?

How would you optimize a SQL query for performance?

Medium · Technical / Domain Questions

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?

Stop tag and share joins from fanning out a page

Medium · join fan-out · semi-joins · many-to-many

resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.

Approach

  1. Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
  2. Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
  3. Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
  4. Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.

Follow-up

  • The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
  • A resource can be shared with the same user twice under different permissions. Does your count change, and should it?

What are some common security vulnerabilities in web applications?

Medium · Technical / Domain Questions

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?

Can you discuss a challenging technical problem you faced and how you resolved it?

Medium · Technical / Domain Questions

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 would you design a system for tracking user engagement on a website?

Medium · Problem-Solving / Case Studies

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?

Given a set of requirements, outline how you would structure a new feature from start to finish.

Medium · Problem-Solving / Case Studies

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?

Read latency spikes on a sixty-second sawtooth

Medium · cache stampede · single-flight · ttl

The cached listing read path serves about 14k reads/second at an 85% hit rate. p99 sits at 35 ms for 57 seconds, jumps to 900 ms for 3, and repeats. During each spike the primary shows several hundred identical listing queries starting within the same millisecond, all carrying one large tenant's id. Cache entries use a 60-second TTL. Give the mechanism, the ordered checks, the fix, and the correctness hazard your fix must not introduce.

Approach

  1. Match the period to a configured number before theorising about load. A spike every 60 seconds against a 60-second TTL is an entry expiring, and you confirm it by correlating spike timestamps with the entry's write time rather than with the traffic curve. If the period had matched a cron or a GC interval instead, this is a different investigation.
  2. Establish the concurrency of the miss. Several hundred identical queries in one millisecond means the miss path has no coalescing: every request that arrives between expiry and repopulation recomputes. The herd size is that key's arrival rate times its recompute time, so at 1.2k reads/second for the hot key and a 250 ms recompute you expect about 300 concurrent misses, which matches what is observed.
  3. Add single-flight on the miss path so one caller per key recomputes under a short-lived lock while the rest wait for its result. Prefer stale-while-revalidate where the read tolerates it: return the expired value immediately and refresh asynchronously, which removes the latency spike rather than serialising it into a queue of waiters.
  4. De-synchronise the keys. Write TTLs with jitter, for example 60 seconds plus or minus 10%, so a deploy or a mass invalidation does not align every key on the same second and turn a per-key herd into a fleet-wide one.

Follow-up

  • The same sawtooth appears on a key that is invalidated on write rather than expired. Is that the same bug?
  • How does your answer change if the recompute takes 4 seconds instead of 250 ms?

Suggested practice checklist

Built from the rounds and topics U.S. News & World Report candidates report.

Day 1 — Map the U.S. News & World Report loop

  • Write out the reported sequence: HR Interaction, Coding Assessment, Technical Phone Interview, In-Person Interview.
  • 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 Coding assessments

  • Spend the session on Coding assessments, which U.S. News & World Report candidates report being tested on.
  • Write one worked example in Coding assessments and time yourself on it.

Deliverable: One timed worked example in Coding assessments.

Day 3 — Work System design (high-level application design)

  • Spend the session on System design (high-level application design), which U.S. News & World Report candidates report being tested on.
  • Write one worked example in System design (high-level application design) and time yourself on it.

Deliverable: One timed worked example in System design (high-level application design).

Day 4 — Work JavaScript

  • Spend the session on JavaScript, which U.S. News & World Report candidates report being tested on.
  • Write one worked example in JavaScript and time yourself on it.

Deliverable: One timed worked example in JavaScript.

Day 5 — Answer out loud: Technical / Domain Questions

  • Answer aloud, timed: Explain the difference between synchronous and asynchronous programming.
  • Answer aloud, timed: How would you optimize a SQL query for performance?

Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.

Day 6 — Answer out loud: Behavioral / Leadership

  • Answer aloud, timed: Describe a time when you had to manage conflicting priorities in a project.
  • Answer aloud, timed: How do you approach feedback and criticism from peers or supervisors?

Deliverable: Spoken answers to 2 reported Behavioral / Leadership question(s), under time.

Day 7 — Answer out loud: Problem-Solving / Case Studies

  • Answer aloud, timed: How would you design a system for tracking user engagement on a website?
  • Answer aloud, timed: Given a set of requirements, outline how you would structure a new feature from start to finish.

Deliverable: Spoken answers to 2 reported Problem-Solving / Case Studies question(s), under time.

Behavioural preparation

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

Describe your experience with RESTful API design and implementation.

Medium · Technical / Domain Questions

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 you had to manage conflicting priorities in a project.

Medium · Behavioral / Leadership

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 approach feedback and criticism from peers or supervisors?

Medium · Behavioral / Leadership

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?

Share an experience where you had to adapt to significant changes in project requirements.

Medium · Behavioral / Leadership

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?