Director, Application & AI Security

We need to output HTML fragment with sections: About the role? Actually we have sections: About Lantern (company description) maybe not needed? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We need to include sections only when posting has real specific content. We have content: About Lantern (company overview) maybe could be "About the role"? Actually "About Lantern" is company description, not role. Could be "About the role" but we have "About Lantern" describing company. Might be better to treat as "About the role"? But the instruction says use headings like About the role, Responsibilities, etc. We can include "About the role" heading with description of role (the paragraphs after company description). However we also have "About Lantern" describing company; maybe we can include that as part of "About the role" or separate? The instruction says do not repeat job title as heading; we can have "About the role" heading with a paragraph summarizing role. The company description could be placed there or maybe we can omit as not required? But we must preserve ALL substantive information; cannot omit company description. So we need to include it somewhere. Could put under "About the role" heading, but that heading is for role description, not company. However we could also add a heading "About Lantern" but that's not in the allowed list? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. "About Lantern" could be considered "About the role"? Not ideal but we can include company overview under "About the role". Or we could create a heading "About the company" but not allowed. Better to follow instruction: use those headings only. So we will have sections: About the role, Responsibilities, Requirements, Qualifications (maybe combine with Requirements?), Skills, Benefits, Pay. The posting includes "Requirements:" list, also "Strong Candidates Will:" maybe could be Skills? Also "Who Thrives in This Role:" maybe also Skills or Qualifications. We need to decide. We must not create sections with filler text. So we need to ensure each heading has substantive content. Let's extract: - About the role: Could combine company description and role overview: "Lantern is the specialty care platform... The Director, Application & AI Security owns application and AI security end to end..." etc. That's substantive. - Responsibilities: list bullet points under "Responsibilities:" heading. - Requirements: list bullet points under "Requirements:" heading. - Qualifications: maybe we can treat "Strong Candidates Will:" as Qualifications or Skills. But we also have "Who Thrives in This Role:" which could be Skills or Qualities. Could combine into "Skills" section. - Benefits: list bullet points under "Benefits:" heading. - Pay: salary range and bonus info. - Schedule: location hybrid info. We must not include boilerplate like EEO, application instructions, etc. We must preserve all substantive information: need to include details like "Location: Hybrid - at least 3 days/wk in our NYC, NY offices". That's schedule. Also need to include "The salary range for this position is $200,000 - $275,000 annually, based on experience, skills, and qualifications. This position is also eligible for an annual bonus, separate from and in addition to the base salary range listed above. Lantern provides this range in good faith in compliance with New York's pay transparency requirements." Also need to include "About You:" section? That's more about candidate traits; maybe could be part of Skills or Qualifications. But we can include under "Skills" or "Qualifications". However "About You:" includes values like LOGIC, INCLUSION, GRIT, etc. That's substantive; we should preserve. Could put under "Skills" heading as personal attributes. We must not include cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So remove the final paragraphs about applying, EEO statement, etc. Now craft HTML. Structure:

About the role

... (company description + role overview)

Responsibilities

• Own application security across the development lifecycle, covering static, dynamic, and interactive analysis (SAST/DAST/SCA/IAST), code and dependency security, API security, and runtime protections such as WAF and API gateways, all delivered through engineering teams rather than filed as findings.
• Own AI and ML security, including model and agent security, prompt-injection and tool-use risk, and data-egress controls for third-party model providers, plus continuous AI security posture management informed by the OWASP LLM Top 10, MITRE ATLAS, and AI risk-management standards (NIST AI RMF, ISO/IEC 42001).
• Own security architecture and threat modeling, including secure-by-design review and ownership of cryptographic standards.
• Own DevSecOps and pipeline security, with scanning as a default in CI/CD and MLOps/LLMOps pipelines, release gating calibrated to risk, and software supply chain and SBOM practice.
• Own the security-review intake as a single front door with risk-based triage, reported against a turnaround commitment, so security accelerates the business rather than bottlenecking it.
• Own the application and AI security tool stack and the secure-design standards behind it.

Key Deliverables in Your First Year

maybe not a standard heading but could be part of Responsibilities? But we have content about key deliverables. Could include under Responsibilities as extra bullet? But better to have its own heading? Not in allowed list but could be considered part of Responsibilities. However we need to preserve all substantive info; we could add a subsection under Responsibilities as a paragraph. But we can also create a heading "Key Deliverables" but not in list; risk of violating instruction. Safer to incorporate into Responsibilities as a paragraph after the list? But we already used list for responsibilities; we could add a

