Paid leave
5 weeks (30 working days) paid leave per year is the baseline; RTT days can add more for roles above 35 hours.
Service-Public · Congés payésShort answer. Be careful: company 62/100, personal fit 90/100. Start with: One-pager: role snapshot + 3 must-answers + 3 risks; Verify “5+ years” and prepare a one-line proof; Verify “Master's degree” and prepare a one-line proof.
Verdict & scores
Company62Be careful
Personal fit90Strong
Prep time280minutes
Fit 90 is decent, but the company scores 62. Price the workload and stability first.
Hard gates passed; coverage 69%. Worth a conversation, not a rushed application. Get a few answers first. The sharpest line is “fast-paced” — Understaffed and permanently behind; priorities change weekly.
| Market | France |
|---|---|
| Industry | Finance |
| Company | Lumière Pay SAS |
| Salary | €70,000 – €90,000 |
| Experience | 5+ years |
| Degree | BAC+5 / WO |
| Location | Paris |
| Legal form | SAS |
| Pack | FR v0.1 |
Company check
| Dimension | Score | Why |
|---|---|---|
| Stability | 57/100 |
|
| Growth | 67/100 |
|
| Management maturity | 73/100 |
|
| Workload | 60/100 |
|
| Pay credibility | 63/100 |
|
| Hiring sincerity | 50/100 |
|
Flags
- Fast-paced: Understaffed and permanently behind; priorities change weekly.
- Degree required: A hard filter on paper; "or equivalent experience" is the escape hatch.
- CDI: Permanent contract; the French default for stable roles.
Market facts
Période d'essai
Trial length depends on contract and status (CDI/CDD); notice during the trial is shorter.
Service-Public · Période d’essaiMutuelle
Employers must cover at least 50% of the health insurance (mutuelle) premium.
Service-Public · MutuelleFrench baseline; convention collective and contract can differ. Information only, not legal advice.
Requirements
Evidence anchors are the exact phrases from the pasted JD. Match is a rule-based read of the candidate text, not a recruiter decision.
| ID | Requirement | Type | Weight | Match | Score | Tier |
|---|---|---|---|---|---|---|
| R01 | Own the payments platform end to end, from checkout to settlement | Core | 90 | Strong | 20.7 | P1 |
| R02 | Scale the payment path through peak events | Core | 90 | Strong | 20.7 | P1 |
| R03 | Break the monolith into services and drive DDD adoption | Core | 79 | Weak | 44.0 | P0 |
| R04 | Mentor 2 engineers and lead design reviews | Soft | 38 | Unknown | 11.4 | P2 |
| R05 | Partner with product, risk, and finance | Core | 70 | Unknown | 35.7 | P0 |
| R06 | 5+ years of backend engineering experience | Hard gate | 100 | Strong | 25.7 | P2 |
| R07 | Master’s degree (BAC+5) in Computer Science or equivalent | Hard gate | 100 | Strong | 25.7 | P2 |
| R08 | CDI contract | Logistics | 16 | Unknown | 2.9 | P3 |
| R09 | 5 weeks holiday (30 working days) | Logistics | 16 | Unknown | 2.9 | P3 |
| R10 | Convention collective | Logistics | 16 | Unknown | 2.9 | P3 |
| R11 | 4-month période d’essai | Logistics | 16 | Unknown | 2.9 | P3 |
| R12 | Mutuelle | Logistics | 16 | Unknown | 2.9 | P3 |
| R13 | 13e mois | Logistics | 16 | Unknown | 2.9 | P3 |
| R14 | Hybrid: 2 days a week in the Paris office | Logistics | 16 | Unknown | 2.9 | P3 |
| R15 | Expert in Java or Kotlin | Core | 70 | Strong | 16.1 | P1 |
| R16 | comfortable with JVM memory model and GC tuning | Core | 70 | Weak | 39.0 | P0 |
| R17 | Hands-on with Spring Boot, Kafka, MySQL, and Redis | Core | 70 | Strong | 16.1 | P1 |
| R18 | DDD or domain modeling experience | Plus | 35 | Weak | 6.9 | P2 |
| R19 | Payments or fintech background | Plus | 46 | Partial | 6.8 | P2 |
Jargon decoder
Fast-paced
Workload“fast-paced”
Understaffed and permanently behind; priorities change weekly.
Why it matters: Teams that plan well do not advertise chaos as a benefit.
Ask: What does a normal week look like? How often do priorities change?
Degree required
Gate“Master’s degree”
A hard filter on paper; "or equivalent experience" is the escape hatch.
Why it matters: ATS screens on degree fields before a human sees the resume.
Ask: Is the degree requirement strict, or is equivalent experience accepted?
CDI
Stability“CDI”
Permanent contract; the French default for stable roles.
Why it matters: CDD or freelance changes notice, benefits, and loan/visa evidence.
Ask: Is this a CDI or CDD?
Période d'essai
Stability“période d’essai”
Trial period; length and notice depend on status and contract.
Why it matters: It is the easiest exit for the employer.
Ask: How long is the trial period, and what notice applies?
Convention collective
Pay“convention collective”
Sector agreement may set pay, leave, and benefits beyond the contract.
Why it matters: It can override the offer in your favor, or add constraints.
Ask: Which convention collective applies?
Hybrid
Management“Hybrid”
Office days are mandatory in practice; the "flexible" part is the commute.
Why it matters: Hybrid policies vary wildly; the JD rarely states the real cadence.
Ask: How many days a week in office, and is it enforced?
Nice to have
Gate“Nice to have”
Not required on paper, but the bar moves once there are enough applicants.
Why it matters: Nice-to-haves become tie-breakers, then filters.
Ask: How do you weigh nice-to-haves against core requirements?
RTT
Workload“RTT”
Extra days off for working above 35 hours; rules vary by agreement.
Why it matters: RTT can be 5–12 days and is not the same as holiday.
Ask: How many RTT days, and how are they accrued?
Mutuelle
Pay“mutuelle”
Health insurance; the employer must cover at least half.
Why it matters: Coverage quality varies a lot.
Ask: What does the mutuelle cover, and what is my share?
13e mois
Pay“13e mois”
A 13th month is common but not universal; check pro-rating.
Why it matters: It may be split or conditional.
Ask: Is the 13e mois pro-rated, and when is it paid?
No reporting line
StabilityNo reporting line or team size. It may be a new role, or one they would rather not describe.
Why it matters: A normal req names the manager and the team; the absence is information.
Ask: Who does this role report to? How big is the team?
New or backfill?
StabilityNot stated. Default to inheriting history.
Why it matters: A backfill begs the question of why the last person left; a new role begs for budget proof.
Ask: Is this a new role or a backfill? Why did the last person leave?
Prep list
11 items · 280 minutes · 42% coverage
Brief
P0One-pager: role snapshot + 3 must-answers + 3 risks10 minutes
Output: One page (snapshot / must-answers / risks / to verify)
Done when: Explain in 2 minutes what the role really optimizes for and your two biggest risks
“Break the monolith into services and drive DDD adoption”
gate
P2Verify “5+ years” and prepare a one-line proof10 minutes
Output: A 15-second factual statement (conclusion + one fact)
Done when: Give the conclusion first; expand only if asked
“5+ years of backend engineering experience”
P2Verify “Master's degree” and prepare a one-line proof10 minutes
Output: A 15-second factual statement (conclusion + one fact)
Done when: Give the conclusion first; expand only if asked
“Master’s degree (BAC+5) in Computer Science or equivalent”
deep_dive
P0Draw an honest boundary around “DDD”25 minutes
Output: A 60-second boundary statement + closest adjacent work + a 3-month catch-up plan
Done when: No invented experience; say exactly how far you got and how you would close the gap
“Break the monolith into services and drive DDD adoption”
P0Draw an honest boundary around “JVM”25 minutes
Output: A 60-second boundary statement + closest adjacent work + a 3-month catch-up plan
Done when: No invented experience; say exactly how far you got and how you would close the gap
“comfortable with JVM memory model and GC tuning”
P0Explain the part of “with product, risk, and finance” you actually owned35 minutes
Output: A 5-minute version + one architecture/flow sketch
Done when: Motivation, boundary, and rollback are all clear
“Partner with product, risk, and finance”
P1Explain the part of “the payments platform end to end, from…” you actually owned35 minutes
Output: A 5-minute version + one architecture/flow sketch
Done when: Motivation, boundary, and rollback are all clear
“Own the payments platform end to end, from checkout to settlement”
P1Explain the part of “the payment path through peak events” you actually owned35 minutes
Output: A 5-minute version + one architecture/flow sketch
Done when: Motivation, boundary, and rollback are all clear
“Scale the payment path through peak events”
P1Turn “Java” into a 2-minute case30 minutes
Output: A 2-minute script (context → approach → metric → trade-off) + one number
Done when: Finish in 2 minutes and answer “what if the volume grows 10x?”
“Expert in Java or Kotlin”
project
P1Map two projects onto the top three requirements45 minutes
Output: 30s / 2min versions + three follow-up answers per project
Done when: Survive three layers of follow-up on any project
“Break the monolith into services and drive DDD adoption”
reverse_qa
P1Five questions that price the risk20 minutes
Output: Five questions + the answer you want to hear
Done when: At least three questions make the interviewer pause
One-pager
Snapshot: Lumière Pay SAS · Senior Backend Engineer (Payments) · €70,000 – €90,000 · 5+ years · Paris
Three must-answer questions
- How far did you get with “the monolith into services and drive…”? If you never did it formally, what is the closest thing?
- What is the most complex thing you have done with JVM?
- What scale did you run “with product, risk, and finance” at? Any numbers?
Risks to verify
- Fast-paced: Understaffed and permanently behind; priorities change weekly.
- Degree required: A hard filter on paper; "or equivalent experience" is the escape hatch.
- CDI: Permanent contract; the French default for stable roles.
Questions to ask
- What does a normal week look like? How often do priorities change?
- Is the degree requirement strict, or is equivalent experience accepted?
- Is this a CDI or CDD?
- How long is the trial period, and what notice applies?
- Who does this role report to? How big is the team?
- Is this a new role or a backfill? Why did the last person leave?
Open with: 6 years in E-commerce. Open with the number that best proves E-commerce, not your degree.
Cite this page
Jargon HR. “Example report: Senior Backend Engineer (Payments) (France · Payments backend)”. 2026-11-10. https://miaotuijian.cn/examples/fr-payments.html
This is a fictional sample built to demonstrate the checker. It is not a real vacancy and not legal advice.