CalibrdReady. Confident. Hired.← All guides

Vinted interview, decoded.

Updated · Sources at the end

Vinted hires engineers through homework, not puzzles. After an informal intro meeting, you get a take-home task modelled on the work Vinted's teams do, in the language you choose. The technical interview that follows is built around your own code: you walk the reviewers through it, then change it live to meet new requirements, then design one of Vinted's sub-systems with them. The last step is a try-out with the team you would join. Vinted's engineers described this process on the company's engineering blog, and candidates have published the homework briefs themselves.

Vinted runs Europe's largest second-hand fashion marketplace. It was founded in Vilnius in 2008, still has its headquarters there, and opened an engineering hub in Berlin in 2021. In 2025 it reported €1.1 billion in revenue, €62 million in net profit and €10.8 billion in goods sold on the platform, with more than 2,200 employees.

Free · 2 minutes · no account

The questions for your exact Vinted role and level.

See the questions Vinted asks ↓Run a free mock interview →

Interviewing at Vinted? Below are the questions built from what it says it tests. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who Vinted hires

This guide follows the software engineer path: backend, frontend and mobile engineers, from Vinted Academy juniors to senior engineers. Most engineering roles are in Vilnius, with a second engineering hub in Berlin. Candidates have also published homework for site reliability, machine learning and data engineering roles, so the same homework-first shape reaches beyond product engineering.

02

What is the Vinted interview process?

The most detailed official description is a post on Vinted's engineering blog from September 2020, written by a backend engineer who went through the process and later ran it. It names four steps for every engineering candidate: intro meeting, homework, technical interview and try-out. Vinted's current careers pages could not be read for this guide, so check the steps with your recruiter; the homework briefs candidates published in 2024 and 2025 show the homework step is still in use.

01
Intro meeting
An informal conversation with a team lead

Getting to know each other and each side's expectations. The engineering blog says you won't be quizzed on anything; it is the place to ask about engineering practices, culture or anything you want to avoid.

02
Homework
Take-home, in the language you choose, at your own pace

A technical problem like the work Vinted's teams do. Reviewers look at four things: whether you followed the requirements and the output is right, whether the code is clean and simple, whether the design is easy to extend without being over-engineered, and whether it is well tested.

03
Technical interview
About two hours, with the people who reviewed your homework

An introduction, a review of your homework and its design decisions, a live change to your homework to meet new requirements, a system design task on one of Vinted's sub-systems, and time for your questions. You can ask for a short break.

04
Try-out
Time with the team you would join; the format depends on the team

Meeting your future teammates and seeing their day-to-day work. It is still part of the evaluation: the team looks at how you would fit its way of working. Your future team lead explains the format beforehand.

03

The Vinted homework: what it asks and how it is judged

What it asks and how it is judged

The homework is the step Vinted's process is built on: the technical interview reviews it and then asks you to change it. The engineering blog says you choose how much time to spend and which language to use, and recommends one you know well. The candidate who wrote the post spent about a week polishing hers and was told she had over-engineered it: the aim is production-quality code, not a showcase. The briefs below are the ones candidates have published; yours may differ by role.

  • Backend: the shipping discount calculator: Candidates' published solutions describe a file of transactions and a set of shipping discount rules: always charge the lowest small-parcel price across carriers, make the third large-parcel shipment through one carrier free once a month, and cap discounts at €10 a month. Design the rules so one can be added or removed without touching the others, because the interview asks you to change them.
  • Frontend: the infinite-scroll image app: The published brief asks for an app that loads images from an API such as Pexels with infinite scroll, lets you favourite items and keeps favourites after a reload, works at three or more screen sizes, lazy-loads images and serves the right size. It prefers TypeScript and React or plain JavaScript, and forbids other libraries. Build the basics first, then polish.
  • How it is reviewed: Four checks, in the blog's words: requirements, code quality, solution design and testing culture. Follow the brief exactly, keep the code simple, make it easy to extend, and write tests even if you are new to them; the frontend brief says so itself.
  • Getting ready for the interview: The same reviewers take you through their feedback, then ask you to change your code. Bring your own laptop with the project running, and check you can share your screen: the blog's author lost interview time to a missing adapter.

Vinted publishes a repository of mocked APIs on its own GitHub "that can be used for the Vinted Homework", so some briefs call it instead of an outside API.

04

What Vinted screens for

The engineering blog says plainly what the reviewers look for, and it is mostly how you work, not what you know.

  • Code you would ship: the reviewer's advice to one candidate was to treat the homework as production code, with neither polish for its own sake nor shortcuts
  • Following requirements exactly, with output that matches what was asked
  • Designs that are easy to extend and change, without being over-engineered
  • A testing habit: enough tests, and code that is easy to test
  • Thinking out loud in the system design task: clarifying requirements, explaining your reasoning and changing course when the requirements change
