How you will be judged.

Structures a tracking system, differentiates between blocking and non-blocking issues, communicates differently to technical vs. non-technical audiences. Shows maturity beyond their experience level.

Anticipates conflicts before they happen by building relationships early. Creates decision frameworks that teams adopt. Has examples of changing another team's approach through influence, not authority.

Shapes how the organization makes decisions. Creates processes that scale across products and sites. Has repaired broken cross-functional relationships and can articulate the root cause and structural fix. Other teams seek them out to mediate.

Has reshaped how an organization of 100+ engineers collaborates. Can describe systemic changes they drove (not just individual negotiations). Their frameworks are used by teams they've never met. VP-level leaders seek their counsel.

Solves problems cleanly and fast. Connects the analysis to design decisions (e.g., 'this deflection would crack the display'). Knows CAD origin/plane discipline. Shows intuition for what matters vs. what is noise.

Designs mechanisms that work AND are elegant — considers the user feel curve, the sound of the mechanism, assembly sequence, and cost. Tolerance stack leads directly to specification decisions. Shows the judgment that comes from having built things that failed and fixed them.

Makes architecture decisions that shape the product for 3+ generations. Evaluates emerging technologies (new alloys, compliant mechanisms, additive manufacturing) with a practical eye. Sets the standard that 50 engineers follow.

Sets the technical agenda for the company's hardware engineering function. Their architectural decisions shape the product for 5+ years. Has published, patented, or given industry talks. Engineers two levels below them can articulate 'the standard that [name] set.'

Validates their own reasoning — checks FEA results against hand calcs, questions boundary conditions, and thinks about failure modes the test might miss. Shows scientific rigor.

Knows when to distrust FEA results (fiber orientation in GF plastics, joint stiffness assumptions) and designs tests to validate specific model uncertainties. Designs DOEs to optimize manufacturing processes. Can diagnose a 25% FEA-to-test discrepancy systematically.

Builds a validation philosophy: when to test, when to analyze, when to accept risk. Can make the call to ship a product with incomplete validation data and articulate exactly what compensating controls are in place. The organization trusts their judgment.

Has built a validation organization from scratch — lab strategy, staffing, equipment, standards, and the culture of engineering rigor that makes it all work. Their standards are cited by other companies.

Builds the tolerance stack and immediately identifies which dimension dominates the variation. Understands that Cpk = 1.33 is 63 DPPM (one-sided) and can relate it to production yield at volume.

Identifies dominant contributors through sensitivity analysis and tightens only what matters. Understands rolled throughput yield and sets per-dimension Cpk targets to achieve a final assembly yield target. Has used real process data to update tolerance models.

Connects statistical quality to business: quantifies cost-of-poor-quality, builds the ROI case for tighter tolerances, sets Cpk targets based on rolled throughput yield for the full product. Uses Gen 1 field data to systematically improve Gen 2 specs.

Has built the quality culture for an organization — not just the tools and processes, but the mindset. Can present to the CFO in business terms: 'investing $2M in tighter tooling saves $15M in warranty costs and 0.5 NPS points.' Their quality philosophy becomes the company's quality philosophy.

Thinks about the entire manufacturing chain: tooling, cycle time, secondary operations, inspection. Can explain why a design that 'works' in CAD might fail in production (e.g., weld lines near snap roots).

Optimizes for cost AND quality simultaneously: reduces part count, minimizes secondary operations, designs for automated assembly. Can evaluate CNC vs. MIM vs. casting for a titanium part with specific cost-at-volume estimates. Has personally solved factory yield problems.

Defines the DFM/DFA standards for the organization. Makes build-vs-buy decisions for manufacturing processes. Can evaluate whether to invest $5M in in-house CNC capability or qualify a die-casting process. Has designed assembly lines for 50K+ units/day.

Has made manufacturing strategy decisions worth $100M+ (CNC vs die-cast line investment, aluminum-to-titanium transition, in-sourcing vs outsourcing). Their DFM standards are so embedded that new products pass DFM review on the first try 80% of the time.

Connects thermal design to user experience (skin temperature limits), proposes specific solutions (graphite sheets, thermal pads with specific thermal conductivity values), and thinks about multi-physics interactions.

Optimizes across multiple physics simultaneously: thermal solution that does not degrade acoustic performance, sealing solution that does not interfere with antenna performance. Provides specific numbers for thermal conductivity, contact pressure, and seal compression.

Defines the multi-physics simulation strategy for the organization: which tools, which staffing, which processes. Makes the business case for CFD investment. Builds the cross-functional 'contract' between PD and thermal/acoustic/EMI teams.

Has built a world-class multi-physics engineering capability. Recruits top talent. Their thermal or acoustic or sealing philosophy is adopted across the company. Has solved problems that required inventing new approaches because existing methods were insufficient.

Thinks at system level immediately: weight budget, power budget, thermal budget. Proposes tradeoffs proactively ('if we use a larger battery, we need a thinner PCB, which affects antenna performance'). Shows product intuition.

Thinks like a system engineer: power budget, weight budget, thermal budget, cost budget — all simultaneously. Proposes tradeoffs that balance performance against schedule and cost. Can redesign on the fly when constraints change ('ID just cut 1mm from Z-height — what breaks?').

Thinks in platforms, not products. Defines what should be shared vs. customized across a product family. Makes architecture decisions that trade off current-gen performance for multi-gen extensibility. The CTO trusts their product architecture judgment.

Has defined the product architecture that shipped to tens of millions of users. Can trace a line from their architecture decisions to business outcomes (market share, margin, customer satisfaction). Other companies study their products to understand how they were built.