Principal CAD Engineer - Physical Verification

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove cookie/navigation/legal etc. We need to parse the posting. Overview: description about SCHIE etc. That could be "About the role" or maybe "Overview". The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these headings. We have: - Overview paragraph: description of team, mission, role. Could go under "About the role". Should preserve all substantive info. - Responsibilities: bullet list of responsibilities. - Qualifications: includes Required Qualifications (education+experience), Other Requirements (security screening), Preferred Qualifications. - Skills: maybe we can extract from Preferred Qualifications: hands-on experience with PV tools, scripting skills, ability to debug, LDAP/IdM, Linux server admin, Azure EntraID, system automation, supporting engineering at semiconductor. - Benefits: The posting mentions "Certain roles may be eligible for benefits and other compensation. Find additional benefits and pay information here: link". That's not specific benefits; it's a generic statement. According to rule: never create Benefits section unless posting actually states them. It says "Certain roles may be eligible for benefits and other compensation." That's vague, not specific. So we should not include Benefits section. - Pay: The posting includes pay range: "Silicon Engineering IC5 - The typical base pay range for this role across the U.S. is USD $142,800 - $274,800 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $188,000 - $304,200 per year." That's specific pay info, so we should include Pay section. - Schedule: Not mentioned. No schedule info. So omit. - Skills: We have some skill-like content in Preferred Qualifications. We could put them under Skills section. However we also have Qualifications section that includes Required and Preferred. The instruction says we can have Qualifications and Skills separate. We need to decide what goes where. The posting has "Required Qualifications:" and "Other Requirements" and "Preferred Qualifications". Those are qualifications. Skills could be derived from Preferred Qualifications like hands-on experience, proficiency, scripting skills, ability to debug, LDAP/IdM, Linux admin, Azure EntraID, system automation, supporting engineering. Those are skills/experience. We could put them under Skills. But we must not duplicate content. We need to preserve all substantive info; we can split but must not lose any. We could keep Qualifications section for education/experience requirements and maybe other requirements (security). Then Skills section for the hands-on experience, tools, scripting, debugging, LDAP, Linux, Azure, automation, semiconductor experience. We must not create sections with filler like "commensurate with experience". Not relevant. We must not include duplicated lines. Ensure we don't repeat same content. We need to strip boilerplate: "We are committed to a diverse and inclusive workspace..." that's EEO statement; remove. Also "Microsoft is an equal opportunity employer..." remove. Also "If you need assistance with religious accommodations..." remove. Also "This position will be open for a minimum of 5 days..." maybe considered application instructions; remove. Also "Find additional benefits and pay information here: link" maybe we keep link? It's about benefits and pay; but we already have Pay section; we could keep the link as part of Pay? The instruction: remove application instructions. The link is not exactly instruction but it's a reference. Might be considered boilerplate. Safer to remove it. Also remove "Difference makes us better." maybe keep as part of About? It's a tagline; could keep but it's not substantive? Might be okay to keep. We need to preserve all substantive information: the overview description, responsibilities bullet list, qualifications (education/experience, security screening), preferred qualifications (skills), pay ranges. Let's extract details. Overview paragraph: "Microsoft Silicon, Cloud Hardware, and Infrastructure Engineering (SCHIE) is the team behind Microsoft’s expanding Cloud Infrastructure and responsible for powering Microsoft’s “Intelligent Cloud” mission. SCHIE delivers the core infrastructure and foundational technologies for Microsoft's over 200 online businesses including Bing, MSN, Office 365, Xbox Live, Teams, OneDrive, and the Microsoft Azure platform globally with our server and data center infrastructure, security and compliance, operations, globalization, and manageability solutions. Our focus is on smart growth, high efficiency, and delivering a trusted experience to customers and partners worldwide and we are looking for engineers to help achieve that mission. Do you have a passion for advanced silicon signoff and physical verification at leading‑edge technology nodes? You will be part of a team responsible for driving state‑of‑the‑art Physical Verification CAD solutions for Microsoft’s silicon design teams. In this role, you will foster the enablement and support of advanced‑node DRC, LVS, Antenna, and ESD signoff flows, working closely with EDA vendors, and internal design teams. You will own PV signoff methodology end to end, identify gaps, and drive scalable, production‑ready solutions across multiple silicon programs." That's the overview. Responsibilities bullet list: - Lead methodology enablement, project alignment, centralized CAD flow management, and Physical Design support for the Silicon organization. - The role will own and advance Physical Verification and PERC methodologies, partnering closely with design teams to improve productivity, quality, and execution consistency - Develop, maintain, and support Physical Verification (PV) flows across all Silicon projects, spanning early design (shift‑left) through final signoff, including DRC, LVS, ERC, antenna, and advanced checks. - Own PV methodology, including guidelines, checklists, milestone definitions, and waiver strategies, ensuring consistent and predictable execution across programs and nodes. - Partner closely with Physical Design teams to: - Enable early PV runs - Debug complex DRC/LVS/ERC/PERC issues - Identify systemic design or flow gaps and drive fixes to closure. - Lead resolution of PV‑related flow and design issues, including tool stability, runtime scalability, deck integration, waiver correctness, and cross‑tool debug. - Drive cross‑functional alignment with CAD, Technology, and external EDA partners to communicate PV requirements, influence roadmap priorities, and unblock execution at critical project milestones. - Support PDK and node enablement activities, ensuring PV flows are validated, production‑ready, and aligned with foundry decks and internal signoff criteria across multiple technology variants. - Lead the development and deployment of AI-enabled agents to automate and optimize Physical Verification (PV) and PERC workflows across the Silicon organization. - Contribute to PV activities, including training material, documentation, onboarding labs, and continuous improvement of automation and debug infrastructure. We need to preserve all; we can keep as

