CalibrdReady. Confident. Hired.← All guides

Trade Republic careers and interviews, from the take-home to the savings plan question.

Updated · Sources at the end

Trade Republic hires software engineers through homework and a conversation about it. Candidates describe a short intro call, a take-home project with about five days to finish, then a technical interview where two senior engineers go through the code you sent. A system design round with two senior engineers follows, and the question candidates report comes straight from the product: design the infrastructure that runs customers' savings plans on schedule. The loop ends with a behavioural interview with two engineering managers.

The design question is the one to prepare most for. A savings plan is a standing order to buy a fixed amount of a stock, ETF or crypto asset every period, so the system has to run a large batch on fixed dates, move real money, and never buy twice or skip a customer. This guide covers how to take that round and how to prepare a take-home you will have to defend line by line.

Trade Republic was founded in Berlin in 2015 and received a full banking licence from the European Central Bank in December 2023. Its job ads describe it as the largest savings platform in Europe, active in 18 countries with more than 10 million customers and over €150 billion in assets. A secondary share sale in December 2025 valued it at €12.5 billion.

Free · 2 minutes · no account

The questions for your exact Trade Republic role and level.

See the questions Trade Republic asks ↓Run a free mock interview →

Interviewing at Trade Republic? Below are the questions candidates report. For the ones your exact role and level will get, paste the posting. Your first mock is free.

01

Who Trade Republic hires

Trade Republic's engineering hiring is mostly experienced backend and mobile engineers. On 16 October 2026 its board listed backend engineers in Berlin, London and Paris, a Haskell backend role in Berlin, Android and iOS engineers in Berlin and Paris, analytics engineers in London and Paris, a data scientist in Berlin and three security engineers. Backend ads ask for the JVM ecosystem (Kotlin, Spring, Vert.x, Hibernate or jOOQ), high-availability services on AWS, and delivery through GitHub Actions and Kubernetes. The iOS team writes 100% Swift with SwiftUI, UIKit, Combine and WebSockets; Android uses Kotlin, Jetpack Compose, RxJava2 and Kotlin Flow. The Berlin data scientist sits in the Operations Platform team and builds customer service automation, including LLM agents in production. Every ad says relocation support is available, and the London and Paris backend ads add visa support. In May 2026 Trade Republic also opened a Graduate Backend Engineering Programme in Berlin for people with up to a year of experience, rotating through product, platform, mobile, data and infrastructure teams. The ads publish no salary.

Before you apply, see how your resume reads to a hiring manager with a free resume review.

Engineering and data candidates describe the same idea, a piece of homework you then discuss, inside two different loops.

  • Track · Eng

    Software engineering

    An intro call, a take-home of about five days, a technical interview on your code with two senior engineers, a system design round with two senior engineers, and a behavioural round with two engineering managers. Backend candidates report building API endpoints; a frontend candidate reports building a small app on WebSockets. This is the loop this guide covers in most detail.

  • Track · Data

    Data science and analytics

    Senior data scientists report a recruiter briefing, a case study to submit within a week, a technical interview on the case study plus data science and ML engineering questions, a product mindset interview, and an offer call. Analytics engineers report an intro call, a technical screen, a SQL interview, an analytical solution design interview, a cross-functional round and a culture round.

  • Track · Grad

    Graduate Backend Engineering Programme

    A Berlin programme posted in May 2026 for graduates with up to a year of experience, asking for computer science fundamentals, the basics of system design and one modern language. Trade Republic has not published its selection steps, and the first intake had closed by October 2026.

02

What is the Trade Republic interview process?

Trade Republic does not publish its interview stages. The shape below comes from candidate reports on Glassdoor and kununu between 2023 and 2026, seen in search snippets. Glassdoor puts the average at a little over three weeks, and engineering reports range from three weeks to two months.

01
Intro call
About 15 minutes

Your background, your recent work and why Trade Republic. One candidate had it with a staff engineer, others with a recruiter or an engineering director. Ask here how long the take-home gives you and what the later rounds are.

02
Take-home project
About five days to submit

Backend candidates report implementing a set of API endpoints; one described a mix of data engineering and backend work; a frontend candidate built a small app on WebSockets. Candidates call the instructions clear. The section below covers how to build it so you can defend it.

03
Technical interview on your code
With two senior engineers

The engineers go through what you submitted and ask why you built it that way, what you would change and how it would hold up with more load or new requirements.

04
System design
With two senior engineers

Reported questions come from the product: design the infrastructure that executes savings plans regularly, and implement an automatic investment that runs every billing period. The design section below goes through it.

05
Behavioural interview
With two engineering managers

Past projects, ownership and how you work with others. Some candidates also report a bar raiser round late in the loop, so ask your recruiter whether yours has one.

06
Case study and product mindset
A take-home case study, then two interviews

The case study is submitted within a week and discussed in the technical interview, alongside data science and ML engineering questions. The product mindset round asks how you would solve problems in the team's area.

Data science
07
Decision
Through your recruiter