after list describing key deliverables. That preserves info. Similarly "How You Will Work:" could be a paragraph under Responsibilities or separate? Might be part of Responsibilities. We need to decide: The instruction says use

• for any list of duties/requirements/benefits, and

  for prose. So we can have prose sections for non-list content. Thus after Responsibilities list, we can add a

  for "How You Will Work:" and "Key Deliverables in Your First Year:" as prose. Now Requirements: list. Then Qualifications/Skills: we have "Strong Candidates Will:" and "Who Thrives in This Role:" and "About You:" maybe combine into Skills section as list? Some are prose. Could make a

  for Strong Candidates Will items, and a
  for Who Thrives items, and a

  for About You. But we need to decide headings: maybe "Skills" heading for Strong Candidates Will and Who Thrives, and "Qualifications" for Requirements? However Requirements already covers qualifications. Could rename Requirements as "Requirements" and Skills as "Skills". We'll keep Requirements heading for the list of minimum requirements. Then Skills heading for Strong Candidates Will and Who Thrives and About You. But we also have "Qualifications" as a possible heading; but we already used Requirements. Could also have Qualifications separate but content overlapping. Safer to follow examples: they listed Requirements, Qualifications, Skills as separate. We could put the bullet list under Requirements, and then under Qualifications we could put education/bachelor's degree etc? Actually Requirements already includes bachelor's degree. So maybe we treat Requirements as the list, and Qualifications as the education bullet? But that splits. Better to follow instruction: use headings only when posting has real specific content. We have content for Requirements (list). We have content for Strong Candidates Will (list). We have content for Who Thrives in This Role (list). We have content for About You (prose). We could map Strong Candidates Will to "Qualifications", Who Thrives to "Skills", About You to maybe also Skills or Qualifications. But we need to avoid duplication. Let's decide: - Requirements: the list under "Requirements:" heading (minimum 8 years, etc.) - Qualifications: maybe the "Strong Candidates Will:" list (these are preferred qualifications). That fits. - Skills: maybe the "Who Thrives in This Role:" list (attributes) plus "About You:" prose. But we also have "Strong Candidates Will:" includes items like experience standing up AI golden path, etc. Those are qualifications/skills. Could be either. We'll produce:

  Requirements

  ...

  Qualifications

  ... (Strong Candidates Will)

  Skills

  ... (Who Thrives in This Role)

  About You: ... (the prose about LOGIC, INCLUSION, GRIT, etc.)

  Now Benefits: list. Pay: paragraph. Schedule: paragraph (Location hybrid). Now we must ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML fragment. Let's extract exact text for each. Company description + role overview: "About Lantern Lantern is the specialty care platform connecting people with the best care when they need it most. By curating a Network of Excellence comprised of the nation's top specialists for surgery, cancer care, infusions and more, Lantern delivers excellent care with significant cost savings to employers and their workforces. Lantern also pairs members with a dedicated care team, including Care Advocates and nurses, for the entirety of their care journey, helping them get back to good health, back to their families and back to work. With convenient access to specialists nationwide, Lantern means quality care is within driving distance for most. Lantern is trusted by the nation's largest employers to deliver care to more than 6 million members across the country. Learn more about us at lanterncare.com. Lantern is the specialty care platform, connecting people with high-quality, affordable specialty care close to home. We operate in a regulated healthcare environment (HIPAA, HITRUST, SOC 2), we handle protected health information at scale, and we are becoming an AI healthcare company, with AI adoption a top company priority. The Director, Application & AI Security owns application and AI security end to end: the security of the software and the AI systems Lantern builds. It is the seat most directly tied to our AI strategy. The job is to make it safe to move fast, building the golden paths and secure defaults that let teams ship product and adopt AI without waiting in a permission queue, while keeping PHI and external-model data egress genuinely protected. You will lead a growing function. At hire, the team includes a senior application security engineer, with several open roles to fill across security architecture, AI/ML security, DevSecOps, and product security. You will build that team and set the secure-design standards the whole engineering organization builds against. Our security philosophy is open by default, secure by design. Security exists to help the business move fast, safely, and the default answer is “yes, safely,” because guardrails are built into the platform, pipelines, and tooling rather than enforced by someone saying no. Gates exist only where risk genuinely warrants them, and even then they are automated, fast, and transparent." We can trim duplicated "Lantern is the specialty care platform" appears twice; we can keep but not duplicate? It's okay to keep as is. Now Responsibilities list: we have bullet points after "