{"active":true,"apply_url":"https://jobs.lever.co/swile/681e64ef-03ec-4a6e-90ad-ecce9d48bd09/apply","company":{"claimed":false,"name":"Swile","slug":"swile","website":"https://www.swile.co"},"countries":["FR"],"employment_type":"full-time","first_seen_at":"2026-10-15T12:24:26Z","getwork_url":"https://getwork.dev/jobs/lv-swile-681e64ef-03ec-4a6e-90ad-ecce9d48bd09/","id":"lv-swile-681e64ef-03ec-4a6e-90ad-ecce9d48bd09","injection_flag":false,"last_seen_at":"2026-10-28T15:00:11Z","location":"Paris, France","published_at":"2026-08-26T13:20:02Z","regions":["europe"],"remote":"hybrid","role_family":"security","salary":null,"seniority":"staff","stack":[],"stack_mentioned":[],"title":"Staff Security Engineer","untrusted_description":"Build security platforms, not security processes\nWe are looking for a Staff Security Engineer to strengthen the security of our products, data and engineering platform.\nThis is a highly technical and hands-on role. You will work closely with Engineering teams to continuously harden our systems while helping design the next generation of our security architecture.\nYou will operate across two horizons:\nStrengthen security today: continuously harden our applications, access controls and data-protection mechanisms against evolving threats.\nBuild the privacy architecture of tomorrow: move beyond traditional perimeter and access-control security by designing systems where sensitive data is cryptographically isolated, minimally exposed, and increasingly usable without being directly revealed.\nThe ultimate objective is not simply to make Swile harder to breach. It is to make a breach increasingly uninteresting, because there is less usable data available to steal.\n\nWhat you will do\nWe want Security Engineering to create capabilities that scale across hundreds of engineers.\n\nYou will:\n\n-\nIdentify and reduce high-impact security risks across our applications, APIs and internal tools.\n\n-\nStrengthen authentication, authorization and access controls.\n\n-\nImprove the protection of sensitive and personal data.\n\n-\nDesign controls that limit the blast radius of compromised accounts, services or infrastructure.\n\n-\nImprove security monitoring, auditability and detection of suspicious access patterns.\n\n-\nPerform threat modelling and targeted security reviews.\n\n-\nBuild reusable security capabilities directly into our engineering platform and development lifecycle.\n\n-\nContribute to long-term architectures around data isolation, encryption, tokenisation and privacy-preserving systems.\n\n-\nPartner with engineering teams to address systemic security risks rather than individual findings.\n\nWhere possible, a security requirement should become code rather than documentation.\n\nWhat we are looking for\nYou are first and foremost a strong engineer.\n\nYou have significant experience building or securing production software and distributed systems. You are comfortable reading and writing production code, designing systems and working directly with Engineering teams.\n\nYou have deep security engineering expertise and strong experience in several of the following areas:\n\n-\nApplication and Product Security\n\n-\nAPI Security\n\n-\nIAM, authentication and authorization\n\n-\nOAuth2 / OIDC, WebAuthn / FIDO2\n\n-\nRBAC / ABAC and privilege management\n\n-\nCloud security\n\n-\nCryptography, KMS / HSM and envelope encryption\n\n-\nTokenisation and secrets management\n\n-\nData Security and Privacy Engineering\n\n-\nThreat modelling and secure software architecture\n\n-\nSecurity monitoring and detection\n\nStronger attacker mindset\n\nYou naturally ask:\n\n-\nWhat happens if this employee becomes malicious?\n\n-\nWhat happens if this backend is compromised?\n\n-\nWhat happens if someone dumps this database?\n\n-\nCan this endpoint be called directly?\n\n-\nHow much data can one account access before we notice?\n\n-\nWhere else does this information get replicated?\n\n-\nWhy do we have this data at all?\n\nYou think in terms of attack paths, blast radius and least privilege, not just compliance requirements.\n\nPragmatism\n\nYou know that security engineering is a prioritisation problem.\n\nYou can distinguish between:\n\n-\nsomething that needs to be fixed this week;\n\n-\nsomething that requires an architectural redesign;\n\n-\nsomething cryptographically elegant but operationally unnecessary.\n\nYou are comfortable deploying simple, high-impact controls quickly while designing stronger long-term foundations.\n\nWhat would make you stand out\n\nExperience with:\n\n-\nlarge-scale SaaS or fintech platforms;\n\n-\nhighly sensitive or regulated data;\n\n-\nmulti-tenant architectures;\n\n-\ninsider risk or data-loss prevention;\n\n-\nadvanced cryptographic or privacy-enhancing technologies.\n\nWhat success looks like\n\n-\nSensitive data is exposed to fewer systems and people.\n\n-\nAccess to sensitive resources is increasingly scoped, attributable and auditable.\n\n-\nCompromising a single account or service has a limited blast radius.\n\n-\nSecurity controls are increasingly enforced by the platform rather than by process.\n\n-\nProduct teams can build secure systems faster and with less friction.\n\nWhat this role is not\n\nThis is not primarily a GRC, SOC, compliance, policy-writing or penetration-testing role.\n\nThose disciplines are important, but this role exists to change how our products and systems are engineered.\n\nWe expect this person to design systems, write code, influence architecture and ship security capabilities into production.\n\nLocalization of this position\nThis position can be based at our offices in Paris, Toulouse, or Montpellier on a flex-remote basis.","url":"https://jobs.lever.co/swile/681e64ef-03ec-4a6e-90ad-ecce9d48bd09"}