Security Engineer Intern

About the role Our Security team protects Swile's products, data and engineering platform. We work with a simple principle: when something is recurring, we automate it, and when a security requirement can become code, we write the code. As a Security Engineer Intern, you will not shadow the team, you will be part of it. You will handle real alerts, run your own audits and own projects end to end, with a dedicated mentor in the team throughout your internship. What you will do Detection and response Handle day to day security alerts: triage, investigate, qualify, escalate when needed. Improve what we detect: reduce noise, close detection gaps, propose new signals. Automate the recurring: when an alert or a manual check keeps coming back, script it away. This is where we expect you to leave a mark. Security audits Run targeted audits, from a few days to a few weeks, on applications, configurations or third party providers. Turn findings into a prioritised remediation plan rather than a list of tickets. Projects you will own Ad hoc security projects across the engineering platform. Security review and hardening of the tools and integrations we rely on (Dust, third party providers, internal integrations). Fraud Support fraud investigations: dig, follow the trail, understand how an abuse pattern works and how we could detect it earlier. What we are looking for This is an internship, so how you think matters more than what you already know. You learn fast and you are genuinely curious about security. You are a doer: you answer quickly, you close loops, you do not let things sit. You are pragmatic: you calibrate your response to the actual level of urgency and risk, and you know that not everything is a P1. You are open minded and comfortable asking questions across engineering teams. You are comfortable working in English, written and spoken. You have some scripting ability (Python or equivalent) and a basic understanding of web applications, APIs and cloud environments. Nice to have that would make you stand out Personal projects, CTFs, homelab, bug bounty or security writeups. First exposure to a SIEM, to detection rules or to log analysis at scale. Curiosity for fraud and abuse patterns in a financial product. What this internship is not Not a pure GRC, compliance or policy writing internship. Not a pentest internship. Not a role where you watch dashboards without changing them. Practical details Location: Paris preferred. Duration and start date: 3-6 months internship, ASAP or from January 2027 Mentor: a Security Engineer from the team.

Requirements: requirement can become code, we write the code. As a Security Engineer Intern, you will not shadow the team, you will be part of it. You will handle real alerts, run your own audits and own projects end to end, with a dedicated mentor in the team throughout your internship. What you will do Detection and response Handle day to day security alerts: triage, investigate, qualify, escalate when needed. Improve what we detect: reduce noise, close detection gaps, propose new signals. Automate the recurring: when an alert or a manual check keeps coming back, script it away. This is where we expect you to leave a mark. Security audits Run targeted audits, from a few days to a few weeks, on applications, configurations or third party providers. Turn findings into a prioritised remediation plan rather than a list of tickets. Projects you will own Ad hoc security projects across the engineering platform. Security review and hardening of the tools and integrations we rely on (Dust, third party providers, internal integrations). Fraud Support fraud investigations: dig, follow the trail, understand how an abuse pattern works and how we could detect it earlier. What we are looking for This is an internship, so how you think matters more than what you already know. You learn fast and you are genuinely curious about security. You are a doer: you answer quickly, you close loops, you do not let things sit. You are pragmatic: you calibrate your response to the actual level of urgency and risk, and you know that not everything is a P1. You are open minded and comfortable asking questions across engineering teams. You are comfortable working in English, written and spoken. You have some scripting ability (Python or equivalent) and a basic understanding of web applications, APIs and cloud environments. Nice to have that would make you stand out Personal projects, CTFs, homelab, bug bounty or security writeups. First exposure to a SIEM, to detection rules or to log analysis at scale. Curiosity for fraud and abuse patterns in a financial product. What this internship is not Not a pure GRC, compliance or policy writing internship. Not a pentest internship. Not a role where you watch dashboards without changing them. Practical details Location: Paris preferred. Duration and start date: 3-6 months internship, ASAP or from January 2027 Mentor: a Security Engineer from the team.

requirement can become code, we write the code. As a Security Engineer Intern, you will not shadow the team, you will be part of it. You will handle real alerts, run your own audits and own projects end to end, with a dedicated mentor in the team throughout your internship. What you will do Detection and response Handle day to day security alerts: triage, investigate, qualify, escalate when needed. Improve what we detect: reduce noise, close detection gaps, propose new signals. Automate the recurring: when an alert or a manual check keeps coming back, script it away. This is where we expect you to leave a mark. Security audits Run targeted audits, from a few days to a few weeks, on applications, configurations or third party providers. Turn findings into a prioritised remediation plan rather than a list of tickets. Projects you will own Ad hoc security projects across the engineering platform. Security review and hardening of the tools and integrations we rely on (Dust, third party providers, internal integrations). Fraud Support fraud investigations: dig, follow the trail, understand how an abuse pattern works and how we could detect it earlier. What we are looking for This is an internship, so how you think matters more than what you already know. You learn fast and you are genuinely curious about security. You are a doer: you answer quickly, you close loops, you do not let things sit. You are pragmatic: you calibrate your response to the actual level of urgency and risk, and you know that not everything is a P1. You are open minded and comfortable asking questions across engineering teams. You are comfortable working in English, written and spoken. You have some scripting ability (Python or equivalent) and a basic understanding of web applications, APIs and cloud environments. Nice to have that would make you stand out Personal projects, CTFs, homelab, bug bounty or security writeups. First exposure to a SIEM, to detection rules or to log analysis at scale. Curio