Skip to main content
All posts

How to Hire a Physical Design Contract Engineer Without Confusing STA, PD, and Signoff

By Jason Eisenberg · Head of Marketing2 min read
Three staggered clear acrylic slabs on a dark surface, their right edges lit in warm orange against a navy background.

PD, STA, and signoff are different seats. Write the ownership into the req before you burn panel time renegotiating the job in the room.

You open a "physical design" req. Three weeks later your panel is still debating whether the seat owns floorplanning, multi-corner timing, or the last signoff checklist before tape-out.

That argument should have happened in the req, not in the interview.

PD, STA, and Signoff Are Different Seats

Floorplanning, placement, clock tree synthesis, and routing is one ownership story. Multi-mode multi-corner analysis and closure across PVT corners is another. Signoff ownership is a third: the person who owns the final checklist, ECO judgment, and the call that the block is ready to release.

Hiring managers blur those three when the title stays "PD engineer" and the bullet list tries to cover everything from floorplan to GDS. "Which of the three jobs do you actually need?" is the question PD leads ask in that interview, not because they lack breadth, but because they can already see which two you are hoping they will quietly absorb.

Why Soft Boundaries Cost You Panel Time

In design reviews, physical design engineers say process node experience matters on PD seats in a way it does not on many front-end titles. A 28 nm block closure and a 5 nm or 3 nm closure are different problems in their telling: tool behavior, congestion physics, and ECO cost do not travel one-to-one across nodes.

Soft boundaries in the interview usually mean soft boundaries on your critical path. If you cannot say whether the seat owns the floorplan battles, the timing signoff loop, or both, your best candidates will invent the answer for you, and then you will renegotiate the seat after the offer.

What Good Req Language Sounds Like

Blurred:

"Senior PD engineer for advanced node SoC. Own floorplan through signoff, STA, congestion, and ECO. Familiarity with DFT and DV a plus."

Cleaner:

"Principal physical design owner for a 5 nm block. Primary ownership is floorplan, placement, CTS, and routing closure through tape-out. STA partner is named on the program; this seat does not own full-chip timing signoff. Node experience at 7 nm or below required."

Or:

"Staff STA / timing signoff engineer for multi-mode multi-corner closure on a networking SoC. PD partners own implementation; this seat owns timing methodology, corner strategy, and signoff readiness."

One req is recruiting three people and hoping for one… the other staffs a seat a principal can recognize in under a minute.

Screen for Ownership, Not Tool Logos

Tool names are easy to paste. Ownership is harder. Ask which block they closed, at what node, what they owned versus what STA or DFT owned beside them, and where the last painful ECO came from. The candidates who have shipped will answer with a story. The ones who have only watched a flow will answer with a list.

We already published the seat-language playbooks for how to hire a DFT engineer and how to hire a design verification engineer. The same discipline applies here: name the ownership layer before you name the tool deck.

If you have a PD, STA, or signoff seat that keeps getting rewritten after every screen, put the PD seat in front of us and we will help you separate the jobs before the next panel burns another afternoon.

FAQ

Frequently Asked Questions

What Is the Difference Between PD, STA, and Signoff on a Contract Seat?

PD owns implementation (floorplan through routing). STA owns timing analysis and closure across corners. Signoff owns the final release judgment. They overlap in practice, but collapsing all three into one req usually means you are staffing a hope, not a seat.

How Specific Should Process Node Language Be in a PD Req?

Specific enough that a principal can tell whether their shipped work maps. Name the node family and whether the seat has closed at that altitude before. Do not turn a metal-stack rumor into a hard gate unless your program actually requires it.

Jason Eisenberg

Written by

Jason Eisenberg

Head of Marketing