Synopsys ICC2 Engineer Positions: Physical Design Roles
When a physical design posting names ICC2 specifically, it is signaling a full Synopsys implementation flow, not a generic place-and-route req. IC Compiler II is one of the two platforms that dominate digital PnR, and teams built around it usually expect you to work inside the Synopsys stack from netlist to GDS.
ICC2 goes head to head with Cadence Innovus, so tool allegiance tends to follow the rest of a team's flow. Shops that sign off timing in PrimeTime and extract parasitics with StarRC lean toward ICC2 for implementation because the handoffs between those tools are cleaner.
The work itself is the full block flow: floorplanning, power planning, placement, clock tree synthesis, routing, and keeping the block DRC-clean as it closes. Almost all of it runs in Tcl, so fluent scripting and a habit of building reusable flow scripts are what separate the engineers who close blocks from the ones who wait on them. At advanced nodes, many teams now drive ICC2 through Fusion Compiler, which pulls physical-aware synthesis into the same environment for tighter QoR.
ICC2 work is one slice of the wider set of physical design engineer jobs, and the floorplanning and timing instincts you build here carry straight into adjacent implementation roles.
Demand clusters at companies that have committed to the Synopsys flow, from large fabless SoC teams down to smaller design houses that cannot absorb a mid-program tool switch. Pay tracks seniority and tapeout history more than the tool on your resume; US base salaries for production physical design engineers commonly fall in the rough range of $130K to $210K, with staff and principal total compensation higher at the big fabless companies. The salary guide for semiconductor jobs breaks the numbers down by level.
If ICC2 is your primary tool, put it front and center: name the blocks you implemented, the QoR you moved, and the tapeouts you closed. That record reads better than any checklist of tool names. Implementation and custom-layout skills overlap more than the titles suggest, so it is worth seeing how they map onto Cadence Virtuoso analog design roles. Save a search on semidesignjobs.com and new ICC2 openings will land in your inbox.
FAQ
What is the difference between ICC2 and Fusion Compiler
ICC2 is Synopsys's dedicated place-and-route tool that takes an external synthesis netlist as input. Fusion Compiler folds synthesis (Design Compiler Graphical) and implementation (ICC2 engines) into one RTL-to-GDS flow, so physical-aware synthesis can feed back and lift PnR QoR. Teams choose between them based on design complexity and schedule.
What scripting skills do ICC2 roles expect
Tcl is the primary language for ICC2 and drives implementation scripts across every stage of the flow. ICC2 also supports hierarchical scripting through hm (hierarchy manager) commands. Python shows up more and more for pre- and post-processing of ICC2 data, constraint management, and regression automation.
How do ICC2 and PrimeTime work together
ICC2 uses embedded PrimeTime signoff engines for in-design timing analysis, so engineers can check timing inside the implementation environment and then run standalone PrimeTime for final signoff after routing. That tight integration supports timing-driven routing and ECO fixes without exporting netlists to a separate timing tool.