process / device / metrology-yield
Process integration
Connect module changes to device, circuit, metrology, and yield evidence without turning a teaching replay into a production recipe.
- Levels
- 3
- Checkpoints
- 6
Role and competency paths / V122
Eight educational paths turn the public catalog into observable next steps. Each path moves from foundation to cross-domain practice and an evidence-ready handoff.
Start from a broader journeyRole directory
Role pages organize outcomes and prerequisites. Domain pages remain the technical catalog.
process / device / metrology-yield
Connect module changes to device, circuit, metrology, and yield evidence without turning a teaching replay into a production recipe.
equipment-facilities / process / metrology-yield
Separate equipment inventory, chamber state, sensing, and control evidence while keeping operation and safety decisions outside the public teaching path.
device / process / circuit
Connect electrostatics, architecture, transfer metrics, and model-to-measurement evidence without claiming calibration or silicon proof.
circuit / memory / digital-verification
Trace SRAM cell, read, sensing, array, control, and test behavior while preserving metric conditions and evidence limits.
eda-layout / digital-verification / circuit
Read floorplan, routing, IR-drop, clock, extraction, and model-to-measurement reports as bounded evidence rather than signoff proof.
metrology-yield / process / device
Separate measurement-system variation, process variation, data grain, uncertainty, and yield proxies before drawing a conclusion.
packaging-test-reliability / circuit / metrology-yield
Connect assembly, bonding, package parasitics, test, reliability, and failure evidence without claiming qualification or product readiness.
cross-domain
Turn a semiconductor question into an inspectable claim, source, method, evidence, limitation, and next-test structure using public metadata only.
Three-level structure
Consistent levels make prerequisites and stopping points comparable without pretending every role uses the same technical content.
Name the variables, units, artifacts, and evidence classes required to read the role path.
Trace and compare bounded public replays across at least one engineering handoff.
Construct an inspectable evidence record with limitations, stop conditions, and replacement needs.
Career and evidence boundary
Role paths are educational navigation. They do not certify competence, promise employment, rank candidates, or represent employer acceptance.
Optional checklist progress stays in this browser. A checked item is not proof of completion, scientific validity, production readiness, or signoff.