Skip to content
Tech Interview Prep home
Technical interview guide

Oracles & Cross-Chain Interoperability

How smart contracts get real-world data they can't natively access, and how assets and messages move between otherwise-isolated chains.

Read
50 min
Practice MCQs
25
Interview QA
25
Edition
v5
Editorial status
Reviewed

Scope: Chainlink Data Feeds, Sequencer Uptime Feeds, VRF v2.5 and CCIP documentation; Uniswap v2 oracle design; IBC core and ICS-23 specifications; EIP-3668 reviewed 2026-09-07.

Interview QA

Treat each question like a live interview question: answer out loud first (structure, assumptions, tradeoffs), then open the model answer to spot gaps and rehearse a tighter follow-up.

Curated: · Written: · Reviewed:

QA-1

Define the oracle boundary for an application.

QA-2

Configure a price-feed registry.

QA-3

Implement a defensive feed adapter.

QA-4

Choose a maximum feed age for lending.

QA-5

Evaluate oracle decentralization.

QA-6

Design an AMM-derived oracle.

QA-7

Specify oracle disagreement and outage states.

QA-8

Gate L2 risk actions on sequencer status.

QA-9

Integrate verifiable randomness into a game.

QA-10

Define a canonical cross-chain message envelope.

QA-11

Secure a cross-chain admin handler.

QA-12

Implement replay-safe message execution.

QA-13

Set bridge confirmation thresholds.

QA-14

Evaluate a light-client bridge.

QA-15

Assess a committee bridge's controls.

QA-16

Threat-model an optimistic message bridge.

QA-17

How do cross-chain token transfer protocols use rate limits and independent risk management networks to prevent bridge drain exploits?

QA-18

Choose channel ordering for an application.

QA-19

Design packet recovery behavior.

QA-20

Operate redundant relaying.

QA-21

Verify bridged-token accounting.

QA-22

Implement secure CCIP Read resolution.

QA-23

Upgrade a live bridge lane.

QA-24

How do low-latency pull-based oracle architectures differ from push-based oracle networks for settlement in RWA and perpetual markets?

QA-25

Operate oracle and bridge dependencies.