Engineering Manager, Security *EU​/UK remote*(m​/f​/d

ABOUT US

Pliant is a European fintech specializing in B2B payment solutions. Our modular, API-first platform helps businesses streamline spending, improve cash flow, and integrate payments into their financial workflows. Designed for industries with complex payment needs, such as travel and fleet, Pliant enables greater efficiency, control, and profitability.

We serve two primary customer segments:

• Companies looking to optimize operational processes through intuitive apps and APIs, gaining control, automation, and financial flexibility through extended credit lines.

• Businesses such as financial software platforms, ERP providers, and banks that want to launch or enhance their credit card offerings using Pliant's embedded finance and white-label solutions.

Founded in 2020 and headquartered in Berlin, Pliant supports over 4,000 businesses and more than 20 partners globally. As a licensed e-money institution (EMI), we issue credit cards in 11 currencies across more than 30 countries, helping companies streamline and simplify payments.

Learn more at

Pliant builds corporate payment infrastructure, and the security team's job is to keep that infrastructure secure and compliant without slowing down the engineers building on it. This is the first Engineering Manager role for a team of two security engineers already covering Dev Sec Ops , cloud security, and compliance today. You'll take over the people side while shaping where the function goes next, staying technical enough to drive lower-priority initiatives yourself, participate in reviews, and step in during incidents when the team needs you.

• Own the security foundations the rest of engineering builds on: secure-by-default Terraform and Docker modules, hardened images for ECS and EKS workloads, and guardrails built into the developer platform rather than added afterwards.

• Drive cloud security posture day to day: remediating findings from Wiz, keeping IAM, KMS, Cloud Trail, and Guard Duty tuned as Pliant scales, and ensuring the alerts that fire are ones people should actually act on.

• Automate compliance evidence collection for PCI DSS, SOC 2, ISO 27001, and DORA so audits stop being a scramble.

• Run vulnerability management and incident response end to end: triage, SLAs, remediation, and post-mortems.

• Build the application security practice through threat modeling, architecture reviews, and secure coding guidance that product teams actually use.

• Use and build AI-native security tooling for Vuln Ops, red-teaming, and incident response as the threat landscape evolves.

• Grow the team: two engineers are in place today, and who you hire next sets the technical bar for security at Pliant for a long time.

• Hands-on background in Dev Sec Ops  or cloud security, ideally with real ownership of an AWS environment. IAM, KMS, Cloud Trail, Guard Duty, and SCPs are things you have worked with directly.

• Proficiency in Terraform, including the ability to write secure, reusable modules from scratch.

• Experience securing containerized workloads (ECS, EKS, or Kubernetes), including hardened base images and admission controllers.

• Scripting ability in Python, Bash, or Type Script sufficient to automate compliance checks and triage workflows rather than doing them by hand each quarter.

• Working knowledge of PCI DSS, SOC 2, and/or ISO 27001, plus experience running vulnerability management at scale or leading incident response for something that mattered.

• Experience managing engineers or leading technical work where people trusted your calls before you had the title, including at least one hiring decision worth learning from.

• Ability to explain a security risk clearly to non-security audiences without losing accuracy.

• A point of view on AI as an attacker's tool and how vulnerability response needs to change as discovery-to-exploitation windows keep shrinking.

• Comfort with AI-assisted development tools, and the same rigour reviewing AI-generated PRs as any other.

The first few months are mostly absorbing what is already running and meeting the people who depend on it:
Platform Core, SRE, and the product teams who will come to you when…