Slow communication is a common complaint. Several candidates heard nothing for weeks after a round, and some were rejected late in the loop with a generic email and no feedback. Ask for a timeline at each step and follow up in writing.

03

Trade Republic take-home: build it to defend it

What candidates report and what the ads ask for

The Trade Republic take-home comes after the intro call, with about five days to submit. Backend candidates report implementing API endpoints, one described a task that mixed data engineering and backend work, and a frontend candidate built an app on WebSockets. The next round is a technical interview where two senior engineers go through your submission, so everything you write becomes something you will be asked about. Candidates on Glassdoor, seen in search snippets, call the instructions clear and the evaluation detailed.

  • Read the brief twice and write down your assumptions: Put them in the README. When the reviewers ask why you made a choice, an assumption you wrote down on day one is a much stronger answer than one you work out in the room.
  • Make it correct before you make it clever: This is a bank. Validate input, handle errors explicitly, and think about duplicate requests and amounts. A plain design that is right in every case is easier to defend than a clever one with a gap.
  • Write the tests you would want in production: Cover the happy path and the edge cases you can name: empty input, invalid values, two requests at once. Backend ads ask for reliable, maintainable software delivered iteratively, and tests are the evidence.
  • Use the stack they use if you can: Backend ads name Kotlin, Spring, Vert.x, Hibernate or jOOQ; iOS ads name Swift with SwiftUI and Combine; Android ads name Kotlin with Compose and Flow. If the brief lets you choose, the closer you are to their stack, the more the review can be about design.
  • Leave a short list of what you would do next: End the README with what you left out and why: persistence, scaling, monitoring, more tests. It shows judgement about the time limit, and it gives the reviewers good questions to ask you.
  • Rehearse the review before it happens: Open your code a day before the interview and explain each file out loud. Prepare answers to the questions you would ask yourself: what breaks with ten times the traffic, what you would change first, and which decision you are least sure of.

Trade Republic does not publish the take-home. Ask the recruiter how long you have, whether you can choose the language, and whether the review round includes live changes to your code.

The rest of the loop depends on your role. Pick it, or paste the posting, and Calibrd predicts the rounds and questions you are likely to get at Trade Republic.

Predict my Trade Republic questions →
04

Trade Republic system design: the savings plan question

Reported prompts and how to take them

Candidates report a system design round with two senior engineers, and the questions they name come from Trade Republic's own product: design the infrastructure that regularly executes savings plans, and implement an automatic investment that runs every billing period. Both are scheduled jobs that move customer money inside a regulated bank, so correctness is the centre of the answer and scale comes second.

  • Start with the requirements: Ask how many plans there are, which dates and how often they run, which assets (stocks, ETFs, crypto), whether plans can buy fractions, and when orders must reach the market. Writing these down first shows you will not build the wrong system fast.
  • Make every execution happen exactly once: Give each plan and period a unique execution key and store it before you charge or trade. Retries and restarts then find the existing record instead of buying twice. Add a reconciliation job that compares due plans with executed ones, so a skipped customer is found the same day.
  • Split the run into steps you can retry: Create the due executions, check and reserve the customer's cash, group orders per instrument, send them to the trading venue, then book the fills back to each customer. Each step reads from the last one's stored state, so a crash halfway restarts at the right place.
  • Plan for the peak days: Most plans run on the same few days of the month. Spread the work across workers by plan ID, think about how many orders the venue accepts, and say what happens if the run is not done when the trading window closes.
  • Cover the failures out loud: Insufficient funds, a closed market or a holiday, an instrument that is suspended, a partial fill, a price that moved. For each one, say what the system does and what the customer sees in the app.
  • Finish with how you would run it: Name the metrics you would watch (plans due, executed, failed, money reserved versus spent), the alerts, and the audit trail a bank needs. Running it after launch is part of the ownership the ads ask for.

These are the prompts candidates report; yours may be a different part of the product. The same approach fits most of them: clarify, make money movement exactly once, then scale.

05

What Trade Republic screens for

Trade Republic's job ads all close with the same description of its culture, and the rounds give you room to show it.

  • Ownership: the ads say the culture rewards it, and the review of your take-home is where you show you own every decision in it
  • Excellence: correctness matters in a bank that moves customers' savings, so tests and edge cases count in the take-home
  • High energy and a focus on outcomes: the ads say people care about results and hold each other accountable
  • The mission to close the pension gap and make building wealth easy, safe and free for everyone in Europe
  • Reliability and maintainability: backend ads ask for software delivered iteratively with continuous delivery
06

Trade Republic interview questions

Candidate-reported themes

Candidates report the format of the rounds more often than the questions. The system design questions are reported; the rest follow what Trade Republic's job ads say it looks for.

Behavioural & motivation

  • Why Trade Republic?Listening for: Specificity · Connection · Research
  • Walk me through a decision in your take-home you would make differently now.Listening for: A real decision · The trade-off · What they'd do
  • Tell me about a time you owned a system where a mistake would have cost customers money or trust.Listening for: The stakes · How they kept it right · The outcome
  • Tell me about a time you held a teammate, or yourself, accountable for an outcome.Listening for: A clear gap · How they raised it · What changed
  • Tell me about yourself.Listening for: Frame · Evidence · Length

