Job Details
Security Engineer
Sargent and Lundy · Chicago, IL
Tailor My Resume
Start free. No credit card.
Required Experience
- Bachelor's degree in Computer Science, Information Systems, Cybersecurity, or a related field. Equivalent professional experience will be considered.
- 5+ years of hands-on Security Engineering experience with demonstrated ownership of enterprise security platforms in production. Pure governance, audit, or policy-only backgrounds will not match the work in this role.
- Deep, hands-on IAM lifecycle experience with Microsoft Entra (SSO, MFA, conditional access, lifecycle workflows) and applied Zero Trust implementation.
- Hands-on cloud security experience with Microsoft Azure (required) and Oracle Cloud Infrastructure (strongly preferred), including technical configuration of native security services.
- Hands-on configuration and operation of the Palo Alto security platform: Prisma (Access and Cloud), Cortex XDR, and XSIAM.
- Implementation-level experience with Microsoft Purview for DLP, including policy authoring, classification, labeling, tuning, and incident handling.
- Working knowledge of AI risks (data exposure, prompt injection, model misuse, shadow AI) and the controls used to mitigate them in an enterprise setting.
- Comfort working across on-prem and cloud environments and across Windows, macOS, and Linux endpoints.
- Familiarity with compliance frameworks (ISO 27001, NIST 800-171, CMMC Level 2, SOC 2) and the ability to translate a control requirement into a working configuration.
- Certifications: CompTIA Security+ or (ISC)² SSCP or PCCSE (Palo Alto Networks Certified Cloud Security Engineer) an equivalent foundational technical certification.
Preferred Experience
- Microsoft Azure Security certification (AZ-500 or equivalent).
- Microsoft Purview Information Protection and DLP certification or equivalent.
- Oracle Cloud Infrastructure security credentials.
- Microsoft Cybersecurity Architect (SC-100),
- CISSP or CCSP.
Soft Skills
- Strong written and verbal communication. You can walk an engineer through a config in one conversation and a business stakeholder through the impact in the next.
- Bias for action. You would rather build a working control and iterate than spend weeks producing a perfect document.
- Comfort with ambiguity. You can take a vague security ask and break it into a concrete configuration plan.
- Collaboration across teams. You will work daily with SOC, IT Infrastructure, Cloud, App Dev, and GRC, and the role only works if those partnerships do.
- Operational discipline. You document what you build, version your configurations, and leave the next engineer better than you found it.