AppSec Engineer

About the role

ShipMonk is a fast-growing 3PL whose operations run 24/7 across Europe and the US. Our Security team covers compliance, incident response, identity, and security operations for the whole company. We're hiring an engineer who will work across all of these areas rather than specialize in one. Your time will be split roughly evenly between day-to-day operations and building the capabilities we don't have yet. AI is part of how we work. We expect you to adapt quickly and use AI tools to improve work efficiency and strengthen our company's security posture.

What you'll do

• Security culture and practices: challenge existing development practices and drive a security-first mindset across engineering teams.
• Vulnerability management and penetration testing: identify and assess vulnerabilities in our applications through internal penetration testing.
• CI/CD security automation: build and maintain automated vulnerability discovery (SAST, DAST, dependency and secret scanning) in the CI/CD pipeline.
• Secure developer education: educate developers on secure coding practices so security issues are caught before code reaches production.
• Identity and access: own Okta security policies, Okta privileged access; audit integrated apps; run a regular access review cycle, secure access requests process.
• Incident response and investigations: triage, contain and analyse incidents; reconstruct timelines; provide evidence to Legal and HR; review reported phishing.
• Detection and monitoring: automatically read and process logs, and set up automated playbooks for our core tooling such as Okta, AWS, Snowflake, Google Workspace, and our ShipMonk app; build detection engineering and threat hunting capabilities.
• Cloud, SaaS and endpoint security: secure Google Workspace, SSO/SAML integrations and third-party OAuth apps; define MDM security baselines; give security input early in design decisions.
• Application security: understanding of vulnerabilities, patching, stakeholder management.
• Compliance and risk: support SOC 2 Type II, GDPR, and ISO27001 security frameworks; coordinate penetration tests and follow up on remediation. Respond to customer security questionnaires; run vendor assessments and subprocessor management; maintain the risk register.
• AI-assisted security: use AI tools for investigations, log analysis, detection writing, automation and compliance work; help shape how the team uses AI safely and effectively.
• Awareness: run security communications, phishing simulations and tabletop exercises.

What you bring

• 3+ years in security engineering, security operations or similar role
• Hands-on experience with incident response and log analysis.
• Strong IAM skills: Okta or a similar identity provider, SSO/SAML, MFA
• Experience securing cloud and SaaS environments such as Google Workspace, GCP, or AWS.
• Experience with a SIEM and writing detection rules.
• Scripting skills (Python or similar) and comfort working with APIs.
• Working knowledge of SOC 2 or ISO 27001.
• Hands-on use of AI tools such as LLM assistants or coding agents in daily work, alongside an agile mindset with a habit of learning and adapting.
• Fluency in English and the ability to push security work forward across teams.

Nice to have: Vanta, Datadog, Snowflake, GitLab, or threat hunting experience.

Why join

You’ll be building a security function, not maintaining one. Half your time goes to things we don’t have yet: detection engineering, automated playbooks, threat hunting. You’ll design them, pick the approach, and see them run in production.

The scope is wide on purpose. You’ll touch identity, incident response, cloud, compliance, and awareness in the same quarter, so you’ll grow faster than in a team where one person owns one tool. Our stack is modern and real: Okta, AWS, Snowflake, Google Workspace, and our own ShipMonk platform, which runs warehouses across Europe and the US around the clock.

We use AI in daily work, not as a slide in a strategy deck. You’ll get room to try new tools for investigations, log analysis, and detection writing, and to help decide how the team uses them safely.