Technology Consultant - CTJ - TS/SCI
Microsoft · Springfield, VA · 1 mo ago
Hybrid$62k–$119k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading. Use
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, duplicated lines, application instructions, EEO, etc. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading with filler/placeholder text. So we need to extract content.
Let's parse the posting.
Overview: description about Microsoft Federal, mission, etc. That could be "About the role" or maybe "Overview". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings.
We have sections: Overview (maybe About the role), Responsibilities (explicit), Qualifications (explicit), Preferred Qualifications (maybe Skills?), Pay (explicit), Benefits (maybe mention "Certain roles may be eligible for benefits and other compensation." but not specific details; we should not create Benefits section unless posting actually states them. It says "Certain roles may be eligible for benefits and other compensation." That's vague; not specific benefits. So we should not create Benefits section because no specific benefit details. Similarly Schedule: not mentioned. So we omit Benefits and Schedule.
Skills: we could include "Preferred Qualifications" as Skills? The instruction says use Skills heading if there is real specific content. Preferred Qualifications list includes experience, certifications, knowledge, etc. That could be considered Skills. We'll map Preferred Qualifications to Skills heading.
Requirements: The posting has "Required Qualifications" and "Other Requirements". Those are requirements. We'll put under Requirements heading.
Qualifications: There's also "Qualifications" heading? Actually they have "Required Qualifications" and "Preferred Qualifications". The instruction says we can have Qualifications section. Might be redundant with Requirements. But we need to follow instruction: Use headings as given. We have both Requirements and Qualifications. We could treat "Required Qualifications" as Requirements, and "Preferred Qualifications" as Skills. The Qualifications heading could be used for something else like "Education" maybe? But we have education in Required Qualifications. Might be okay to put education under Requirements. The Qualifications heading could be omitted if no distinct content. However we have "Required Qualifications" which is basically qualifications. The instruction says we can have Qualifications section. But we also have Requirements. To avoid duplication, maybe we combine? But we need to follow instruction: include a section ONLY when posting has real specific content for it. If we have both Requirements and Qualifications content, we could include both. However the content overlaps; but we can still include both if they have distinct content. Let's see: Required Qualifications includes Bachelor's degree or equivalent experience, Security Clearance Requirements, Microsoft Cloud Background Check, Citizenship verification. That's more like requirements. Qualifications heading could be used for "Preferred Qualifications"? But they already have that label. The instruction list includes Qualifications as a possible heading separate from Requirements and Skills. So we could map:
- About the role: Overview paragraph(s)
- Responsibilities: Responsibilities section
- Requirements: Required Qualifications (including security clearance, background check, citizenship)
- Qualifications: maybe education? But education is also in Required Qualifications. Could split: Required Qualifications includes education and experience; but we already used that for Requirements. Might be okay to have Requirements cover education+experience+clearance etc. Then Qualifications could be empty -> we should not include. So we omit Qualifications heading.
- Skills: Preferred Qualifications (certifications, knowledge, experience with tools, etc.)
- Pay: Pay range info.
- Benefits: omitted (no specific)
- Schedule: omitted.
Now we need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, equal opportunity, accommodation, application instructions (position will be open for minimum 5 days...), etc. Also remove duplicated lines like "Ability to meet Microsoft, customer and/or government security screening requirements are required for this role." appears twice; we need to keep only once.
Also remove cookie/navigation/legal/EEO etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content.
Overview paragraph(s):
"The Microsoft Federal organization was established to address the unique mission, legal/regulatory requirements, and procurement rules and processes of the United States Government (USG). Microsoft Federal is committed to ensuring its resources – including appropriately qualified, experienced, and certified personnel (with necessary security clearances or otherwise) are available as needed to meet USG evolving needs. To that end, Microsoft embraces, as a mission-critical philosophy, flexibility in the recruiting, hiring, and workforce assignment of Microsoft Federal personnel. Microsoft Federal personnel can expect to serve in various roles in the Microsoft Federal organization during the course of their career to meet evolving USG needs, regardless of segment – Civilian, Defense, or intelligence community. We are seeking a Technical Consultant to join Microsoft Federal and support the delivery of secure, cloud-first solutions for U.S. Government customers. This role is focused on developing the next generation of Azure and DevSecOps Software Development Consultants who can help federal customers modernize legacy environments, accelerate secure cloud adoption, and deliver mission-critical capabilities through automation, platform engineering, and security-first practices. As a Technical Consultant, you will work alongside cloud architects, platform engineers, and security professionals to help customers modernize infrastructure, automate delivery pipelines, and implement secure cloud platforms in Microsoft Azure. This role is ideal for an early-career consultant who is passionate about cloud engineering, automation, platform operations, cybersecurity, software development, and infrastructure as code. You will gain hands-on experience with Azure services, DevSecOps practices, Azure Kubernetes Service (AKS), CI/CD pipelines, infrastructure automation, and secure workload deployment within government environments. At Microsoft, our mission—to empower every person and every organization on the planet to achieve more—guides how we partner with customers to deliver trusted, impactful solutions. With a growth mindset culture, we innovate responsibly and measure success by shared progress—people, teams, and customers. Join us to do meaningful work that changes the world and helps shape what’s next for everyone."
That's a lot; we keep it as prose under About the role.
Responsibilities: The posting has a "Responsibilities" heading with subheadings: Business Development, Intellectual Property Management, Operational Excellence, Readiness, Technical Delivery. Under each there are bullet-like sentences. We need to convert to - for any list of duties/requirements/benefits. So we should produce a list of responsibilities. Could combine all bullet points into a single list, or separate lists per subheading? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
with each duty as - . We'll need to extract each duty sentence.
Let's list them:
Business Development:
- Identifies opportunities to expand or accelerate the adoption and consumption of cloud and Microsoft technologies.
Intellectual Property Management:
- Develops knowledge in intellectual property (IP) and leverages IP to complete assigned project tasks.
- Communicates areas that need refreshing or gaps in intellectual property.
- Contributes to intellectual property development with guidance/supervision.
- Provides feedback for continuous improvement.
Operational Excellence:
- Completes operational tasks and readiness and ensures timeliness and accuracy.
- Follows Microsoft policies, compliance, and procedures (e.g., Enterprise Services Authorization Policy, Standards of Business Conduct, labor logging, expenses, travel guidelines).
Readiness:
- Learns new technologies or services based on business demands and industry trends.
- Obtains relevant accreditations and certification(s) as advised by the domain leadership team.
- Shares experiences, best practices, and product news within the team.
- Participates in relevant technical communities at Microsoft.
Technical Delivery:
- Implements technical solutions by completing assigned project tasks with defined quality standards and following Industry Solutions processes.
- Seeks to understand relationships with customers/partners/stakeholders and contribute to the drivers of satisfaction, dissatisfaction, and the root cause.
- Follows the capacity process outlined by Resource, Insights, Capacity, and Capability (RICC) team.
- Participates in meetings with customers/partners to understand their business needs and/or scenario they are trying to solve.
- Identifies issues and risks and engages with customers/partners or internal stakeholders (e.g., Project Managers) as appropriate to address and resolve issues.
- Support Azure cloud engineering and DevSecOps initiatives for Microsoft Federal customers.
- Implement and maintain cloud infrastructure using Infrastructure as Code (IaC).
- Deploy, configure, and operate Azure services and platforms.
- Develop and maintain CI/CD pipelines with Azure DevOps and Git-based workflows.
- Support containerized workloads and Kubernetes-based platforms.
- Integrate security and compliance controls throughout the software delivery lifecycle.
- Monitor, troubleshoot, and optimize cloud infrastructure and applications.
- Collaborate with customers and stakeholders to define requirements, identify risks, and deliver secure solutions.
- Document technical implementations and operational procedures.
- Embody our culture and values.
We need to keep all these as list items.
Now Requirements: from "Required Qualifications" and "Other Requirements". Let's extract:
Required Qualifications:
- Bachelor's Degree in Computer Science, Engineering, Finance, Business, or related field OR equivalent experience.
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. (duplicate)
- 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 customer 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.
We need to deduplicate duplicate sentence about ability to meet screening requirements appears twice; keep once.
Also note "Other Requirements" includes "Security Clearance Requirements:" and then the sentence about active TS/SCI. We'll combine.
We'll produce list items for each distinct requirement.
Now Skills: from Preferred Qualifications:
- 6+ months of experience in technology, consulting, engineering, or a related business environment.
- Industry certifications in cloud, security, Agile, Scrum, project management, or related disciplines.
- Foundational knowledge of Microsoft Azure services, including compute, networking, identity, storage, monitoring, and security.
- Experience with scripting or programming languages such as PowerShell, Python, C#, Bash, or JavaScript.
- Understanding of source control and Git-based development workflows.
- Exposure to Infrastructure as Code (IaC), CI/CD, and automation practices using tools such as Bicep, ARM Templates, Terraform, Azure DevOps, or GitHub.
- Familiarity with Linux and Windows administration fundamentals.
- Knowledge of container and cloud-native technologies, including Docker, Kubernetes, and Azure Kubernetes Service (AKS).
- Understanding of cloud security, compliance, Zero Trust principles, and secure software delivery practices.
- Experience or exposure to Microsoft Entra ID, Azure Networking, Azure Monitor, Log Analytics, Application Insights, or similar cloud operations technologies.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, duplicated lines, application instructions, EEO, etc. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading with filler/placeholder text. So we need to extract content. Let's parse the posting. Overview: description about Microsoft Federal, mission, etc. That could be "About the role" or maybe "Overview". The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings.
We have sections: Overview (maybe About the role), Responsibilities (explicit), Qualifications (explicit), Preferred Qualifications (maybe Skills?), Pay (explicit), Benefits (maybe mention "Certain roles may be eligible for benefits and other compensation." but not specific details; we should not create Benefits section unless posting actually states them. It says "Certain roles may be eligible for benefits and other compensation." That's vague; not specific benefits. So we should not create Benefits section because no specific benefit details. Similarly Schedule: not mentioned. So we omit Benefits and Schedule.
Skills: we could include "Preferred Qualifications" as Skills? The instruction says use Skills heading if there is real specific content. Preferred Qualifications list includes experience, certifications, knowledge, etc. That could be considered Skills. We'll map Preferred Qualifications to Skills heading.
Requirements: The posting has "Required Qualifications" and "Other Requirements". Those are requirements. We'll put under Requirements heading.
Qualifications: There's also "Qualifications" heading? Actually they have "Required Qualifications" and "Preferred Qualifications". The instruction says we can have Qualifications section. Might be redundant with Requirements. But we need to follow instruction: Use headings as given. We have both Requirements and Qualifications. We could treat "Required Qualifications" as Requirements, and "Preferred Qualifications" as Skills. The Qualifications heading could be used for something else like "Education" maybe? But we have education in Required Qualifications. Might be okay to put education under Requirements. The Qualifications heading could be omitted if no distinct content. However we have "Required Qualifications" which is basically qualifications. The instruction says we can have Qualifications section. But we also have Requirements. To avoid duplication, maybe we combine? But we need to follow instruction: include a section ONLY when posting has real specific content for it. If we have both Requirements and Qualifications content, we could include both. However the content overlaps; but we can still include both if they have distinct content. Let's see: Required Qualifications includes Bachelor's degree or equivalent experience, Security Clearance Requirements, Microsoft Cloud Background Check, Citizenship verification. That's more like requirements. Qualifications heading could be used for "Preferred Qualifications"? But they already have that label. The instruction list includes Qualifications as a possible heading separate from Requirements and Skills. So we could map:
- About the role: Overview paragraph(s)
- Responsibilities: Responsibilities section
- Requirements: Required Qualifications (including security clearance, background check, citizenship)
- Qualifications: maybe education? But education is also in Required Qualifications. Could split: Required Qualifications includes education and experience; but we already used that for Requirements. Might be okay to have Requirements cover education+experience+clearance etc. Then Qualifications could be empty -> we should not include. So we omit Qualifications heading.
- Skills: Preferred Qualifications (certifications, knowledge, experience with tools, etc.)
- Pay: Pay range info.
- Benefits: omitted (no specific)
- Schedule: omitted.
Now we need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: EEO, equal opportunity, accommodation, application instructions (position will be open for minimum 5 days...), etc. Also remove duplicated lines like "Ability to meet Microsoft, customer and/or government security screening requirements are required for this role." appears twice; we need to keep only once.
Also remove cookie/navigation/legal/EEO etc.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract substantive content.
Overview paragraph(s):
"The Microsoft Federal organization was established to address the unique mission, legal/regulatory requirements, and procurement rules and processes of the United States Government (USG). Microsoft Federal is committed to ensuring its resources – including appropriately qualified, experienced, and certified personnel (with necessary security clearances or otherwise) are available as needed to meet USG evolving needs. To that end, Microsoft embraces, as a mission-critical philosophy, flexibility in the recruiting, hiring, and workforce assignment of Microsoft Federal personnel. Microsoft Federal personnel can expect to serve in various roles in the Microsoft Federal organization during the course of their career to meet evolving USG needs, regardless of segment – Civilian, Defense, or intelligence community. We are seeking a Technical Consultant to join Microsoft Federal and support the delivery of secure, cloud-first solutions for U.S. Government customers. This role is focused on developing the next generation of Azure and DevSecOps Software Development Consultants who can help federal customers modernize legacy environments, accelerate secure cloud adoption, and deliver mission-critical capabilities through automation, platform engineering, and security-first practices. As a Technical Consultant, you will work alongside cloud architects, platform engineers, and security professionals to help customers modernize infrastructure, automate delivery pipelines, and implement secure cloud platforms in Microsoft Azure. This role is ideal for an early-career consultant who is passionate about cloud engineering, automation, platform operations, cybersecurity, software development, and infrastructure as code. You will gain hands-on experience with Azure services, DevSecOps practices, Azure Kubernetes Service (AKS), CI/CD pipelines, infrastructure automation, and secure workload deployment within government environments. At Microsoft, our mission—to empower every person and every organization on the planet to achieve more—guides how we partner with customers to deliver trusted, impactful solutions. With a growth mindset culture, we innovate responsibly and measure success by shared progress—people, teams, and customers. Join us to do meaningful work that changes the world and helps shape what’s next for everyone."
That's a lot; we keep it as prose under About the role.
Responsibilities: The posting has a "Responsibilities" heading with subheadings: Business Development, Intellectual Property Management, Operational Excellence, Readiness, Technical Delivery. Under each there are bullet-like sentences. We need to convert to - for any list of duties/requirements/benefits. So we should produce a list of responsibilities. Could combine all bullet points into a single list, or separate lists per subheading? The instruction: Use
- for any list of duties/requirements/benefits. So we can create a
with each duty as - . We'll need to extract each duty sentence.
Let's list them:
Business Development:
- Identifies opportunities to expand or accelerate the adoption and consumption of cloud and Microsoft technologies.
Intellectual Property Management:
- Develops knowledge in intellectual property (IP) and leverages IP to complete assigned project tasks.
- Communicates areas that need refreshing or gaps in intellectual property.
- Contributes to intellectual property development with guidance/supervision.
- Provides feedback for continuous improvement.
Operational Excellence:
- Completes operational tasks and readiness and ensures timeliness and accuracy.
- Follows Microsoft policies, compliance, and procedures (e.g., Enterprise Services Authorization Policy, Standards of Business Conduct, labor logging, expenses, travel guidelines).
Readiness:
- Learns new technologies or services based on business demands and industry trends.
- Obtains relevant accreditations and certification(s) as advised by the domain leadership team.
- Shares experiences, best practices, and product news within the team.
- Participates in relevant technical communities at Microsoft.
Technical Delivery:
- Implements technical solutions by completing assigned project tasks with defined quality standards and following Industry Solutions processes.
- Seeks to understand relationships with customers/partners/stakeholders and contribute to the drivers of satisfaction, dissatisfaction, and the root cause.
- Follows the capacity process outlined by Resource, Insights, Capacity, and Capability (RICC) team.
- Participates in meetings with customers/partners to understand their business needs and/or scenario they are trying to solve.
- Identifies issues and risks and engages with customers/partners or internal stakeholders (e.g., Project Managers) as appropriate to address and resolve issues.
- Support Azure cloud engineering and DevSecOps initiatives for Microsoft Federal customers.
- Implement and maintain cloud infrastructure using Infrastructure as Code (IaC).
- Deploy, configure, and operate Azure services and platforms.
- Develop and maintain CI/CD pipelines with Azure DevOps and Git-based workflows.
- Support containerized workloads and Kubernetes-based platforms.
- Integrate security and compliance controls throughout the software delivery lifecycle.
- Monitor, troubleshoot, and optimize cloud infrastructure and applications.
- Collaborate with customers and stakeholders to define requirements, identify risks, and deliver secure solutions.
- Document technical implementations and operational procedures.
- Embody our culture and values.
We need to keep all these as list items.
Now Requirements: from "Required Qualifications" and "Other Requirements". Let's extract:
Required Qualifications:
- Bachelor's Degree in Computer Science, Engineering, Finance, Business, or related field OR equivalent experience.
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. (duplicate)
- 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 customer 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.
We need to deduplicate duplicate sentence about ability to meet screening requirements appears twice; keep once.
Also note "Other Requirements" includes "Security Clearance Requirements:" and then the sentence about active TS/SCI. We'll combine.
We'll produce list items for each distinct requirement.
Now Skills: from Preferred Qualifications:
- 6+ months of experience in technology, consulting, engineering, or a related business environment.
- Industry certifications in cloud, security, Agile, Scrum, project management, or related disciplines.
- Foundational knowledge of Microsoft Azure services, including compute, networking, identity, storage, monitoring, and security.
- Experience with scripting or programming languages such as PowerShell, Python, C#, Bash, or JavaScript.
- Understanding of source control and Git-based development workflows.
- Exposure to Infrastructure as Code (IaC), CI/CD, and automation practices using tools such as Bicep, ARM Templates, Terraform, Azure DevOps, or GitHub.
- Familiarity with Linux and Windows administration fundamentals.
- Knowledge of container and cloud-native technologies, including Docker, Kubernetes, and Azure Kubernetes Service (AKS).
- Understanding of cloud security, compliance, Zero Trust principles, and secure software delivery practices.
- Experience or exposure to Microsoft Entra ID, Azure Networking, Azure Monitor, Log Analytics, Application Insights, or similar cloud operations technologies.
- for any list of duties/requirements/benefits. So we can create a
- with each duty as
- . We'll need to extract each duty sentence. Let's list them: Business Development: - Identifies opportunities to expand or accelerate the adoption and consumption of cloud and Microsoft technologies. Intellectual Property Management: - Develops knowledge in intellectual property (IP) and leverages IP to complete assigned project tasks. - Communicates areas that need refreshing or gaps in intellectual property. - Contributes to intellectual property development with guidance/supervision. - Provides feedback for continuous improvement. Operational Excellence: - Completes operational tasks and readiness and ensures timeliness and accuracy. - Follows Microsoft policies, compliance, and procedures (e.g., Enterprise Services Authorization Policy, Standards of Business Conduct, labor logging, expenses, travel guidelines). Readiness: - Learns new technologies or services based on business demands and industry trends. - Obtains relevant accreditations and certification(s) as advised by the domain leadership team. - Shares experiences, best practices, and product news within the team. - Participates in relevant technical communities at Microsoft. Technical Delivery: - Implements technical solutions by completing assigned project tasks with defined quality standards and following Industry Solutions processes. - Seeks to understand relationships with customers/partners/stakeholders and contribute to the drivers of satisfaction, dissatisfaction, and the root cause. - Follows the capacity process outlined by Resource, Insights, Capacity, and Capability (RICC) team. - Participates in meetings with customers/partners to understand their business needs and/or scenario they are trying to solve. - Identifies issues and risks and engages with customers/partners or internal stakeholders (e.g., Project Managers) as appropriate to address and resolve issues. - Support Azure cloud engineering and DevSecOps initiatives for Microsoft Federal customers. - Implement and maintain cloud infrastructure using Infrastructure as Code (IaC). - Deploy, configure, and operate Azure services and platforms. - Develop and maintain CI/CD pipelines with Azure DevOps and Git-based workflows. - Support containerized workloads and Kubernetes-based platforms. - Integrate security and compliance controls throughout the software delivery lifecycle. - Monitor, troubleshoot, and optimize cloud infrastructure and applications. - Collaborate with customers and stakeholders to define requirements, identify risks, and deliver secure solutions. - Document technical implementations and operational procedures. - Embody our culture and values. We need to keep all these as list items. Now Requirements: from "Required Qualifications" and "Other Requirements". Let's extract: Required Qualifications: - Bachelor's Degree in Computer Science, Engineering, Finance, Business, or related field OR equivalent experience. 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. (duplicate) - 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 customer 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. We need to deduplicate duplicate sentence about ability to meet screening requirements appears twice; keep once. Also note "Other Requirements" includes "Security Clearance Requirements:" and then the sentence about active TS/SCI. We'll combine. We'll produce list items for each distinct requirement. Now Skills: from Preferred Qualifications: - 6+ months of experience in technology, consulting, engineering, or a related business environment. - Industry certifications in cloud, security, Agile, Scrum, project management, or related disciplines. - Foundational knowledge of Microsoft Azure services, including compute, networking, identity, storage, monitoring, and security. - Experience with scripting or programming languages such as PowerShell, Python, C#, Bash, or JavaScript. - Understanding of source control and Git-based development workflows. - Exposure to Infrastructure as Code (IaC), CI/CD, and automation practices using tools such as Bicep, ARM Templates, Terraform, Azure DevOps, or GitHub. - Familiarity with Linux and Windows administration fundamentals. - Knowledge of container and cloud-native technologies, including Docker, Kubernetes, and Azure Kubernetes Service (AKS). - Understanding of cloud security, compliance, Zero Trust principles, and secure software delivery practices. - Experience or exposure to Microsoft Entra ID, Azure Networking, Azure Monitor, Log Analytics, Application Insights, or similar cloud operations technologies.