Cloud Engineering Consultant - CTJ - TS/SCI

We need to output 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). Do NOT repeat the job title as a heading. The posting includes Overview, Responsibilities, Qualifications, etc. We need to include sections only when posting has real, specific content. So we need sections: Overview (maybe as

Overview

), Responsibilities (

Responsibilities

), Qualifications (

Qualifications

), maybe Skills? The posting includes Preferred Qualifications and Required Qualifications; we can combine under Qualifications. Also Pay: there is pay range info. So we need a Pay section with that content. Benefits: not explicitly mentioned besides "Certain roles may be eligible for benefits and other compensation." That's vague; we should not create Benefits section unless specific content. So skip Benefits. Schedule: not mentioned. So we will have Overview, Responsibilities, Qualifications, Pay. 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, and application instructions. So we need to strip the EEO statement at end, the "Microsoft is an equal opportunity employer..." and the accommodation request. Also remove "This position will be open for a minimum of 5 days..." maybe that's application instruction? It's about posting duration; could be considered application instruction? Probably remove. Also remove "Find additional benefits and pay information here: https://..." maybe keep as part of Pay? It's a link; we could keep but it's more like reference. Might keep as part of Pay but it's a link; but it's not boilerplate. However it's a link to benefits/pay info; we could keep as part of Pay. But the instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." There's no Job ID. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to parse the responsibilities section: It has many bullet-like paragraphs but not explicit bullet list. We need to convert to

  • for any list of duties/requirements/benefits. The responsibilities are a series of sentences each starting with a bold heading like "Business Development", "Intellectual Property Management", etc. Those could be considered list items. We'll treat each bold heading and its description as a list item. Similarly Qualifications: Required Qualifications and Preferred Qualifications; we can list each as
  • . Pay: we have pay range info; we can put in

    . We must not include filler like "commensurate with experience". Not present. Let's extract content. Overview paragraph: "Overview As a Cloud Engineering Consultant on a development team, you will partner with customers and their integrators to modernize infrastructure and accelerate cloud adoption. You’ll design and implement secure, scalable, and automated solutions in Microsoft Azure—migrating from on-premises environments and guiding them through integration strategies that optimize workload performance, scalability, and operational efficiency in the cloud. Your work will leverage technologies such as Infrastructure as Code (IaC) with BICEP, Azure DevOps Server (ADO), Azure Kubernetes Service (AKS), containers, Azure Virtual Desktop (AVD), Azure DNS, Azure Firewall, Microsoft Entra ID, Conditional Access, and Privileged Identity Management (PIM). This Opportunity Will Allow You To Accelerate your career growth by leading complex cloud transformation initiatives. Hone your skills in cloud-native technologies and secure automation practices. Develop deep business acumen by aligning DevOps strategies with customer goals and compliance frameworks. 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. Might be long but okay. Responsibilities: The section starts with "Responsibilities" then list of headings: - Business Development: description. - Intellectual Property Management: description. - Operational Excellence: description. - Pre-Sales Support: description. - Readiness: description. - Technical Delivery: description. We need to convert each to

  • with maybe heading inside? But we can just put the heading as part of the li text. We must preserve all substantive information. So include the full description under each. Qualifications: Required Qualifications: "Bachelor's Degree in Computer Science, Engineering, Finance, Business, or related field AND 3+ years leadership experience in relevant area of businessOR equivalent experience." Note there's a missing space before "OR". We'll keep as is. Other Requirements: Security Clearance Requirements etc. That's part of qualifications. We need to include all that. Preferred Qualifications: list of items. We'll combine Required and Preferred under Qualifications section, maybe separate subheadings? But we only have h3 for section headings; we could have

    Qualifications

    then inside we can have

    for prose? But we need to use

    • for any list of duties/requirements/benefits. So we should list each requirement as
    • . Could separate Required and Preferred as separate
      groups with maybe a

      heading? But we cannot add extra headings besides h3. We could use

      to label "Required Qualifications:" then

      for items. That's allowed:

      for prose. So we can do:

      Qualifications

      Required Qualifications:

      • ...
      ...

      Preferred Qualifications:

      • ...
      ...
      That seems okay. Pay: we have pay range info. We'll put in

      . We must not include the link? Could keep as part of Pay: "Find additional benefits and pay information here: https://careers.microsoft.com/us/en/us-corporate-pay". That's not boilerplate; it's a reference. We'll keep. Now we need to strip boilerplate: The EEO statement at end, the accommodation request, the "Microsoft is an equal opportunity employer..." and the following sentences. Also remove "This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled." That's like application instruction; remove. Also remove "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 part of Other Requirements? Actually it's under Other Requirements? It appears after Security Clearance Requirements. It's a requirement; we should keep it as part of Qualifications? It's under Other Requirements? Actually the text: "Other Requirements Security Clearance Requirements: Candidates must be able 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: The successful candidate must have an active U.S. Government Top Secret/SCI Security Clearance. Ability to meet Microsoft, customer and/or government security screening requirements are required for this role. Failure to maintain or obtain the appropriate clearance and/or customer screening requirements may result in employment action up to and including termination. Clearance Verification: This position requires successful verification of the stated security clearance to meet federal government customer requirements. You will be asked to provide clearance verification information prior to an offer of employment. 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 position requires verification of U.S citizenship due to citizenship-based legal restrictions. Specifically, this position supports United States federal, state, and/or local United States government agency customers and is subject to certain citizenship-based restrictions where required or permitted by applicable law. To meet this legal requirement, citizenship will be verified via a valid passport, or other approved documents, or verified US government clearance." All that is part of Other Requirements, which is substantive; we should keep. Thus Qualifications section will include Required Qualifications, Other Requirements (Security Clearance, Background Check, Citizenship), and Preferred Qualifications. Now we need to ensure we don't duplicate lines. The posting repeats "Ability to meet Microsoft, customer and/or government security screening requirements are required for this role." twice? Actually appears twice: once in the bullet list and again later. We need to deduplicate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". So we should remove duplicated lines. So we need to detect duplicate sentences and keep only one occurrence. Let's identify duplicates: - "Ability to meet Microsoft, customer and/or government security screening requirements are required for this role." appears twice in the Other Requirements block. We'll keep one. - Also "Candidates must be able to meet Microsoft, customer and/or government security screening requirements are required for this role." appears at start of Other Requirements and also later? Actually first sentence: "Candidates must be able to meet Microsoft, customer and/or government security screening requirements are required for this role." That's a bit garbled. Then later: "Ability to meet Microsoft, customer and/or government security screening requirements are required for this role." So they are similar but not identical. We'll keep both as they are not exact duplicates? Might be considered duplicated meaning but instruction says duplicated lines (exact). We'll keep both. Now we need to format. Let's craft HTML. We'll start with

      Overview

      then

      with the overview text. Then

      Responsibilities

      then
      with each responsibility as
      • . We need to extract each responsibility block. Let's copy the responsibilities text exactly as in posting, but we need to ensure we keep all details. Responsibilities section: "Responsibilities Business Development Identifies opportunities to expand or accelerate the adoption and consumption of cloud and Microsoft technologies. Facilitates, as appropriate, other team members to scale the business with existing customers by articulating value propositions of strategic Microsoft products, including security to facilitate trust in the services, and developing new offerings for the domain. Drives innovation and digital transformation. Ensures the use of the existing intellectual property (IP). Intellectual Property Management Acts as an ambassador in the consumption of intellectual property (IP) by leveraging and/or modifying existing IP or creating repeatable content where applicable. Provides feedback on Managed IP for continuous improvement, reports IP gaps, reviews IP to be considered for harvesting and curation and ensures it is logged for consumption. Improves Industry Solutions offerings quality and collaborates with portfolio and solution teams by providing feedback. Operational Excellence Completes operational tasks and readiness and ensures timeliness and accuracy while maintaining adherence to security standards through Delivery Compliance, Privacy, and Security (DCPS). Follows Microsoft policies, compliance, and procedures (e.g., Enterprise Services Authorization Policy, Standards of Business Conduct, labor logging, expenses, travel guidelines). Leads by example and guides team members on operational tasks, readiness, and compliance. Pre-Sales Support Collaborates with internal stakeholders (e.g., Solution Architect, Pursuit Lead, Consulting Account Executive, Industry Solutions Delivery Engineering & Architecture Group) in the pre-sale process by understanding business and security requirements and providing industry and technical input and/or solution offerings to help shape the deal. Supports drafting proposals and/or statement of work (SOW).Provides input on staffing and skill requirements and ensures SME involvement to define security capacity for delivery to Resource Deployment, Technical Delivery Managers (TDMs), and/or Project Managers. Readiness Learns new technologies or services based on business demands and industry trends and evaluates their impact on security posture, revisiting the Industry Solutions Delivery (ISD)