• items. Qualifications: Required Qualifications: Doctorate ... OR Master's ... OR Bachelor's ... OR equivalent experience. Other Requirements: Ability to meet Microsoft, customer and/or government security screening requirements are required for this role. These requirements include, but are not limited to, the following specialized security screenings: Microsoft Cloud Background Check: This position will be required to pass the Microsoft Cloud background check upon hire/transfer and every two years thereafter. This role will require access to information that is controlled for export under export control regulations, potentially under the U.S. International Traffic in Arms Regulations or Export Administration Regulations, the EU Dual Use Regulation, and/or other export control regulations. As a condition of employment, the successful candidate will be required to provide either proof of their country of citizenship or proof of their US. residency or other protected status (e.g., under 8 U.S.C. 1324b(a)(3)) for assessment of eligibility to access the export-controlled information. To meet this legal requirement, and as a condition of employment, the successful candidate’s citizenship will be verified with a valid passport. Lawful permanent residents, refugees, and asylees may verify status using other documents, where applicable. Preferred Qualifications: BS + 15 years / MS + 13 years of relevant experience in Physical Verification, Physical Design, or CAD methodology roles. Hands‑on experience with Physical Verification checks, including DRC, LVS, ERC, Antenna, Metal Fill, etc. Proficiency with industry‑standard PV tools, such as Calibre. Scripting skills in at least one language (TCL, Python, Perl, or equivalent) for flow automation, debug, and data analysis. Ability to debug complex, cross‑domain issues, reason about root cause (design vs flow vs tool), and drive issues to closure across teams. 3+ experience in managing LDAP and IdM environment or equivalent 7+ Years’ Linux Server Administration Understanding of Microsoft Azure EntraID authentication methodology 3+ Years’ system automation experience such as Shell, Perl, or Python, Ansible 3+ Years supporting Engineering at a semiconductor company Pay: "Silicon Engineering IC5 - The typical base pay range for this role across the U.S. is USD $142,800 - $274,800 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $188,000 - $304,200 per year." We should include that. Now we need to output HTML fragment with

  headings and appropriate content. We should not include any markdown fences. We need to decide ordering: About the role, Responsibilities, Qualifications, Skills, Pay. Possibly also Requirements? But we have qualifications covering education/experience and other requirements (security). Could split: Qualifications for education/experience, Requirements for security screening. But the instruction list includes Requirements as a possible heading. We could have both Qualifications and Requirements sections. Let's see: The posting has "Required Qualifications:" and "Other Requirements". So we could map Required Qualifications to Qualifications section, and Other Requirements to Requirements section. Preferred Qualifications could go to Skills section (or maybe also Qualifications). But we already have Qualifications for required; we could put preferred under Skills. Thus sections: - About the role: overview paragraph. - Responsibilities: bullet list. - Qualifications: required qualifications (education/experience) maybe also note equivalent experience. - Requirements: other requirements (security screening). - Skills: preferred qualifications (hands-on experience, tools, scripting, debugging, LDAP/IdM, Linux admin, Azure EntraID, system automation, semiconductor experience). - Pay: pay ranges. We must not include Benefits or Schedule. Now ensure we preserve all substantive info. Let's extract each piece exactly. About the role: We'll include the overview paragraph as

  . Might need to keep the sentences exactly. Ensure no extra whitespace. Responsibilities: We'll list each bullet as

  . Need to preserve the exact phrasing. Let's copy responsibilities lines: 1. Lead methodology enablement, project alignment, centralized CAD flow management, and Physical Design support for the Silicon organization. 2. The role will own and advance Physical Verification and PERC methodologies, partnering closely with design teams to improve productivity, quality, and execution consistency 3. Develop, maintain, and support Physical Verification (PV) flows across all Silicon projects, spanning early design (shift‑left) through final signoff, including DRC, LVS, ERC, antenna, and advanced checks. 4. Own PV methodology, including guidelines, checklists, milestone definitions, and waiver strategies, ensuring consistent and predictable execution across programs and nodes. 5. Partner