PKI Venafi Architect (1152663)
for section headings. 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, navigation, legal, EEO, etc. Also remove application instructions. Keep all substantive info.
We need to parse the posting.
Given content:
Location: Chicago, IL, USA Salary: $160,000.00 USD Annually - $165,000.00 USD Annually Description PKI Venafi Architect Location: Remote (U.S.) Salary: $160,000 - $165,000 Base Salary Employment Type: Full-Time About The Opportunity We are seeking an experienced PKI Venafi Architect to lead enterprise-wide Public Key Infrastructure (PKI), certificate lifecycle management, and machine identity security initiatives. This role will be responsible for architecting, deploying, and optimizing secure PKI environments while driving automation and governance across enterprise applications, cloud platforms, and security ecosystems. The ideal candidate will possess deep expertise in Venafi Trust Protection Platform (TPP), PKI architecture, certificate lifecycle management, cryptographic controls, and cloud security solutions. Key ResponsibilitiesPKI & Security Architecture Design, implement, and maintain enterprise PKI architecture, including:Root Certificate Authorities (CA)Issuing CAsCertificate Revocation Lists (CRL)Online Certificate Status Protocol (OCSP)Hardware Security Modules (HSM)Trust frameworksDevelop certificate governance standards, policies, and cryptographic control frameworks.Architect scalable, highly available PKI and Certificate Lifecycle Management (CLM) solutions.Drive enterprise machine identity and certificate management strategy.Venafi Platform Architecture Design, administer, and optimize Venafi Trust Protection Platform (TPP).Define onboarding standards, workflows, discovery jobs, reporting, policy management, and access controls.Architect integrations between Venafi and enterprise applications, cloud platforms, and security tools.Lead platform upgrades, enhancements, and performance optimization initiatives. Certificate Lifecycle Automation Architect and implement automated certificate provisioning, renewal, and deployment solutions.Build automation frameworks utilizing:Venafi APIsvCertPowerShellPythonAnsibleGitHub ActionsAzure DevOpsCI/CD PipelinesDrive enterprise adoption of certificate lifecycle automation.Application & Cloud Integration Lead onboarding of enterprise applications into CLM services.Support certificate deployment and automation across:Windows ServerLinux/UnixIISApacheTomcatWebLogicKubernetesAzureAWSF5 Load BalancersKafkaSolacePingFederateProvide architectural guidance and troubleshooting support for complex certificate and trust-related issues.Governance & Compliance Ensure compliance with:NISTPCI-DSSSOXISO 27001FedRAMPInternal security standardsConduct cryptographic risk assessments and certificate posture reviews.Define certificate ownership and governance processes.Support audit and regulatory compliance initiatives. Required Qualifications Bachelor's degree in Computer Science, Cybersecurity, Engineering, or related field.10+ years of Information Security experience.5+ years of hands-on PKI architecture experience.5+ years working with Venafi Trust Protection Platform.Expertise in:PKIX.509 CertificatesTLS/SSLCertificate Lifecycle Management (CLM)CRL/OCSPHardware Security Modules (HSM)Digital SignaturesCryptographic Key ManagementExperience designing PKI solutions within Azure and AWS environments.Strong scripting and automation skills using PowerShell and Python. Preferred Qualifications CISSP, CISM, CCSP, or similar cybersecurity certification.Venafi Certified Professional or Venafi Certified Architect certification.Experience with:KeyfactorDigiCertEntrustMicrosoft ADCSHashiCorp VaultAzure Key VaultAWS Certificate ManagerPrevious experience within banking, financial services, insurance (BFSI), or other highly regulated industries.Technical SkillsPKI & Cryptography PKI ArchitectureX.509 CertificatesTLS/SSLPKCS StandardsDigital SignaturesHSM IntegrationCRL / OCSP Venafi Venafi Trust Protection Platform (TPP)Venafi TLS ProtectCertificate DiscoveryPolicy ManagementWorkflow AutomationReporting & Governance Cloud & DevOps Microsoft AzureAWSKubernetesGitHub ActionsAzure DevOpsCI/CD PipelinesInfrastructure as Code (IaC) Programming & Automation PowerShellPythonREST APIsAnsible Leadership Expectations Serve as the organization's PKI and Machine Identity subject matter expert.Provide technical leadership and guidance to engineering and operations teams.Develop enterprise PKI roadmaps and modernization strategies.Mentor junior engineers and establish certificate lifecycle management best practices.Drive Zero Trust and identity-centric security initiatives. Apply today to join a team focused on securing enterprise identities, automating certificate management, and modernizing PKI infrastructure. Client offers a comprehensive benefits package that may include medical, dental, and vision coverage, 401(k) with company match, life and disability insurance, paid time off, paid holidays, wellness programs, and opportunities for professional growth and development. Benefits eligibility may vary based on employment status and location. By providing your phone number, you consent to: (1) receive automated text messages and calls from the Judge Group, Inc. and its affiliates (collectively "Judge") to such phone number regarding job opportunities, your job application, and for other related purposes. Message & data rates apply and message frequency may vary. Consistent with Judge's Privacy Policy, information obtained from your consent will not be shared with third parties for marketing/promotional purposes. Reply STOP to opt out of receiving telephone calls and text messages from Judge and HELP for help. Contact: jprovenzano@judge.com This job and many more are available through The Judge Group. Find us on the web at www.judge.com
We need to extract sections: About the role (the "About The Opportunity" paragraph). Responsibilities (the "Key Responsibilities" section). Requirements (maybe "Required Qualifications"). Qualifications (maybe "Preferred Qualifications"? Actually they have both Required and Preferred. Could treat Required as Requirements, Preferred as Qualifications? Or we could combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly.
We have:
- About the role: The paragraph after "About The Opportunity". We'll put that in
About the role
then ...
.
- Responsibilities: The "Key Responsibilities" section includes multiple sub-sections: PKI & Security Architecture, Venafi Platform Architecture, Certificate Lifecycle Automation, Application & Cloud Integration, Governance & Compliance. We'll list each bullet as - maybe with sub-bullets? But we can just list each responsibility as separate
- . We'll need to preserve all details. Could break into multiple
- items.
- Requirements: The "Required Qualifications" bullet list: Bachelor's degree..., 10+ years..., 5+ years..., 5+ years..., Expertise in: (list), Experience designing PKI solutions within Azure and AWS environments, Strong scripting and automation skills using PowerShell and Python.
We'll put those as
- items.
- Qualifications: The "Preferred Qualifications" list: CISSP, CISM, CCSP, or similar cybersecurity certification; Venafi Certified Professional or Venafi Certified Architect certification; Experience with: Keyfactor, DigiCert, Entrust, Microsoft ADCS, HashiCorp Vault, Azure Key Vault, AWS Certificate Manager; Previous experience within banking, financial services, insurance (BFSI), or other highly regulated industries.
We'll put those as
- .
- Skills: There's a "Technical Skills" section with many items grouped under categories: PKI & Cryptography, Venafi, Cloud & DevOps, Programming & Automation, Leadership Expectations? Actually Leadership Expectations is separate but could be part of Skills or maybe separate. But we have a heading for Skills; we can include the technical skills list. Also Leadership Expectations could be considered part of Skills or maybe separate but we don't have a heading for Leadership. We could include Leadership Expectations under Skills as part of the list, or we could omit if not fitting. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Leadership Expectations into Skills or maybe into Responsibilities? But better to put under Skills as "Leadership Expectations". However the heading "Skills" is for technical skills; but we can still include leadership as part of Skills. Or we could create a separate section but not in allowed list? The allowed headings list includes those specific ones; we should not create other headings. So we must fit everything into those headings. So we can put Leadership Expectations under Skills as part of the list.
- Benefits: The paragraph about benefits: "Client offers a comprehensive benefits package that may include medical, dental, and vision coverage, 401(k) with company match, life and disability insurance, paid time off, paid holidays, wellness programs, and opportunities for professional growth and development. Benefits eligibility may vary based on employment status and location." We'll put that as
- items maybe each benefit.
- Pay: Salary info: "$160,000 - $165,000 Base Salary". Also earlier location line had salary range. We'll put Pay section with that info as
.
- Schedule: Employment Type: Full-Time. Could also include location? But location is not schedule. We'll put Schedule section with "Full-Time". Possibly also mention Remote (U.S.)? That's location but not schedule. We'll keep schedule as Full-Time.
We must not include boilerplate like contact info, application instructions, etc. So remove the "Apply today..." paragraph? Actually that is substantive? It's a call to apply; but instruction says remove application instructions. The sentence "Apply today to join a team focused on securing enterprise identities, automating certificate management, and modernizing PKI infrastructure." is basically a call to apply; we should remove it. Also remove the benefits eligibility sentence? That is part of benefits; we can keep it as part of benefits but it's not boilerplate. It's okay.
Remove the "By providing your phone number..." etc. Remove contact, etc.
Now produce HTML fragment.
We need to ensure we don't repeat job title as heading. No markdown.
We'll output something like:
About the role
We are seeking an experienced PKI Venafi Architect to lead enterprise-wide Public Key Infrastructure (PKI), certificate lifecycle management, and machine identity security initiatives. This role will be responsible for architecting, deploying, and optimizing secure PKI environments while driving automation and governance across enterprise applications, cloud platforms, and security ecosystems. The ideal candidate will possess deep expertise in Venafi Trust Protection Platform (TPP), PKI architecture, certificate lifecycle management, cryptographic controls, and cloud security solutions.
Responsibilities
- PKI & Security Architecture: Design, implement, and maintain enterprise PKI architecture, including Root Certificate Authorities (CA), Issuing CAs, Certificate Revocation Lists (CRL), Online Certificate Status Protocol (OCSP), Hardware Security Modules (HSM), Trust frameworks; develop certificate governance standards, policies, and cryptographic control frameworks; architect scalable, highly available PKI and Certificate Lifecycle Management (CLM) solutions; drive enterprise machine identity and certificate management strategy.
- Venafi Platform Architecture: Design, administer, and optimize Venafi Trust Protection Platform (TPP); define onboarding standards, workflows, discovery jobs, reporting, policy management, and access controls; architect integrations between Venafi and enterprise applications, cloud platforms, and security tools; lead platform upgrades, enhancements, and performance optimization initiatives.
- Certificate Lifecycle Automation: Architect and implement automated certificate provisioning, renewal, and deployment solutions; build automation frameworks utilizing Venafi APIs, VCert, PowerShell, Python, Ansible, GitHub Actions, Azure DevOps, CI/CD
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Keep all substantive info. We need to parse the posting. Given content: Location: Chicago, IL, USA Salary: $160,000.00 USD Annually - $165,000.00 USD Annually Description PKI Venafi Architect Location: Remote (U.S.) Salary: $160,000 - $165,000 Base Salary Employment Type: Full-Time About The Opportunity We are seeking an experienced PKI Venafi Architect to lead enterprise-wide Public Key Infrastructure (PKI), certificate lifecycle management, and machine identity security initiatives. This role will be responsible for architecting, deploying, and optimizing secure PKI environments while driving automation and governance across enterprise applications, cloud platforms, and security ecosystems. The ideal candidate will possess deep expertise in Venafi Trust Protection Platform (TPP), PKI architecture, certificate lifecycle management, cryptographic controls, and cloud security solutions. Key ResponsibilitiesPKI & Security Architecture Design, implement, and maintain enterprise PKI architecture, including:Root Certificate Authorities (CA)Issuing CAsCertificate Revocation Lists (CRL)Online Certificate Status Protocol (OCSP)Hardware Security Modules (HSM)Trust frameworksDevelop certificate governance standards, policies, and cryptographic control frameworks.Architect scalable, highly available PKI and Certificate Lifecycle Management (CLM) solutions.Drive enterprise machine identity and certificate management strategy.Venafi Platform Architecture Design, administer, and optimize Venafi Trust Protection Platform (TPP).Define onboarding standards, workflows, discovery jobs, reporting, policy management, and access controls.Architect integrations between Venafi and enterprise applications, cloud platforms, and security tools.Lead platform upgrades, enhancements, and performance optimization initiatives. Certificate Lifecycle Automation Architect and implement automated certificate provisioning, renewal, and deployment solutions.Build automation frameworks utilizing:Venafi APIsvCertPowerShellPythonAnsibleGitHub ActionsAzure DevOpsCI/CD PipelinesDrive enterprise adoption of certificate lifecycle automation.Application & Cloud Integration Lead onboarding of enterprise applications into CLM services.Support certificate deployment and automation across:Windows ServerLinux/UnixIISApacheTomcatWebLogicKubernetesAzureAWSF5 Load BalancersKafkaSolacePingFederateProvide architectural guidance and troubleshooting support for complex certificate and trust-related issues.Governance & Compliance Ensure compliance with:NISTPCI-DSSSOXISO 27001FedRAMPInternal security standardsConduct cryptographic risk assessments and certificate posture reviews.Define certificate ownership and governance processes.Support audit and regulatory compliance initiatives. Required Qualifications Bachelor's degree in Computer Science, Cybersecurity, Engineering, or related field.10+ years of Information Security experience.5+ years of hands-on PKI architecture experience.5+ years working with Venafi Trust Protection Platform.Expertise in:PKIX.509 CertificatesTLS/SSLCertificate Lifecycle Management (CLM)CRL/OCSPHardware Security Modules (HSM)Digital SignaturesCryptographic Key ManagementExperience designing PKI solutions within Azure and AWS environments.Strong scripting and automation skills using PowerShell and Python. Preferred Qualifications CISSP, CISM, CCSP, or similar cybersecurity certification.Venafi Certified Professional or Venafi Certified Architect certification.Experience with:KeyfactorDigiCertEntrustMicrosoft ADCSHashiCorp VaultAzure Key VaultAWS Certificate ManagerPrevious experience within banking, financial services, insurance (BFSI), or other highly regulated industries.Technical SkillsPKI & Cryptography PKI ArchitectureX.509 CertificatesTLS/SSLPKCS StandardsDigital SignaturesHSM IntegrationCRL / OCSP Venafi Venafi Trust Protection Platform (TPP)Venafi TLS ProtectCertificate DiscoveryPolicy ManagementWorkflow AutomationReporting & Governance Cloud & DevOps Microsoft AzureAWSKubernetesGitHub ActionsAzure DevOpsCI/CD PipelinesInfrastructure as Code (IaC) Programming & Automation PowerShellPythonREST APIsAnsible Leadership Expectations Serve as the organization's PKI and Machine Identity subject matter expert.Provide technical leadership and guidance to engineering and operations teams.Develop enterprise PKI roadmaps and modernization strategies.Mentor junior engineers and establish certificate lifecycle management best practices.Drive Zero Trust and identity-centric security initiatives. Apply today to join a team focused on securing enterprise identities, automating certificate management, and modernizing PKI infrastructure. Client offers a comprehensive benefits package that may include medical, dental, and vision coverage, 401(k) with company match, life and disability insurance, paid time off, paid holidays, wellness programs, and opportunities for professional growth and development. Benefits eligibility may vary based on employment status and location. By providing your phone number, you consent to: (1) receive automated text messages and calls from the Judge Group, Inc. and its affiliates (collectively "Judge") to such phone number regarding job opportunities, your job application, and for other related purposes. Message & data rates apply and message frequency may vary. Consistent with Judge's Privacy Policy, information obtained from your consent will not be shared with third parties for marketing/promotional purposes. Reply STOP to opt out of receiving telephone calls and text messages from Judge and HELP for help. Contact: jprovenzano@judge.com This job and many more are available through The Judge Group. Find us on the web at www.judge.com We need to extract sections: About the role (the "About The Opportunity" paragraph). Responsibilities (the "Key Responsibilities" section). Requirements (maybe "Required Qualifications"). Qualifications (maybe "Preferred Qualifications"? Actually they have both Required and Preferred. Could treat Required as Requirements, Preferred as Qualifications? Or we could combine? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have: - About the role: The paragraph after "About The Opportunity". We'll put that in
About the role
then...
. - Responsibilities: The "Key Responsibilities" section includes multiple sub-sections: PKI & Security Architecture, Venafi Platform Architecture, Certificate Lifecycle Automation, Application & Cloud Integration, Governance & Compliance. We'll list each bullet as- items.
- Qualifications: The "Preferred Qualifications" list: CISSP, CISM, CCSP, or similar cybersecurity certification; Venafi Certified Professional or Venafi Certified Architect certification; Experience with: Keyfactor, DigiCert, Entrust, Microsoft ADCS, HashiCorp Vault, Azure Key Vault, AWS Certificate Manager; Previous experience within banking, financial services, insurance (BFSI), or other highly regulated industries.
We'll put those as
- .
- Skills: There's a "Technical Skills" section with many items grouped under categories: PKI & Cryptography, Venafi, Cloud & DevOps, Programming & Automation, Leadership Expectations? Actually Leadership Expectations is separate but could be part of Skills or maybe separate. But we have a heading for Skills; we can include the technical skills list. Also Leadership Expectations could be considered part of Skills or maybe separate but we don't have a heading for Leadership. We could include Leadership Expectations under Skills as part of the list, or we could omit if not fitting. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Leadership Expectations into Skills or maybe into Responsibilities? But better to put under Skills as "Leadership Expectations". However the heading "Skills" is for technical skills; but we can still include leadership as part of Skills. Or we could create a separate section but not in allowed list? The allowed headings list includes those specific ones; we should not create other headings. So we must fit everything into those headings. So we can put Leadership Expectations under Skills as part of the list.
- Benefits: The paragraph about benefits: "Client offers a comprehensive benefits package that may include medical, dental, and vision coverage, 401(k) with company match, life and disability insurance, paid time off, paid holidays, wellness programs, and opportunities for professional growth and development. Benefits eligibility may vary based on employment status and location." We'll put that as
- items maybe each benefit.
- Pay: Salary info: "$160,000 - $165,000 Base Salary". Also earlier location line had salary range. We'll put Pay section with that info as
. - Schedule: Employment Type: Full-Time. Could also include location? But location is not schedule. We'll put Schedule section with "Full-Time". Possibly also mention Remote (U.S.)? That's location but not schedule. We'll keep schedule as Full-Time. We must not include boilerplate like contact info, application instructions, etc. So remove the "Apply today..." paragraph? Actually that is substantive? It's a call to apply; but instruction says remove application instructions. The sentence "Apply today to join a team focused on securing enterprise identities, automating certificate management, and modernizing PKI infrastructure." is basically a call to apply; we should remove it. Also remove the benefits eligibility sentence? That is part of benefits; we can keep it as part of benefits but it's not boilerplate. It's okay. Remove the "By providing your phone number..." etc. Remove contact, etc. Now produce HTML fragment. We need to ensure we don't repeat job title as heading. No markdown. We'll output something like:
About the role
We are seeking an experienced PKI Venafi Architect to lead enterprise-wide Public Key Infrastructure (PKI), certificate lifecycle management, and machine identity security initiatives. This role will be responsible for architecting, deploying, and optimizing secure PKI environments while driving automation and governance across enterprise applications, cloud platforms, and security ecosystems. The ideal candidate will possess deep expertise in Venafi Trust Protection Platform (TPP), PKI architecture, certificate lifecycle management, cryptographic controls, and cloud security solutions.
Responsibilities
- PKI & Security Architecture: Design, implement, and maintain enterprise PKI architecture, including Root Certificate Authorities (CA), Issuing CAs, Certificate Revocation Lists (CRL), Online Certificate Status Protocol (OCSP), Hardware Security Modules (HSM), Trust frameworks; develop certificate governance standards, policies, and cryptographic control frameworks; architect scalable, highly available PKI and Certificate Lifecycle Management (CLM) solutions; drive enterprise machine identity and certificate management strategy.
- Venafi Platform Architecture: Design, administer, and optimize Venafi Trust Protection Platform (TPP); define onboarding standards, workflows, discovery jobs, reporting, policy management, and access controls; architect integrations between Venafi and enterprise applications, cloud platforms, and security tools; lead platform upgrades, enhancements, and performance optimization initiatives.
- Certificate Lifecycle Automation: Architect and implement automated certificate provisioning, renewal, and deployment solutions; build automation frameworks utilizing Venafi APIs, VCert, PowerShell, Python, Ansible, GitHub Actions, Azure DevOps, CI/CD
- items maybe each benefit.
- Pay: Salary info: "$160,000 - $165,000 Base Salary". Also earlier location line had salary range. We'll put Pay section with that info as
- .
- Skills: There's a "Technical Skills" section with many items grouped under categories: PKI & Cryptography, Venafi, Cloud & DevOps, Programming & Automation, Leadership Expectations? Actually Leadership Expectations is separate but could be part of Skills or maybe separate. But we have a heading for Skills; we can include the technical skills list. Also Leadership Expectations could be considered part of Skills or maybe separate but we don't have a heading for Leadership. We could include Leadership Expectations under Skills as part of the list, or we could omit if not fitting. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Leadership Expectations into Skills or maybe into Responsibilities? But better to put under Skills as "Leadership Expectations". However the heading "Skills" is for technical skills; but we can still include leadership as part of Skills. Or we could create a separate section but not in allowed list? The allowed headings list includes those specific ones; we should not create other headings. So we must fit everything into those headings. So we can put Leadership Expectations under Skills as part of the list.
- Benefits: The paragraph about benefits: "Client offers a comprehensive benefits package that may include medical, dental, and vision coverage, 401(k) with company match, life and disability insurance, paid time off, paid holidays, wellness programs, and opportunities for professional growth and development. Benefits eligibility may vary based on employment status and location." We'll put that as