Senior Researcher

We need to output HTML fragment with sections only when there is real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: Overview (intro) maybe "About the role". There's a paragraph about Microsoft, Azure Data engineering team, mission, etc. That's about the role? Could be "About the role". We'll put that in

. Responsibilities: there is a long list of responsibilities after "Responsibilities". We'll put each bullet as

inside

. Qualifications: there is "Required/minimum qualifications" and "Job Requirements: Other & Additional". Also "Preferred/Additional Qualifications". Also "Research Sciences IC4 - The typical base pay range..." That's pay info. Also "Certain roles may be eligible for benefits and other compensation." That's benefits but vague. Also "Find additional benefits and pay information here: link". That's not specific benefit details. So we should not create Benefits section unless specific benefits listed. There's no specific benefits like health insurance, 401k, etc. So we omit Benefits. Pay: we have pay range info. That's specific: "Research Sciences 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." That's specific pay info. So we include Pay section. Schedule: not mentioned. So omit. Skills: maybe not explicit. There's "Ability to meet Microsoft, customer and/or government security screening requirements". That's more a requirement. Could be under Requirements. Also "Published research at top conferences", "2+ years experience in Natural language processing, Information Retrieval or post-training", "2+ years experience in hands-on experimentation." Those are preferred qualifications. So we can put them under Qualifications (Preferred). Or we could have a Skills section but not needed. We'll keep Qualifications covering required and preferred. Requirements: maybe we separate "Required/minimum qualifications" as Requirements? But the instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. Typically Requirements could be the mandatory qualifications. Qualifications could be preferred? But they are similar. We'll follow: Requirements = Required/minimum qualifications. Qualifications = Preferred/Additional Qualifications. Skills maybe not present; we could omit. Thus sections: - About the role: overview paragraphs (maybe multiple p). We'll combine into one

with the overview text. - Responsibilities: list of responsibilities. - Requirements: required/minimum qualifications bullet? It's a paragraph: "Bachelor's Degree in Computer Science or related technical field AND 4+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python OR equivalent experience." Also "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." That's also a requirement. We'll put as

