Educational role path

EDA and layout engineering

Read floorplan, routing, IR-drop, clock, extraction, and model-to-measurement reports as bounded evidence rather than signoff proof.

Levels: 3
Checkpoints: 6
Artifact tasks: 12

Optional local checklist

Track what you have reviewed.

This records selected checkpoint IDs only. Artifact content, identity, free text, and click history are not stored.

0 / 6

Progress stays on this browser and is never used for ranking.

Competency level

Foundation

Name the variables, units, artifacts, and evidence classes required to read the role path.

1.1

Identify report metrics

Identify congestion, utilization, path, clock, IR-drop, and extraction fields with units and report grain.

Prerequisite: Start here
Evidence boundary: Report vocabulary does not establish a clean implementation or signoff result.

Public artifact tasks

lessonFloorplan report handoffList the report fields and their interpretation limits.mapEDA and layout domainLocate the physical-design evidence lane.

1.2

Calculate a bounded RC estimate

Calculate a bounded RC or delay estimate and state the geometry, units, and assumptions used.

Prerequisite: Identify report metrics
Evidence boundary: A hand estimate is not extracted parasitic or timing signoff.

Public artifact tasks

lessonCTS and routing handoffIdentify where estimate and report evidence differ.calculatorEngineering calculatorsUse a bounded calculator and record all assumptions.

Competency level

Cross-domain practice

Trace and compare bounded public replays across at least one engineering handoff.

2.1

Compare floorplan states

Compare two floorplan replay states and attribute a congestion or IR difference to the displayed change.

Prerequisite: Calculate a bounded RC estimate
Evidence boundary: The replay does not represent a proprietary design or implementation outcome.

Public artifact tasks

simulationFloorplan replayCompare fixed report states.labFloorplan labRecord metric grain and limitations.

2.2

Trace a report handoff

Trace one CTS or routing result into an IR-drop or timing question while preserving report grain and conditions.

Prerequisite: Compare floorplan states
Evidence boundary: A report handoff does not close timing, power, or physical verification.

Public artifact tasks

simulationCTS routing IR handoffFollow one report field across the handoff.labCTS routing IR labRecord the unresolved evidence fields.

Competency level

Evidence-ready

Construct an inspectable evidence record with limitations, stop conditions, and replacement needs.

3.1

Evaluate model-to-measurement evidence

Evaluate where a public design artifact ends and implementation, test-structure, measurement, and calibration evidence must begin.

Prerequisite: Trace a report handoff
Evidence boundary: Public artifacts do not include proprietary reports, runsets, or silicon signoff.

Public artifact tasks

lessonOpen-silicon evidence ladderMap the required evidence rungs.labModel-to-measurement labMark missing proof and stop points.

3.2

Document the signoff boundary

Document why public report literacy cannot certify DRC, LVS, PEX, timing, power, reliability, or tapeout readiness.

Prerequisite: Evaluate model-to-measurement evidence
Evidence boundary: Only authorized tools, decks, data, and responsible signoff owners can establish readiness.

Public artifact tasks

sourceSource policyCheck source class and access status.releaseRelease ledgerVerify the public artifact version and limitations.

Role boundary

Evidence first. Career promises stay out.

This path is vendor-neutral and excludes proprietary runsets, licensed decks, credentials, private reports, and signoff claims.

Role paths are educational navigation. They do not certify competence, promise employment, rank candidates, or represent employer acceptance.

Review source policy