Revolut Engineering Hiring Process 2026

You applied to Revolut, refreshed your email 19 times, and now you finally have an interview invite. Nice. Also terrifying. Because Revolut interviews have a reputation: fast, direct, data-heavy, and not exactly the “let’s chat about your hobbies” type.

If you are aiming for an engineering role at Revolut in 2026, you need to prepare like you are joining a company that moves quickly, measures everything, and expects engineers to own outcomes, not just tickets.

This guide breaks down the Revolut engineering hiring process, what each stage usually looks like, how to prepare, what salary range to expect in Europe and the UK, and how to avoid the usual traps candidates fall into.

Revolut Engineering Hiring Process 2026: What To Expect#

Revolut is one of Europe’s biggest fintech companies, founded in London in 2015. It now operates across banking, payments, crypto, trading, business accounts, credit products, fraud prevention, risk, compliance tech, and internal platforms.

That means engineering roles can vary a lot.

A backend engineer working on payments infrastructure will not have the same interview loop as a mobile engineer working on consumer app flows or a data engineer building risk pipelines.

Still, the broad hiring process is usually similar:

1. Recruiter screen
2. Technical screening or online assessment
3. Technical interview
4. System design or architecture interview
5. Hiring manager interview
6. Bar raiser or values interview
7. Offer and negotiation

Sometimes stages are merged. Sometimes they add one. Sometimes they move absurdly fast.

That last part is worth saying twice: Revolut can move fast. If they like you, you may get interview stages packed into a short window. Do not wait until stage two to start preparing.

Roles Revolut Hires For In Engineering#

Revolut hires across a wide range of technical roles, including:

• Backend Engineer
• Java Engineer
• Kotlin Engineer
• Python Engineer
• Frontend Engineer
• Android Engineer
• iOS Engineer
• Full Stack Engineer
• Data Engineer
• Machine Learning Engineer
• Site Reliability Engineer
• Security Engineer
• QA Automation Engineer
• Engineering Manager
• Staff Engineer
• Product Owner with technical background

Backend roles are especially common. Revolut has historically used Java, Kotlin, PostgreSQL, Kafka, and cloud infrastructure across many teams, though stack details depend on the product area.

Mobile roles are also important because Revolut is app-first. If you are interviewing for Android or iOS, expect strong focus on architecture, performance, user experience, code quality, and shipping stable features in a high-scale consumer product.

For data roles, expect SQL, data modelling, pipeline design, metrics thinking, and business impact.

Revolut Engineering Culture: The Bit You Need To Understand#

Revolut is not trying to hire engineers who only want tidy Jira tickets and quiet sprints.

The company is known for being intense, ambitious, and metrics-driven. That does not mean every team is chaos. But it does mean interviewers will often test whether you can handle ownership, ambiguity, speed, and accountability.

You should be ready to talk about:

• Times you shipped under pressure
• How you made trade-offs
• How you handled incidents
• How you improved a metric
• How you worked with product, risk, compliance, or operations
• How you dealt with disagreement
• How you debugged something ugly
• How you made systems safer, faster, or cheaper

If you only talk about “I implemented the endpoint,” you may sound too passive.

Better: “I owned the checkout latency reduction project. We moved p95 latency from 900ms to 340ms by caching merchant configuration, cutting unnecessary network calls, and adding better database indexes. That improved payment success rate by 1.2 percentage points.”

That is the language Revolut likes: ownership plus numbers.

Stage 1: Recruiter Screen#

The recruiter call is usually 20 to 30 minutes.

Expect questions like:

• Why Revolut?
• Why are you looking to move?
• What type of role are you targeting?
• What is your current notice period?
• What are your salary expectations?
• Are you open to relocation or remote work?
• What tech stack do you use?
• Can you describe your recent projects?

This is not the time to ramble through your life story from university onward.

Keep it tight.

A good answer to “Why Revolut?” might sound like:

“I’m interested in Revolut because the engineering work sits close to real financial products at serious scale. I’ve worked on payments and identity systems before, and I like roles where backend decisions affect customer experience and business metrics directly. I’m especially interested in teams working on fraud prevention, cards, or business banking.”

That is much stronger than:

“I like fintech and I use the app.”

Everyone uses the app, mate.

Salary Expectations In The Recruiter Screen

You may be asked about compensation early.

Do not give a random number because you got nervous.

Revolut salaries vary by country, level, seniority, and team. Based on public salary data from platforms like Levels.fyi, Glassdoor, and job listings across Europe, rough 2026 engineering salary expectations may look like this:

Revolut may also offer equity or share-based compensation depending on role and location. Ask the recruiter how compensation is structured.

You can say:

“I’m currently targeting roles around £110,000 to £130,000 base depending on level, scope, and total package. I’m happy to discuss once we know the level fit.”

If you are in the EU:

“I’m looking around €95,000 to €115,000 base for senior backend roles, depending on scope and total compensation.”

If you are in Switzerland:

“For Zurich-based senior engineering roles, I’d expect something around CHF 140,000 to CHF 165,000 base, depending on level and package.”

Do not undercut yourself just to sound flexible.

Stage 2: Online Assessment Or Technical Screen#

Depending on the role, Revolut may use an online coding test, a live coding screen, or a technical recruiter-led assessment.

For software engineering roles, expect algorithmic coding, practical problem-solving, or backend-focused exercises.

Common topics include:

• Arrays and strings
• Hash maps
• Sorting
• Binary search
• Trees and graphs
• Dynamic programming basics
• Concurrency
• API design
• SQL queries
• Data modelling
• Debugging messy logic

The difficulty can range from medium LeetCode style to practical business problems.

For example:

• Detect suspicious transactions based on rules
• Design a simple ledger operation
• Parse event streams
• Calculate balances after ordered transactions
• Build a rate limiter
• Find duplicate users based on fuzzy matching
• Implement a cache with expiry
• Process card payment events in order

Revolut is a fintech, so expect money-related precision to matter. If you use floating point numbers for currency without thinking, that is a red flag.

Use integers for minor units, like cents or pence, or a proper decimal type depending on language.

How To Prepare For Revolut Coding Tests

You do not need to grind 500 LeetCode questions. But you do need to be sharp.

Focus on:

• 30 to 50 medium-level coding problems
• Clean function design
• Edge cases
• Time and space complexity
• Writing tests quickly
• Explaining your approach out loud
• Handling money and timestamps safely
• Basic concurrency if relevant to your language

If you code in Java or Kotlin, practise with collections until you are fast. Revolut backend interviews often expect fluency, not “let me Google how HashMap works.”

If you code in Python, do not rely on clever one-liners that nobody wants to maintain.

If you code in JavaScript or TypeScript, be ready to discuss async behaviour, event loops, and type safety.

For mobile roles, coding screens may include:

• Building a small UI component
• Refactoring a view model
• Handling API response states
• Fixing threading issues
• Designing app state flow
• Writing tests around business logic

Stage 3: Technical Interview#

The technical interview is often live with one or two engineers.

It may involve coding, debugging, design discussion, or a deep review of your previous work.

Expect questions like:

• Walk me through a complex system you built.
• Why did you choose that architecture?
• What would break at 10x scale?
• How did you test it?
• How did you monitor it?
• What trade-offs did you make?
• How would you reduce latency?
• How would you handle partial failure?
• How do you avoid duplicate financial transactions?
• How do you design idempotent APIs?

For fintech roles, idempotency is huge.

If a customer taps “send money” and the network times out, what happens when the client retries? You cannot send the money twice. You need idempotency keys, transaction boundaries, clear state transitions, reconciliation, and audit trails.

A strong answer might include:

• Client sends an idempotency key per operation
• Server stores request state and result
• Duplicate requests return the original result
• Database constraints prevent duplicate transaction creation
• Ledger entries are immutable
• State machine controls transaction lifecycle
• Monitoring catches stuck pending transactions
• Reconciliation jobs compare internal and external records

That kind of answer tells the interviewer you have thought about real systems, not just happy-path APIs.

Questions Revolut May Ask Backend Engineers

For backend roles, prepare for questions around:

• Microservices communication
• Event-driven architecture
• Kafka or similar messaging systems
• Database transactions
• Indexing and query performance
• Distributed locking
• Caching
• Rate limiting
• API versioning
• Observability
• Incident response
• Security basics
• Data consistency
• Ledger design

Sample question:

“Design a wallet transfer service where users can send money to each other instantly.”

You should cover:

• User account model
• Balance representation
• Ledger entries
• Transaction states
• Double-entry accounting basics
• Idempotency
• Atomicity
• Fraud checks
• Limits
• Notifications
• Audit logs
• Reconciliation
• Failure handling
• Monitoring

Do not just say, “I’ll update sender balance and receiver balance.”

That answer gets buried in the garden.

Money systems need traceability. Every balance should be derived from ledger entries or backed by a strong accounting model. Direct balance mutation without audit history is scary.

Questions Revolut May Ask Frontend Engineers

For frontend roles, expect:

• State management
• API error handling
• Performance
• Accessibility
• Component architecture
• Testing
• Security
• TypeScript
• Browser behaviour
• Build tooling
• Design systems

Sample question:

“How would you build a transaction history page for millions of users?”

Good points to include:

• Pagination or cursor-based loading
• Skeleton states
• Filtering and search
• API contract with backend
• Caching strategy
• Empty and error states
• Time zone handling
• Accessibility
• Virtualized lists if needed
• Observability for frontend errors
• Safe display of sensitive data

If you mention “just fetch all transactions,” expect pain.

Questions Revolut May Ask Mobile Engineers

For Android and iOS, expect practical questions around:

• App architecture
• Offline behaviour
• API retries
• Secure local storage
• Push notifications
• Performance profiling
• Memory leaks
• Threading and coroutines
• Swift concurrency
• Kotlin Flow
• Dependency injection
• Modular app design
• App release safety

Sample question:

“How would you handle a card freeze action in the app?”

You should mention:

• Immediate UI feedback
• Backend confirmation
• Loading and disabled states
• Idempotent request
• Retry logic
• Error recovery
• Analytics event
• Security checks
• State sync if user has multiple devices
• Push or polling update
• Testing for race conditions

Again, Revolut cares about user trust. If the app says a card is frozen, it had better be frozen.

Stage 4: System Design Interview#

For mid-level roles, system design may be lighter. For senior and staff roles, it is often one of the most important stages.

You may be asked to design something like:

• Payment processing system
• Peer-to-peer transfer system
• Fraud detection platform
• Currency exchange service
• Card authorization flow
• Notification platform
• KYC document processing pipeline
• Transaction monitoring service
• Subscription billing system
• Internal permissions platform
• Real-time analytics dashboard

The interviewer wants to see how you think.

They are not expecting a perfect diagram. They are looking for structured trade-offs.

A Good System Design Structure

Use this flow:

1. Clarify requirements
2. Define core use cases
3. Estimate scale
4. Sketch API contracts
5. Design data model
6. Choose storage
7. Explain services and boundaries
8. Handle failure cases
9. Discuss consistency
10. Add observability
11. Talk about security and compliance
12. Review trade-offs

For Revolut, always think about:

• Financial correctness
• Audit logs
• Fraud and abuse
• Latency
• Availability
• Regulatory constraints
• Data privacy
• Operational visibility
• Cost

If you are designing currency exchange, for example, you need to discuss exchange rates, rate expiry, quote locking, fees, settlement, ledger posting, and reconciliation.

If you are designing card authorization, you need to discuss low latency, network timeouts, merchant category rules, balance checks, risk checks, and fallback decisions.

Example: Designing A Peer-To-Peer Transfer System

Let’s say the prompt is:

“Design a system where Revolut users can send money instantly to each other.”

Start by clarifying:

• Same currency only or multi-currency?
• Domestic only or international?
• Are transfers reversible?
• Do we need limits?
• How many transactions per second?
• Is this internal ledger only?
• Are external bank rails involved?

Then propose services:

• User service
• Account service
• Ledger service
• Transfer orchestration service
• Risk service
• Notification service
• Compliance screening service
• Audit service

Data model:

• User
• Account
• Wallet
• LedgerEntry
• Transfer
• TransferState
• IdempotencyKey
• RiskDecision
• AuditEvent

Important state transitions:

• Created
• Risk checking
• Approved
• Posted
• Completed
• Failed
• Reversed

For correctness:

• Use database transactions where possible
• Use immutable ledger entries
• Use unique constraints for idempotency
• Use outbox pattern for reliable event publishing
• Avoid distributed transactions unless absolutely needed
• Reconcile balances regularly
• Alert on mismatches

For scale:

• Partition ledger by account or region
• Keep hot paths small
• Use async events for notifications and analytics
• Cache read-only user profile data
• Keep writes strongly consistent for money movement

For observability:

• Track transfer success rate
• Track p95 and p99 latency
• Alert on stuck states
• Alert on ledger imbalance
• Log correlation IDs
• Build dashboards by region and currency

This is the level of answer you want.

Not academic waffle. Practical, safe, measurable.

Stage 5: Hiring Manager Interview#

The hiring manager interview checks whether you fit the team’s needs.

Expect questions like:

• What kind of work motivates you?
• How do you handle unclear requirements?
• Tell me about a time you disagreed with product.
• Tell me about a production incident.
• How do you prioritise technical debt?
• How do you mentor others?
• What are your career goals?
• What would your current manager say you need to improve?
• How do you handle pressure?

Revolut managers often care about pace and ownership.

They want people who can take a messy goal and make progress without waiting for perfect instructions.

Use STAR, But Do Not Sound Like A Robot

STAR means:

• Situation
• Task
• Action
• Result

It is useful, but if you sound like you memorised a government form, the vibe dies.

Instead, tell the story naturally.

Weak answer:

“I was responsible for improving system performance. I worked with the team and improved it.”

Better answer:

“Our onboarding API was timing out during peak traffic, especially after marketing campaigns. I owned the investigation. I found two slow database queries and one external vendor call sitting in the critical path. We added indexes, cached low-risk vendor responses for 10 minutes, and moved one check async. Timeout rate dropped from 4.8% to 0.3%, and onboarding completion improved by about 2%.”

That answer has context, action, and numbers.

Stage 6: Bar Raiser Or Values Interview#

Some Revolut loops include a final cultural or bar-raiser style interview.

This can feel blunt. Do not panic.

They may probe:

• Ownership
• Bias for action
• Resilience
• Customer focus
• Data-driven decisions
• High standards
• Communication
• Conflict
• Learning from mistakes

You may get follow-up questions that feel repetitive:

• Why did you do that?
• What was your exact role?
• What did others do?
• What was the measurable impact?
• What would you do differently?
• How do you know it worked?

They are testing depth.

If you exaggerate, they will probably find the soft spot and poke it.

So choose real stories where you can answer details.

Stories To Prepare Before The Interview

Prepare 6 to 8 stories from your experience.

Have stories for:

1. A major technical project
2. A production incident
3. A conflict with a stakeholder
4. A time you moved fast
5. A time you improved quality
6. A time you used data to make a decision
7. A time you mentored someone
8. A mistake you made

For each story, write down:

• What happened
• Your role
• The technical challenge
• The business impact
• Metrics before and after
• What you learned

You do not need to memorise scripts. You need clean recall.

Revolut Interview Difficulty Compared With Other EU Companies#

Revolut interviews are generally more intense than many traditional European tech employers.

Compared with Wise, Monzo, N26, Klarna, Adyen, Booking.com, Spotify, Zalando, Delivery Hero, and Checkout.com, Revolut tends to stand out for pace, direct questioning, and strong ownership expectations.

That does not mean it is harder in every technical sense.

Google Zurich or Meta London may ask tougher algorithmic questions. Palantir London may go deeper on problem-solving. Amazon Luxembourg may be more structured around leadership principles. Bloomberg London may have fast technical rounds with a lot of coding.

Revolut’s challenge is the mix:

• You need technical depth
• You need product thinking
• You need fintech awareness
• You need metrics
• You need strong communication
• You need to handle pressure

If you like calm, slow-moving environments with lots of consensus, Revolut may not be your dream place.

If you like shipping, ownership, and high-growth fintech problems, it can be attractive.

Revolut Engineering Salaries In 2026#

Let’s talk money properly.

Revolut compensation depends on level, location, and market conditions. It can include base salary, equity, and benefits. Some roles may be remote or hybrid, but location still affects pay.

Here are realistic salary bands to think about for 2026, based on public market data and typical fintech compensation across Europe.

United Kingdom

London remains one of Revolut’s major hubs.

Typical base salary ranges:

• Junior Software Engineer: £45,000 to £65,000
• Mid Software Engineer: £70,000 to £95,000
• Senior Software Engineer: £95,000 to £130,000
• Lead Engineer: £120,000 to £160,000
• Staff Engineer: £140,000 to £190,000+
• Engineering Manager: £115,000 to £175,000

For comparison, Wise senior engineers in London often sit around £90,000 to £130,000 base, Monzo senior engineers around £90,000 to £125,000, and Checkout.com senior engineers can reach similar or higher ranges depending on team.

European Union

Revolut has hired across countries including Poland, Portugal, Spain, Lithuania, Romania, Germany, France, and Ireland.

Approximate base ranges:

• Junior Software Engineer: €35,000 to €55,000
• Mid Software Engineer: €55,000 to €85,000
• Senior Software Engineer: €80,000 to €125,000
• Lead Engineer: €105,000 to €150,000
• Staff Engineer: €125,000 to €175,000+
• Engineering Manager: €105,000 to €165,000

In Poland, senior fintech backend roles at companies like Revolut, Allegro, and Box can often range from around €70,000 to €120,000 equivalent, depending on contract type.

In Germany, senior engineers at N26, Trade Republic, Zalando, and Delivery Hero often land around €80,000 to €130,000 base.

In the Netherlands, Booking.com, Adyen, and Uber Amsterdam can pay strong senior packages, often around €90,000 to €150,000 base for experienced engineers.

Switzerland

Switzerland is its own beast.

If you are comparing with Google Zurich, UBS, Swissquote, Avaloq, or fintech roles in Zurich and Geneva, salary expectations are higher.

Approximate base ranges:

• Mid Software Engineer: CHF 105,000 to CHF 135,000
• Senior Software Engineer: CHF 130,000 to CHF 170,000
• Staff Engineer: CHF 165,000 to CHF 220,000+
• Engineering Manager: CHF 150,000 to CHF 220,000+

If a role is remote but tied to a lower-cost EU country, do not expect Zurich-level pay.

How To Prepare In 14 Days#

If your interview is soon, here is a practical 14-day plan.

Days 1 To 3: Coding Refresh

Do:

• 10 array and hash map problems
• 5 string parsing problems
• 5 sorting or binary search problems
• 3 graph or tree problems
• 2 dynamic programming basics

Practise explaining out loud.

Use your interview language. If you will interview in Java, practise in Java. Sounds obvious, but people still prepare in Python then interview in Kotlin and wonder why they move like a sleepy turtle.

Days 4 To 5: Fintech System Basics

Study:

• Idempotency
• Ledger entries
• Double-entry accounting basics
• Payment states
• Reconciliation
• Fraud checks
• Rate limiting
• Audit logs
• KYC and AML basics
• Data privacy

You do not need to become a banking lawyer. You just need to show you understand money systems are not normal CRUD apps.

Days 6 To 8: System Design Practice

Practise designing:

• Wallet transfer system
• Card authorization system
• Currency exchange quote system
• Notification service
• Fraud detection event pipeline

For each, talk through requirements, APIs, data model, failure handling, consistency, and metrics.

Record yourself once. Painful, yes. Useful, also yes.

Days 9 To 10: Behavioural Stories

Prepare your 6 to 8 stories.

Add numbers wherever possible:

• Latency reduction
• Cost savings
• Error rate drop
• Revenue impact
• Conversion improvement
• Deployment frequency
• Incident reduction
• Team productivity

If you do not have exact numbers, use reasonable approximations and say “around” or “roughly.”

Do not invent.

Days 11 To 12: Mock Interviews

Do at least two mock interviews.

One coding.

One system design.

If you cannot find someone, talk to yourself with a timer. Yes, you will feel ridiculous. No, it does not matter.

Days 13 To 14: Company And Role Prep

Read:

• Revolut engineering blog posts
• Product announcements
• Recent funding or financial news
• Job description line by line
• Team-specific requirements
• Your own CV

Prepare smart questions, such as:

• What is the team’s biggest technical challenge this year?
• How do engineers measure impact?
• How are incidents handled?
• What does success look like in the first six months?
• How are product and engineering decisions made?
• What are the main reliability goals for the team?

Common Mistakes Candidates Make#

Let’s save you from the obvious traps.

Mistake 1: Being Too Generic

“I want to work at a fast-growing fintech” is not enough.

Say what kind of engineering problems interest you.

Payments? Fraud? Cards? Wealth? Internal platforms? Data infrastructure? Mobile performance?

Specific beats vague.

Mistake 2: Ignoring Fintech Details

If you design a money transfer system and forget idempotency, audit logs, or reconciliation, that is bad.

Revolut builds financial products. Correctness matters.

Mistake 3: Talking Only About Code

Code is the job, but not the whole job.

Talk about impact, customers, metrics, incidents, trade-offs, and team decisions.

Mistake 4: Weak Communication During Coding

Interviewers need to see your thinking.

Say:

