PKI Security Services Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the job description and extract relevant content.
Let's extract:
- Position Description: description about team, tasks.
- Key Responsibilities: list of bullet points.
- End-to-End Ownership: more details (maybe part of responsibilities).
- Design and develop robust, secure, and scalable RESTful APIs... (maybe part of responsibilities).
- Cryptographic Engineering: details.
- Infrastructure and CI/CD Integration: details.
- Security & Compliance: details.
- Skills Required: list of skills.
- Skills Preferred: list.
- Experience Required: details.
- Experience Preferred: details.
- Education Required: Bachelor's Degree.
- Additional Information: Hybrid Position 4 days a week on site (Schedule). Also mention Everforth Apex description (About the company). Benefits: Everforth Apex Benefits Overview: medical, dental, vision, life, disability, insurance, ESPP, 401K, HSA, SupportLinc EAP, corporate discount, training program, certification prep, etc. Also mention benefits package.
- Pay: Not mentioned. So we should NOT include Pay section.
- Schedule: we have Hybrid Position 4 days a week on site => schedule info.
- Benefits: we have benefits details.
- About the role: maybe the Position Description and team description.
- Responsibilities: combine Key Responsibilities, End-to-End Ownership, Design and develop..., Cryptographic Engineering, Infrastructure and CI/CD Integration, Security & Compliance.
- Requirements: maybe Experience Required, Education Required.
- Qualifications: maybe Skills Required? Or we could treat Skills as separate section.
- Skills: Skills Required and Skills Preferred.
We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not create empty sections. So include only those with content.
We need to output HTML fragment only, no or . Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like specific technologies, standards, etc.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove the "Everforth Apex Benefits Overview:" maybe we keep benefits content but not the heading? We can keep benefits as a section with heading Benefits and list items.
We must not include the duplicated EEO statements.
We must not include the virtual recruiter link, privacy policy, etc.
We must not include the "Click here for more details." etc.
We must not include the "By applying for this job, you agree to receive calls..." etc.
We must not include the "Everforth Apex Systems is an equal opportunity employer." repeated.
We must not include the address etc? That's maybe not substantive? It's location info maybe not needed but could be considered part of Additional Information? The posting includes address: "4400 Cox Road Suite 200 Glen Allen, Virginia 23060". Might be considered location but not requested as a section. Could be omitted as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So address could be minor metadata; we could drop it or include in a short p under About the role? Probably drop.
We need to preserve all substantive information: responsibilities, skills, experience, education, benefits, schedule.
Let's extract details:
**About the role / Position Description**:
"The Product Cybersecurity PKI & Key Mgmt Security Services team generates, distributes, stores, and manages lifecycle for the cryptographic keys and certificates in the vehicle product ecosystem. This includes developing and maintaining in-house APIs and web services to provide confidentiality, integrity and authenticity protection for various use cases and features in the product ecosystem. We are seeking an exceptional Software Engineer specializing in Public Key Infrastructure (PKI) and secure API services to own the end-to-end lifecycle of mission-critical cryptographic systems. You will design, build, deploy, and maintain high-assurance PKI and security service APIs that power certificate issuance, lifecycle management, revocation, and integration for the connected vehicle product ecosystem."
Also maybe "Employees in this job function develop and maintain the back-end/ server-side parts of an application, typically consisting of APIs, databases and other services containing business logic. They work with various languages and tools to create and maintain services on-prem or in the cloud."
That seems like generic description of role; we can include.
**Responsibilities**:
List from "Key Responsibilities:" bullet points:
- Engage with customers to understand their use-cases and requirements
- Solve complex problems by designing, developing, and delivering using various tools, languages, frameworks, and technologies
- Align with architecture guidelines for unified and coherent approach to development
- Design, develop, and deliver new code using various tools, languages, frameworks, and technologies
- Develop and maintain back-end applications like APIs and microservices using server-side languages like Java, Python, C#, etc.
- Collaborate with front-end developers to integrate user interface elements and with cross functional teams like product owners, designers, architects etc.
- Manage application deployment to the cloud or on-prem, health and performance monitoring, security hardening and disaster recovery for deployed applications
- Manage data storage and retrievals in applications by utilizing database technologies such as Oracle, MySQL, MongoDB, etc.
- Promote improvements in programming practices, such as test-driven development, continuous integration, and continuous delivery
- Optimize back-end infrastructure and deployment practices to improve application resiliency and reliability
- Support security practices to safeguard user data including encryption and anonymization
- Write and manage code that interfaces with HSMs to apply cryptography and issue certificates
Then "End-to-End Ownership: Lead the full lifecycle of PKI and Key Management services supporting our vehicle products and ecosystem — lead customer requirements gathering, architecture design, implementation, testing, deployment, monitoring, and post-launch support."
Then "Design and develop robust, secure, and scalable RESTful APIs and web services for various features and use cases: CRL/OCSP, ACME, Certificate Issuance, message encryption/decryption, software signing, key rotation and certificate lifecycle management, HSM integration with PKCS11. Implement access control methods that enforce least privilege access principles using OAuth or mTLS."
Then "Cryptographic Engineering: Implement and harden PKI and key services with deep knowledge of PKI industry standards, X.509, PKCS standards, elliptic curve cryptography (ECC) and RSA, post-quantum readiness, and hardware security module CSP integration. Apply hybrid encryption techniques with AES. Define and enforce PKI certificate policies and certificate profiles."
Then "Infrastructure and CI/CD Integration: Release and Deploy your apps through build server, CI/CD pipeline, and infrastructure involving on-premises and cloud Kubernetes"
Then "Security & Compliance: Monitor and address findings regularly in code base through SAST, DAST, software quality and security vulnerability scanning. Drive and support testing at each stage of the development process."
We can combine these into a responsibilities list.
**Requirements** (maybe Experience Required + Education Required):
Experience Required:
- Engineer 3 Exp: Prac. In 2 coding lang. or adv. Prac. in 1 lang.
- 6+ years in IT; 4+ years in software engineering/development and secure coding practices using object oriented programming
- Strong knowledge and applicability of software architecture, development, methodologies and design principles including test-driven development
- Strong understanding and ability to apply cryptographic algorithms and standards in software, including RSA, ECC, AES, X.509
- Proven track record of owning customer-facing products from ideation to general acceptance, and flexibility to manage multiple projects and deliverables throughout lifecycle
Education Required:
- Bachelor's Degree
**Qualifications** maybe not needed separate; but we could treat Skills as Qualifications? The instruction says use headings like Qualifications. We could put Skills Required under Skills section, and maybe Qualifications under Requirements? But we need to follow the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have to decide which content goes where.
We can map:
- About the role: Position Description + generic job function description.
- Responsibilities: all the responsibility bullets.
- Requirements: Experience Required + Education Required.
- Qualifications: maybe Skills Required? Or we could treat Skills Required as Skills section, and Qualifications as maybe nothing else. But we need to include a Qualifications section only if there is real specific content. We have Skills Required list; that could go under Skills section. Qualifications could be maybe "Experience Required" but we already put that under Requirements. Could also put "Experience Preferred" under Qualifications? But we have Skills Preferred separate.
Better: Use Requirements for Experience Required and Education Required. Use Skills for Skills Required and Skills Preferred (maybe separate subheadings? but we just need a list). Use Qualifications maybe for nothing; we could omit Qualifications section if no specific content besides what we already used. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we don't have distinct qualifications beyond experience and skills, we can omit Qualifications.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule.
Check if we have Pay: none, so omit.
Now extract Skills Required list:
"Skills Required: Computer engineeringSoftware Development LifecycleSoftware TestingPostgreSQLSoftware DocumentationApplication DevelopmentBouncy Castle CryptographicCloud InfrastructureGoogle Cloud Platform.NET Core.NET DeveloperCyber SecurityC#Application TestingAgile Software Development"
This seems jumbled without spaces. We need to parse: likely each skill separated by missing spaces. Let's try to split:
Computer engineering
Software Development Lifecycle
Software Testing
PostgreSQL
Software Documentation
Application Development
Bouncy Castle Cryptographic
Cloud Infrastructure
Google Cloud Platform
.NET Core
.NET Developer
Cyber Security
C#
Application Testing
Agile Software Development
We should keep them as separate items.
Skills Preferred list:
"Skills Preferred: Kubernetes, Technical Communication, Technical Requirements, Technical Documentation, Application Architect, Technical Analysis"
So items: Kubernetes, Technical Communication, Technical Requirements, Technical Documentation, Application Architect, Technical Analysis.
Now Benefits: Everforth Apex Benefits Overview paragraph includes:
- medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection.
- ESPP (employee stock purchase program)
- 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure.
- HSA (Health Savings Account on the HDHP plan)
- SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions
- corporate discount savings program and other discounts.
- professional development: on-demand training program, access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA.
- dedicated customer service team for Consultants that can address questions around benefits and other resources, as well as a certified Career Coach.
- full list of benefits, programs, support teams and resources within our ‘Welcome Packet’.
We should preserve all that.
Schedule: "Hybrid Position 4 days a week on site". Also maybe mention location? But we can just put schedule.
Now we need to format as HTML.
We'll produce:
About the role
... (combined description)
Responsibilities
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive info; do not invent or summarize away detail. So we need to keep details like specific technologies, standards, etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove the "Everforth Apex Benefits Overview:" maybe we keep benefits content but not the heading? We can keep benefits as a section with heading Benefits and list items. We must not include the duplicated EEO statements. We must not include the virtual recruiter link, privacy policy, etc. We must not include the "Click here for more details." etc. We must not include the "By applying for this job, you agree to receive calls..." etc. We must not include the "Everforth Apex Systems is an equal opportunity employer." repeated. We must not include the address etc? That's maybe not substantive? It's location info maybe not needed but could be considered part of Additional Information? The posting includes address: "4400 Cox Road Suite 200 Glen Allen, Virginia 23060". Might be considered location but not requested as a section. Could be omitted as minor metadata. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So address could be minor metadata; we could drop it or include in a short p under About the role? Probably drop. We need to preserve all substantive information: responsibilities, skills, experience, education, benefits, schedule. Let's extract details: **About the role / Position Description**: "The Product Cybersecurity PKI & Key Mgmt Security Services team generates, distributes, stores, and manages lifecycle for the cryptographic keys and certificates in the vehicle product ecosystem. This includes developing and maintaining in-house APIs and web services to provide confidentiality, integrity and authenticity protection for various use cases and features in the product ecosystem. We are seeking an exceptional Software Engineer specializing in Public Key Infrastructure (PKI) and secure API services to own the end-to-end lifecycle of mission-critical cryptographic systems. You will design, build, deploy, and maintain high-assurance PKI and security service APIs that power certificate issuance, lifecycle management, revocation, and integration for the connected vehicle product ecosystem." Also maybe "Employees in this job function develop and maintain the back-end/ server-side parts of an application, typically consisting of APIs, databases and other services containing business logic. They work with various languages and tools to create and maintain services on-prem or in the cloud." That seems like generic description of role; we can include. **Responsibilities**: List from "Key Responsibilities:" bullet points: - Engage with customers to understand their use-cases and requirements - Solve complex problems by designing, developing, and delivering using various tools, languages, frameworks, and technologies - Align with architecture guidelines for unified and coherent approach to development - Design, develop, and deliver new code using various tools, languages, frameworks, and technologies - Develop and maintain back-end applications like APIs and microservices using server-side languages like Java, Python, C#, etc. - Collaborate with front-end developers to integrate user interface elements and with cross functional teams like product owners, designers, architects etc. - Manage application deployment to the cloud or on-prem, health and performance monitoring, security hardening and disaster recovery for deployed applications - Manage data storage and retrievals in applications by utilizing database technologies such as Oracle, MySQL, MongoDB, etc. - Promote improvements in programming practices, such as test-driven development, continuous integration, and continuous delivery - Optimize back-end infrastructure and deployment practices to improve application resiliency and reliability - Support security practices to safeguard user data including encryption and anonymization - Write and manage code that interfaces with HSMs to apply cryptography and issue certificates Then "End-to-End Ownership: Lead the full lifecycle of PKI and Key Management services supporting our vehicle products and ecosystem — lead customer requirements gathering, architecture design, implementation, testing, deployment, monitoring, and post-launch support." Then "Design and develop robust, secure, and scalable RESTful APIs and web services for various features and use cases: CRL/OCSP, ACME, Certificate Issuance, message encryption/decryption, software signing, key rotation and certificate lifecycle management, HSM integration with PKCS11. Implement access control methods that enforce least privilege access principles using OAuth or mTLS." Then "Cryptographic Engineering: Implement and harden PKI and key services with deep knowledge of PKI industry standards, X.509, PKCS standards, elliptic curve cryptography (ECC) and RSA, post-quantum readiness, and hardware security module CSP integration. Apply hybrid encryption techniques with AES. Define and enforce PKI certificate policies and certificate profiles." Then "Infrastructure and CI/CD Integration: Release and Deploy your apps through build server, CI/CD pipeline, and infrastructure involving on-premises and cloud Kubernetes" Then "Security & Compliance: Monitor and address findings regularly in code base through SAST, DAST, software quality and security vulnerability scanning. Drive and support testing at each stage of the development process." We can combine these into a responsibilities list. **Requirements** (maybe Experience Required + Education Required): Experience Required: - Engineer 3 Exp: Prac. In 2 coding lang. or adv. Prac. in 1 lang. - 6+ years in IT; 4+ years in software engineering/development and secure coding practices using object oriented programming - Strong knowledge and applicability of software architecture, development, methodologies and design principles including test-driven development - Strong understanding and ability to apply cryptographic algorithms and standards in software, including RSA, ECC, AES, X.509 - Proven track record of owning customer-facing products from ideation to general acceptance, and flexibility to manage multiple projects and deliverables throughout lifecycle Education Required: - Bachelor's Degree **Qualifications** maybe not needed separate; but we could treat Skills as Qualifications? The instruction says use headings like Qualifications. We could put Skills Required under Skills section, and maybe Qualifications under Requirements? But we need to follow the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have to decide which content goes where. We can map: - About the role: Position Description + generic job function description. - Responsibilities: all the responsibility bullets. - Requirements: Experience Required + Education Required. - Qualifications: maybe Skills Required? Or we could treat Skills Required as Skills section, and Qualifications as maybe nothing else. But we need to include a Qualifications section only if there is real specific content. We have Skills Required list; that could go under Skills section. Qualifications could be maybe "Experience Required" but we already put that under Requirements. Could also put "Experience Preferred" under Qualifications? But we have Skills Preferred separate. Better: Use Requirements for Experience Required and Education Required. Use Skills for Skills Required and Skills Preferred (maybe separate subheadings? but we just need a list). Use Qualifications maybe for nothing; we could omit Qualifications section if no specific content besides what we already used. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So if we don't have distinct qualifications beyond experience and skills, we can omit Qualifications. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Schedule. Check if we have Pay: none, so omit. Now extract Skills Required list: "Skills Required: Computer engineeringSoftware Development LifecycleSoftware TestingPostgreSQLSoftware DocumentationApplication DevelopmentBouncy Castle CryptographicCloud InfrastructureGoogle Cloud Platform.NET Core.NET DeveloperCyber SecurityC#Application TestingAgile Software Development" This seems jumbled without spaces. We need to parse: likely each skill separated by missing spaces. Let's try to split: Computer engineering Software Development Lifecycle Software Testing PostgreSQL Software Documentation Application Development Bouncy Castle Cryptographic Cloud Infrastructure Google Cloud Platform .NET Core .NET Developer Cyber Security C# Application Testing Agile Software Development We should keep them as separate items. Skills Preferred list: "Skills Preferred: Kubernetes, Technical Communication, Technical Requirements, Technical Documentation, Application Architect, Technical Analysis" So items: Kubernetes, Technical Communication, Technical Requirements, Technical Documentation, Application Architect, Technical Analysis. Now Benefits: Everforth Apex Benefits Overview paragraph includes: - medical, dental, vision, life, disability, and other insurance plans that offer an optional layer of financial protection. - ESPP (employee stock purchase program) - 401K program which allows you to contribute typically within 30 days of starting, with a company match after 12 months of tenure. - HSA (Health Savings Account on the HDHP plan) - SupportLinc Employee Assistance Program (EAP) with up to 8 free counseling sessions - corporate discount savings program and other discounts. - professional development: on-demand training program, access to certification prep and a library of technical and leadership courses/books/seminars once you have 6+ months of tenure, and certification discounts and other perks to associations that include CompTIA and IIBA. - dedicated customer service team for Consultants that can address questions around benefits and other resources, as well as a certified Career Coach. - full list of benefits, programs, support teams and resources within our ‘Welcome Packet’. We should preserve all that. Schedule: "Hybrid Position 4 days a week on site". Also maybe mention location? But we can just put schedule. Now we need to format as HTML. We'll produce:
About the role
... (combined description)
Responsibilities