Product Security Technical Lead

Job description

Work Schedule Standard (Mon-Fri) Environmental Conditions Office Job Description DESCRIPTIONJoin Thermo Fisher Scientific, the world leader in serving science, and help build secure software that enables our customers to make the world healthier, cleaner, and safer. As a Product Security Technical Lead, you will drive the technical implementation of key DevSecOps practices across software development teams. You will define technical standards, provide implementation guidance, and help engineering teams embed security into their CI/CD pipelines and software development lifecycle. Working closely with Product Security, CyberOps, DevOps, Software Engineering, and Architecture teams, you will promote consistent, scalable, and practical security solutions that support secure software delivery. RESPONSIBILITIESDefine technical direction, standards, and implementation guidance for CI/CD security. Lead the implementation of SBOM, SAST, Secret Scanning, Code Signing, and secure build practices across engineering teams. Review technical designs, CI/CD pipeline changes, automation scripts, and implementation quality. Provide hands-on technical guidance, troubleshooting, and reusable implementation patterns. Collaborate with CyberOps, DevOps, Software Engineering, Architecture, and Product Security teams. Ensure security practices are consistently embedded throughout the software development lifecycle (SDLC). Identify technical risks, dependencies, and implementation gaps early to support successful delivery. REQUIREMENTSStrong background in DevOps, CI/CD, and software engineering. 6 -8 years of experience with DevSecOps practices and security tooling. Ability to define technical standards and translate them into practical implementation guidance. Strong technical review, architecture, and problem-solving skills. Experience working across multiple engineering teams and aligning technical stakeholders. Strong written and verbal communication skills. SUCCESS IN THIS ROLESecurity controls are implemented consistently across development teams. Engineering teams have clear technical standards, reusable scripts, and practical guidance. Adoption of SBOM, SAST, Secret Scanning, and Code Signing is streamlined and scalable. Technical risks and dependencies are identified early. Security is embedded into the software delivery process rather than introduced at the end.