• items. - Qualifications: preferred/additional qualifications: "Published research at top conferences", "2+ years experience in Natural language processing, Information Retrieval or post-training", "2+ years experience in hands-on experimentation." Also maybe "Research Sciences IC4 - The typical base pay range..." but that's pay, not qualification. So we list those three as
• . - Pay: the pay range info as

  . We must not include boilerplate like EEO, equal opportunity, application instructions, etc. Also remove duplicated lines. Also remove navigation etc. We must preserve all substantive information. Ensure we don't lose any detail. Let's extract the overview text: "Overview Microsoft is a company where passionate innovators come to collaborate, envision what can be and take their careers further. This is a world of more possibilities, more innovation, more openness, and the sky is the limit thinking in a cloud-enabled world. Microsoft’s Azure Data engineering team is leading the transformation of analytics in the world of data with products like databases, data integration, big data analytics, messaging & real-time analytics, and business intelligence. The products our portfolio include Microsoft Fabric, Azure SQL DB, Azure Cosmos DB, Azure PostgreSQL, Azure Data Factory, Azure Synapse Analytics, Azure Service Bus, Azure Event Grid, and Power BI. Our mission is to build the data platform for the age of AI, powering a new class of data-first applications and driving a data culture. The Databases organization delivers trusted, scalable operational AI ready databases that power application development across cloud, hybrid, and on premises environments. Our portfolio includes SQL, Azure Cosmos DB, DocumentDB, PostgreSQL, and MySQL, supporting developers as they build AI native applications and run critical workloads at global scale. We work on models, agents and indexing infrastructure for semantic retrieval and memories. Among other things, we developed DiskANN (github.com/Microsoft/DiskANN), the vector engine used across Microsoft and broadly in industry. We develop cutting edge models for semantic retrieval quality across modalities, agents for semantic retrieval and memories. We are a small team with a lot of freedom in setting technical direction and drive cross-company projects with large scope and own outcomes. We do not just value differences or different perspectives. We seek them out and invite them in so we can tap into the collective power of everyone in the company. As a result, our customers are better served." We'll put that in a

  . Responsibilities list: after "Responsibilities" we have a paragraph with many sentences separated by periods. Let's split into bullet points each sentence? The instruction: Use

  • for any list of duties/requirements/benefits. So we should convert each duty into a
  • . The responsibilities are: - Masters one or more subareas (e.g., Object Recognition, Text Classification) and gains expertise in a broad area of research (e.g., Machine Learning [ML], Natural Language - Processing, Computer Vision, Statistical Modeling). - Understands the corresponding literature, applicable research techniques, and academic context. - Identifies and articulates problems in an area of research that directly or indirectly impact business opportunities. - Advances a research agenda through one or more research projects, yielding new algorithms, prototypes, theories, tools, methods, analyses, insights, or collections of data in one or more subareas or a broad area of research. - Expands collaborative relationships with relevant product and business groups inside or outside of Microsoft as a domain expert and provides expertise or technology to them. - Takes initiative and participates in activities such as incorporating relevant data security considerations and guidelines, technology transfers, benchmarking technology with public domain data, filing patents, authoring white papers, developing or maintaining tools/services for internal Microsoft use, or consulting for product or business groups. - Collaborates with other relevant researchers, research groups, or engineering teams to contribute to or advance a research agenda. - Contributes to organizing workshops or conference sessions. - Publishes papers as lead author for high-quality conferences and journals, with an impact similar to that of a (United States) assistant professor. - Embody our culture and values We'll make each a
  • . Requirements: required/minimum qualifications plus security screening. We'll make two
  • maybe: - Bachelor's Degree in Computer Science or related technical field AND 4+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python OR 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. We could split the second into two li? But it's one requirement with detail. We'll keep as one li. Qualifications (preferred): list: - Published research at top conferences - 2+ years experience in Natural language processing, Information Retrieval or post-training - 2+ years experience in hands-on experimentation We'll make li each. Pay: we have the pay range info. We'll put as

    . We must not include any filler like "commensurate with experience". Not present. We must not include Benefits section because no specific benefits. We must not include Schedule. We must not include Skills. We must not include any EEO etc. Now produce HTML fragment:

    About the role

    Overview Microsoft is a company where passionate innovators come to collaborate, envision what can be and take their careers further. This is a world of more possibilities, more innovation, more openness, and the sky is the limit thinking in a cloud-enabled world. Microsoft’s Azure Data engineering team is leading the transformation of analytics in the world of data with products like databases, data integration, big data analytics, messaging & real-time analytics, and business intelligence. The products our portfolio include Microsoft Fabric, Azure SQL DB, Azure Cosmos DB, Azure PostgreSQL, Azure Data Factory, Azure Synapse Analytics, Azure Service Bus, Azure Event Grid, and Power BI. Our mission is to build the data platform for the age of AI, powering a new class of data-first applications and driving a data culture. The Databases organization delivers trusted, scalable operational AI ready databases that power application development across cloud, hybrid, and on premises environments. Our portfolio includes SQL, Azure Cosmos DB, DocumentDB, PostgreSQL, and MySQL, supporting developers as they build AI native applications and run critical workloads at global scale. We work on models, agents and indexing infrastructure for semantic retrieval and memories. Among other things, we developed DiskANN (github.com/Microsoft/DiskANN), the vector engine used across Microsoft and broadly in industry. We develop cutting edge models for semantic retrieval quality across modalities, agents for semantic retrieval and memories. We are a small team with a lot of freedom in setting technical direction and drive cross-company projects with large scope and own outcomes. We do not just value differences or different perspectives. We seek them out and invite them in so we can tap into the collective power of everyone in the company. As a result, our customers are better served.

    Responsibilities

    • Masters one or more subareas (e.g., Object Recognition, Text Classification) and gains expertise in a broad area of research (e.g., Machine Learning [ML], Natural Language - Processing, Computer Vision, Statistical Modeling).
    • Understands the corresponding literature, applicable research techniques, and academic context.
    • Identifies and articulates problems in an area of research that directly or indirectly impact business opportunities.
    • Advances a research agenda through one or more research projects, yielding new algorithms, prototypes, theories, tools, methods, analyses, insights, or collections of data in one or more subareas or a broad area of research.
    • Expands collaborative relationships with relevant product and business groups inside or outside of Microsoft as a domain expert and provides expertise or technology to them.
    • Takes initiative and participates in activities such as incorporating relevant data security considerations and guidelines, technology transfers, benchmarking technology with public domain data, filing patents, authoring white papers, developing or maintaining tools/services for internal Microsoft use, or consulting for product or business groups.
    • Collaborates with other relevant researchers, research groups, or engineering teams to contribute to or advance a research agenda.
    • Contributes to organizing workshops or conference sessions.
    • Publishes papers as lead author for high-quality conferences and journals, with an impact similar to that of a (United States) assistant professor.
    • Embody our culture and values

    Requirements