Graphshard70 minMobile Engineer

Retry Dependency DAG Recovery

Mobile Engineer signal: topological sort + cycle detection in a network retry queue context. This is a ProdMatch-owned mobile engineer drill, framed as a March 2026 Wingify Connectivity simulation, not a copied platform question.

Company context

Wingify · Connectivity

Freshness

March 2026

Product surface

network retry queue

ProdMatch interview simulation based on product-team patterns; not a claim of a real company question.

Question

You own network retry queue for a Mobile Engineer loop. Given requests and directed dependencies between them, return a valid execution order. If a cycle exists, return an empty list and identify that the rollout is blocked.

Input

n nodes labelled 0..n-1 and dependency pairs [before, after].

Output

A valid order of all nodes, or [] when dependencies contain a cycle.

Constraints

1 <= n <= 200000
0 <= dependencies.length <= 400000
The graph may be disconnected.

Concepts

offline sync
local cache
gesture streams
topological sort
cycle detection
dependency graph

requests: 4, deps: [[0,1],[0,2],[2,3]] -> [0,1,2,3] or [0,2,1,3]

Approach

Try framing your own approach first. The 30 seconds you think before peeking is where learning happens.

Clean Solution

Reveal the approach first.

How well did you understand?

Your rating tunes when this problem shows up again.

Common Mistakes

Mark visited when enqueueing, not after repeated dequeue.
Do not ignore disconnected components if the product surface can have them.

Next Similar Problems

Sync Dependency DAG Recoverymedium Sync Evidence Path Finderhard Feed Dependency DAG Recoveryhard