Google ile giriş. Kart gerekmez.
About the Role
Xsolla seeks a technically strong Security Engineer with a focus on vulnerability management to join a new security team during a critical build-out phase. You own the vulnerability management lifecycle across our infrastructure, cloud, container and application estate: from discovery and prioritization to validated findings, ready-to-apply fixes and verified closure.
We are not looking for someone who forwards scanner reports. We are looking for an engineer who can independently confirm that a vulnerability is real and exploitable in our environment, understand its root cause, and come to the development or infrastructure team with a concrete, tested solution: a patch plan, a configuration change, a pull request, a hardened image, or a compensating control. You earn trust with engineering teams by being technically right and by making the fix easy.
You work closely with the security program manager, platform and infrastructure teams, and application developers, and you help shape how vulnerability management is run at Xsolla as the program matures. Depending on your level, you will either drive the program day to day (Middle) or define its strategy, standards and tooling and mentor others (Senior).
Our tech stack includes GCP, vSphere/ESX, Kubernetes and container workloads, MariaDB, CockroachDB, Go, PHP, and Python. You do not need expertise in all of these, but you are comfortable navigating a mixed environment and learning what you need.
As always true in job descriptions, there is an intangible value that is hard to capture. We look for a diverse set of perspectives and skills. Even if you don't match every requirement, we encourage you to apply if you think you can be highly successful in this role.
Responsibilities
Run the Vulnerability Management Lifecycle - Operate and continuously improve the end-to-end process: asset discovery, scanning, triage, prioritization, remediation, verification and reporting.
Scan Across the Whole Estate - Manage authenticated and unauthenticated scanning of hosts, network segments, cloud workloads, Kubernetes clusters, container images, and application dependencies (SCA), ensuring coverage and minimizing blind spots.
Validate Findings Technically - Reproduce and confirm vulnerabilities hands-on: analyze affected versions and configurations, check reachability and exploitability, build or adapt a proof of concept where appropriate, eliminate false positives, and document the evidence and real impact.
Deliver Ready-to-Use Solutions - Do not stop at "this is vulnerable". Propose and test the fix: package upgrades and patch procedures, base image and dependency updates, Kubernetes and OS hardening, configuration management and IaC changes (Puppet, Terraform, Helm), WAF virtual patching, network segmentation, or other compensating controls. Where it makes sense, submit the change yourself as a pull request or merge request, or hand over precise step-by-step instructions that the team can apply with confidence.
Prioritize by Real Risk - Go beyond CVSS. Combine exploitability (EPSS, CISA KEV, public exploits), validated impact, asset criticality, internet exposure, reachability and compensating controls to decide what must be fixed first.
Drive Remediation with Engineering - Partner with infrastructure, platform and development teams to agree on fixes, workarounds and timelines. Provide clear, actionable tickets with evidence, root cause and a recommended solution rather than raw scan output.
Define and Enforce SLAs - Establish, track and report remediation SLAs by severity and asset class, manage exceptions and risk acceptances, and escalate when deadlines are at risk.
Verify Remediation - Re-test after fixes are applied and confirm closure with evidence, including regression checks that the fix does not break the service.
Respond to New Threats - Monitor vulnerability intelligence and advisories, assess exposure to newly disclosed critical vulnerabilities (zero-days, actively e