Security Engineer, Corporate Security

All security disciplines work under the umbrella of the combined PSI (Platform, Security & Infrastructure) team: we build the paved path and tooling that hundreds of engineers around the world rely on every day to ship. Corporate Security owns the estate everyone at Flexport actually touches — the laptops, the identity provider, the SaaS sprawl, the browser. Get it right and nobody notices. Get it wrong and it's the fastest way into everything else we're trying to protect.

This is a security engineering role, not an IT support role. You'll spend your time writing code and shipping automation, not administering a helpdesk queue or babysitting a ticket tray.

What you'll do

• Identity & access
  • Advance our identity posture: SSO coverage, phishing-resistant MFA rollout, SCIM lifecycle automation, and least-privilege access across the SaaS and cloud estate.
  • Build the detections and guardrails that catch account takeover, MFA fatigue attacks, and session token theft before they turn into incidents.
• Endpoint & device lifecycle
  • Write and ship device policy as code — configuration profiles, remediation scripts, and enforcement rules across macOS and Windows — with staged rollout and rollback built in from day one.
  • Maintain and improve our EDR stack's detection and response coverage across the fleet.
• SaaS posture
  • Reduce SaaS risk at scale through SSPM tooling and automation, including detection of risky OAuth grants, shadow IT, and configuration drift across our critical SaaS applications.
  • Own security configuration for the SaaS tools hundreds of Flexporters use daily (Google Workspace, Slack, and similar), and keep pace as we add AI agents and MCP integrations to that surface.
• Automation & enablement
  • Automate the parts of corporate security that don't need a human — device provisioning, access reviews, vendor security questionnaires — so the team scales with headcount instead of straining against it.
  • Write runbooks and documentation that make the rest of the team more capable, and partner with IT and People teams to ship controls that don't create the friction that drives people to workarounds.

You should have

• Typically 2–5 years of experience in corporate, enterprise, or IT security engineering — we care more about what you've shipped than the exact number. If you meet most of this, apply; we'd rather see your work than filter you out on a résumé line.
• Hands-on experience with modern endpoint management and EDR tooling (Jamf, Kandji, Intune, CrowdStrike, SentinelOne, or similar).
• Working knowledge of identity protocols (SAML, OIDC, SCIM) and a major identity provider (Okta, Entra, Google Workspace, or similar).
• Comfort writing real code or scripts (Python, Go, or similar) to replace manual, ticket-driven work with automation.
• Clear, practical communicator who can explain a control tradeoff to an engineer, a salesperson, and a VP without changing the facts.

Nice to have

• Experience with SSPM tooling and OAuth-grant governance.
• Exposure to DLP or insider-risk tooling.
• Familiarity with infrastructure-as-code (Terraform) for managing security configuration.
• A point of view on how agentic AI tools and MCP integrations change what corporate security needs to watch for
• Interest in growing into a broader corporate security or detection engineering scope over time.

How we work

• We're in the San Francisco office regularly to work through incidents and detection design in person.
• We stay closely aligned with teammates on other continents via Slack, video, and async docs.
• We have the latest hardware and software, including frontier AI models on day one.
• We're agile, but not dogmatic. Teams decide how they work best.

Why this role is special

• Broad, real ownership: at this level elsewhere you might own a slice of a control; here you'll own well-defined projects end to end, from design through rollout, with support scoping the ambiguous parts.
• Every device policy or identity control you ship protects every Flexporter, immediately — no six-month rollout to a subset of customers.
• You're part of PSI: security is treated as infrastructure to build, not policy to enforce, and platform and infrastructure engineers are a Slack message away.