Technical

  • Design the infrastructure that executes millions of savings plans on the same few days each month.Savings plan execution: Reported in the system design round: design the infrastructure that regularly executes savings plansListening for: Exactly once · The batch · When things fail
  • Practice: a customer's card is charged every month to fund an investment. The payment call times out. How do you make sure they are charged once and invested once?Recurring investment every billing period: Reported: how would you implement an automatic investment tool that runs every billing period. A practice question in that styleListening for: Clear states · Safe retries · Recovery
  • Practice: you built endpoints to create and list a customer's orders. Two senior engineers ask what happens when the same create request arrives twice. What do you say?The backend take-home: Reported: implementing a set of API endpoints in about five days, then defending them. A practice question in that styleListening for: Sees the risk · A sound fix · Proves it
  • Practice: build a screen that shows live prices for a watchlist of 50 stocks from a WebSocket. How do you handle reconnects and many updates a second?Live prices on the client: Reported for a frontend candidate: a take-home app built on WebSockets; the iOS ads name WebSockets and reactive data flow. A practice question in that styleListening for: Connection · Update rate · Structure and tests
  • Practice: support receives thousands of tickets a day in many languages. How would you use an LLM to route them, and how would you know it works?Data science: customer service automation: The Berlin data scientist ad describes LLM agents and workflows for customer service in production. A practice question in that styleListening for: A working design · Evaluation · Business impact

These are the reported themes, and your loop is role-specific. Paste the actual posting and Calibrd predicts the questions for that exact role and level. How the questions are predicted →

Predict my Trade Republic questions →
07

How to prepare for a Trade Republic interview

  1. Read the ad for your role closely and match its stack where the take-home lets you choose.
  2. Use the app, or read how savings plans work on Trade Republic's site, so the design round's product is familiar.
  3. Ask the recruiter on the intro call for the take-home time limit and every later round.
  4. Write down your assumptions in the take-home README and end it with what you would do next.
  5. Test the edge cases that matter for money: duplicate requests, invalid amounts, two requests at the same time.
  6. Explain your submission out loud, file by file, the day before the review.
  7. Practise one scheduled money-movement design end to end: exactly-once execution, retries, reconciliation and the peak day.
  8. Prepare two stories about owning a system where mistakes were costly, with numbers.
  9. Ask for a timeline after every round and follow up in writing if it passes; slow replies are a common complaint.
  10. Ask for the salary range on the first call, since the ads publish none.

This guide covers Trade Republic's software engineering hiring, its data science and analytics loops, and its graduate backend programme. 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 Personio, Goldman Sachs or JPMorgan Chase? 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 Trade Republic mock: spoken answers, coached on the spot. Your first mock is free.

Run a Trade Republic mock →
08

FAQ & sources

What is Trade Republic's interview process?

Trade Republic does not publish its interview stages. The stages, in order: Intro call; Take-home project; Technical interview on your code; System design; Behavioural interview; Case study and product mindset; Decision.

What does Trade Republic look for in candidates?

Trade Republic's job ads all close with the same description of its culture, and the rounds give you room to show it. Ownership; Excellence; High energy and a focus on outcomes; The mission to close the pension gap and make building wealth easy, safe and free for everyone in Europe.

What questions does Trade Republic ask in interviews?

Candidates report the format of the rounds more often than the questions. Technical themes: Savings plan execution; Recurring investment every billing period; The backend take-home; Live prices on the client; Data science: customer service automation.

What is the Trade Republic take-home project?

The Trade Republic take-home comes after the intro call, with about five days to submit. Backend candidates report implementing API endpoints, one described a task that mixed data engineering and backend work, and a frontend candidate built an app on WebSockets. Covered on this page: Read the brief twice and write down your assumptions; Make it correct before you make it clever; Write the tests you would want in production; Use the stack they use if you can; Leave a short list of what you would do next; Rehearse the review before it happens.

What is asked in the Trade Republic system design interview?

Candidates report a system design round with two senior engineers, and the questions they name come from Trade Republic's own product: design the infrastructure that regularly executes savings plans, and implement an automatic investment that runs every billing period. Both are scheduled jobs that move customer money inside a regulated bank, so correctness is the centre of the answer and scale comes second. Covered on this page: Start with the requirements; Make every execution happen exactly once; Split the run into steps you can retry; Plan for the peak days; Cover the failures out loud; Finish with how you would run it.

How do I prepare for a Trade Republic interview?

Read the ad for your role closely and match its stack where the take-home lets you choose. Use the app, or read how savings plans work on Trade Republic's site, so the design round's product is familiar.

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 Trade Republic role

Practise your Trade Republic interview, out loud.

Paste a real Trade Republic posting and Calibrd predicts the questions for that role and level, benchmarks the pay, and flags the gaps an interviewer will probe in your resume — 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 Trade Republic 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.

Trade Republic Careers and Interview: Take-Home — Calibrd