Make dependencies visible. A dependency that only exists in someone's head is a risk. Use a visual dependency map that is reviewed weekly.
Look for: dependency mapping at planning stage, regular cross-team sync meetings, buffer time at integration points, clear ownership of interfaces, and early warning systems when a dependency is at risk. Best candidates use visual dependency maps and integrate dependency risk into their status reporting.
Practical PM skill. Unmanaged dependencies are one of the top causes of project delays. Ask: "What do you do when a dependency team tells you they will be two weeks late?"