Backend Engineer, Money Movement and Revenue Streams (Vinted, UAB)
Darbdavys: Vinted, UAB
Miestas: Vilnius
Paskelbta: 2026-10-25
💶 3558 - 4808 €/mėn. Prieš mokesčius · visa darbo diena · paskelbta 2026-10-02
Kandidatuoti šaltinyje (cv.lt) →
Job description:
We're searching for a Backend Engineer to join the Bridge team, inside the Payments Money Movement team domain. As the name says, we connect Vinted Pay to the outside financial world. Bridge owns how money leaves the platform and reaches our members: bank accounts, payouts, and the migration from different payment service providers into Vinted Pay.
We're at an important stage. We're moving millions of members and their payment flows from external providers to Vinted Pay, with zero downtime and without losing a single transaction. At the same time, we're building new revenue streams on top of our payments capabilities. The systems we build now will carry Vinted Pay for years, so there's real architectural work here, not just feature delivery.
Work in a cross-functional team of 3-4 backend engineers, frontend engineers, engineering manager, product manager and decision scientist.
Build migration, payout flows in Ruby, orchestrate them as durable Temporal workflows across services.
Own topics end-to-end: from an ambiguous requirement to a written proposal, cross-team alignment, implementation, and monitoring in production.
Work in AI-assisted way: agentic coding tools (Claude Code, Codex and others) are part of the daily workflow here - for building, debugging, investigating production issues, and writing docs. We expect you to use them well and make the team better at it.
See your code affect millions of members almost instantly. Our main branch gets rolled out straight to production on each merge. We deploy many times per day.
Work with diverse tech stack: Ruby language, MySQL, OpenSearch, Redis, Kafka, Temporal, Prometheus, Grafana. We don't expect you to be familiar with all of them beforehand, but we expect you will be excited to learn them fast.
Write unit tests for all of the code you write and contribute to integration and E2E test writing and its usage.
Take ownership of alerts and business metrics for your team to ensure our services achieve 99.99% availability.
You will participate in on-call rotations to ensure our product performs well.
Requirements:
You take ownership of features and projects from start to finish, you break problems down so others can tackle them too - not just you.
You navigate ambiguity well - given a vague requirement, you extract the real need, propose a solution with trade-offs, and drive it to agreement.
You think like a product engineer - you ask why before how, question requirements that don't make sense, and care about what the user and the business actually get - not just that the ticket is closed.
You are a pragmatic problem solver - you think practically, choose the best solutions, avoid over-engineering, and prioritise simplicity.
You document what you build - proposals, RFCs, ADRs - so the next person doesn't have to reverse-engineer your thinking.
You care about observability and monitoring - if something breaks, your team shouldn't be flying blind.
You embrace AI tooling and agentic…
We're searching for a Backend Engineer to join the Bridge team, inside the Payments Money Movement team domain. As the name says, we connect Vinted Pay to the outside financial world. Bridge owns how money leaves the platform and reaches our members: bank accounts, payouts, and the migration from different payment service providers into Vinted Pay.
We're at an important stage. We're moving millions of members and their payment flows from external providers to Vinted Pay, with zero downtime and without losing a single transaction. At the same time, we're building new revenue streams on top of our payments capabilities. The systems we build now will carry Vinted Pay for years, so there's real architectural work here, not just feature delivery.
Work in a cross-functional team of 3-4 backend engineers, frontend engineers, engineering manager, product manager and decision scientist.
Build migration, payout flows in Ruby, orchestrate them as durable Temporal workflows across services.
Own topics end-to-end: from an ambiguous requirement to a written proposal, cross-team alignment, implementation, and monitoring in production.
Work in AI-assisted way: agentic coding tools (Claude Code, Codex and others) are part of the daily workflow here - for building, debugging, investigating production issues, and writing docs. We expect you to use them well and make the team better at it.
See your code affect millions of members almost instantly. Our main branch gets rolled out straight to production on each merge. We deploy many times per day.
Work with diverse tech stack: Ruby language, MySQL, OpenSearch, Redis, Kafka, Temporal, Prometheus, Grafana. We don't expect you to be familiar with all of them beforehand, but we expect you will be excited to learn them fast.
Write unit tests for all of the code you write and contribute to integration and E2E test writing and its usage.
Take ownership of alerts and business metrics for your team to ensure our services achieve 99.99% availability.
You will participate in on-call rotations to ensure our product performs well.
Requirements:
You take ownership of features and projects from start to finish, you break problems down so others can tackle them too - not just you.
You navigate ambiguity well - given a vague requirement, you extract the real need, propose a solution with trade-offs, and drive it to agreement.
You think like a product engineer - you ask why before how, question requirements that don't make sense, and care about what the user and the business actually get - not just that the ticket is closed.
You are a pragmatic problem solver - you think practically, choose the best solutions, avoid over-engineering, and prioritise simplicity.
You document what you build - proposals, RFCs, ADRs - so the next person doesn't have to reverse-engineer your thinking.
You care about observability and monitoring - if something breaks, your team shouldn't be flying blind.
You embrace AI tooling and agentic…