05

Vinted interview questions

Drawn from what they say they test

Vinted's interviews are built around your homework and a system design task, not a bank of questions, and no candidate account we could read lists spoken questions. What follows is built from what the engineering blog says each step looks at.

Behavioural & motivation

  • Walk me through a design decision in your homework, and what you would change with more time.Listening forThe reason, not the what · A named trade-off · An honest next step
  • Tell me about a time you had to change code you wrote because the requirements moved.Listening forA real change · How they changed it · What it taught
  • Why Vinted, and why this team?Listening forSpecificity · Connection · Research

Technical

  • Practice: take a rules-based task you have written (for example, discounts applied per transaction) and add a new rule that interacts with an existing one. Talk through where the change goes and why.Changing your homework liveNew requirements added to your own solution during the technical interviewListening forFinds the right place · Extends, not rewrites · Tests the change
  • Practice: design the search behind a marketplace with a billion listings, where new items must become searchable within seconds.System design on a Vinted sub-systemDesigned together with the interviewers; data persistence, caching, performance, data structures and algorithmsListening forClarifies first · A sound core · Adapts on the spot
  • Practice: explain how you would build an infinite-scroll image grid that loads the right image size for the screen and keeps favourites after a reload, with no third-party libraries.Frontend fundamentalsThe frontend homework: infinite scroll, favourites, responsive images, testsListening forLoading on scroll · The right image · Favourites that persist

These come from what the company says it tests, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level.

Predict my Vinted questions →
06

Pay

Software engineer, Lithuania · Levels.fyi€48.1K–€67K+
IC2 software engineer · Levels.fyi€39K–€51.1K+

Vinted does not publish salaries. The Levels.fyi figures (read on 29 September 2026 from its listings) cover software engineers in Lithuania, where most of Vinted's engineers work; Berlin roles are paid against the German market. The sample is small. Calibrd benchmarks an offer against your level and location in the report.

07

How to prepare for a Vinted interview

  1. Treat the homework as production code: follow the brief exactly, keep it simple and write tests. Over-polishing costs you as much as shortcuts.
  2. Design the homework to be changed. The technical interview asks you to add new requirements to it live.
  3. Practise one system design out loud on a marketplace problem, such as search over a billion items or a listing feed, covering storage, caching and performance.
  4. Bring your laptop with the homework running, and check screen sharing before the day.
  5. Use the intro meeting to ask about the team's engineering practices; the blog says that is what it is for.
  6. Plan for the try-out: it is time with your future team and still part of the decision.

The official process description dates from September 2020. Candidates' published homework from 2024 and 2025 shows the homework step is unchanged, but confirm the other steps with your recruiter. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at Allegro, Criteo or Dataiku? Their guides follow the same format, from the first screen to the offer.

Knowing the questions isn’t the same as answering them out loud. Run a Vinted mock: spoken answers, coached on the spot. Your first mock is free.

Run a Vinted mock →
08

FAQ & sources

What is Vinted's interview process?

The most detailed official description is a post on Vinted's engineering blog from September 2020, written by a backend engineer who went through the process and later ran it. The stages, in order: Intro meeting; Homework; Technical interview; Try-out.

What does Vinted look for in candidates?

The engineering blog says plainly what the reviewers look for, and it is mostly how you work, not what you know. Code you would ship; Following requirements exactly, with output that matches what was asked; Designs that are easy to extend and change, without being over-engineered; A testing habit.

What questions does Vinted ask in interviews?

Vinted's interviews are built around your homework and a system design task, not a bank of questions, and no candidate account we could read lists spoken questions. Technical themes: Changing your homework live; System design on a Vinted sub-system; Frontend fundamentals.

What is the Vinted homework assignment?

The homework is the step Vinted's process is built on: the technical interview reviews it and then asks you to change it. The engineering blog says you choose how much time to spend and which language to use, and recommends one you know well. Covered on this page: Backend: the shipping discount calculator; Frontend: the infinite-scroll image app; How it is reviewed; Getting ready for the interview.

How do I prepare for a Vinted interview?

Treat the homework as production code: follow the brief exactly, keep it simple and write tests. Over-polishing costs you as much as shortcuts. Design the homework to be changed. The technical interview asks you to add new requirements to it live.

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.

Prep for a real Vinted role

Practise your Vinted interview, out loud.

Paste a real Vinted posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your CV — then listens to your spoken answers and coaches them. Your first mock is free.

Set up your workspace for free →Add to Chrome, it reads the posting for you →

Free to start · No card · Encrypted at rest, never used to train AI, remove anytime

Two weeks out?

Email me the Vinted prep checklist

The round that decides it, the questions they ask, and what to do before, in one email. Nothing else unless you sign up.

Vinted Interview: Homework, System Design, Try-out — Calibrd