What does oracle design mean in blockchain developer job descriptions, and what skills are expected?

I saw a blockchain developer job post where the nice-to-have section mentioned oracle design, and I am curious what hiring teams actually expect when they write this.

Do they mean a smart contract developer should know how to connect Chainlink or Pyth price feeds?

Or do they expect deeper knowledge of how to explain oracle design in blockchain developer interviews when stale price checks, push vs pull oracle models, data source quality, fallback logic, liquidation risk, flash loan manipulation, and protocol-level failure handling are involved?

I usually see oracles explained as “bringing off-chain data on-chain,” but that feels too basic for real DeFi, RWA, lending, insurance, or prediction-market systems.

For people who have worked on smart contracts, audits, DeFi protocols, backend data systems, or hiring:

Is oracle design mainly a smart contract skill, a data engineering skill, a Web3 security skill, or a mix of all three?

For a junior or mid-level blockchain developer, how much oracle knowledge is actually expected?

And what kind of project proof would show that someone understands oracle design beyond just copying a tutorial or saying “use Chainlink”?