Principal Optical 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, maybe also Pay. We need to include sections only when posting has real specific content. So we will have sections: Overview (maybe as About the role? But they said use headings like About the role, Responsibilities, etc. The posting has "Overview" then "Responsibilities", "Qualifications". Also there is pay info. So we can map Overview to About the role? Or we could just use Overview as heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use those headings if appropriate. The posting has Overview, Responsibilities, Qualifications, and Pay. So we can use About the role
for Overview, Responsibilities
, Qualifications
, Pay
. Also maybe Benefits? Not present. Schedule? Not present. So we include only those sections.
We need to preserve all substantive information, 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 the EEO paragraph, the accommodation sentence, the "Find additional benefits and pay information here:" link? That's maybe considered benefits/pay info but it's a link; we might keep the pay range but drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits/pay info is not exactly boilerplate but could be considered navigation? It's a link to external site; maybe we should keep the pay info but not the link? The instruction says preserve ALL substantive information; the link is not substantive? It's a reference; could be considered boilerplate. Safer to drop the link and just keep the pay ranges.
Also need to remove duplicated lines: there may be repeated sentences? Not obvious.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus for Overview we will have a
containing the overview paragraphs (maybe multiple paragraphs). For Responsibilities we will have a
with each responsibility as - . For Qualifications we will have required qualifications and preferred qualifications; we can split into Required and Preferred maybe as subheadings? But instruction only allows those section headings; we could embed both required and preferred within Qualifications section using
and
. Could also separate into Required Qualifications and Preferred Qualifications as ? Not allowed. Better to keep within Qualifications section: have a
for required qualifications prose, then a
for list? The required qualifications are a bit complex: they have multiple options (Master's + 7 years OR Bachelor's + 8 years OR equivalent). Also other requirements (security screening). Preferred qualifications also have multiple options and bullet list of expertise.
We need to preserve all substantive information; we can represent as prose sentences.
We'll produce:
About the role
Overview text...
Responsibilities
- ...
...
Qualifications
Required Qualifications: ...
Other Requirements: ...
Preferred Qualifications: ...
Deep expertise and hands-on in one or more of the following: ...
Experience with AI infrastructure, GPU fabrics, InfiniBand, Ethernet, or UALink ecosystems.
Knowledge of Optical Engineering and Optical Engineering concepts, testing procedures, standards, tools and appropriate analysis methods.
Experience developing high-density fiber infrastructure, including fiber shuffle solutions, patch panels, connectors, cable assemblies, and rack-scale optical systems.
Hands-on testing and validation experience in active and passive fiber optic components and end-to-end fiber links.
But we need to use - for any list of duties/requirements/benefits. The responsibilities are a list, so we use ul. For qualifications, there are lists within the text (like deep expertise list). Those could be turned into ul as well. However the instruction: "Use
- for any list of duties/requirements/benefits, and
for prose." So if we have a list of expertise, we should make it a ul. Similarly for the list of options for degrees? Might be better to keep as prose? But they are options separated by OR; could be a list. Safer to turn any enumerated items into ul.
Thus for Required Qualifications we could have a ul with three options: Master's + 7 years, Bachelor's + 8 years, equivalent experience. Then Other Requirements as a p. Then Preferred Qualifications: we could have a ul with four options (Doctorate+6 years, Master's+8 years, Bachelor's+12 years, equivalent experience). Then Deep expertise list as ul. Then Experience with AI infrastructure etc as ul? Actually that's a single sentence listing multiple items; could be ul. Knowledge of Optical Engineering... could be p. Experience developing high-density fiber infrastructure... could be ul. Hands-on testing... could be p.
We need to preserve all substantive information; we must not lose any detail.
Let's extract the exact text.
Overview paragraph(s):
"Overview 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. As Microsoft's cloud business continues to grow the ability to deploy new offerings and hardware infrastructure on time, in high volume with high quality and lowest cost is of paramount importance. To achieve this goal, the Cloud Hardware Systems Engineering (CHSE) team is instrumental in defining and delivering operational measures of success for hardware manufacturing, improving the planning process, quality, delivery, scale and sustainability related to Microsoft cloud hardware. We are looking for engineers with a dedicated passion for customer focused solutions, insight and industry knowledge to envision and implement future technical solutions that will manage and optimize the Cloud infrastructure. We are seeking a Principal Optical Engineer to drive the architectural design, production roadmap, engineering efforts for next-generation optical interconnects in hyperscale AI infrastructure. This role will serve as an architect/engineer responsible for Cloud/AI optical interconnects, and rack-scale fiber management. The candidate will work across silicon, systems, networking, platform architecture, datacenter engineering, and external ecosystem partners to bring innovative optical technologies from concept through large-scale production deployment. The ideal candidate combines deep expertise in optical systems with strong architecture, ecosystem, and execution skills, and can influence platform-level decisions across multiple generations of AI infrastructure. #SCHIE"
We need to remove the "#SCHIE" tag maybe as boilerplate? It's a tag; could be considered metadata; but it's not substantive. We'll drop it.
Now Responsibilities list:
"This individual will serve as one of Microsoft's technical leaders in optics and photonics, shaping the company's multi-generation roadmap for Cloud/AI interconnects and rack-scale optical infrastructure. Success in this role will directly influence platform architecture, deployment scalability, power efficiency, cost structure, and time-to-revenue for future AI systems. Define and drive Microsoft's optical interconnect strategy for next-generation AI platforms. Evaluate emerging technologies and determine the optimal migration path across multiple platform generations. Lead architecture and product definition for rack-scale fiber management supporting AI clusters Define bandwidth density, latency, reliability, power efficiency, serviceability, manufacturability, and cost targets. Lead development of rack-scale fiber management solutions including Fiber shuffles, Fiber connectors, and fiber cabling Develop standards and best practices for large-scale deployment of optical infrastructure across AI datacenters. Drive supplier roadmaps to align with Microsoft's future platform requirements. Influence industry standards and ecosystem direction through joint development initiatives and technical forums. Drive architecture reviews and technical decision making across multiple organizations. Guide optical technologies through proof-of-concept, qualification, productization, manufacturing readiness, and fleet deployment. Support root-cause analysis and operational issue resolution for deployed systems."
We need to split into separate items. Some sentences are run together missing punctuation. We'll parse:
- This individual will serve as one of Microsoft's technical leaders in optics and photonics, shaping the company's multi-generation roadmap for Cloud/AI interconnects and rack-scale optical infrastructure.
- Success in this role will directly influence platform architecture, deployment scalability, power efficiency, cost structure, and time-to-revenue for future AI systems.
- Define and drive Microsoft's optical interconnect strategy for next-generation AI platforms.
- Evaluate emerging technologies and determine the optimal migration path across multiple platform generations.
- Lead architecture and product definition for rack-scale fiber management supporting AI clusters
- Define bandwidth density, latency, reliability, power efficiency, serviceability, manufacturability, and cost targets.
- Lead development of rack-scale fiber management solutions including Fiber shuffles, Fiber connectors, and fiber cabling
- Develop standards and best practices for large-scale deployment of optical infrastructure across AI datacenters.
- Drive supplier roadmaps to align with Microsoft's future platform requirements.
- Influence industry standards and ecosystem direction through joint development initiatives and technical forums.
- Drive architecture reviews and technical decision making across multiple organizations.
- Guide optical technologies through proof-of-concept, qualification, productization, manufacturing readiness, and fleet deployment.
- Support root-cause analysis and operational issue resolution for deployed systems.
Note some lines missing verb; but we keep as is.
Now Qualifications:
Required Qualifications: "Master's Degree in Electrical Engineering, Computer Engineering, Mechanical Engineering, or related field AND 7+ years technical engineering experience OR Bachelor's Degree in Electrical Engineering, Computer Engineering, Mechanical Engineering, or related field AND 8+ years technical engineering experience OR equivalent experience."
Other Requirements: "Ability to meet Microsoft, customer, and/or government security screening requirements is required for this role. These requirements include, but are not limited to, the following specialized security screening:Microsoft Cloud Background Check. This position is required to pass the Microsoft Cloud Background Check upon hire or transfer and every two years thereafter."
Preferred Qualifications: "Knowledge and experience of Fiber Optics including related tools, devices, processes, design, operations, or manufacturing, etc. Doctorate Degree in Electrical Engineering, Optical Engineering, Mechanical Engineering, or related field AND 6+ years of technical engineering experience OR Master's Degree in Electrical Engineering, Optical Engineering, Mechanical Engineering, or related field AND 8+ years of technical engineering experience OR Bachelor's Degree in Electrical Engineering, Optical Engineering, Mechanical Engineering, or related field AND 12+ years of technical engineering experience OR equivalent experience."
Then list: "Deep expertise and hands-on in one or more of the following:Data center networkingHigh-speed copper or optical interconnectsHigh-speed optical transmission systemsCo-Packaged Optics (CPO) or Near-Packaged Optics (NPO)Silicon PhotonicsPluggable opticsAdvanced packagingRack-scale fiber management Experience with AI infrastructure, GPU fabrics, InfiniBand, Ethernet, or UALink ecosystems. Knowledge of Optical Engineering and Optical Engineering concepts, testing procedures, standards, tools and appropriate analysis methods.Experience developing high-density fiber infrastructure, including fiber shuffle solutions, patch panels, connectors, cable assemblies, and rack-scale optical systems. Hands-on testing and validation experience in active and passive fiber optic components and end-to-end fiber links."
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use those headings if appropriate. The posting has Overview, Responsibilities, Qualifications, and Pay. So we can use About the role
for Overview, Responsibilities
, Qualifications
, Pay
. Also maybe Benefits? Not present. Schedule? Not present. So we include only those sections.
We need to preserve all substantive information, 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 the EEO paragraph, the accommodation sentence, the "Find additional benefits and pay information here:" link? That's maybe considered benefits/pay info but it's a link; we might keep the pay range but drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits/pay info is not exactly boilerplate but could be considered navigation? It's a link to external site; maybe we should keep the pay info but not the link? The instruction says preserve ALL substantive information; the link is not substantive? It's a reference; could be considered boilerplate. Safer to drop the link and just keep the pay ranges.
Also need to remove duplicated lines: there may be repeated sentences? Not obvious.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus for Overview we will have a
containing the overview paragraphs (maybe multiple paragraphs). For Responsibilities we will have a
with each responsibility as - . For Qualifications we will have required qualifications and preferred qualifications; we can split into Required and Preferred maybe as subheadings? But instruction only allows those section headings; we could embed both required and preferred within Qualifications section using
and
. Could also separate into Required Qualifications and Preferred Qualifications as ? Not allowed. Better to keep within Qualifications section: have a
for required qualifications prose, then a
for list? The required qualifications are a bit complex: they have multiple options (Master's + 7 years OR Bachelor's + 8 years OR equivalent). Also other requirements (security screening). Preferred qualifications also have multiple options and bullet list of expertise.
We need to preserve all substantive information; we can represent as prose sentences.
We'll produce:
About the role
Overview text...
Responsibilities
- ...
...
Qualifications
Required Qualifications: ...
Other Requirements: ...
Preferred Qualifications: ...
Deep expertise and hands-on in one or more of the following: ...
Experience with AI infrastructure, GPU fabrics, InfiniBand, Ethernet, or UALink ecosystems.
Knowledge of Optical Engineering and Optical Engineering concepts, testing procedures, standards, tools and appropriate analysis methods.
Experience developing high-density fiber infrastructure, including fiber shuffle solutions, patch panels, connectors, cable assemblies, and rack-scale optical systems.
Hands-on testing and validation experience in active and passive fiber optic components and end-to-end fiber links.
But we need to use - for any list of duties/requirements/benefits. The responsibilities are a list, so we use ul. For qualifications, there are lists within the text (like deep expertise list). Those could be turned into ul as well. However the instruction: "Use
- for any list of duties/requirements/benefits, and
for prose." So if we have a list of expertise, we should make it a ul. Similarly for the list of options for degrees? Might be better to keep as prose? But they are options separated by OR; could be a list. Safer to turn any enumerated items into ul.
Thus for Required Qualifications we could have a ul with three options: Master's + 7 years, Bachelor's + 8 years, equivalent experience. Then Other Requirements as a p. Then Preferred Qualifications: we could have a ul with four options (Doctorate+6 years, Master's+8 years, Bachelor's+12 years, equivalent experience). Then Deep expertise list as ul. Then Experience with AI infrastructure etc as ul? Actually that's a single sentence listing multiple items; could be ul. Knowledge of Optical Engineering... could be p. Experience developing high-density fiber infrastructure... could be ul. Hands-on testing... could be p.
We need to preserve all substantive information; we must not lose any detail.
Let's extract the exact text.
Overview paragraph(s):
"Overview 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. As Microsoft's cloud business continues to grow the ability to deploy new offerings and hardware infrastructure on time, in high volume with high quality and lowest cost is of paramount importance. To achieve this goal, the Cloud Hardware Systems Engineering (CHSE) team is instrumental in defining and delivering operational measures of success for hardware manufacturing, improving the planning process, quality, delivery, scale and sustainability related to Microsoft cloud hardware. We are looking for engineers with a dedicated passion for customer focused solutions, insight and industry knowledge to envision and implement future technical solutions that will manage and optimize the Cloud infrastructure. We are seeking a Principal Optical Engineer to drive the architectural design, production roadmap, engineering efforts for next-generation optical interconnects in hyperscale AI infrastructure. This role will serve as an architect/engineer responsible for Cloud/AI optical interconnects, and rack-scale fiber management. The candidate will work across silicon, systems, networking, platform architecture, datacenter engineering, and external ecosystem partners to bring innovative optical technologies from concept through large-scale production deployment. The ideal candidate combines deep expertise in optical systems with strong architecture, ecosystem, and execution skills, and can influence platform-level decisions across multiple generations of AI infrastructure. #SCHIE"
We need to remove the "#SCHIE" tag maybe as boilerplate? It's a tag; could be considered metadata; but it's not substantive. We'll drop it.
Now Responsibilities list:
"This individual will serve as one of Microsoft's technical leaders in optics and photonics, shaping the company's multi-generation roadmap for Cloud/AI interconnects and rack-scale optical infrastructure. Success in this role will directly influence platform architecture, deployment scalability, power efficiency, cost structure, and time-to-revenue for future AI systems. Define and drive Microsoft's optical interconnect strategy for next-generation AI platforms. Evaluate emerging technologies and determine the optimal migration path across multiple platform generations. Lead architecture and product definition for rack-scale fiber management supporting AI clusters Define bandwidth density, latency, reliability, power efficiency, serviceability, manufacturability, and cost targets. Lead development of rack-scale fiber management solutions including Fiber shuffles, Fiber connectors, and fiber cabling Develop standards and best practices for large-scale deployment of optical infrastructure across AI datacenters. Drive supplier roadmaps to align with Microsoft's future platform requirements. Influence industry standards and ecosystem direction through joint development initiatives and technical forums. Drive architecture reviews and technical decision making across multiple organizations. Guide optical technologies through proof-of-concept, qualification, productization, manufacturing readiness, and fleet deployment. Support root-cause analysis and operational issue resolution for deployed systems."
We need to split into separate items. Some sentences are run together missing punctuation. We'll parse:
- This individual will serve as one of Microsoft's technical leaders in optics and photonics, shaping the company's multi-generation roadmap for Cloud/AI interconnects and rack-scale optical infrastructure.
- Success in this role will directly influence platform architecture, deployment scalability, power efficiency, cost structure, and time-to-revenue for future AI systems.
- Define and drive Microsoft's optical interconnect strategy for next-generation AI platforms.
- Evaluate emerging technologies and determine the optimal migration path across multiple platform generations.
- Lead architecture and product definition for rack-scale fiber management supporting AI clusters
- Define bandwidth density, latency, reliability, power efficiency, serviceability, manufacturability, and cost targets.
- Lead development of rack-scale fiber management solutions including Fiber shuffles, Fiber connectors, and fiber cabling
- Develop standards and best practices for large-scale deployment of optical infrastructure across AI datacenters.
- Drive supplier roadmaps to align with Microsoft's future platform requirements.
- Influence industry standards and ecosystem direction through joint development initiatives and technical forums.
- Drive architecture reviews and technical decision making across multiple organizations.
- Guide optical technologies through proof-of-concept, qualification, productization, manufacturing readiness, and fleet deployment.
- Support root-cause analysis and operational issue resolution for deployed systems.
Note some lines missing verb; but we keep as is.
Now Qualifications:
Required Qualifications: "Master's Degree in Electrical Engineering, Computer Engineering, Mechanical Engineering, or related field AND 7+ years technical engineering experience OR Bachelor's Degree in Electrical Engineering, Computer Engineering, Mechanical Engineering, or related field AND 8+ years technical engineering experience OR equivalent experience."
Other Requirements: "Ability to meet Microsoft, customer, and/or government security screening requirements is required for this role. These requirements include, but are not limited to, the following specialized security screening:Microsoft Cloud Background Check. This position is required to pass the Microsoft Cloud Background Check upon hire or transfer and every two years thereafter."
Preferred Qualifications: "Knowledge and experience of Fiber Optics including related tools, devices, processes, design, operations, or manufacturing, etc. Doctorate Degree in Electrical Engineering, Optical Engineering, Mechanical Engineering, or related field AND 6+ years of technical engineering experience OR Master's Degree in Electrical Engineering, Optical Engineering, Mechanical Engineering, or related field AND 8+ years of technical engineering experience OR Bachelor's Degree in Electrical Engineering, Optical Engineering, Mechanical Engineering, or related field AND 12+ years of technical engineering experience OR equivalent experience."
Then list: "Deep expertise and hands-on in one or more of the following:Data center networkingHigh-speed copper or optical interconnectsHigh-speed optical transmission systemsCo-Packaged Optics (CPO) or Near-Packaged Optics (NPO)Silicon PhotonicsPluggable opticsAdvanced packagingRack-scale fiber management Experience with AI infrastructure, GPU fabrics, InfiniBand, Ethernet, or UALink ecosystems. Knowledge of Optical Engineering and Optical Engineering concepts, testing procedures, standards, tools and appropriate analysis methods.Experience developing high-density fiber infrastructure, including fiber shuffle solutions, patch panels, connectors, cable assemblies, and rack-scale optical systems. Hands-on testing and validation experience in active and passive fiber optic components and end-to-end fiber links."
for prose. Thus for Overview we will have a
containing the overview paragraphs (maybe multiple paragraphs). For Responsibilities we will have a
- with each responsibility as
- . For Qualifications we will have required qualifications and preferred qualifications; we can split into Required and Preferred maybe as subheadings? But instruction only allows those section headings; we could embed both required and preferred within Qualifications section using
and
- . Could also separate into Required Qualifications and Preferred Qualifications as
- ... ...
- for any list of duties/requirements/benefits. The responsibilities are a list, so we use ul. For qualifications, there are lists within the text (like deep expertise list). Those could be turned into ul as well. However the instruction: "Use
- for any list of duties/requirements/benefits, and
for prose." So if we have a list of expertise, we should make it a ul. Similarly for the list of options for degrees? Might be better to keep as prose? But they are options separated by OR; could be a list. Safer to turn any enumerated items into ul. Thus for Required Qualifications we could have a ul with three options: Master's + 7 years, Bachelor's + 8 years, equivalent experience. Then Other Requirements as a p. Then Preferred Qualifications: we could have a ul with four options (Doctorate+6 years, Master's+8 years, Bachelor's+12 years, equivalent experience). Then Deep expertise list as ul. Then Experience with AI infrastructure etc as ul? Actually that's a single sentence listing multiple items; could be ul. Knowledge of Optical Engineering... could be p. Experience developing high-density fiber infrastructure... could be ul. Hands-on testing... could be p. We need to preserve all substantive information; we must not lose any detail. Let's extract the exact text. Overview paragraph(s): "Overview 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. As Microsoft's cloud business continues to grow the ability to deploy new offerings and hardware infrastructure on time, in high volume with high quality and lowest cost is of paramount importance. To achieve this goal, the Cloud Hardware Systems Engineering (CHSE) team is instrumental in defining and delivering operational measures of success for hardware manufacturing, improving the planning process, quality, delivery, scale and sustainability related to Microsoft cloud hardware. We are looking for engineers with a dedicated passion for customer focused solutions, insight and industry knowledge to envision and implement future technical solutions that will manage and optimize the Cloud infrastructure. We are seeking a Principal Optical Engineer to drive the architectural design, production roadmap, engineering efforts for next-generation optical interconnects in hyperscale AI infrastructure. This role will serve as an architect/engineer responsible for Cloud/AI optical interconnects, and rack-scale fiber management. The candidate will work across silicon, systems, networking, platform architecture, datacenter engineering, and external ecosystem partners to bring innovative optical technologies from concept through large-scale production deployment. The ideal candidate combines deep expertise in optical systems with strong architecture, ecosystem, and execution skills, and can influence platform-level decisions across multiple generations of AI infrastructure. #SCHIE" We need to remove the "#SCHIE" tag maybe as boilerplate? It's a tag; could be considered metadata; but it's not substantive. We'll drop it. Now Responsibilities list: "This individual will serve as one of Microsoft's technical leaders in optics and photonics, shaping the company's multi-generation roadmap for Cloud/AI interconnects and rack-scale optical infrastructure. Success in this role will directly influence platform architecture, deployment scalability, power efficiency, cost structure, and time-to-revenue for future AI systems. Define and drive Microsoft's optical interconnect strategy for next-generation AI platforms. Evaluate emerging technologies and determine the optimal migration path across multiple platform generations. Lead architecture and product definition for rack-scale fiber management supporting AI clusters Define bandwidth density, latency, reliability, power efficiency, serviceability, manufacturability, and cost targets. Lead development of rack-scale fiber management solutions including Fiber shuffles, Fiber connectors, and fiber cabling Develop standards and best practices for large-scale deployment of optical infrastructure across AI datacenters. Drive supplier roadmaps to align with Microsoft's future platform requirements. Influence industry standards and ecosystem direction through joint development initiatives and technical forums. Drive architecture reviews and technical decision making across multiple organizations. Guide optical technologies through proof-of-concept, qualification, productization, manufacturing readiness, and fleet deployment. Support root-cause analysis and operational issue resolution for deployed systems." We need to split into separate items. Some sentences are run together missing punctuation. We'll parse: - This individual will serve as one of Microsoft's technical leaders in optics and photonics, shaping the company's multi-generation roadmap for Cloud/AI interconnects and rack-scale optical infrastructure. - Success in this role will directly influence platform architecture, deployment scalability, power efficiency, cost structure, and time-to-revenue for future AI systems. - Define and drive Microsoft's optical interconnect strategy for next-generation AI platforms. - Evaluate emerging technologies and determine the optimal migration path across multiple platform generations. - Lead architecture and product definition for rack-scale fiber management supporting AI clusters - Define bandwidth density, latency, reliability, power efficiency, serviceability, manufacturability, and cost targets. - Lead development of rack-scale fiber management solutions including Fiber shuffles, Fiber connectors, and fiber cabling - Develop standards and best practices for large-scale deployment of optical infrastructure across AI datacenters. - Drive supplier roadmaps to align with Microsoft's future platform requirements. - Influence industry standards and ecosystem direction through joint development initiatives and technical forums. - Drive architecture reviews and technical decision making across multiple organizations. - Guide optical technologies through proof-of-concept, qualification, productization, manufacturing readiness, and fleet deployment. - Support root-cause analysis and operational issue resolution for deployed systems. Note some lines missing verb; but we keep as is. Now Qualifications: Required Qualifications: "Master's Degree in Electrical Engineering, Computer Engineering, Mechanical Engineering, or related field AND 7+ years technical engineering experience OR Bachelor's Degree in Electrical Engineering, Computer Engineering, Mechanical Engineering, or related field AND 8+ years technical engineering experience OR equivalent experience." Other Requirements: "Ability to meet Microsoft, customer, and/or government security screening requirements is required for this role. These requirements include, but are not limited to, the following specialized security screening:Microsoft Cloud Background Check. This position is required to pass the Microsoft Cloud Background Check upon hire or transfer and every two years thereafter." Preferred Qualifications: "Knowledge and experience of Fiber Optics including related tools, devices, processes, design, operations, or manufacturing, etc. Doctorate Degree in Electrical Engineering, Optical Engineering, Mechanical Engineering, or related field AND 6+ years of technical engineering experience OR Master's Degree in Electrical Engineering, Optical Engineering, Mechanical Engineering, or related field AND 8+ years of technical engineering experience OR Bachelor's Degree in Electrical Engineering, Optical Engineering, Mechanical Engineering, or related field AND 12+ years of technical engineering experience OR equivalent experience." Then list: "Deep expertise and hands-on in one or more of the following:Data center networkingHigh-speed copper or optical interconnectsHigh-speed optical transmission systemsCo-Packaged Optics (CPO) or Near-Packaged Optics (NPO)Silicon PhotonicsPluggable opticsAdvanced packagingRack-scale fiber management Experience with AI infrastructure, GPU fabrics, InfiniBand, Ethernet, or UALink ecosystems. Knowledge of Optical Engineering and Optical Engineering concepts, testing procedures, standards, tools and appropriate analysis methods.Experience developing high-density fiber infrastructure, including fiber shuffle solutions, patch panels, connectors, cable assemblies, and rack-scale optical systems. Hands-on testing and validation experience in active and passive fiber optic components and end-to-end fiber links."
- for any list of duties/requirements/benefits, and
? Not allowed. Better to keep within Qualifications section: have a
for required qualifications prose, then a
- for list? The required qualifications are a bit complex: they have multiple options (Master's + 7 years OR Bachelor's + 8 years OR equivalent). Also other requirements (security screening). Preferred qualifications also have multiple options and bullet list of expertise.
We need to preserve all substantive information; we can represent as prose sentences.
We'll produce:
About the role
Overview text...
Responsibilities
Qualifications
Required Qualifications: ...
Other Requirements: ...
Preferred Qualifications: ...
Deep expertise and hands-on in one or more of the following: ...
Experience with AI infrastructure, GPU fabrics, InfiniBand, Ethernet, or UALink ecosystems.
Knowledge of Optical Engineering and Optical Engineering concepts, testing procedures, standards, tools and appropriate analysis methods.
Experience developing high-density fiber infrastructure, including fiber shuffle solutions, patch panels, connectors, cable assemblies, and rack-scale optical systems.
Hands-on testing and validation experience in active and passive fiber optic components and end-to-end fiber links.
But we need to use