Job intelligence
Senior Backend Engineer (Data serving)
Pleo
Before relying on the listing: Confirm Compensation and Application closing time with the employer or source. See verification questions
Executive opportunity brief
The decision in one screen
A compact evidence-first read of compensation, flexibility, mobility and what still needs verification. No universal quality score is used.
Fast read
Opportunity DNA
This opportunity needs a closer read before drawing a strong conclusion, especially around the pay picture is incomplete.
A financial comparison will need the approved compensation range.
Geographic eligibility is restricted to a country or region.
The listing does not make the minimum education or experience threshold clear enough yet.
Work authorization, sponsorship or relocation wording may materially limit who can take the role.
Part of the application route can be assessed, but the full external process may contain additional steps.
At least one recent enabled source can still renew this vacancy.
This fingerprint summarizes what is clear, constrained or still unanswered in the current listing. It is a reading aid, not an overall job score.
Decision evidence check
3 of 5 core facts stated
This checks whether the listing states the facts that commonly change an employment decision. It measures disclosure completeness, not whether the opportunity is good or bad.
Facts already stated
- Work arrangement
- Advertised location
- Employment type
What to verify next
- Compensation: What is the approved compensation range, and what portion is guaranteed base pay rather than variable compensation?
- Application closing time: Is there a firm application deadline, a rolling review window or no stated closing date?
Advertised location is not proof of work authorization, sponsorship, or legal eligibility. Unknown information is not a negative score; verify those questions separately.
Decision levers
What could make or break the fit?
Reasons to look closer
Nothing stands out strongly enough yet to call a clear advantage. The role may still be attractive for reasons the listing does not spell out.
Trade-offs to weigh
- The pay picture is incomplete: No usable salary range is stated, so a meaningful financial comparison is not possible yet.
- Location rules could change the fit: Geographic eligibility is restricted to a country or region.
- Sponsorship could be a hard constraint: The listing says sponsorship is unavailable or that work authorization is required without sponsorship.
Questions worth asking before you invest more time
- Ask for the approved compensation range before comparing this opportunity financially.
- Confirm whether a degree is actually required, preferred, or replaceable with equivalent experience.
- Confirm the actual minimum experience requirement rather than assuming preferred background is mandatory.
These questions come from details the listing leaves open. An unanswered point is not treated as a disadvantage.
Opportunity neighborhood
Keep your options open
These live roles sit close enough to this opportunity to make useful comparison points. Look across several employers before deciding what pay, flexibility or access trade-offs you are willing to accept.
Principal Software Engineer - XTM One
Filigran · France, Germany, Italy, Portugal, Spain, UK
Why it is nearby: Same seniority band · Same country · Similar work arrangement
Software Engineering Manager, Mobile Products
NerdWallet · USA
Why it is nearby: Same seniority band · Similar work arrangement · Same employment type
Different angle: Different country
AI Platform Engineer
Supabase · Anywhere
Why it is nearby: Same seniority band · Similar work arrangement · Same employment type
Software Engineering Manager - Security
Thought Machine · United Kingdom, London
Why it is nearby: Same country · Same employment type · Recently posted
Different angle: Seniority is not explicit · Different work arrangement
This neighborhood is drawn from current inventory in the same broad occupation. Similarity is based on explicit listing facts; missing details do not count against a job.
Role market context
How much current choice is visible around this kind of work?
This compares the vacancy with current High Paid Job inventory in the broad Software engineering roles family. It describes visible choice and disclosure, not future demand or career quality.
200 most recent current roles sampled for the disclosure measures below.
Distinct employers in the bounded current sample, not an estimate of all employers hiring in the market.
Current sampled roles stating at least four of the five Core Decision Facts.
Requires a numeric amount, explicit ISO currency and supported pay period.
Listings with explicit enough remote, hybrid or on-site evidence to classify.
Missing deadline evidence remains unknown and is not interpreted as an open-ended application window.
Currencies with explicit pay evidence in the sample: USD (29) · EUR (11) · GBP (8) · SEK (2). Raw amounts across different currencies are not compared.
This describes current visible High Paid Job inventory in the same broad occupation family. Percentages use a bounded recent sample and are not a forecast, a complete labor-market census or an employer-quality measure.
Constraint opportunity lab
What changes the size of the current opportunity pool?
Each line applies one stricter evidence-based constraint to the same bounded current role-family sample. It helps you see the trade-off in visible choice without deciding which trade-off is right for you.
Counts only affirmative or possible sponsorship evidence, or relocation explicitly offered. Unknown is not treated as no.
A much stricter subset: only listings with explicit worldwide-remote evidence remain.
Requires amount, explicit ISO currency and a supported pay period. Missing pay evidence remains unknown.
Uses only roles where a country is known. Roles without country evidence are excluded from this denominator.
Shows the subset with enough stated evidence for a more informed first comparison.
Includes roles whose seniority is genuinely unspecified rather than assuming they belong to another level.
Counts roles explicitly classified as worldwide remote, region-restricted remote or remote with restrictions still unclear.
Uses only roles with a stated employment type.
These are counterfactual filters over a bounded sample of current HPJ inventory in the same broad occupation family. They show how visible choice changes when one evidence-based constraint is applied; they do not tell you which constraint you should choose or predict hiring outcomes. The calculation uses the 200 most recent current roles from 3459 visible roles in this broad family.
Salary transparency context
Is pay disclosure typical for this kind of role?
This listing does not state usable structured compensation. About 26% of the bounded current role sample does.
Compensation counts only when amount, ISO currency and supported pay period are all known.
Pay disclosure is limited in the current role sample.
This employer’s current visible listings disclose pay materially less often than the current same-role sample.
This compares salary-disclosure behavior in current visible listings. It does not compare raw salary amounts across currencies, infer undisclosed pay as zero, or rate employer quality.
Private offer & negotiation lab
Turn an offer into evidence, not guesswork
Enter an annual base offer and, if you want, your own target. HPJ compares only within one explicit currency and never chooses a target for you.
Negotiation evidence available: current same-currency market context.
Enter an annual base offer to compare it with explicit same-currency evidence. HPJ will not suggest a target for you.
Review the full package · 10 terms
Mark what is confirmed, what needs clarification and what you want to prioritize. These choices and notes stay in this browser.
The approved base-pay range is not established in the listing.
Variable compensation is mentioned; verify amount, formula, target and eligibility.
Equity or long-term incentive language is mentioned; verify grant type, vesting and valuation basis.
Retirement or pension benefits are mentioned; verify employer contribution and vesting.
Health-benefit language is mentioned; verify coverage, dependants and employee cost.
Paid-leave language is mentioned; verify the exact entitlement and carry-over rules.
A work-arrangement signal is available; verify schedule details before relying on it.
Relocation support not established
Sponsorship explicitly unavailable
A review cycle is mentioned; verify timing and whether compensation can change at that review.
Questions worth taking into the offer conversation
- What is the approved base-pay range for this role?
- Is there a bonus, commission or other variable-pay component, and how is it calculated?
- Does the package include equity or another long-term incentive, and what are the vesting terms?
- What retirement or pension contribution does the employer provide?
- If relocation is relevant, what expenses, timing and repayment conditions are covered?
- When is the first performance and compensation review after joining?
- What is the approved compensation range, and what portion is guaranteed base pay rather than variable compensation?
- Is there a firm application deadline, a rolling review window or no stated closing date?
Occupation intelligence
What broader career references connect to this role?
HPJ uses broad comparison families for current-market analysis. External taxonomy results are reference candidates for that broad family, not a declaration that this vacancy has been authoritatively classified into a specific occupation.
European occupation references
- software developer
- embedded systems software developer
- industrial mobile devices software developer
- ICT application developer
- IoT developer
This service uses the ESCO classification of the European Commission.
U.S. occupation references
- Software Developers 15-1252.00
- Computer Programmers 15-1251.00
- Software Quality Assurance Analysts and Testers 15-1253.00
- Computer Systems Analysts 15-1211.00
- Computer Systems Engineers/Architects 15-1299.08
This site incorporates information from O*NET Web Services by the U.S. Department of Labor, Employment and Training Administration (USDOL/ETA). O*NET® is a trademark of USDOL/ETA.
Career reference research
Skills worth investigating
Official occupational context, paired with exact phrases visible in this vacancy. It is not a skills test or an applicant-fit score.
ESCO · European occupation
software developer
Usually essential in this ESCO occupation
- use software design patterns
- computer programming
- engineering principles
- use software libraries
- technical drawings
- debug software
- integrated development environment software
Context-dependent ESCO skills
- Pascal (computer programming)
- migrate existing data
- Groovy
- Scratch (computer programming)
- screen reader
O*NET · U.S. occupation
Software Developers
O*NET occupation skills
- ProgrammingPhrase in listing
- Critical Thinking
- Judgment and Decision Making
- Active Learning
- Reading Comprehension
- Systems Analysis
- Active Listening
- Complex Problem Solving
Build my private skill preparation brief Your evidence · Practice · Interview questions
Plan how you might demonstrate or investigate occupational skills. These are broad-family reference examples, not confirmed vacancy requirements. Nothing you enter is sent to High Paid Job.
Private to this browser. Up to 20 reference skills; not a qualification assessment or hiring prediction.
Useful next question: Which of these occupational reference skills does the hiring manager actually expect for this specific role, and what evidence would demonstrate them?
These skills belong to one reference occupation selected for HPJ’s broad career family, not a verified classification of this vacancy. Text overlap only means a phrase appears in the available listing text; it does not establish an employer requirement, your proficiency, or a qualification gap. A missing mention is unknown, not a deficit.
Adjacent current roles to investigate
Head of Strategy and Product
Bjak · United Kingdom
same stated country · same seniority band · same employment typeSenior Data Analyst, Marketing Measurement
Airalo · Germany, Spain, UK
same stated country · same employment type · similar work-arrangement evidenceDirector of Product - Network
Nomi Health · USA
same seniority band · same employment type · similar work-arrangement evidenceAdjacent-family roles are exploration prompts from current HPJ inventory. They are not inferred qualification matches and they do not imply a promotion path.
Career move map
What sits one step away?
This listing is currently read as Leadership. Nearby roles one visible seniority step away can help you judge whether to widen the search, stretch upward or compare the responsibilities more carefully.
Broader-entry direction
Senior Full Stack Engineer | Experimentation - Product Analytics | UK | Remote
Grafana Labs · Germany, Ireland, Spain, Sweden, UK
Same country · Similar work arrangement · Same employment typeSenior Systems Test Engineer
Salience Labs · Oxford, United Kingdom
Same country · Same employment type · Recently postedThese are live roles one visible seniority step away in the same broad occupation family. They can reveal nearby options, but they are not a guaranteed promotion path and do not account for your personal experience.
Skill bridge
What does this role connect to?
AWS is one of the signals this listing shares with skills appearing often across current Software engineering roles opportunities.
Skills named in this listing
Shared with the current career sample
- AWS Seen in 37 sampled listings
- Google Cloud Seen in 19 sampled listings
- Kubernetes Seen in 28 sampled listings
- PostgreSQL Seen in 15 sampled listings
Combinations also appearing together
- AWS + Google Cloud appeared together in 17 sampled listings
- AWS + Kubernetes appeared together in 17 sampled listings
- AWS + Python appeared together in 12 sampled listings
Additional signals in this listing: Docker · Generative AI · Kotlin
Application edge
- If these skills match your background, prepare one concrete example that shows how you used AWS, Docker, and Google Cloud rather than relying on a keyword-only claim.
- The listing mentions extra application steps. Review those requirements before starting so you can prepare the requested material in one pass.
If the named skills are genuinely transferable in your own experience, the occupation map also points to adjacent current families worth researching: Data & AI roles, Cybersecurity roles, and Product roles. This is exploration context, not a qualification match.
Skill signals come from explicit text mentions. A mention is not automatically a requirement, and absence from the current top-skill list does not make a skill rare or unimportant. The current career comparison draws on 120 sampled listings; 107 contain a recognized skill signal.
Application Decision Lab
Turn the listing into a preparation plan
Separate what the listing actually states from what you still need to prepare or verify. Your selections and short notes stay in this browser and are never submitted to High Paid Job.
AWS
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
Docker
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
Google Cloud
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
Generative AI
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
Kotlin
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
Kubernetes
This skill or technology is explicitly mentioned in the available listing text. A mention is not automatically a mandatory requirement; prepare a concrete example only if it is relevant to your experience.
Prepare for a stated application step
An assessment, test or work-sample step is explicitly mentioned.
Questions worth resolving before you rely on the opportunity
- Compensation: What is the approved compensation range, and what portion is guaranteed base pay rather than variable compensation?
- Application closing time: Is there a firm application deadline, a rolling review window or no stated closing date?
Decision analysis
What the listing really tells you
For Senior Backend Engineer (Data serving) at Pleo, the most useful clues right now are the location rules are clear enough to judge, sponsorship and relocation signals are visible, and the application route gives a few useful clues. Looking at them together makes the trade-offs easier to see.
The location rules are clear enough to judge
Location flexibility can be assessed here: Remote with some uncertainty or restrictions, with a Remote Freedom reading of 62/100. The most important location constraint is geographic eligibility is restricted to a country or region..
Sponsorship and relocation signals are visible
Sponsorship explicitly unavailable. These details help frame the practical questions to ask; they are not immigration advice or a guarantee of eligibility.
The application route gives a few useful clues
Provider-mediated application path · 1 visible process step. The external application may contain additional steps that are not visible from the listing itself.
The listing can be traced to a current source
1 recent enabled source can currently renew this vacancy across 1 source classes. That improves traceability, although it does not verify the employer itself.
How this analysis is assembled
Built from the pay, location, qualification, mobility, application and source details available for this vacancy. Anything the listing leaves unresolved stays unresolved.
Analysis evidence coverage
How much analysis can the current evidence support?
Comparable salary data is not available for this job yet.
Measures observable location flexibility and explicit restrictions; it does not determine whether remote work is personally desirable.
Missing compensation is not treated as negative evidence; this dimension simply remains unavailable.
The listing was posted about 1 days ago.
At least one enabled source recently observed the vacancy. The source chain is traceable, but this is not independent employer verification.
There is no universal opportunity score because pay, flexibility and access matter differently to different people. Compare Jobs lets you weight the evidence around your own priorities.
Decision checklist
What is supported, uncertain or worth checking?
This checklist separates supported strengths, visible cautions and missing evidence. It is not an overall recommendation or guarantee that the job is suitable for you.
Supported strengths
No standout strength is supported strongly enough to list here. That is not a negative rating.
Visible cautions
- Geographic eligibility is restricted to a country or region.
- The role may involve non-standard hours or on-call work.
- This is remote work with a geographic restriction, not a worldwide-remote vacancy.
Still unknown
- There is not enough comparable salary evidence to establish this job’s current pay position.
Pay vs. barriers
Opportunity Efficiency not assessed
The current pay position is not reliable enough to weigh compensation against the stated barriers.
1 explicit Remote Freedom restriction signal is present and is shown separately from qualification requirements.
- Current comparable pay position is unavailable.
- Education requirement is not established.
- Required prior-experience level is not established.
This section weighs pay context against clearly stated barriers without collapsing unlike requirements into one universal score. Degree, experience, licensing, clearance and location limits remain separate, and missing qualification details stay unknown.
Beyond the headline
Not enough evidence for a hidden-value finding
Potential hidden value appears only when several distinct non-pay advantages are actually supported. Missing requirements or benefits are never counted as positives.
Still check: The current application path is provider-mediated rather than directly classified as an employer-authorized or official route.
Hidden Value is an experimental evidence summary, not an investment-style score or guarantee of employability. It only uses explicit current listing evidence and does not infer that an unmentioned qualification is unnecessary.
Compensation intelligence
How competitive is this pay?
Comparable salary data is not available for this job yet.
Why this analysis?
- Comparable salary data is not available for this job yet.
- Salary confidence: Not available. No disclosed salary can currently be normalized for comparison. Missing compensation is not treated as low-quality salary evidence.
- Range quality: No disclosed range.
Employer compensation communication
Pay transparency at Pleo
Limited current pay transparency
This score uses the employer’s current visible listings and combines how often pay is disclosed with how useful those ranges are. Bonus, equity and benefit mentions are shown separately and do not raise the score.
This pattern comes from the employer’s current visible vacancies. It describes hiring and pay transparency in those listings, not employee satisfaction or a permanent judgement of the employer.
Current employer intelligence
Pleo — current opportunity snapshot
Employer Evidence Profile
How often this employer’s current visible sampled vacancies state decision-critical information. These percentages describe evidence coverage, not employer quality.
Current sampled listings with advertised compensation evidence.
Current sampled listings whose work arrangement is clearer than unknown.
Current sampled listings with a supported country signal.
Current sampled listings with an explicit closing time.
Current sampled listings with a usable posting date.
Current sampled listings that explicitly indicate confirmed, possible or unavailable sponsorship evidence.
Current sampled listings with an explicit relocation signal.
Low coverage means the current visible listings state the information less often. It does not prove that the employer lacks the policy, benefit or support.
Common current occupation families: Software engineering (5) · Sales (5) · Customer success (4)
Visible seniority mix: Senior / lead (15) · Leadership (6)
Current employment-type mix: Full time (33) · Contract (1)
Most visible hiring countries in this sample: United Kingdom (16) · Portugal (3) · Spain (1) · Denmark (1)
Other current roles from this employer
Customer Support Specialist (Danish Speaking)
London
Seniority not clearly specified · On-site / hybridDigital Onboarding Specialist I - Lisbon / Madrid
Portugal, Spain
Senior / lead · Remote — restrictions unclearSenior Backend Engineer (Data serving)
United Kingdom
Senior / lead · On-site / hybridFraud Operations Analyst
Portugal
Seniority not clearly specified · Remote — restrictions unclearThese are other current vacancies visible from the same employer, not endorsements or evidence of future hiring plans.
There are not yet five current disclosed salaries in one currency, so an employer pay median would be too thin to be useful.
Questions worth asking this employer
- What compensation range applies to this role, and which parts of total compensation are fixed versus variable?
- If work authorization matters to you, what sponsorship policy applies to this specific role and location?
- If a move is required, is relocation assistance available for this position?
- What is the expected application and interview timeline if the listing does not state a closing date?
These questions are prompted by missing or thin evidence in the employer’s current visible vacancies. Missing evidence is not treated as a negative judgement.
This employer snapshot uses the employer’s current visible listings. Remote and sponsorship rates use only vacancies with explicit evidence, while missing information stays unknown. Salary medians are shown separately by currency and need at least five disclosed salaries. Zero confirmed sponsorship means none was explicitly found in this sample, not that sponsorship is unavailable.
This snapshot describes the employer’s current visible vacancies—things such as pay disclosure and work arrangement. It is not an employee-satisfaction or hiring-quality rating, and different currencies stay separate.
Work-location intelligence
Remote Freedom
Remote with some uncertainty or restrictions
Why this score?
- The role is remote but the source identifies a country or regional restriction.
Location restrictions detected
- Geographic eligibility is restricted to a country or region.
Remote Freedom measures observable location flexibility only. Unknown work-location information remains unscored. Timezone wording is penalized only when it appears restrictive; general collaboration across time zones is not treated as a restriction. A score does not guarantee legal work eligibility, payroll availability or visa sponsorship.
International applicant intelligence
Visa & relocation signals
Sponsorship status is shown only when the listing provides clear enough wording. Employer history or headquarters location is not used to guess an answer.
The available job text explicitly indicates sponsorship is unavailable or that work authorization is required without sponsorship.
The available listing details do not contain a clear enough relocation statement.
Tradeoff check
What’s the catch?
These are visible conditions worth checking before treating the headline compensation as the whole story:
- The role may involve non-standard hours or on-call work.
- This is remote work with a geographic restriction, not a worldwide-remote vacancy.
Application-path intelligence
What can we see about the application process?
Provider-mediated application path
The current application path comes through a publisher or aggregator. The destination may still lead to an employer-authorized hiring system, but that is not clear enough to assume.
Current destination: jobicy.com · HTTPS
Visible application steps or requirements
- An assessment, test or work-sample step is explicitly mentioned.
Application effort is estimated from visible listing and source details. Optional steps are kept separate from mandatory ones, and the external form may contain additional requirements that are not visible here.
Application safety context
Application safety check
Basic application-safety context available
The current application destination has a basic transport-safety signal such as HTTPS. This does not verify the employer, vacancy, recruiter or application process.
Evidence checked: Source provenance · Application destination · Listing wording
Observable transport-safety signals
- The available application destination uses HTTPS.
Before you share money or sensitive information
- Confirm the vacancy on the employer’s official careers site when practical, especially if a recruiter contacts you outside the listed application path.
- Check that recruiter email domains and application destinations are consistent with the employer or an identifiable recruiting provider.
- Do not pay application, processing, training or equipment fees merely to be considered for a job.
- Do not send cryptocurrency, gift cards, online-banking credentials or PINs as part of an application.
- Treat unusually fast offers or interviews conducted only through informal messaging channels as reasons to verify the employer independently.
This is a limited safety screen, not employer verification and not a fraud determination. Never send money, cryptocurrency, passwords or sensitive banking credentials merely because a listing appears on a job platform.
Original listing details
The section below comes from the listing source. The decision sections above use the job’s structured pay, location, qualification, mobility and application details to give you additional context.
About Pleo
Messy spend management is tricky business. And tedious processes are a lose-lose situation for all involved, not just finance. At Pleo, we're changing that. We build spend solutions that make managing money seamless, empowering, and surprisingly effective for finance teams and employees alike - with a vision to help all businesses ‘go beyond’.
The word ‘Pleo’ actually means ‘more than you’d expect’, and living by that mantra has been the secret to our success over the last 10 years.
Now, we’re at a pivotal moment in our journey; every move we make has a direct impact on our 40,000+ customers, our business, and our collective success. We need people who take pride in uncovering customer needs, who turn complex problems into simple solutions, challenge the way things are done (respectfully), and always aim high. With great ambitions driving us forward, we can’t say we’ve got this whole thing figured out. And frankly, that’s half the fun! What we can say is that we’re a driven, progressive, and, importantly, a kind bunch of 850+ people from over 100 nationalities, all committed to delivering the future of business spending, together.
Please note: applications will be open until Tuesday 13th October 2026 at 08.00 CEST.
We will not review any application before the closing date so please use this time to submit a high quality application.
About the role
We're looking for a Senior Backend Engineer to join the Data Serving team that owns the production-grade boundary between Pleo's raw product data and everyone who consumes it, including internal product teams, AI agents, and customers directly accessing their own data. This Senior Backend Engineer role builds and owns that boundary: APIs and the low-latency serving layer underneath it. You will build customer-facing infrastructure where contract stability and latency are non-negotiable, and where the clean abstraction you maintain is what lets every downstream consumer trust the data without ever touching a raw source.
Who you’ll be working with and reporting to
You will report to our VP of Data, and work closely with our Staff Data Platform Engineer, Data Engineers, Product Managers and others Engineers across the business. You'll also coordinate closely with the GenAI Platform and Data Infrastructure teams.
What you’ll be doing
As a Senior Backend Engineer, you will:
-
Build and own the Data API boundary: delivering clean, versioned, and performant endpoints for internal dashboards, customer-facing features, and third-party tools (e.g., Fivetran connectors via incremental syncs and cursor pagination).
-
Design and optimise the read models, indexes, and caching strategies in Postgres (and future OLAP stores) to guarantee low-latency query performance.
-
Build reliable integrations with Pleo’s Kotlin-based product backend services to ensure the serving layer surfaces the correct data required for a customer facing feature.
-
Own the reliability and performance of the services you build: monitoring, incident response, and SLOs appropriate to customer-facing infrastructure.
-
Partner with Data Engineers to define clean contracts between the ingestion/aggregation layer and the serving DB, ensuring read patterns match storage schemas.
-
Partner with the Authorization team to secure APIs using industry-standard authentication and authorization protocols.
-
Build a near-real-time data aggregation service to collect and unify data across Pleo services.
-
Design metadata, lineage, and governance capabilities that make the serving layer explainable, auditable, and trustworthy.
-
Own access control and permission management services, including row and column-level data access with full audit trails.
To put things into context, you can expect to work with the following tech stack: AWS (product side), GCP (data side), Docker, Kubernetes, BigQuery, PostgreSQL dbt, Kafka, Airflow, Python, Kotlin and more!
What you bring
You’ll thrive in this role if you have:
-
Strong backend engineering experience building and owning reporting and analytics API services and serving-layer infrastructure.
-
A mindset focusing on reliability, latency, and SLOs.
-
Experience owning API boundary layers including clean endpoint design, versioning, contract stability, and ensuring downstream consumers are never exposed to raw data sources.
-
Strong expertise designing performant read-heavy systems, including relational database optimisation, indexing strategies, materialised views, caching, and API performance tuning.
-
Solid database fundamentals (SQL and non-SQL) and strong SQL querying skills, as well as deep expertise in Kafka.
-
Deep experience with a JVM-based language (Pleo's product backend is Kotlin-based).
-
AWS or GCP with Kubernetes experience. You must be familiar with configuring, deploying and operating containerised applications in a k8s environment.
-
Experience working at the boundary between data systems and product backend services, with a real understanding of the operational differences between the two.
-
The ability to move quickly and independently. This is a hands-on delivery role with clear scope, not an architecture or advisory engagement.
-
Experience in fintech, payments, or other regulated product environments.
Why is this role a good fit for you
This role is a good fit for you if:
-
You are passionate about building systems that serve other engineers.
-
You understand what it means to design, build and maintain services with high performance, availability and reliability requirements.
-
You have a very deep understanding of the data world and know how to bridge the gap between data and engineering.
This role is not a good fit for you if:
-
You need to operate within very large and structured teams with clear hierarchy. This role sits within a small and specialist team with a lot of autonomy.
-
You do not wish to be responsible for services with high availability requirements. You will be held accountable for the quality and availability of those services alongside your team.
-
You prefer to be handed over clearly defined scope of work. You will be expected to define and design the solutions as much as building them.
How you’ll develop in this role
In your first 6 months at Pleo, you will:
-
Get deep into the current state: the upstream Kotlin services the serving layer will pull from, the internal consumers already waiting on the API (Data & AI Products, GenAI Platform), and any prototype serving logic that needs to be replaced or formalised.
-
Ship the first production version of the Reporting API (a defined set of endpoints with agreed contracts, versioning, and SLOs) with at least one internal consumer live against it.
-
Establish the access control, tenant isolation, and row/column-level security model for the API. You will have proven out low-latency query performance on Postgres, with clear metrics around reliability and SLOs, and established a clear architectural benchmark to understand when (or if) an OLAP layer would ever be necessary.
Please note: We can hire on a remote, hybrid or in-person set-up in any of the locations listed on the advert but you will need to be physically based in the country of your choice with a valid right to work. We are unable to offer visa sponsorship for this role in any of the listed locations.
Show me the benefits
-
Your own Pleo card (no more out-of-pocket spending!)
-
Lunch is on us for your work days - enjoy catered meals or receive a lunch allowance based on your local office
-
Comprehensive private healthcare - depending on your location, coverage options include Vitality, Alan or Médis.
-
25 days of annual leave + public holidays (additional days may apply in select countries based on local standards).
-
For our Team, we offer both hybrid and fully remote working options.
-
We use MyndUp to give our employees access to free mental health and well-being support with great success so far
-
Paid parental leave - we want to make sure that we're supportive of families and help you feel that you don't have to compromise your family due to work
The interview process
We want to ensure you are set-up for success and understand what will be expected of you. If your application is successful, our interview process is as follows:
-
Intro call: A 30-minute chat with our Talent Partner to discuss the role and your background.
-
Core skills test: An async AI-assisted programming test to assess your coding fundamentals.
-
Hiring Manager interview: A 60-minute chat deep diving into your experience.
-
Pleo Challenge: A 75-minute system design interview focusing on your architecture, infrastructure and problem-solving skills.
Transparency is important to us so we also wanted to share some insights about what we’re looking for in applications to ensure you can set yourself up for success!
With this in mind, we want to help you understand what we really care about when reviewing your application:
-
We receive a lot of CVs, and many of them are AI-generated. We love seeing people leverage AI - it’s a big focus for us internally too- but without human intervention, these CVs can sometimes become generic and fail to show a candidate in the best light. What we're really looking for is the specific details of real impact that only you - not AI - know from your previous experience. A top tip from us is to use the “Achieved X, as measured by Y, by doing Z” formula (credit: Laszlo Bock, ~2014) to give a really clear picture of what you’ve worked on. A final note: including links to your previous companies' websites is a huge help and allows us to truly understand your background.
-
Every single application we receive is reviewed by a human (yes, hundreds of them) because we believe that candidates' efforts should be matched by an equal level of human care. This means that we expect a similar level of attention put into your application. Read and answer the application questions carefully, they make a huge difference in our decision-making process.
-
This role focuses heavily on building services for internal / external users consumption. It is absolutely critical to have extensive API design and development experience, expertise in OLAP systems and to be able to work in Kotlin. Ensure your CV reflects clearly of the actual experience you have across those areas.
About your application
-
English first. Since it's our company language, please submit your application in English. You’ll be using it a lot if you join us.
-
A fair look for everyone. Our talent team reads every single application to ensure the process is fair. To keep things running smoothly, we only accept applications through our system—our support team can’t pass on calls or emails.
-
Diversity drives us. We can only reach our goals if our team reflects the world around us. That starts with you hitting apply, even if you don't tick every single box. We encourage people from all backgrounds and experiences to join us.
-
Interview at your best. We want you to feel comfortable throughout the process. If you have any accessibility requirements or need a specific format, email belonging@pleo.io. We’ll design a process that works for you.
-
Your data is safe. When you apply, we process your personal data as a data processor. For more information on how Pleo processes personal data, read our Privacy Policy here.
-
Applying for multiple roles? Nothing is stopping you, and we assess every role independently. However, we do look for alignment, so make sure you can explain why your interest and experience are right for each specific role.
-
Reapplying. If you’re applying for the same role again, please wait six months from your last decision before hitting submit.
Listing provenance
Where did this job come from?
See where this vacancy came from and whether more than one current source can still support it. Source names help with traceability and attribution; they are not endorsements or guarantees.
At least one enabled source recently observed the vacancy. The source chain is traceable, but this is not independent employer verification.
- Continuity
- One recent renewable source
- Source-class independence
- One renewable source class
- Last source observation
- Observed today
This records when High Paid Job last observed the vacancy in source evidence. It confirms source presence, not that the employer edited the vacancy at that time.
- 1 enabled source recently observed this vacancy.
Source confidence is about traceability and continuity. It is separate from application safety and should not be read as an employer reputation rating.
The vacancy is supplied by an external job publisher. Source information helps show where the listing came from; it is not a guarantee about the employer or vacancy.
Listing source: Jobicy. Destination: jobicy.com. The application opens in a new tab so you can keep this report open.
