Senior Backend Engineer, Vinted Pay (Vinted, UAB)
Darbdavys: Vinted, UAB
Miestas: Kaunas
Paskelbta: 2026-10-24
💶 5250 - 7100 €/mėn. Prieš mokesčius · paskelbta 2026-10-21
Kandidatuoti šaltinyje (cv.lt) →
Job description:
As a Senior Backend Engineer, you will be responsible for building and running the verification systems behind Vinted Pay: identity verification (document and biometric checks), electronic KYC (identity and address matching against external data sources) and bank account verification (Confirmation of Payee and Verification of Payee). These checks answer one question for millions of members: "is this person who they say they are, and is this really their bank account?" Every onboarding, balance activation and payout in Vinted Pay passes through them.
You will join Verifications, a team in the Vinted Pay domain made up of 3-4 backend engineers, an engineering manager (your reporting line), a product manager and a decision scientist. The team is young and the service is still taking shape: verification logic is being extracted from older Ruby services into a single Go service that is becoming the source of truth for every verification a member has ever done, and we are making verification resilient to provider outages instead of dependent on any one vendor. This is architectural work with direct product and compliance impact, not just feature delivery.
Problems arrive ambiguous. Engineers here aren't handed specs - they work out what's actually needed together with product and compliance, align it across teams, and build it.
Work in a compact team where nobody owns just one corner: engineers deliberately move between identity verification, eKYC and bank verification, so over time you'll know the whole domain, not a slice of it.
Build and own third-party integrations end-to-end: the client, the callbacks, the durable Temporal workflow that drives a verification to a final decision even when the provider never calls back, the dashboards and SLA alerts, and the shared channel with the vendor when something is wrong on their side.
Design for provider failure: build the provider router that spreads traffic across providers by weight, tracks provider health, remembers what failed for a member and reroutes their retry, so that one provider outage no longer means a member can't verify.
Run A/B tests between providers to decide where traffic should go, and roll verification rules out to new markets.
Own topics end-to-end: from an ambiguous requirement to a written technical plan in the repository, through cross-team alignment, implementation, rollout behind feature flags, and monitoring in production.
Handle personal data with care: PII tagging, log masking, and GDPR retention and deletion across our database, object storage and external providers are part of everyday work, not an afterthought.
Work in an AI-assisted way: agentic coding tools (Claude Code, Cursor, Codex and others) are part of the daily workflow here, for building, debugging, investigating production issues, and writing plans and docs. We expect you to use them well and make the team better at it.
See your code affect millions of users almost instantly. Our main branch gets…
As a Senior Backend Engineer, you will be responsible for building and running the verification systems behind Vinted Pay: identity verification (document and biometric checks), electronic KYC (identity and address matching against external data sources) and bank account verification (Confirmation of Payee and Verification of Payee). These checks answer one question for millions of members: "is this person who they say they are, and is this really their bank account?" Every onboarding, balance activation and payout in Vinted Pay passes through them.
You will join Verifications, a team in the Vinted Pay domain made up of 3-4 backend engineers, an engineering manager (your reporting line), a product manager and a decision scientist. The team is young and the service is still taking shape: verification logic is being extracted from older Ruby services into a single Go service that is becoming the source of truth for every verification a member has ever done, and we are making verification resilient to provider outages instead of dependent on any one vendor. This is architectural work with direct product and compliance impact, not just feature delivery.
Problems arrive ambiguous. Engineers here aren't handed specs - they work out what's actually needed together with product and compliance, align it across teams, and build it.
Work in a compact team where nobody owns just one corner: engineers deliberately move between identity verification, eKYC and bank verification, so over time you'll know the whole domain, not a slice of it.
Build and own third-party integrations end-to-end: the client, the callbacks, the durable Temporal workflow that drives a verification to a final decision even when the provider never calls back, the dashboards and SLA alerts, and the shared channel with the vendor when something is wrong on their side.
Design for provider failure: build the provider router that spreads traffic across providers by weight, tracks provider health, remembers what failed for a member and reroutes their retry, so that one provider outage no longer means a member can't verify.
Run A/B tests between providers to decide where traffic should go, and roll verification rules out to new markets.
Own topics end-to-end: from an ambiguous requirement to a written technical plan in the repository, through cross-team alignment, implementation, rollout behind feature flags, and monitoring in production.
Handle personal data with care: PII tagging, log masking, and GDPR retention and deletion across our database, object storage and external providers are part of everyday work, not an afterthought.
Work in an AI-assisted way: agentic coding tools (Claude Code, Cursor, Codex and others) are part of the daily workflow here, for building, debugging, investigating production issues, and writing plans and docs. We expect you to use them well and make the team better at it.
See your code affect millions of users almost instantly. Our main branch gets…