Explain why you want this company and leadership

### 1) “Why this company/role?”—answer with alignment, not generic interest Use a 3-part structure: **A. Present your current baseline (30–60 seconds):** - Your current domain (e.g., substrate/package layout, SI/PI collaboration, verification, vendor handoff) - Typical project types and complexity - What you personally owned vs supported **B. Show specific pull factors (the “why them”):** Pick 2–3 concrete anchors such as: - Product/tech direction (e.g., multi-die packaging, higher density, faster iteration) - Team model (small team, higher ownership) - Tool flow you want to deepen (or transferable flow) - Business/customer impact **C. Close with why you’ll succeed there (the “why you”):** - Tie your experience to their likely needs (throughput ~14 projects/year suggests repeatable flow, strong documentation, fast ramp, and context switching) - Mention your working style for global teams (async updates, clear handoffs, written decisions) Pitfalls: - Don’t say only “career growth” without role-specific reasons. - Don’t criticize your current employer; keep it forward-looking. --- ### 2) Leadership question—use STAR + “scope/impact” details Use **STAR (Situation, Task, Action, Result)**, but add two items interviewers value: - **Scope:** budget/timeline/team size, number of stakeholders, risk level - **Mechanisms:** how you ran the project (cadence, reviews, checklists, decision logs) **A. Situation & Task (context + goal)** - What was being built (package type, complexity, constraints) - The objective (schedule, yield/reliability, cost, performance) - Your role and authority (lead vs coordinator) **B. Actions (what you actually did)** Examples of strong leadership actions in a packaging/design context: - Set milestones: stackup freeze, placement freeze, routing freeze, verification signoff - Created/owned a risk register: warpage/thermal hotspots, assembly constraints, vendor lead times - Ran cross-functional alignment: mechanical keepouts, SI/PI constraints, manufacturing DFM - Implemented review discipline: early routing strategy reviews, frequent DRC/DFM runs - Managed cross-site collaboration: clear task decomposition, documented handoffs, overlapping hours **C. Results (quantify when possible)** - Schedule: “met tapeout by X; reduced re-spin risk; avoided ECOs late” - Quality: “passed signoff with 0 critical DRC at final; improved checklist reduced errors” - Efficiency: “reduced review cycle time; standardized templates” **D. Reflection (what you learned)** Strong candidates add 1–2 sentences: - “Next time I would…” - “The mechanism that worked best was…” --- ### If you have not formally led a team You can still answer well: - Lead a **project slice** (e.g., owned substrate escape routing + verification signoff) - Lead through influence (drive decisions, coordinate stakeholders) - Mention mentoring/onboarding a junior teammate Be explicit: “I wasn’t the official manager, but I led X by owning the schedule/risk management and coordinating Y stakeholders.” --- ### Global small-team leadership signals Because the team spans the US and Philippines, emphasize: - Written updates and decision logs - Clear definitions of “done” for each handoff - Respectful time-zone planning (rotating meeting times; async-first) - Proactive escalation when blocked This directly addresses the role’s real constraints and makes your leadership story more credible.