Compliance Engineer
- Location
- Bellevue, WA
- Employment
- Full Time
- Work model
- On-Site
- Level
- Mid
- H-1B history
- 498 approvals (FY2023)
- Posted
Skills
About this role
To get the best candidate experience, please consider applying for a maximum of 3 roles within 12 months to ensure you are not duplicating efforts. Job Category Software Engineering Job Details About Salesforce Salesforce is the #1 AI CRM, where humans with agents drive customer success together. Here, ambition meets action. Tech meets trust. And innovation isn’t a buzzword — it’s a way of life. The world of work as we know it is changing and we're looking for Trailblazers who are passionate about bettering business and the world through AI, driving innovation, and keeping Salesforce's core values at the heart of it all. Ready to level-up your career at the company leading workforce transformation in the agentic era? You’re in the right place! Agentforce is the future of AI, and you are the future of Salesforce. We are looking for a Principal Compliance Engineer who can take a FedRAMP or DoD requirement and determine whether the system meets it. You review the architecture and the running implementation for government cloud services and for on-prem products: network design, access, cryptography, containers, data stores, and the pipeline that builds them. You are part of the engineering team and evaluate the system changes before they happen. You evaluate government-cloud and on-prem environments against FedRAMP, DoD, FIPS 140-3, STIG, and CIS requirements. You identify gaps in the running system and in the build, determine the remediation, and drive that remediation through implementation until the control is met. This includes live clusters and product configuration, FIPS validation in the pipeline and the image, and vulnerabilities in the versions that are deployed. You cover both cloud and on-premises deployment models. Government cloud work is FedRAMP Rev 5 and DoD IL5: what the platform inherits, what the service implements, and whether a change is significant. On-prem work covers the stack the customer runs, including the operating system, Kubernetes, the container runtime, databases, and the application. You provide secure-configuration recommendations, support customer authority-to-operate efforts, conduct CVE reviews, determine compensating controls where a requirement cannot be met directly, and manage end-of-life monitoring. What You'll Actually Be Doing: Review architectural designs for new products, system changes, and FedRAMP onboarding for security and compliance impact. This includes network security, boundary protection, ingress and egress, identity and access, privileged access, service accounts, tenant isolation, encryption in transit and at rest, key management and PKI, audit logging, session management, backup and recovery, and privacy and PII handling. Apply FedRAMP Rev 5 and DoD IL5 as engineering requirements. Decide what is inherited, what is shared, what the product must implement, and what remains the customer's responsibility. Support significant-change packages, System Security Plan updates, and control narratives that cite the implementation. Evaluate STIG and CIS controls for operating systems, Kubernetes, container platforms, and databases. Review scanner findings, determine false positives, identify compensating controls, and identify gaps in scan coverage. Write the finding, the evidence, and the recommended remediation.. Evaluate FIPS 140-2/3 adherence in the build and at runtime. Including approved module and provider selection, TLS configuration, and detection of non-approved algorithms and providers in product code, connectors, and base images. Follow the control into the engineering system. Evaluate Dockerfiles, Helm charts, Kubernetes manifests, CI logs, and service configuration. Use CI/CD and static analysis, including Semgrep, to turn compliance checks into repeatable pipeline gates. Decide when a finding is a real deviation and when the pipeline or the control interpretation is wrong. Own vulnerability evidence for authorized systems. Triage KEV and critical CVEs against the