> Markdown version of [/jobs/ext/3697378-software-engineer-3-security](https://www.wearedevelopers.com/jobs/ext/3697378-software-engineer-3-security). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Software Engineer 3, Security

- **Company:** Commission Junction LLC
- **Location:** Agoura Hills, CA, United States
- **Experience:** Experienced
- **Salary:** $88,540.0
- **Contract:** Temporary contract
- **Skills:** Java (Programming Language), Artificial Intelligence, Amazon Web Services, Software System Penetration Testing, JIRA, Continuous Integration, DevOps, Issue Tracking Systems, Java Virtual Machine (JVM), Python (Programming Language), Scala (Programming Language), Software Vulnerability Management, Cloud Platform System, Software Security, Veracode, Kotlin, Gitlab-ci, Kubernetes, Devsecops, Static Application Security Testing, Programming Languages, Dynamic Application Security Testing
- **Published:** October 12, 2026
- **Apply:** https://www.juju.com/job/1_publicisgroupe2-168582

## About the Role

into GitLab CI/CD pipelines so issues are caught at build and merge-request time, not only in point-in-time scans + Contribute to security standards and best practices, and coach teams through adopting them + Help verify AI-proposed fixes and risk assessments against the actual code, config, and runtime context before they're accepted Technologies We Use: + Application security tools: Veracode, Wiz + SAST/DAST tooling embedded in CI/CD + Vulnerability management and ticketing systems (Jira or equivalent) + Cloud environments: AWS, Kubernetes + Infrastructure as Code: Terraform and Kubernetes manifests + CI/CD pipelines and developer platforms (GitLab CI/CD, ArgoCD) + Programming languages: comfortable reading and fixing code in at least one of Python, Go, or the JVM languages (Java, Scala, Kotlin) - CJ's codebases span all of these **Qualifications** What we look for: + 3+ years of software or infrastructure engineering experience, with hands-on
exposure to application or infrastructure security + Bachelor's degree or equivalent experience + Can read code and infrastructure config, not just interpret scanner output + Understands common vulnerability classes and how to reason about exploitability and impact + Enough AWS/Kubernetes fluency to have credible technical conversations with the teams that operate them + Comfortable translating technical findings for non-security stakeholders and driving fixes through influence rather than authority Nice to Have: + Experience wiring automated security scanning into CI/CD pipelines + Familiarity with threat modeling and secure-by-design review + Interest in emerging threats, including AI systems, and willingness to learn fast What Success Looks Like: + Engineering teams understand why a finding matters (or doesn't) instead of closing tickets to clear a queue + Audits and client security reviews go smoothly because evidence and answers are ready, not

## Description

As a Software Engineer 3 focused on security within Engineering Experience (EngExp), you help drive the team's evolution from DevOps to DevSecOps.
You work with engineering teams across the org to find, prioritize, and close out vulnerabilities in CJ's code and infrastructure, and you help serve as a technical bridge between engineering and the Global Security Office (GSO), auditors, and clients on security topics.
You turn raw findings (Wiz, Veracode, pentest reports) into evidence-backed, actionable guidance.
This is a hands-on role: you read and write code, and when you have the context to fix a vulnerability yourself, you do - not just file a ticket and hand it off. **Responsibilities** What You'll Do: Triage and respond to vulnerabilities identified through tools such as Wiz, Veracode, and penetration tests, and help drive them to resolution + Analyze infrastructure and codebases to produce evidence-backed answers about real risk - exploitability, reachability, and impact - rather than relaying scanner severity alone + Help operate the vulnerability queue end to end: intake, prioritization, tracking, and validation of fixes + Partner with engineers to articulate the actual threat (or lack of one) behind a code or infrastructure finding + Remediate findings directly when you have the context - whether in EngExp's own infrastructure or another team's - and drive remediation through partnership where you don't + Integrate security checks (SAST/DAST)