Principal SoC Design Engineer

We need to produce HTML fragment with sections: Overview (maybe not a heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. The posting includes Overview, Responsibilities, Qualifications, Preferred Qualifications, Pay info (Silicon Engineering IC5 - typical base pay range...), maybe Benefits? There's a line: "Certain roles may be eligible for benefits and other compensation. Find additional benefits and pay information here: ..." That's not specific benefits; we should not create Benefits section unless posting actually states them. It only mentions eligibility and link; not specific benefits. So we should not create Benefits section. Pay: we have specific pay ranges; we should create a Pay section with that info. Schedule: not mentioned. Skills: maybe we can include Preferred Qualifications as Skills? But we have Qualifications (required) and Preferred Qualifications. Could combine into Qualifications section with subparts? The instruction: use headings for section headings like Qualifications, Skills, Benefits, Pay, Schedule. We have Qualifications (required) and Preferred Qualifications. Could put both under Qualifications heading, with required and preferred lists. Or separate: Qualifications and Skills. Preferred qualifications could be considered Skills. But better to follow typical: Qualifications (required) and Skills (preferred). However the instruction says "Prefer a few substantive sections over many thin ones." So maybe combine required and preferred into Qualifications section, with subheadings? But we cannot use

etc? Only

for section headings. Could use

to differentiate. Probably better: have Qualifications (required) and Skills (preferred). Let's extract content. Overview: The first paragraph(s) up to "#SCHIE". Actually there is a line "#SCHIE". That seems like a tag. We should include overview content before that. The overview includes description of SCHIE, mission, etc. We'll put that in a

after maybe an

About the role? But instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't say we must have About the role heading; we can choose to include if there is substantive content. The overview is substantive. Could use About the role as heading. Or we could not include a heading and just put

overview. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use them if appropriate. The overview could be under About the role. Let's do

About the role

then

with overview text. Responsibilities: we have a block after "#SCHIE Responsibilities". We'll extract that. Qualifications: Required Qualifications block. We'll put that under

Qualifications

with

• for each bullet? The required qualifications are a set of alternatives: Doctorate... OR Master's... OR Bachelor's... OR equivalent experience. Also Other Requirements (security screening). We'll need to preserve all substantive information. Could list each alternative as separate
• . Also include Other Requirements as separate
• maybe with subtext. Preferred Qualifications: we could put under

  Skills

  (or maybe

  Preferred Qualifications

  but not in examples). Use Skills heading. Pay: we have pay range info. We'll put under

  Pay

  with

  containing the ranges. We must not include boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So remove the EEO statement, the accommodation request, the equal opportunity employer paragraph, the "If you need assistance..." etc. Also remove the line about position open for minimum 5 days etc? That's maybe considered application instructions? It's about posting duration; could be considered metadata; maybe drop. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." The "This position will be open for a minimum of 5 days..." is minor metadata; we could drop it. Also the link to benefits and pay information: we already captured pay; the link is extra; maybe drop. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the pay ranges exactly as stated. Let's extract text. Overview text: "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 passionate engineers to help achieve that mission. We are looking for a Principal SoC Design Engineer to work in the dynamic Microsoft Artificial Intelligence System on Chip (AISoC) Silicon team. The candidate must be a highly motivated self-starter who will thrive in this cutting-edge technical environment. Microsoft’s mission is to empower every person and every organization on the planet to achieve more. As employees we come together with a growth mindset, innovate to empower others, and collaborate to realize our shared goals. Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond." We should keep that as a paragraph. Responsibilities: "You will be part of the SOC design team driving many facets of high performance, high bandwidth AI accelerator designs. The tasks will include working on verification of Intellectual Property (IP) microarchitecture specification, Register Transfer Level (RTL) design, System on Chip (SOC) integration including clocking and resets, Synthesis and static checks such as Lint and Clock/Reset domain crossings. Throughout the program you will be interacting with various teams, including architecture, verification, and physical design, ensuring that the design is implemented and verified to the spec." Qualifications Required Qualifications: "Doctorate in Electrical Engineering, Computer Engineering, Computer Science, or related field AND 3+ years technical engineering experienceOR Master's Degree in Electrical Engineering, Computer Engineering, Computer Science, or related field AND 6+ years technical engineering experienceOR Bachelor's Degree in Electrical Engineering, Computer Engineering, Computer Science, or related field AND 8+ years technical engineering experienceOR equivalent experience." Note there is missing spaces before OR; we should preserve as is but maybe add spaces for readability? We must not invent or summarize away detail; but we can format as list items preserving the text. We'll keep the exact strings but maybe add line breaks. 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." We'll keep that as a list item maybe. Preferred Qualifications: "10+ years expertise in Verification of SoC complexes 8+ years of experience delivering successful IP or Application Specific Integrated Circuits (ASIC)/SOC designs. 8+ years of experience in Lint, CD/RDC, Smoke, Synthesis, Timing constraints, Power, Performance, Area (PPA) trade-offs and Post-Silicon Debug Experience with SoC Verification and Integration Experience with Clocking and reset Experience with Complex algorithmic designs for AI usages Experience with Script development." Note there is missing punctuation; we keep as is. 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. Certain roles may be eligible for benefits and other compensation. Find additional benefits and pay information here: https://careers.microsoft.com/us/en/us-corporate-pay" We should keep the pay ranges; the line about benefits eligibility and link maybe we can drop as it's not specific benefits. But we could keep as part of Pay section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Pay is stated. The extra line about benefits eligibility is not specific benefits; but it's part of the same paragraph. We could keep it as part of Pay section but it's not pay info. Might be considered boilerplate? It's not exactly boilerplate but it's generic. Safer to keep only the pay range sentences, drop the benefits eligibility line and link. However we must preserve ALL substantive information; the benefits eligibility line is substantive? It says "Certain roles may be eligible for benefits and other compensation." That's generic; maybe considered boilerplate. The link is definitely boilerplate. I'd drop that sentence. Thus Pay section will have two sentences: the typical base pay range... and the different range for specific locations. Now produce HTML:

  About the role

  Overview text...

  Responsibilities

  Responsibilities text...

  Qualifications

  • Doctorate in Electrical Engineering, Computer Engineering, Computer Science, or related field AND 3+ years technical engineering experience
  • Master's Degree in Electrical Engineering, Computer Engineering, Computer Science, or related field AND 6+ years technical engineering experience
  • Bachelor's Degree in Electrical Engineering, Computer Engineering, Computer Science, or related field AND 8+ years technical engineering experience
  • equivalent experience
  • 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.

  Skills