Microsoft Active Directory & Entra ID Engineer III
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include. The posting includes: Who We Are (company overview), Description (role overview), Key Responsibilities (list), Required Essential Skills & Experience (list), Desirable Experience (list), Preferred Certifications (list), Personal Attributes (list), What We Offer (benefits list). Also there is mention of "Benefits listed above may vary depending on the nature of your employment with Avnet." That's a note but we can include within What We Offer.
We should not include sections like Pay or Schedule because not specified. Also we should not include "About the role" heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can choose headings that match content. For "Who We Are" maybe we can use About Avnet
or Who We Are
. The examples include "About the role". But we can use any appropriate heading. Probably better to use headings that reflect sections: "About Avnet", "Role Overview", "Key Responsibilities", "Required Skills & Experience", "Desirable Experience", "Preferred Certifications", "Personal Attributes", "Benefits". However we need to avoid filler. All these sections have substantive content.
We need to use - for any list of duties/requirements/benefits. For prose we use
. So for each section we can have a heading
then either
or
.
We must not repeat job title as heading. Not needed.
We need to remove boilerplate: EEO, legal, accommodation contact, etc. Also remove duplicated lines. Also remove "Applicants for this position must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time" - that's maybe minor metadata but could be folded into a short or dropped. It's substantive? It's a requirement about work authorization. Could be considered part of Requirements. But we already have Required Essential Skills & Experience; we could include that as a bullet under Required? However the instruction says "fold minor metadata into a short
or drop it." This is about work authorization and visa sponsorship. Might be considered minor metadata. We could include a short
after the role overview. But we need to preserve ALL substantive information; is this substantive? It's a requirement for applicants. Might be considered substantive. However the instruction says "fold minor metadata into a short
or drop it." So we could put it in a
under a section like "Eligibility". But we don't have a heading for eligibility. Could add a short paragraph after the role overview.
But we also have "This position will have access to ITAR product and therefore be authorized to access product. This position requires the employee to be a U.S. Citizen or National, or a lawful permanent resident as defined by 8 U.S.C. 1101(a)(20), or a protected individual as defined by 8 U.S.C. 1324b(a)(3)." That's also eligibility/citizenship requirement. That's substantive. We could include that as a short
under a section like "Eligibility Requirements". However we already have Required Essential Skills & Experience; we could add bullets for citizenship requirement? But that's not a skill. Might be better to have a separate short paragraph after the responsibilities or before benefits.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine eligibility into the Required Skills & Experience section as a note, but that might be mixing. However we can add a
after the Required Skills & Experience heading but before the list? Actually we need to use
- for any list. So we could have a
for prose (like eligibility note) and then a
for skills.
Thus structure:
About Avnet
... (Who We Are)
Role Overview
... (Description)
Key Responsibilities
... each responsibility as -
Required Skills & Experience
Applicants must be authorized to work for any employer in the U.S.; visa sponsorship is not available. This position requires U.S. Citizenship, National status, lawful permanent residency, or protected individual status due to ITAR access.
... each required skill as -
Desirable Experience
... each desirable as -
Preferred Certifications
... each cert as -
Personal Attributes
... each attribute as -
Benefits
... each benefit as -
Benefits listed above may vary depending on the nature of your employment with Avnet.
We must not include Pay or Schedule sections.
We need to ensure we preserve all substantive information from the original. Let's extract the content.
Who We Are paragraph:
"Who We Are At Avnet, relationships matter. We are a global, FORTUNE ® 500 technology distributor and solutions company that delivers design, supply chain and logistics expertise to customers at every stage of a product’s lifecycle. Our employees have a front row seat to the latest innovations shaping the world we live in and the future we share. We’re driven to help our customers around the world succeed and we do so by earning the trust of some of the biggest names in technology. Working at Avnet means being a part of a global team. We work collaboratively and with integrity, doing business the right way. For more than a century, we have partnered together to help our customers, suppliers and teammates realize the transformative possibilities of technology. Experience what’s next at Avnet!"
We can keep that as a paragraph.
Description:
"We are seeking an experienced Microsoft Identity & Access Management professional with a minimum of 5 years' hands-on experience managing, supporting, and enhancing Microsoft Active Directory and Microsoft EntraID environments. The successful candidate will possess a strong understanding of hybrid identity architectures, including how on-premises Active Directory integrates and synchronizes with Microsoft EntraID. They will have proven experience implementing secure authentication solutions, Conditional Access policies, SAML-based application integrations, and modern identity management best practices. This role is critical in ensuring the security, reliability, and efficiency of our identity infrastructure and access management services."
We can keep that as a paragraph.
Key Responsibilities: list items:
- Active Directory Administration
- Manage and support Microsoft Active Directory environments.
- Administer users, groups, organizational units, and Group Policy Objects (GPOs).
- Troubleshoot authentication, replication, DNS, and Active Directory-related issues.
- Implement and maintain Active Directory security best practices.
- Support AD upgrades, migrations, and disaster recovery processes.
- Active Directory Sites and Services.
- Microsoft EntraID Administration
- Administer Microsoft EntraID (formerly Azure Active Directory).
- Configure and manage users, groups, enterprise applications, and identities.
- Support identity lifecycle management processes.
- Configure and monitor authentication methods and identity protection capabilities.
- Implement and maintain EntraID security controls.
- Hybrid Identity Management
- Manage and troubleshoot Active Directory synchronization with EntraID.
- Support Azure AD Connect / Entra Connect environments.
- Understand authentication mechanisms including: Password Hash Synchronization (PHS), Pass-through Authentication (PTA), Federation, Single Sign-On (SSO).
- Conditional Access & Authentication
- Design and implement Conditional Access policies.
- Configure Multi-Factor Authentication (MFA).
- Manage authentication methods and authentication strengths.
- Support passwordless authentication technologies including: Microsoft Authenticator, FIDO2 Security Keys, Windows Hello for Business.
- Application Integration
- Configure and support SAML-based application integrations.
- Manage Single Sign-On (SSO) solutions.
- Troubleshoot identity federation and authentication issues.
- Work with application owners and vendors to onboard enterprise applications.
- Security & Compliance
- Review identity security posture and recommend improvements.
- Monitor and investigate authentication and access-related incidents.
- Support audit and compliance requirements.
- Implement least-privilege access principles and role-based access controls (RBAC).
We need to flatten into a single list? The instruction: Use - for any list of duties/requirements/benefits. Could have nested lists? Probably okay but simpler to have flat list items each as a duty. Could keep sub-bullets but still
- . We'll just make each bullet a
- . Might be long but okay.
Required Essential Skills & Experience list:
- Minimum 5 years' experience administering Microsoft Active Directory.
- Minimum 5 years' experience working with Microsoft Entra ID (Azure AD).
- Strong understanding of hybrid identity architecture.
- Proven experience with Azure AD Connect / Entra Connect / Entra Connect. (Actually "Azure AD Connect / Entra Connect")
- Strong understanding of how Active Directory and Entra ID communicate and synchronise.
- Experience implementing and managing Conditional Access policies.
- Knowledge of authentication methods and identity protection controls.
- Experience implementing and supporting Multi-Factor Authentication.
- Strong understanding of Single Sign-On technologies.
- Hands-on experience integrating and troubleshooting SAML applications.
- Experience with DNS, LDAP, Kerberos, and Group Policy.
- Strong troubleshooting and problem-solving skills.
We also have the eligibility note we will add as a
before the list.
Desirable Experience list:
- Experience with Microsoft Intune.
- Experience with Privileged Identity Management (PIM).
- Experience with Identity Governance.
- PowerShell scripting and automation experience.
- Experience with Microsoft Defender products.
- Knowledge of OAuth 2.0 and OpenID Connect.
- Experience in regulated or enterprise environments.
Preferred Certifications list:
- Microsoft Certified: Identity and Access Administrator Associate (SC-300)
- Microsoft Certified: Azure Administrator Associate (AZ-104)
- Microsoft Certified: Security Operations Analyst Associate (SC-200)
- Microsoft Certified: Security, Compliance, and Identity Fundamentals (SC-900)
- Microsoft Certified: Azure Fundamentals (AZ-900)
Personal Attributes list:
- Strong communication skills.
- Ability to explain technical concepts to non-technical stakeholders.
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: Who We Are (company overview), Description (role overview), Key Responsibilities (list), Required Essential Skills & Experience (list), Desirable Experience (list), Preferred Certifications (list), Personal Attributes (list), What We Offer (benefits list). Also there is mention of "Benefits listed above may vary depending on the nature of your employment with Avnet." That's a note but we can include within What We Offer. We should not include sections like Pay or Schedule because not specified. Also we should not include "About the role" heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can choose headings that match content. For "Who We Are" maybe we can use About Avnet
or Who We Are
. The examples include "About the role". But we can use any appropriate heading. Probably better to use headings that reflect sections: "About Avnet", "Role Overview", "Key Responsibilities", "Required Skills & Experience", "Desirable Experience", "Preferred Certifications", "Personal Attributes", "Benefits". However we need to avoid filler. All these sections have substantive content.
We need to use - for any list of duties/requirements/benefits. For prose we use
. So for each section we can have a heading
then either
or
.
We must not repeat job title as heading. Not needed.
We need to remove boilerplate: EEO, legal, accommodation contact, etc. Also remove duplicated lines. Also remove "Applicants for this position must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time" - that's maybe minor metadata but could be folded into a short or dropped. It's substantive? It's a requirement about work authorization. Could be considered part of Requirements. But we already have Required Essential Skills & Experience; we could include that as a bullet under Required? However the instruction says "fold minor metadata into a short
or drop it." This is about work authorization and visa sponsorship. Might be considered minor metadata. We could include a short
after the role overview. But we need to preserve ALL substantive information; is this substantive? It's a requirement for applicants. Might be considered substantive. However the instruction says "fold minor metadata into a short
or drop it." So we could put it in a
under a section like "Eligibility". But we don't have a heading for eligibility. Could add a short paragraph after the role overview.
But we also have "This position will have access to ITAR product and therefore be authorized to access product. This position requires the employee to be a U.S. Citizen or National, or a lawful permanent resident as defined by 8 U.S.C. 1101(a)(20), or a protected individual as defined by 8 U.S.C. 1324b(a)(3)." That's also eligibility/citizenship requirement. That's substantive. We could include that as a short
under a section like "Eligibility Requirements". However we already have Required Essential Skills & Experience; we could add bullets for citizenship requirement? But that's not a skill. Might be better to have a separate short paragraph after the responsibilities or before benefits.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine eligibility into the Required Skills & Experience section as a note, but that might be mixing. However we can add a
after the Required Skills & Experience heading but before the list? Actually we need to use
- for any list. So we could have a
for prose (like eligibility note) and then a
for skills.
Thus structure:
About Avnet
... (Who We Are)
Role Overview
... (Description)
Key Responsibilities
... each responsibility as -
Required Skills & Experience
Applicants must be authorized to work for any employer in the U.S.; visa sponsorship is not available. This position requires U.S. Citizenship, National status, lawful permanent residency, or protected individual status due to ITAR access.
... each required skill as -
Desirable Experience
... each desirable as -
Preferred Certifications
... each cert as -
Personal Attributes
... each attribute as -
Benefits
... each benefit as -
Benefits listed above may vary depending on the nature of your employment with Avnet.
We must not include Pay or Schedule sections.
We need to ensure we preserve all substantive information from the original. Let's extract the content.
Who We Are paragraph:
"Who We Are At Avnet, relationships matter. We are a global, FORTUNE ® 500 technology distributor and solutions company that delivers design, supply chain and logistics expertise to customers at every stage of a product’s lifecycle. Our employees have a front row seat to the latest innovations shaping the world we live in and the future we share. We’re driven to help our customers around the world succeed and we do so by earning the trust of some of the biggest names in technology. Working at Avnet means being a part of a global team. We work collaboratively and with integrity, doing business the right way. For more than a century, we have partnered together to help our customers, suppliers and teammates realize the transformative possibilities of technology. Experience what’s next at Avnet!"
We can keep that as a paragraph.
Description:
"We are seeking an experienced Microsoft Identity & Access Management professional with a minimum of 5 years' hands-on experience managing, supporting, and enhancing Microsoft Active Directory and Microsoft EntraID environments. The successful candidate will possess a strong understanding of hybrid identity architectures, including how on-premises Active Directory integrates and synchronizes with Microsoft EntraID. They will have proven experience implementing secure authentication solutions, Conditional Access policies, SAML-based application integrations, and modern identity management best practices. This role is critical in ensuring the security, reliability, and efficiency of our identity infrastructure and access management services."
We can keep that as a paragraph.
Key Responsibilities: list items:
- Active Directory Administration
- Manage and support Microsoft Active Directory environments.
- Administer users, groups, organizational units, and Group Policy Objects (GPOs).
- Troubleshoot authentication, replication, DNS, and Active Directory-related issues.
- Implement and maintain Active Directory security best practices.
- Support AD upgrades, migrations, and disaster recovery processes.
- Active Directory Sites and Services.
- Microsoft EntraID Administration
- Administer Microsoft EntraID (formerly Azure Active Directory).
- Configure and manage users, groups, enterprise applications, and identities.
- Support identity lifecycle management processes.
- Configure and monitor authentication methods and identity protection capabilities.
- Implement and maintain EntraID security controls.
- Hybrid Identity Management
- Manage and troubleshoot Active Directory synchronization with EntraID.
- Support Azure AD Connect / Entra Connect environments.
- Understand authentication mechanisms including: Password Hash Synchronization (PHS), Pass-through Authentication (PTA), Federation, Single Sign-On (SSO).
- Conditional Access & Authentication
- Design and implement Conditional Access policies.
- Configure Multi-Factor Authentication (MFA).
- Manage authentication methods and authentication strengths.
- Support passwordless authentication technologies including: Microsoft Authenticator, FIDO2 Security Keys, Windows Hello for Business.
- Application Integration
- Configure and support SAML-based application integrations.
- Manage Single Sign-On (SSO) solutions.
- Troubleshoot identity federation and authentication issues.
- Work with application owners and vendors to onboard enterprise applications.
- Security & Compliance
- Review identity security posture and recommend improvements.
- Monitor and investigate authentication and access-related incidents.
- Support audit and compliance requirements.
- Implement least-privilege access principles and role-based access controls (RBAC).
We need to flatten into a single list? The instruction: Use - for any list of duties/requirements/benefits. Could have nested lists? Probably okay but simpler to have flat list items each as a duty. Could keep sub-bullets but still
- . We'll just make each bullet a
- . Might be long but okay.
Required Essential Skills & Experience list:
- Minimum 5 years' experience administering Microsoft Active Directory.
- Minimum 5 years' experience working with Microsoft Entra ID (Azure AD).
- Strong understanding of hybrid identity architecture.
- Proven experience with Azure AD Connect / Entra Connect / Entra Connect. (Actually "Azure AD Connect / Entra Connect")
- Strong understanding of how Active Directory and Entra ID communicate and synchronise.
- Experience implementing and managing Conditional Access policies.
- Knowledge of authentication methods and identity protection controls.
- Experience implementing and supporting Multi-Factor Authentication.
- Strong understanding of Single Sign-On technologies.
- Hands-on experience integrating and troubleshooting SAML applications.
- Experience with DNS, LDAP, Kerberos, and Group Policy.
- Strong troubleshooting and problem-solving skills.
We also have the eligibility note we will add as a
before the list.
Desirable Experience list:
- Experience with Microsoft Intune.
- Experience with Privileged Identity Management (PIM).
- Experience with Identity Governance.
- PowerShell scripting and automation experience.
- Experience with Microsoft Defender products.
- Knowledge of OAuth 2.0 and OpenID Connect.
- Experience in regulated or enterprise environments.
Preferred Certifications list:
- Microsoft Certified: Identity and Access Administrator Associate (SC-300)
- Microsoft Certified: Azure Administrator Associate (AZ-104)
- Microsoft Certified: Security Operations Analyst Associate (SC-200)
- Microsoft Certified: Security, Compliance, and Identity Fundamentals (SC-900)
- Microsoft Certified: Azure Fundamentals (AZ-900)
Personal Attributes list:
- Strong communication skills.
- Ability to explain technical concepts to non-technical stakeholders.
. So for each section we can have a heading
then either
or
- .
We must not repeat job title as heading. Not needed.
We need to remove boilerplate: EEO, legal, accommodation contact, etc. Also remove duplicated lines. Also remove "Applicants for this position must be authorized to work for any employer in the U.S. We are unable to sponsor or take over sponsorship of an employment visa at this time" - that's maybe minor metadata but could be folded into a short
- for any list. So we could have a
for prose (like eligibility note) and then a
- for skills.
Thus structure:
- for any list of duties/requirements/benefits. Could have nested lists? Probably okay but simpler to have flat list items each as a duty. Could keep sub-bullets but still
- . We'll just make each bullet a
- . Might be long but okay.
Required Essential Skills & Experience list:
- Minimum 5 years' experience administering Microsoft Active Directory.
- Minimum 5 years' experience working with Microsoft Entra ID (Azure AD).
- Strong understanding of hybrid identity architecture.
- Proven experience with Azure AD Connect / Entra Connect / Entra Connect. (Actually "Azure AD Connect / Entra Connect")
- Strong understanding of how Active Directory and Entra ID communicate and synchronise.
- Experience implementing and managing Conditional Access policies.
- Knowledge of authentication methods and identity protection controls.
- Experience implementing and supporting Multi-Factor Authentication.
- Strong understanding of Single Sign-On technologies.
- Hands-on experience integrating and troubleshooting SAML applications.
- Experience with DNS, LDAP, Kerberos, and Group Policy.
- Strong troubleshooting and problem-solving skills.
We also have the eligibility note we will add as a
before the list. Desirable Experience list: - Experience with Microsoft Intune. - Experience with Privileged Identity Management (PIM). - Experience with Identity Governance. - PowerShell scripting and automation experience. - Experience with Microsoft Defender products. - Knowledge of OAuth 2.0 and OpenID Connect. - Experience in regulated or enterprise environments. Preferred Certifications list: - Microsoft Certified: Identity and Access Administrator Associate (SC-300) - Microsoft Certified: Azure Administrator Associate (AZ-104) - Microsoft Certified: Security Operations Analyst Associate (SC-200) - Microsoft Certified: Security, Compliance, and Identity Fundamentals (SC-900) - Microsoft Certified: Azure Fundamentals (AZ-900) Personal Attributes list: - Strong communication skills. - Ability to explain technical concepts to non-technical stakeholders.
About Avnet
... (Who We Are)
Role Overview
... (Description)
Key Responsibilities
- ... each responsibility as
Required Skills & Experience
Applicants must be authorized to work for any employer in the U.S.; visa sponsorship is not available. This position requires U.S. Citizenship, National status, lawful permanent residency, or protected individual status due to ITAR access.
- ... each required skill as
Desirable Experience
- ... each desirable as
Preferred Certifications
- ... each cert as
Personal Attributes
- ... each attribute as
Benefits
- ... each benefit as
Benefits listed above may vary depending on the nature of your employment with Avnet.
We must not include Pay or Schedule sections. We need to ensure we preserve all substantive information from the original. Let's extract the content. Who We Are paragraph: "Who We Are At Avnet, relationships matter. We are a global, FORTUNE ® 500 technology distributor and solutions company that delivers design, supply chain and logistics expertise to customers at every stage of a product’s lifecycle. Our employees have a front row seat to the latest innovations shaping the world we live in and the future we share. We’re driven to help our customers around the world succeed and we do so by earning the trust of some of the biggest names in technology. Working at Avnet means being a part of a global team. We work collaboratively and with integrity, doing business the right way. For more than a century, we have partnered together to help our customers, suppliers and teammates realize the transformative possibilities of technology. Experience what’s next at Avnet!" We can keep that as a paragraph. Description: "We are seeking an experienced Microsoft Identity & Access Management professional with a minimum of 5 years' hands-on experience managing, supporting, and enhancing Microsoft Active Directory and Microsoft EntraID environments. The successful candidate will possess a strong understanding of hybrid identity architectures, including how on-premises Active Directory integrates and synchronizes with Microsoft EntraID. They will have proven experience implementing secure authentication solutions, Conditional Access policies, SAML-based application integrations, and modern identity management best practices. This role is critical in ensuring the security, reliability, and efficiency of our identity infrastructure and access management services." We can keep that as a paragraph. Key Responsibilities: list items: - Active Directory Administration - Manage and support Microsoft Active Directory environments. - Administer users, groups, organizational units, and Group Policy Objects (GPOs). - Troubleshoot authentication, replication, DNS, and Active Directory-related issues. - Implement and maintain Active Directory security best practices. - Support AD upgrades, migrations, and disaster recovery processes. - Active Directory Sites and Services. - Microsoft EntraID Administration - Administer Microsoft EntraID (formerly Azure Active Directory). - Configure and manage users, groups, enterprise applications, and identities. - Support identity lifecycle management processes. - Configure and monitor authentication methods and identity protection capabilities. - Implement and maintain EntraID security controls. - Hybrid Identity Management - Manage and troubleshoot Active Directory synchronization with EntraID. - Support Azure AD Connect / Entra Connect environments. - Understand authentication mechanisms including: Password Hash Synchronization (PHS), Pass-through Authentication (PTA), Federation, Single Sign-On (SSO). - Conditional Access & Authentication - Design and implement Conditional Access policies. - Configure Multi-Factor Authentication (MFA). - Manage authentication methods and authentication strengths. - Support passwordless authentication technologies including: Microsoft Authenticator, FIDO2 Security Keys, Windows Hello for Business. - Application Integration - Configure and support SAML-based application integrations. - Manage Single Sign-On (SSO) solutions. - Troubleshoot identity federation and authentication issues. - Work with application owners and vendors to onboard enterprise applications. - Security & Compliance - Review identity security posture and recommend improvements. - Monitor and investigate authentication and access-related incidents. - Support audit and compliance requirements. - Implement least-privilege access principles and role-based access controls (RBAC). We need to flatten into a single list? The instruction: Use
or dropped. It's substantive? It's a requirement about work authorization. Could be considered part of Requirements. But we already have Required Essential Skills & Experience; we could include that as a bullet under Required? However the instruction says "fold minor metadata into a short
or drop it." This is about work authorization and visa sponsorship. Might be considered minor metadata. We could include a short
after the role overview. But we need to preserve ALL substantive information; is this substantive? It's a requirement for applicants. Might be considered substantive. However the instruction says "fold minor metadata into a short
or drop it." So we could put it in a
under a section like "Eligibility". But we don't have a heading for eligibility. Could add a short paragraph after the role overview. But we also have "This position will have access to ITAR product and therefore be authorized to access product. This position requires the employee to be a U.S. Citizen or National, or a lawful permanent resident as defined by 8 U.S.C. 1101(a)(20), or a protected individual as defined by 8 U.S.C. 1324b(a)(3)." That's also eligibility/citizenship requirement. That's substantive. We could include that as a short
under a section like "Eligibility Requirements". However we already have Required Essential Skills & Experience; we could add bullets for citizenship requirement? But that's not a skill. Might be better to have a separate short paragraph after the responsibilities or before benefits. Given the instruction to prefer a few substantive sections over many thin ones, we could combine eligibility into the Required Skills & Experience section as a note, but that might be mixing. However we can add a
after the Required Skills & Experience heading but before the list? Actually we need to use