You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Company hidden

Data Product Lead

  • Hybrid
  • 6+ years
  • English (C1)

Salary

Not stated

Similar roles pay €80K - 125K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The role owns the data products behind every credit and payments decision across BNPL and Acquiring & Payments.

The company is building its own fintech platform from scratch, at large international scale, and the engineers will shape its architecture and core components.

The team is lean and AI-native, based in Poland, and you would set architectural standards from the start on a greenfield build where design choices last for years.

You work with the feature store, decisioning and underwriting datasets, a Databricks lakehouse, self-serve analytics products, LLM and agentic tooling, data from alternative-data providers, and data from payment-scheme and acquirer partners.

Responsibilities

  • Set and prioritise the roadmap for feature stores, decisioning and underwriting datasets, and self-serve analytics products, sequencing work by commercial and risk impact.
  • Turn credit, underwriting, fraud and commercial needs into prioritised data-product specs with clear acceptance criteria that Data Engineering and ML teams can build against.
  • Work with the Head of Data Engineering & Analytics and the Head of ML & MLOps Engineering to match the roadmap to platform capacity, feature-store architecture and delivery order.
  • Make AI-first and agentic delivery the team's default, and design data products where agents are components of the decisioning surface, with guardrails, evals and human-in-the-loop.
  • Lead the Data Consultants in working AI-first.
  • Define and track portfolio success metrics, including adoption, self-serve usage and decisioning-data SLAs.
  • Report progress and trade-offs to the Data Products & Management Director and cross-functional stakeholders.
  • Lead up to 3 Data Consultants whose capacity flexes across both domains, and own their capacity planning.

Requirements

  • 5+ years in product management for data products or data platforms, including leading or coordinating technical and analytical teams, directly or through a matrix.
  • 3+ years in fintech, credit, lending or payments, with knowledge of BNPL origination, underwriting and transaction or acquiring flows.
  • Strong data-product strategy and roadmap ownership for feature stores and decisioning datasets, with a solid grasp of point-in-time correctness, freshness, lineage and self-serve enablement.
  • Able to turn business, credit-risk and ML needs into buildable, prioritised specs, and to manage stakeholders and roadmaps across several product lines and delivery teams.
  • Working knowledge of the regulations that govern credit and payments data.
  • 2+ years of AI-first data-product leadership, including agents in the decisioning or data-product surface, with guardrails, evals, human-in-the-loop, and control of agent-loop cost and latency.
  • A leader who makes AI-first ways of working the default, including LLM-assisted analysis and agentic tooling, and expects the team to design with agents.
  • Hands-on: you query data yourself with SQL and use AI tools every day.
  • Frames data-product decisions in terms of ROI and outcomes.
  • Able to translate between Data Engineering, ML, business and risk stakeholders, and to influence Credit & Fraud Risk, Engineering and Commercial teams without direct authority.
  • Able to reprioritise a roadmap across two product lines under real capacity limits.
  • Fluent English (B2+).
  • Bonus points for: feature store or ML-enabled decisioning products; acquiring or merchant payments data, including merchant acquiring and payment-scheme data structures; ML/MLOps fundamentals enough to work credibly with ML & MLOps Engineering; IFRS 9 or credit provisioning data concepts; building self-serve analytics products for commercial or risk teams; Databricks or lakehouse platform familiarity.

Conditions

Hybrid working, ideally 1 day a week in the Warsaw or Kraków office.

B2B contract.

Where you’d work

Hybrid, 1 to 2 days a week in the office

About the company

Company hidden

Office in Krakow, Poland

Your chances

Likely still hiring, not crowded yet, and you'd be among the first.

  • 15 checks run
  • 5 good signs
  • 1 red flag

Still hiring?

10 checks

Likely active

In its favour2

  • Still on the company's own careers site, checked 1 h agoModerate evidence
  • Found in the last 48 hours, before the big job boardsModerate evidence

Against it1

  • Listed again after an earlier listing of the same role closedModerate evidence

How crowded?

5 checks

Low

In its favour3

  • In its Early Window: not on the big job boards yetStrong evidence
  • Hybrid in Krakow: only people nearby can take itSlight evidence
  • Lead level: far fewer people qualifySlight evidence

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details13 facts · Role, Location, Compensation, Employment, Requirements
Tech stack
  • SQL
  • Databricks
  • LLMs
Seniority
Lead
Type
Contract
Specialty
Product Manager
Region
Europe
Pay period
Annual
Show 7 more factsShow less

Role

Category
Product & Project
Specialty
Product Manager
Seniority
Lead
Experience
5+ years
Tech stack
  • SQL
  • Databricks
  • LLMs

Location

Work model
Hybrid
Region
Europe
Office
  • Krakow, Poland
Days in the office
1 to 2 days

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Contract

Requirements

Languages
  • English (C1)

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason