TravelPerk (Perk) interview, decoded.

Perk tells engineering candidates to use AI in the coding interview. Every engineering job ad it runs in 2026 says the same thing: "We expect candidates to use AI tools in our coding interviews. The bar is understanding your code and owning what you produce." That changes how you prepare: the test is whether you can drive the tool, check what it writes and explain every line of it.

Perk is the company that was called TravelPerk until November 2025, when it renamed itself, joined travel and spend management in one product and set up dual headquarters in Boston and London. It was founded in Barcelona in 2015, has more than 1,800 people across 12 offices, and was valued at $2.7 billion in its Series E in January 2025. Most of the engineering roles open in September 2026 are in Barcelona and London. The stack is Python on AWS, and the Flights area has grown from one team to four since 2025.

Free · 2 minutes · no account

The questions for your exact Perk role and level.

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

Interviewing at Perk? 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 Perk hires

The roles and the background

Perk hires senior and staff software engineers, frontend engineers, DevOps engineers and engineering managers, with most openings in Barcelona and London and a few in Boston. The ads describe product engineers who own a feature from the customer problem to measuring its impact, and who run their own services in production. English is the official language at the office. The ads say Perk can help with relocation from anywhere "for certain roles", without promising a visa, and one candidate on Reddit reports being stopped at the recruiter stage over sponsorship.

02

What is the Perk interview process?

Round by round

Perk doesn't publish its engineering loop, and the candidate accounts we could open are few. The shape below combines what the job ads say about the coding interview with one Barcelona candidate's account from July 2026. Treat the order and number of rounds as approximate and ask your recruiter for the plan on the first call.

01
Recruiter call
A short call

Background, level, location and, if you are moving, relocation and visa. One candidate describes the call as brief and fast-moving.

02
Coding interview
Live, with AI tools expected

You are expected to use AI tools. The bar the ads set is understanding your code and owning what you produce, so expect to explain and defend what the assistant wrote.

03
Further technical rounds
Several steps

The candidate account describes several technical stages after the coding round. For senior and staff roles the ads centre on design documents, architecture and running services in production, so expect those to be discussed.

04
Decision
By email

The same candidate was told to expect an email within a week, heard nothing for weeks and got no feedback. Ask for a timeline at every stage.

03

What Perk screens for

What every round is really testing

Perk's ads name its values and describe the engineer it wants in detail, and both come through in the interview.

  • Being an owner: taking a feature from the customer's problem through design, code and deployment to its measured impact
  • A 7-star experience for the customer, one of the values the ads name
  • Working as one team, across product, design and operations
  • Pragmatism and simplicity: the ads measure engineering by how reliable and simple the systems are
  • Using AI well in daily work, from writing and reviewing code to agentic coding
04

Perk interview questions

Drawn from what they say they test

No candidate account we could open lists Perk's questions. What follows is built from what its ads say it looks for, so what you practise matches what it screens for.

Behavioural & motivation

  • Tell me about a feature you owned end to end, from the customer's problem to measuring its impact.
  • Describe a time you chose the simpler design over the clever one. What did it save?
  • Tell me about an incident in a service you ran. What changed afterwards?
  • Why Perk, and why this team?

Technical

  • Coding with an AI assistant: Prompting, checking and explaining generated code, with tests to show it works
  • Backend in Python on AWS: About 80% backend work in the Flights area, and closer to half and half in the Boston staff role
  • Design documents and architecture: For senior and staff roles: data models, failure isolation, caching and API versioning
  • Building on messy supplier systems: The Flights ad says one booking involves far more steps, suppliers and failure modes than most people realise
  • Running what you build: SLOs, incident handling and blameless post-mortems, named in the senior and staff ads

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 Perk questions →
05

Perk's AI-allowed coding interview: how to pass it

What Perk asks for, and how to meet it

Yes, and Perk expects you to. Its 2026 engineering ads say candidates should use AI tools in the coding interviews, that the bar is understanding your code and owning what you produce, and that this reflects how its engineers work every day, with agentic coding and AI review on every pull request. The round rewards judgement about the tool, and pasting in output you can't explain falls short of that bar.

  • Decide the approach before you prompt: Say how you will solve the problem and why, then ask the assistant for the parts you have already designed. The interviewer should hear your plan first and see the tool carry it out.
  • Read everything the assistant writes: Go through the generated code out loud, name what each part does and fix what is wrong. Expect questions like "why this data structure?" about lines you did not type.
  • Prove it works: Ask for tests or write them, run them and add the edge cases the assistant missed. Owning what you produce includes knowing it is correct.
  • Practise with the tool you will use: Before the interview, solve a few problems of the kind you expect with an AI assistant, timing yourself and explaining each step aloud as if someone were listening.

Ask your recruiter which tools are allowed and whether you share your screen with your own editor. The ads don't say.

06

Pay

What the offer looks like
Software engineer, Spain · Levels.fyi, 76 reports€59–73K+
Senior software engineer, Boston · job ad, base$140–180K
Staff software engineer, Boston · job ad, base$174–215K

The Spain range is the one Levels.fyi gives for TravelPerk software engineers, read on 26 September 2026; the median package it shows is an L4 engineer in Barcelona with ten years of experience, paid in base salary with no stock. Perk's European ads carry no pay range. The Boston ads give base salary ranges and say pay combines salary and stock options. Calibrd benchmarks the offer against your level and location in the report.

07

How to prepare for a Perk interview

In order
  1. Practise coding with an AI assistant before the interview, explaining your plan first and every generated line after.
  2. Bring two or three stories where you owned a feature from the customer problem to its measured impact. That is the engineer every Perk ad describes.
  3. For senior and staff roles, prepare to walk through a design document you wrote: the problem, the options and why you chose one.
  4. Search for the company under both names. Most reviews and threads still say TravelPerk.
  5. If you need a visa, raise it on the first call. The ads promise relocation help only for certain roles.
  6. Ask for the timeline at each stage and follow up once if it passes. One recent Barcelona candidate heard nothing for weeks.
  7. Plan for three days a week in the office. Perk brought staff back three days a week in 2023, despite a letter of disagreement from its engineers, and the 2026 ads keep the rule.

This guide covers Perk's engineering hiring. What Perk says about its coding interview, stack, office days and relocation comes from its own job ads; candidate accounts are few, and we say where one account is all there is. 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.

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

Run a Perk mock →
08

FAQ & sources

The short answers
What is Perk's interview process?

Perk doesn't publish its engineering loop, and the candidate accounts we could open are few. The shape below combines what the job ads say about the coding interview with one Barcelona candidate's account from July 2026. Treat the order and number of rounds as approximate and ask your recruiter for the plan on the first call. Recruiter call: Background, level, location and, if you are moving, relocation and visa. One candidate describes the call as brief and fast-moving. Coding interview: You are expected to use AI tools. The bar the ads set is understanding your code and owning what you produce, so expect to explain and defend what the assistant wrote. Further technical rounds: The candidate account describes several technical stages after the coding round. For senior and staff roles the ads centre on design documents, architecture and running services in production, so expect those to be discussed. Decision: The same candidate was told to expect an email within a week, heard nothing for weeks and got no feedback. Ask for a timeline at every stage.

What does Perk look for in candidates?

Perk's ads name its values and describe the engineer it wants in detail, and both come through in the interview. Being an owner: taking a feature from the customer's problem through design, code and deployment to its measured impact A 7-star experience for the customer, one of the values the ads name Working as one team, across product, design and operations Pragmatism and simplicity: the ads measure engineering by how reliable and simple the systems are Using AI well in daily work, from writing and reviewing code to agentic coding

What questions does Perk ask in interviews?

No candidate account we could open lists Perk's questions. What follows is built from what its ads say it looks for, so what you practise matches what it screens for. Tell me about a feature you owned end to end, from the customer's problem to measuring its impact. Describe a time you chose the simpler design over the clever one. What did it save? Tell me about an incident in a service you ran. What changed afterwards? Why Perk, and why this team? Coding with an AI assistant Backend in Python on AWS Design documents and architecture Building on messy supplier systems Running what you build

Can you use AI in the Perk coding interview?

Yes, and Perk expects you to. Its 2026 engineering ads say candidates should use AI tools in the coding interviews, that the bar is understanding your code and owning what you produce, and that this reflects how its engineers work every day, with agentic coding and AI review on every pull request. The round rewards judgement about the tool, and pasting in output you can't explain falls short of that bar. Decide the approach before you prompt: Say how you will solve the problem and why, then ask the assistant for the parts you have already designed. The interviewer should hear your plan first and see the tool carry it out. Read everything the assistant writes: Go through the generated code out loud, name what each part does and fix what is wrong. Expect questions like "why this data structure?" about lines you did not type. Prove it works: Ask for tests or write them, run them and add the edge cases the assistant missed. Owning what you produce includes knowing it is correct. Practise with the tool you will use: Before the interview, solve a few problems of the kind you expect with an AI assistant, timing yourself and explaining each step aloud as if someone were listening.

How do I prepare for a Perk interview?

Practise coding with an AI assistant before the interview, explaining your plan first and every generated line after. Bring two or three stories where you owned a feature from the customer problem to its measured impact. That is the engineer every Perk ad describes. For senior and staff roles, prepare to walk through a design document you wrote: the problem, the options and why you chose one. Search for the company under both names. Most reviews and threads still say TravelPerk. If you need a visa, raise it on the first call. The ads promise relocation help only for certain roles. Ask for the timeline at each stage and follow up once if it passes. One recent Barcelona candidate heard nothing for weeks. Plan for three days a week in the office. Perk brought staff back three days a week in 2023, despite a letter of disagreement from its engineers, and the 2026 ads keep the rule.

Prep for a real Perk role

Practise your Perk interview, out loud.

Paste a real Perk 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.

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

Two weeks out?

Email me the Perk 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.

TravelPerk (Perk) Interview: AI Coding Round, Pay — Calibrd