Find hardware mistakes before they become permanent. You will make the evidence for correctness as important as the architecture itself.
Not open yet: Custom silicon gate
This work starts when that stage arrives, so there is no application to submit today and we will not pretend otherwise. What is written below is what the role is for and what would make somebody right for it, published early on purpose so you can decide whether it is worth watching.
The work
Develop simulation, constrained-random tests, assertions and formal properties. Own coverage closure, reset and clock-domain checks, and adversarial tests of privileged interfaces. Connect each verification claim to the specification and document what has not been proven.
The milestone
In your first 90 days after program activation, deliver a verification plan and regression environment that exposes seeded functional and security defects.
Evidence
Bring experience with hardware verification, formal reasoning or rigorous pre-silicon validation. You should be able to explain vacuous proofs, coverage gaps and the limits of a testbench.
Evidence, not credentials. We are describing work you can point at, in whatever form it exists.
The exercise
Specify properties for a secure command interface and identify assumptions that could hide an access-control defect.