“I’ll start with a simple hash map approach. That gives O(n) time and O(n) space. Then I’ll check edge cases like empty input, duplicate values, and large numbers.”

Do not sit silently for 18 minutes then say, “done.”

Mistake 5: Pretending You Know Everything

If you do not know, say so.

Then reason from first principles.

“I haven’t implemented that exact pattern in production, but I understand the goal is to avoid losing events between the database write and message publish. I’d consider an outbox table written in the same transaction, then a worker publishes events and marks them sent.”

That is a good answer.

Mistake 6: Not Preparing Your CV

Anything on your CV is fair game.

If you wrote “Kafka,” be ready to explain partitions, consumer groups, retries, ordering, and dead letter queues.

If you wrote “AWS,” be ready to discuss services you actually used.

If you wrote “improved performance,” know by how much.

What To Ask Revolut Interviewers#

Good questions can help you judge the role and show maturity.

Ask questions like:

• What are the main goals for this team in 2026?
• What technical debt is currently slowing the team down?
• How much ownership do engineers have over product decisions?
• What is the on-call setup?
• How often do incidents happen?
• How do teams balance speed and reliability?
• What metrics does the team care about most?
• How is engineering quality reviewed?
• What does career growth look like for senior engineers?
• What would make someone unsuccessful here?

That last question is spicy, but useful.

If they say, “People struggle when they need too much structure,” believe them.

Offer Negotiation Tips#

If you get an offer, congrats. Do not immediately say yes while still emotionally floating.

Ask for the full package in writing:

• Base salary
• Equity or share options
• Bonus if any
• Signing bonus if any
• Pension contributions
• Health insurance
• Remote or hybrid expectations
• Working location
• Notice period support
• Relocation package
• Level
• Job title
• Manager and team

Then compare with market options.

If you are also interviewing with Wise, Monzo, Adyen, Spotify, Booking.com, Klarna, N26, Trade Republic, Zalando, or Google, mention competing timelines professionally.

Example:

“I’m excited about the Revolut role and the team looks like a strong fit. I’m also in late-stage conversations with two other companies, so I’d like to understand whether there is flexibility on the base salary or equity component. Based on the scope and market data, I was hoping for something closer to £125,000 base.”

Keep it calm. No weird ultimatums.

For EU:

“Given the seniority and the ownership described, I was expecting closer to €115,000 base. Is there room to adjust the offer?”

For Switzerland:

“For this level in Zurich, I was expecting around CHF 160,000 base. Can we discuss whether the package can move closer to that?”

Negotiation is normal. Be polite and specific.

Is Revolut A Good Place For Engineers In 2026?#

It depends what you want.

Revolut can be a strong choice if you want:

• High-impact fintech work
• Fast product cycles
• Strong ownership
• Large-scale systems
• International teams
• Career acceleration
• Exposure to regulated financial products

It may not be ideal if you want:

• Slow pace
• Very predictable work
• Low-pressure environment
• Lots of hand-holding
• Minimal ambiguity
• A traditional bank culture

Read employee reviews, talk to current or former engineers if you can, and ask direct questions during interviews.

The right team matters a lot.

One team may be building a new product under pressure. Another may be improving core infrastructure. Another may be dealing with compliance deadlines. Same company, different daily life.

Final Prep Checklist#

Before your Revolut engineering interview, make sure you can:

• Solve medium coding problems in your main language
• Explain time and space complexity
• Design APIs clearly
• Talk about idempotency and financial correctness
• Explain database transactions and indexing
• Discuss event-driven systems
• Handle system design prompts with structure
• Tell 6 to 8 strong career stories
• Give metrics for your past work
• Explain every major line on your CV
• Ask smart questions about team, scope, and culture
• Discuss salary expectations without panicking

Also, please clean up your CV before applying or before the recruiter forwards it internally.

Revolut gets plenty of strong applicants. If your CV buries the good stuff under vague bullets like “worked on backend services,” you are making life harder for yourself.

Say what you built, what scale it handled, what improved, and what technologies you used.

Example:

Bad:

“Worked on payment APIs and fixed bugs.”

Better:

“Built idempotent payment retry APIs in Java and PostgreSQL, reducing duplicate payment incidents by 37% and cutting manual operations tickets by 22%.”

That is the difference.

If you want to check whether your CV is likely to pass an ATS before applying to Revolut, run it through JobRise for free here: https://jobrise.io/free-ats-checker/