Secure Software Engineer

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 need to extract content from posting. Job title: Secure Software Engineer - Remote (but we don't repeat as heading). We need sections: maybe About the role (job summary), Responsibilities (maybe not explicit), Requirements (maybe required qualifications), Qualifications (maybe preferred qualifications), Skills (maybe combine?), Benefits (none explicit), Pay (salary range given), Schedule (maybe full-time). Let's parse. Posting includes: - Company description: Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential. - Job Title: Secure Software Engineer - Location: 100% Remote (U.S.) - Position Type: Full-time, Direct W2 - Salary Range: $100,000–$150,000 Annually - Experience Required: 6+ years - Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position. - Job Summary: We are looking for an Application Security Engineer to embed security throughout the software development lifecycle, partnering with engineering teams to design secure systems, identify vulnerabilities, and reduce risk across our application portfolio. The role blends hands-on offensive and defensive skills with strong communication and collaboration, helping development teams build secure software efficiently rather than slowing them down. The ideal candidate brings deep technical security expertise, strong software engineering fundamentals, and a track record of shipping security improvements that meaningfully reduce risk in production. - Required Qualifications: list bullet points (though not bullet in text but each line). Let's extract: Bachelor’s degree in Computer Science, Cybersecurity, or a related field. Five or more years of application security or security engineering experience. Strong understanding of OWASP Top 10, common vulnerability classes, and modern exploit patterns. Hands-on experience performing code review across at least two major languages. Deep familiarity with SAST, DAST, SCA, and CI/CD-integrated security tooling. Strong understanding of authentication, authorization, and cryptographic primitives. Experience with cloud security and modern infrastructure controls. Strong communication skills with technical and non-technical audiences. Proficiency in at least one programming language for tooling and automation. Experience working closely with engineering teams in an Agile environment. - Preferred Qualifications: Industry certifications such as OSCP, OSCE, GWAPT, or CISSP. Experience with offensive security tooling and red-team operations. Bug bounty experience, public CVEs, or open-source security contributions. Familiarity with AI/LLM application security considerations. Exposure to regulated industries with strict compliance requirements. - How to Apply: contact info etc (should be removed as boilerplate/application instructions). Remove. - EEO statement: remove. Thus we have content for sections: About the role: could be the company description + job summary? The "About the role" maybe includes job summary and company overview. We'll put that. Responsibilities: Not explicitly listed; the job summary includes responsibilities: embed security throughout SDLC, partnering with engineering teams to design secure systems, identify vulnerabilities, reduce risk, etc. Could treat as responsibilities. But we need to decide if we have enough specific content. The posting does not have a separate "Responsibilities" heading but we can infer responsibilities from job summary. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." We can include responsibilities as a section if we have content derived from the posting (not invented). The job summary includes responsibilities: embed security throughout the software development lifecycle, partnering with engineering teams to design secure systems, identify vulnerabilities, and reduce risk across our application portfolio. The role blends hands-on offensive and defensive skills with strong communication and collaboration, helping development teams build secure software efficiently rather than slowing them down. That is substantive. So we can create Responsibilities section with those bullet points. Requirements: Could be the "Required Qualifications". We'll put that as Requirements. Qualifications: Could be "Preferred Qualifications". We'll put that as Qualifications. Skills: Might be overlapping; maybe we can combine some skill-based items from required qualifications into Skills section. But we already have Requirements and Qualifications; maybe we can skip Skills to avoid thin sections. However we have specific skill items like "Strong understanding of OWASP Top 10", "Hands-on experience performing code review", etc. Those could go under Skills. But we already have them in Requirements. The instruction: Prefer a few substantive sections over many thin ones. So we could combine Required Qualifications and Skills into one section called Requirements (or Qualifications). But we need to follow headings list: we can use any of those headings if we have content. We could have About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. That's six sections. Pay: Salary range given. Schedule: Position Type: Full-time, Direct W2. So schedule: Full-time. We should not include Benefits as none given. We must not repeat job title as heading. We must not include Job ID/requisition numbers. We must output only HTML fragment. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. Thus:

  About the role

  Bright Vision Technologies is a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a fantastic opportunity to join an established and well-respected organization offering tremendous career growth potential.

  We are looking for an Application Security Engineer to embed security throughout the software development lifecycle, partnering with engineering teams to design secure systems, identify vulnerabilities, and reduce risk across our application portfolio. The role blends hands-on offensive and defensive skills with strong communication and collaboration, helping development teams build secure software efficiently rather than slowing them down. The ideal candidate brings deep technical security expertise, strong software engineering fundamentals, and a track record of shipping security improvements that meaningfully reduce risk in production.

  That's about the role (combining company description and job summary). Could be okay.

  Responsibilities

  • Embed security throughout the software development lifecycle.
  • Partner with engineering teams to design secure systems.
  • Identify vulnerabilities and reduce risk across the application portfolio.
  • Apply hands-on offensive and defensive security skills.
  • Collaborate with development teams to build secure software efficiently.
  But we need to ensure we are not inventing detail beyond what's in posting. The posting says: "We are looking for an Application Security Engineer to embed security throughout the software development lifecycle, partnering with engineering teams to design secure systems, identify vulnerabilities, and reduce risk across our application portfolio. The role blends hands-on offensive and defensive skills with strong communication and collaboration, helping development teams build secure software efficiently rather than slowing them down." So we can break that into bullet points: embed security..., partner..., identify vulnerabilities..., reduce risk..., blend hands-on offensive and defensive skills..., strong communication and collaboration..., helping development teams build secure software efficiently. That's all from posting. Good.

  Requirements

  • Bachelor’s degree in Computer Science, Cybersecurity, or a related field.
  • Five or more years of application security or security engineering experience.
  • Strong understanding of OWASP Top 10, common vulnerability classes, and modern exploit patterns.
  • Hands-on experience performing code review across at least two major languages.
  • Deep familiarity with SAST, DAST, SCA, and CI/CD-integrated security tooling.
  • Strong understanding of authentication, authorization, and cryptographic primitives.
  • Experience with cloud security and modern infrastructure controls.
  • Strong communication skills with technical and non-technical audiences.
  • Proficiency in at least one programming language for tooling and automation.
  • Experience working closely with engineering teams in an Agile environment.

  Qualifications

  • Industry certifications such as OSCP, OSCE, GWAPT, or CISSP.
  • Experience with offensive security tooling and red-team operations.
  • Bug bounty experience, public CVEs, or open-source security contributions.
  • Familiarity with AI/LLM application security considerations.
  • Exposure to regulated industries with strict compliance requirements.

  Pay

  Salary Range: $100,000–$150,000 Annually

  Schedule

  Position Type: Full-time, Direct W2

  We should not include location? Could be part of About the role? Not required. The instruction: do not repeat job title as heading; we didn't. We included location maybe in About the role? Not needed but could be included as prose. However location is substantive; we could add a short paragraph about location under About the role or separate section? There's no heading for location; we could fold into About the role as a sentence. Let's add: "Location: 100% Remote (U.S.)" and maybe "Experience Required: 6+ years" but we already have 5+ years required; the posting says Experience Required: 6+ years (contradicts required qualifications of 5+ years). Actually Required Qualifications says Five or more years; Experience Required says 6+ years. We need to preserve all substantive information; we cannot invent or summarize away detail. So we need to include both? The Required Qualifications says five or more years; the Experience Required line says 6+ years. Which is correct? We must preserve both. We could note both in Requirements: maybe combine as "Five or more years of application security or security engineering experience (preferably 6+ years)". But that would be summarizing. Better to include both as separate items: "Five or more years of application security or security engineering experience." and "Experience Required: 6+ years." However that may be redundant but we preserve both. Let's add both as separate list items. Also sponsorship info: "Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position." This is substantive; we need to include it somewhere. Could be under Requirements or a separate section like "Eligibility". But we don't have a heading for that; we could add a subsection under Requirements or maybe under About the role. Since we must preserve all substantive info, we should include it. Let's add a list item under Requirements: "U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply; unable to sponsor new H-1B visa petitions." Also note "Position Type: Full-time, Direct W2" we already have in Schedule. Also "Job Title: Secure Software Engineer" we are not repeating as heading. Also "Location: 100% Remote (U.S.)" we need to include. Let's add a sentence in About the role: "Location: 100% Remote (U.S.)." Also "Experience Required: 6+ years" we add as separate item. Thus update Requirements list: - Bachelor’s degree in Computer Science, Cybersecurity, or a related field. - Five or more years of application security or security engineering experience. - Experience Required: 6+ years. - Strong understanding of OWASP Top 10, common vulnerability classes, and modern exploit patterns. - Hands-on experience performing code review across at least two major languages. - Deep familiarity with