Source Software LEAD Security Engineer - Software Supply Chain

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).

Regular

Language Fluency:
English (Required)

Work Shift:

1st shift (United States of America)

Please review the following job description:

The Open Source Software (OSS) Lead Security Engineer owns the practical execution of open source software security across governance, engineering workflows, tooling, automation, and risk reduction. The role combines security program leadership with hands‑on technical delivery to build secure‑by‑default OSS lifecycle capabilities and reduce software supply chain exposure.

Responsibility for OSS security governance, software supply chain security, engineering enablement, CI/CD control integration, and proactive management of dependency, build, package, artifact, and provenance risks. The Open Source Software and Software Supply Chain Security Lead Engineer is responsible for defining and operating enterprise governance, standards, processes, and preventative controls that enable the secure use of open source software and reduce software supply chain risk across the software development lifecycle.

This role partners closely with CI/CD, Dev Sec Ops , application security, engineering, platform, and risk teams to ensure open source components, build pipelines, artifacts, package sources, and release processes are approved, continuously monitored, remediated, and safely integrated into enterprise applications and delivery pipelines.

• Team Leadership and Talent Development:
  Lead, mentor, and develop a team of security engineers, analysts, and contractors responsible for open source software governance and software supply chain security initiatives. Establish goals, drive accountability, provide ongoing coaching, and support career development to build a high‑performing security organization.
• Governance and Standards:
  Define policies, standards, and control requirements for approved open source usage, dependency hygiene, SBOM generation, secure package sourcing, and software supply chain risk management.
• Secure OSS Lifecycle Management:
  Establish processes for OSS intake, approval, tracking, ownership, version management, vulnerability remediation, end‑of‑life component retirement, and exception governance.
• CI/CD Preventative Controls:
  Work with CI/CD and platform engineering teams to design and implement automated security gates for curated OSS usage, dependency scanning, license checks, artifact validation, provenance controls, build‑time enforcement, and policy‑based blocking of high‑risk components.
• Software Supply Chain Risk Reduction:
  Identify and reduce risks related to vulnerable dependencies, malicious packages, dependency confusion, typo squatting, compromised maintainers, insecure build artifacts, and unauthorized package sources.
• Software Supply Chain Security:
  Establish controls for trusted package sources, dependency provenance, build integrity, artifact signing, repository hygiene, tamper resistance, and secure release practices.
• Threat Response and Incident Detection:
  Establish capabilities to rapidly identify, assess, and respond to open source supply chain threats, malicious package campaigns, zero‑day vulnerabilities, compromised dependencies, and software supply chain security incidents.
• Tooling and Automation:
  Support the deployment, tuning, and integration of software composition analysis, SBOM, package repository, vulnerability management, and developer workflow tools.
• Risk Reporting and Metrics:
  Develop reporting that measures OSS risk posture, remediation velocity, policy exceptions,…