Authentication and authorization underpin nearly every interaction on Vinted. They determine how members, employees, and services prove who they are, and what they are allowed to do.
Today, these responsibilities span our core platform, dedicated identity services, gateways, service-mesh infrastructure, and workforce systems. We are evolving this landscape towards a shared identity model and an authorization platform that is secure, reliable, observable, and straightforward for engineering teams to adopt.
We’re looking for a Senior Backend Engineer II to join the Authentication and Authorization team. You’ll work across two connected areas:
- Evolving authentication towards a consistent, federated identity model for members, employees, and systems
- Building shared authorization capabilities that replace fragmented, service-specific solutions with common concepts, APIs, tooling, and decision observability
This is neither a purely greenfield role nor a legacy-maintenance role. You’ll help extract existing functionality safely, improve production services, and build new platform capabilities.
We’re looking for an experienced engineer, but not necessarily someone who already knows every part of identity and access management. What matters is strong engineering judgement, curiosity, and the ability to learn unfamiliar technologies and domains. You should be comfortable going deep into a technical problem, then zooming out to understand how the solution affects users, services, infrastructure, security, and other engineering teams.
In this position, you’ll
- Design, build, and operate backend services supporting authentication, identity propagation, token exchange, authorization decisions, and policy management
- Help extract authentication functionality from existing systems while preserving feature parity, controlling rollout risk, and retiring legacy paths safely
- Contribute to stable identity and authorization contracts that allow services to evolve without depending on individual identity providers, token formats, or API implementations
- Build shared authorization capabilities, including a capability registry, policy APIs, decision logs, and tools for understanding who or what can access a resource
- Improve supported integration paths - such as SDKs, libraries, conformance tests, documentation, and migration tooling - that make secure adoption easier for other teams
- Work with Registration, Platform, Security, and product-domain engineers to define ownership boundaries, integration contracts, and safe migration plans
- Keep security-critical systems reliable and observable by contributing to SLOs, latency expectations, failure behaviour, monitoring, and operational response
- Take ownership of complex areas of work from design through implementation, rollout, and production operation
- Contribute to technical proposals and architectural decisions, helping the team understand the available trade-offs
- Support other engineers through thoughtful code reviews, pairing, documentation, and knowledge sharing
- Write, review, test, deploy, monitor, and troubleshoot production code
