What a strong Solidity specialist actually knows
Smart contracts are unforgiving. A strong Solidity developer thinks in invariants, writes the tests before the code is trusted, and knows the classic failures: reentrancy, unchecked external calls, oracle manipulation, signature replay and upgrade storage collisions. They use OpenZeppelin as a base and justify every deviation.
They also understand cost. Gas-aware design, storage layout and sensible event use make a protocol cheaper to run, and fuzz and invariant tests in Foundry or Hardhat prove the logic holds when users behave badly.