Senior Application Security Engineer

• Cross-area by default. The security tooling, the findings pipeline and application-layer incident support are yours across all of Product Engineering. When a product needs focused work, such as a security epic for Connect or Salonized, you pick it up with that team, agreed with its Head of Engineering. Infrastructure security stays with Developer Experience and Platform Core.
• Fix with the team, not for the team. You pair on remediation and the team's engineers merge the fix, so the knowledge stays where the code lives.
• Guardrails over gates. The default is a secure path that is quicker to use than to bypass: shared libraries, pipeline templates, pre-commit checks. Blocking is reserved for critical findings on new code and agreed with the area.
• One queue. Findings land in DefectDojo and move into the team's backlog or Now/Next like any other work. There is no parallel security process.
• Through the champions. You work with each team's Security Champion and the Security Champions guild. In eighteen months a threat model or an incident should not need you in the room.
• Your own roadmap. You keep a short Now/Next/Later for security, agreed each quarter with the Heads of Engineering, separate from the DevX roadmap.
• Posture, not paperwork. You present the security posture per area to the CTO and VP of Engineering on a fixed cadence, measured against the DevSecOps Maturity Model.

• Owning application security across Product Engineering and working hands-on with the teams to remediate vulnerabilities in our codebases, from authentication and session handling to payments flows and public APIs, including specific security epics for a product such as Connect or Salonized.
• Owning the security tooling across all areas (secrets detection, dependency scanning, SAST, DefectDojo, threat modelling) and landing SAST in our pipelines: completing the proof of concept with the SAST vendors we are evaluating on two pilot teams, the Marketplace Checkout and Identity team and a SaaS team, tuning rules until engineers trust the output, and feeding every finding into DefectDojo rather than a new dashboard.
• Making DefectDojo work without a human in the loop: team ownership synced from our service catalogue, every team's repositories covered, and an agreed rule for which findings block a pipeline and which only report.
• Building secure defaults into the paved road so the secure way is the easy way: authentication and session libraries, input validation, secrets handling, dependency and container checks in the pipeline templates teams already use.
• Running threat modelling with teams before the work is fully scoped, using and improving our AI-based threat modeller so that it answers an engineer's question plainly and produces backlog items with owners and dates.
• Triaging findings from scanners, the annual penetration test and external reports, agreeing severity and ownership with the team, and tracking them to closure in DefectDojo against our severity SLAs.
• Being the first security call for application-layer incidents across Product Engineering: leading the technical side, assessing with Legal whether personal data was exposed, writing the postmortem actions, and working with Customer Support and Payments on fraud and customer-flagged cases including phishing.
• Owning our security vendor relationships: the annual penetration-test cycle with our testing partner (scoping, scheduling, remediation planning), the responsible-disclosure programme and the security@ inbox, and the SAST vendor once selected.
• Acting as the security reviewer in our third-party risk process for new vendors and integrations, and answering the security questionnaires our partners send us.
• Measuring the security posture per area against the DevSecOps Maturity Model and presenting it to the CTO and VP of Engineering on a fixed cadence.
• Growing the Security Champions programme with the Head of Developer Experience: a named champion in every team, demo-led guild sessions, and two security improvements per area shipped through team backlogs each quarter.
• Keeping a short, current security roadmap (Now/Next/Later), agreed with the Heads of Engineering each quarter and visible to Product Engineering.

• You have worked as an application security engineer, or as a backend engineer who owned security for a product, and you fix vulnerabilities yourself rather than only reporting them.
• You read and write production code in at least one of our languages (Java, Ruby, TypeScript) well enough to pair on a fix, review a merge request and spot the second bug behind the first.
• You know the OWASP ASVS and Top 10 from code rather than slides, and you can run a threat model that ends in backlog items rather than a document.
• You have put SAST, dependency scanning or secrets detection into CI pipelines (GitLab CI or GitHub Actions) and tuned the rules so developers kept trusting them.
• You have worked with a vulnerability management platform and you know how to keep a finding moving to closure without chasing people by hand.
• You understand how authentication, sessions, authorisation and payments flows break in practice: IDOR, token and magic-link misuse, JWT validation mistakes, race conditions, injection, and the odd device-id collision.
• You know enough AWS and Kubernetes to see where application security meets the platform, and when to hand a problem to the platform team instead.
• You explain risk in plain language to engineers, Heads of Engineering and non-technical leaders, and you can say "this one is fine" as clearly as "this one is not".
• You transfer skills on purpose: your measure of success is a team that does not need you for the next one.
• You use AI tooling as a normal part of the work, for threat modelling, code review and reading unfamiliar codebases, and you know where it is wrong.

• Experience in a marketplace, payments or SaaS business handling card data and personal data under PCI DSS and GDPR.
• A bug bounty, CTF or penetration-testing background, or an offensive certification such as OSCP, OSWE or BSCP.
• Running or scaling a Security Champions programme.
• Familiarity with the OWASP DevSecOps Maturity Model or another maturity framework.
• Hands-on time with WAF and bot protection, secrets management, and infrastructure-as-code scanning, ideally in AWS.
• Spring Security or Rails security internals; writing custom SAST rules.

• 28-days holiday, plus bank holidays
• Monthly €40 Treatwell vouchers so you can treat yourself too
• Mental health support through our partnership with Open-Up
• Market-specific benefits that will be discussed in the interview process

Treatwell is an 'Open to All' employer and warmly welcomes everybody to the team. We are committed to making reasonable adjustments to the recruitment process as required. Please add any adjustment requests to your application.