Senior API Developer/ Security Engineer (Vulnerability / Remediation)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Must preserve all substantive info. We need to parse the posting. Content: - Intro: "The position is described below. If you want to apply, click the Apply Now button..." -> remove application instructions. - "After you click Apply Now and complete your application, you'll be invited to create a profile..." -> remove. - "If you already have a profile with us, you can log in to check status." -> remove. - "Need Help? If you have a disability and need assistance with the application, you can request a reasonable accommodation. Send an email to Accessibility (accommodation requests only; other inquiries won't receive a response)." -> remove (EEO/accommodation? Might be considered boilerplate; but it's about accommodation request. Might be considered EEO? Probably remove. - "Regular or Temporary: Regular Language Fluency: English (Required) Work Shift: 1st shift (United States of America)" -> This is metadata; we can fold minor metadata into a short

or drop it. Probably we can include a short paragraph with these details. - "Please review the following job description:" -> just intro. - Then description: "This team uses automated API security tools like Akamai, Salt Security and ReadyAPI tools to identify vulnerabilities in running APIs. This Senior Security Engineer will be experienced with API development and/or API security testing tools such as Akamai, API Security, Salt Security, Traceable, Data Theorem, OWASP ZAP (API extensions), SoapUI, ReadyAPI, or Burp Suite. The team partners with application development, DevSecOps, and technology teams to identify, assess, prioritize, and drive remediation of security vulnerabilities across applications, APIs," - Then "Essential Duties And Responsibilities Following is a summary of the essential functions for this job. Other duties may be performed, both major and minor, which are not mentioned below. Specific activities may change from time to time." Then list of duties. We need to extract duties as bullet list. Duties list: - Lead the enterprise vulnerability management program for automated API testing, including identification, assessment, prioritization, tracking, and remediation of security vulnerabilities. - Performs security testing, and penetration testing tasks for assigned platforms and services, using defined methods to identify and remediate vulnerabilities. - Develop risk-based remediation strategies and collaborate with application teams to reduce organizational security exposure - Reviews relevant security threats, tools, and design options for assigned work, and provides input that supports technical plans and priorities for the job area. - Perform triage and validation of security findings to reduce false positives and improve remediation effectiveness. - Design, implement, and maintain automated API security testing capabilities within CI/CD pipelines. - Implements and updates security baselines, guardrails, and control configurations for systems and applications within the area of responsibility, helping maintain regulatory and policy compliance. - Shares knowledge and best practices with technical teammates, offering informal guidance and support during code reviews, design discussions, and pairing sessions. We need to format as

• each. Then "Required Qualifications" section: list bullet points. Required Qualifications: - Bachelor’s degree or equivalent education, training, and work-related experience. - Minimum of 7 years of experience in security engineering or related cybersecurity roles. - Deep specialized knowledge in cybersecurity principles, theories, and concepts. - Proven experience in software development lifecycle security practices. - Deep knowledge of threat modeling, security testing, and penetration testing. - Experience implementing and managing complex information security technologies. Then "Preferred Qualifications" bullet list. Preferred Qualifications: - Working knowledge of industry security frameworks and standards, including: - NIST SP 800-228 (API Security Guidance) - FFIEC (Federal Financial Institutions Examination Council) guidelines - OWASP API Security Top 10 - Financial-grade API (FAPI – OpenID Foundation) - Strong understanding of API security protocols and frameworks, including OAuth 2.0, OpenID Connect (OIDC), Mutual TLS (mTLS), and JSON Web Tokens (JWT) - Experience within banking or financial services environments - Proficiency or familiarity with Python scripting - Relevant security certifications such as CISSP, OSCP, CEH, or Security+ - Experience with cloud platforms such as AWS and/or Microsoft Azure - Experience in financial services, cybersecurity, regulated enterprise environments, or platforms with high audit and control requirements. - Familiarity with secure tool-calling patterns, API protections, model or prompt change validation, and runtime traceability for AI systems. - Working knowledge of cloud-native security patterns, telemetry analysis, and deployment gating for modern engineering teams. - Plans and manages own work to meet defined objectives and milestones, seeking feedback, pursuing self-development, and adjusting approaches to improve quality and effectiveness over time. Then "General Description of Available Benefits for Eligible Employees of Truist Financial Corporation:" paragraph describing benefits. We need to create a Benefits section if there is real specific content. The paragraph includes details: medical, dental, vision, life insurance, disability, accidental death and dismemberment, tax-preferred savings accounts, 401k plan, at least 10 days vacation, 10 sick days, paid holidays, possibly defined benefit pension plan, restricted stock units, deferred compensation plan. That's specific enough to include Benefits section. We should not include Pay or Schedule sections unless posting actually states them. It does not mention pay or schedule beyond "Work Shift: 1st shift (United States of America)" which we could treat as Schedule? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Work Shift: 1st shift. That's schedule info. So we could include a Schedule section with that detail. However we also have Language Fluency and Regular/Temporary. Those could be minor metadata folded into a short

  . The schedule is specific: 1st shift. So we could include a Schedule section with that. But we must prefer few substantive sections over many thin ones. We have About the role (maybe we can combine intro description), Responsibilities, Requirements (maybe combine Required and Preferred Qualifications?), Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: we could include a brief paragraph summarizing the role (the initial description). That seems appropriate. - Responsibilities: we have duties list. - Requirements: we have Required Qualifications. - Qualifications: maybe we could put Preferred Qualifications under Qualifications? But the instruction says use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have separate headings for Requirements and Qualifications. Likely Requirements = mandatory, Qualifications = preferred or additional. We'll follow that. - Skills: we could extract skills from Preferred Qualifications (like Python scripting, API security protocols, etc.) but we already have them in Preferred Qualifications. Might be redundant. Better to put Preferred Qualifications under Qualifications? Actually we have both Requirements and Qualifications headings. We could put Required Qualifications under Requirements, and Preferred Qualifications under Qualifications. That seems logical. - Skills: maybe we could list specific technical skills like API security tools, etc. But we already have them in responsibilities and qualifications. Could create a Skills section summarizing key skills: API security testing tools (Akamai, Salt Security, ReadyAPI, etc.), CI/CD pipeline automation, threat modeling, penetration testing, etc. But we risk duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills section and put those details under Responsibilities or Qualifications. - Benefits: we have benefits paragraph. - Schedule: we have Work Shift: 1st shift. - Pay: not present, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. We need to output only HTML fragment, no /. Use

  for each section heading. Use

  • for lists. Use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. Must not omit any substantive info. Let's extract all substantive info: From intro: "This team uses automated API security tools like Akamai, Salt Security and ReadyAPI tools to identify vulnerabilities in running APIs. This Senior Security Engineer will be experienced with API development and/or API security testing tools such as Akamai, API Security, Salt Security, Traceable, Data Theorem, OWASP ZAP (API extensions), SoapUI, ReadyAPI, or Burp Suite. The team partners with application development, DevSecOps, and technology teams to identify, assess, prioritize, and drive remediation of security vulnerabilities across applications, APIs," That's a sentence that ends abruptly but we keep as is. We could combine that into About the role paragraph. Also we have "Regular or Temporary: Regular Language Fluency: English (Required) Work Shift: 1st shift (United States of America)" - we can incorporate Regular/Temporary and Language Fluency into About the role or a short paragraph. Since we have Schedule section for Work Shift, we can put Regular/Temporary and Language Fluency in About the role paragraph. Now let's draft. About the role (

    ): "This team uses automated API security tools like Akamai, Salt Security and ReadyAPI tools to identify vulnerabilities in running APIs. The Senior Security Engineer will be experienced with API development and/or API security testing tools such as Akamai, API Security, Salt Security, Traceable, Data Theorem, OWASP ZAP (API extensions), SoapUI, ReadyAPI, or Burp Suite. The team partners with application development, DevSecOps, and technology teams to identify, assess, prioritize, and drive remediation of security vulnerabilities across applications, APIs. The position is regular, requires English fluency, and operates on the 1st shift in the United States." We need to preserve the info about Regular/Temporary, Language Fluency, Work Shift. We included them. Now Responsibilities (

    Responsibilities

    ...). We need to ensure we include all duties exactly as given. List: - Lead the enterprise vulnerability management program for automated API testing, including identification, assessment, prioritization, tracking, and remediation of security vulnerabilities. - Performs security testing, and penetration testing tasks for assigned platforms and services, using defined methods to identify and remediate vulnerabilities. - Develop risk-based remediation strategies and collaborate with application teams to reduce organizational security exposure - Reviews relevant security threats, tools, and design options for assigned work, and provides input that supports technical plans and priorities for the job area. - Perform triage and validation of security findings to reduce false positives and improve remediation effectiveness. - Design, implement, and maintain automated API security testing capabilities within CI/CD pipelines. - Implements and updates security baselines, guardrails, and control configurations for systems and applications within the area of responsibility, helping maintain regulatory and policy compliance. - Shares knowledge and best practices with technical teammates, offering informal guidance and support during code reviews, design discussions, and pairing sessions. Note: some sentences start with capital verb, some lower case. We'll keep as is. Now Requirements (

    Requirements

    ...): - Bachelor’s degree or equivalent education, training, and work-related experience. - Minimum of 7 years of experience in security engineering or related cybersecurity roles. - Deep specialized knowledge in cybersecurity principles, theories, and concepts. - Proven experience in software development lifecycle security practices. - Deep knowledge of threat modeling, security testing, and penetration testing. - Experience implementing and managing complex information security technologies. Now Qualifications (

    Qualifications

    ...): Preferred Qualifications. We need to preserve the bullet structure, including sub-bullets for frameworks list. We have: