Senior Quantum Analog Layout Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. The posting includes Overview, Responsibilities, Qualifications, Other Requirements, Preferred Qualifications, Pay info, etc. We need to include sections only when there is real content. We need to preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip out the equal opportunity employer paragraph, the accommodation request, the "This position will be open for a minimum of 5 days..." maybe that's application instruction? It says "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the EEO paragraph and the accommodation request. Also remove the line about "This position will be open for a minimum of 5 days..." as it's application instruction. Also remove the link to benefits maybe? The instruction: "Prefer a few substantive sections over many thin ones." We need to include Pay section if posting actually states them. Yes, there is pay range info. So we need a Pay section with that info. 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. We should not create Benefits section unless posting actually states them. It does not list specific benefits, just a link. So we should not include Benefits section. Schedule? Not mentioned. So no Schedule section. We need sections: Overview (maybe as About the role?), Responsibilities, Requirements (maybe Qualifications?), Qualifications (maybe Preferred Qualifications?), Skills? Could combine. The instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. We have Overview paragraph at start: "Microsoft's Quantum team is building..." That's about the role. Could be About the role. Responsibilities: we have a block. Qualifications: we have Required/minimum qualifications block, plus Other Requirements (security screening, AI tools). That's qualifications. Preferred Qualifications: separate block. Skills: maybe we could extract from Preferred Qualifications as skills, but we could also put Preferred Qualifications under Skills heading? The instruction says use headings like Skills. We could have a Skills section summarizing the preferred qualifications (tools, experience). But we must not invent or summarize away detail; we need to preserve all substantive info. If we put them under Skills, we need to keep the details. Could also have a Qualifications section for required/minimum, and a Skills section for preferred qualifications (tools, experience). That seems okay. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Overview: The first paragraph(s) before Responsibilities. Original: "Overview Microsoft's Quantum team is building the first scalable, fault-tolerant quantum computer, advancing everything from quantum hardware and error correction to Azure integration. Our full-stack strategy spans the physics of quantum devices through scalable readout and control infrastructures powered by cryo-electronics. As quantum computing enters a pivotal phase of accelerated growth, this position offers a unique opportunity to contribute meaningfully to a transformative technology, such as the Application Specific Integrated Circuits (ASICs) and analog circuitry developed by this team. As a Senior Quantum Analog Layout Engineer on the Quantum 1st Party Hardware ASIC team, you will play a critical leadership role in advancing Microsoft's quantum analog infrastructure, driving Analog Layout designs and coordinating employees, contingent staff, and external vendors to deliver high-quality designs. 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 need to keep all that. Could be a
under
About the role
. Responsibilities: The block after "Responsibilities". Let's capture: "Deliver Schematic-to-Graphic Database System (GDS) layouts for cutting-edge, high-performance, high-speed, low-power IP designs, including interconnectivity solutions and foundational Analog circuit blocks. Execute these layouts across multiple process nodes, including deep Fin Field-Effect Transistor (FinFET), following industry best practices. Develop plans for Analog Mask Layout execution and follow processes and methodologies to deliver IP blocks. Coordinate tasks with junior layout team members as needed. Using Cadence Virtuoso (or other equivalent) design tools and flows; perform layout implementation of analog-intensive IPs and help establish flows, methodologies, and processes for execution alongside peers. Support the on-boarding and off-boarding of contingent layout staff and vendor partners as needed; help direct their day-to-day execution to ensure quality and schedule are met. Work with other members of the team to deliver IPs, including project planning, schedule tracking, and report generation. Follow, augment, or put in place processes and methodologies for high-quality execution alongside peers. Other Embody our culture and values." We need to keep "Other" and "Embody our culture and values." as part of responsibilities? Probably yes. We'll put each bullet as- . The "Other" line maybe not a bullet; but we can treat as a
- for any list of duties/requirements/benefits. So we should list duties as list items. The "Other" and "Embody our culture and values." could be a separate
. But we could also make them list items. Safer: treat them as list items as well. Qualifications (Required/minimum qualifications): block: "Required/minimum qualifications Doctorate in Physics, Engineering, or related field AND 1+ year(s) experience in industry or in a research and development environment, could include completion of a post doctoral research positionOR Master's Degree in Physics, Engineering, or related field AND 4+ years experience in industry or in a research and development environment OR Bachelor's Degree in Physics, Engineering, or related field AND 6+ years experience in industry or in a research and development environment OR equivalent experience." Note there is missing spaces due to OCR: "positionOR". We need to preserve as is? Probably keep the text but we could add a space for readability? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Changing spacing might be considered altering? It's minor formatting; but we could keep as is. Might be okay to add a space to make readable but not inventing content. Safer to keep exactly as given? The original text: "...post doctoral research positionOR Master's Degree...". There's no space. We'll keep it exactly. Then "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. Citizenship & Citizenship Verification: 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 (ITAR) or Export Administration Regulations (EAR), 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 U.S. permanent 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. Ability to leverage AI tools to drive innovation and efficiency (e.g., performance modeling and analysis, research gathering, day to day task automation). Ability to work in an “AI-first” environment using modern AI tools to accelerate discovery through hardware development." We need to keep that as part of qualifications? Could be under Requirements heading. We'll treat as part of Qualifications (maybe Requirements). We'll put under
Requirements
maybe. Preferred Qualifications block: "Preferred Qualifications 10+ years of experience in Analog Mask Layout execution and IP delivery, including delivery of medium-to-large complexity analog blocks into mass production. 5+ years of lead experience covering day-to-day task coordination and overall delivery responsibilities across a layout team. Proficient use of Electronic Design Automation (EDA) tools from Cadence, Mentor, and Synopsys, including advanced Schematic-Driven Layout (SDL). Hands-on layout experience with high-performance analog blocks such as Voltage-Controlled Oscillators (VCOs), charge pumps, interpolators, bandgap references, Operational Transconductance Amplifiers (OTAs), Phase-Locked Loops (PLLs), Analog-to-Digital and Digital-to-Analog Converters (ADCs/DACs), Low-Dropout Regulators (LDOs), Serializer/Deserializers (SerDes), and other foundational analog blocks. In-depth knowledge of analog design and layout guidelines for high-performance, high-speed, and/or low-power designs, including floor-planning, block-level routing, and large macro-level assemblies. Knowledge of industry-standard analog layout techniques such as common-centroid layout, matching, symmetrical layouts, signal shielding, use of dummy devices, and thermal-aware layouts with consideration for Electromigration/IR-drop (EM/IR) and other analog-specific guidelines. Demonstrated ability to coordinate execution with external vendors and contingent staff, including scoping deliverables, tracking progress, and accepting completed work. Ability to learn cryogenic Process Design Kits (PDKs) and apply analog layout techniques to designs that operate at cryogenic temperatures. #Quantum #QuantumCareers #MDQCareers" We need to keep the hashtags? They are likely metadata; could be considered boilerplate? Not sure. They are not substantive; maybe we can drop them as they are like tags. The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Hashtags maybe not boilerplate but could be considered metadata; but they are not substantive. Safer to drop them? The instruction says preserve ALL substantive information; hashtags are not substantive. So we can omit them. Pay section: "Quantum Engineering IC4 - The typical base pay range for this role across the U.S. is USD $119,800 - $234,700 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 $160,200 - $261,000 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 need to include Pay section with that info. The line about benefits and link maybe we can keep as part of Pay section? It's about benefits and pay info link. Since we are not creating a Benefits section, we can include that sentence in Pay section as extra info. However the instruction: "Prefer a few substantive sections over many thin ones." So we can include that sentence in Pay section. We must not include the EEO paragraph, accommodation request, and the line about position open for minimum 5 days. Now construct
after list? However instruction: Use