Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 40 days ago

Data Scientist

Timeleft4 open roles

Where
Remote - Europe
Work mode
Remote
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowData ScientistTimeleft · Remote - Europe

  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on Timeleft's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

8.0% of postings close within 7 days. Measured by our own scanner across the market. Timeleft postings stay open a median of 2 days.

Share of postings closed within
  1. 1.6%1 day
  2. 3.6%3 days
  3. 8.0%7 days
  4. 15.0%14 days
  5. 34.2%30 days
This job: posted 40 days ago

Timeleft median: 2 days open

The posting

⌘Role Overview

The Data Scientist is the first hire on the team whose job is to put machine learning into production, not just into a notebook. You'll build models that power product and other live flows sometimes surfaced to users in real time, not just reported on in a dashboard a week later.

The first flagship project is about personalization across the user journey: a model that decides, per user, what offer to show, wired directly into the product and lifecycle experience rather than sitting in a warehouse table. From there, you'll extend the same muscle: model → API → product surface to other high-leverage moments in the user journey.

You'll work hand-in-hand with Product, Engineering and Lifecycle marketing to ship models as features, not as reports. This is also a foundational role for the team's infrastructure: most of what Data does today is batch (dbt, Lightdash, BigQuery); you'll help establish our first real-time low-latency serving patterns on GCP and work closely with engineering on this.

⌘Key Responsibilities

1. Production ML Development

  • Build, validate, and ship ML models (propensity, pricing/discount optimization, personalization, churn/LTV) that go live in the product, not just proof-of-concept notebooks.
  • Own the full lifecycle: problem framing, feature engineering, training, evaluation, deployment, monitoring, retraining.
  • Write production-grade code (tested, versioned, reviewed) — you'll be shipping alongside Engineering, held to their bar.

2. Personalization across the journey: from paywall to lifecycle

  • Design and ship the personalized discounting model: who gets what offer, and why, served at the moment of the paywall decision.
  • Partner with product on machine learning experiment design (A/B, holdouts) to prove causal lift of the models, not just correlation.
  • Build the measurement framework so pricing/discount decisions are defensible to finance and leadership.

3. ML Infrastructure & MLOps (GCP)

  • Stand up our first low-latency model serving pattern on GCP (e.g., Vertex AI endpoints, Cloud Run, or equivalent)
  • Define the feature pipeline pattern: what's precomputed in BigQuery/dbt vs. what needs to be fresh/real-time via Pub/Sub or similar.
  • Set up model monitoring: drift, staleness, prediction quality so a live model doesn't silently degrade.

4. Product & Engineering Partnership

  • Sit close to Product and Engineering, not just Data this role is measured by what ships to actual users, not just notebooks
  • Translate a product problem ("how might we reactive lapsed payers") into a modeling problem, and a model output into an API contract Engineering can build against.
  • Document handoffs clearly enough that Engineering can own the serving layer long-term without you as a bottleneck.

5. Experimentation & Causal Inference

  • Design uplift/causal models where "who responds to a discount" matters more than "who churns" .
  • Run and interpret experiments that isolate the model's actual incremental impact on revenue/retention.
  • Design the experimentation program for improving data science and machine learning models with the same rigour we use across our already ongoing experimentation programs

⌘Expected Outcomes

  • Personalized discounting model live in production, serving real paywall decisions to real users: shipped end-to-end, not a prototype sitting in staging.
  • A documented, reusable low-latency serving pattern established on GCP (Vertex AI endpoints or Cloud Run) — the next model doesn't require rebuilding this from scratch.
  • Proven incremental lift on a core business metric (paywall conversion, discount margin efficiency, or lapsed-payer reactivation — pick the one you want as the flagship KPI), demonstrated through a controlled experiment, not just before/after comparison.
  • Model monitoring in place — drift and staleness alerts mean the team knows within days, not months, if a live model silently degrades.
  • A repeatable model-to-production playbook that others in the team can follow

⌘Skills & Competencies

Must have (hard skills)

  • Strong Python for data science and ML (scikit-learn, XGBoost/LightGBM; PyTorch or TensorFlow a plus if deep learning is relevant to future use cases).
  • Proven track record shipping models to production, not just modeling in a notebook. Can talk through at least one model that served live traffic.
  • Hands-on experience with a cloud ML platform, ideally GCP (Vertex AI, BigQuery ML, Cloud Run/Functions) or fast ability to translate equivalent AWS/Azure experience.
  • Solid SQL; comfortable working against a dbt/BigQuery warehouse.
  • Software engineering fundamentals: git, code review, testing, CI/CD: You'll be shipping code Engineering has to trust.
  • Causal inference / uplift modelling or applied experimentation experience: pricing and discounting need "what if we hadn't," not just "who churns."

Nice to have

  • Experience with streaming/event pipelines (Pub/Sub, Dataflow, Kafka): useful as we move off pure batch.
  • Experience with pricing, discounting, personalization specifically.
  • Familiarity with feature stores or the DIY equivalent (versioned feature pipelines).
  • Multi-armed bandits or reinforcement learning for pricing/personalization.
  • Startup experience: comfortable being the first person to build something rather than joining an existing ML platform team.

Soft skills

  • Genuinely energised by "does this move the metric," not just "is this model accurate."
  • Can hold their own in a room with Engineering and with Business: Speaks commercial as well as the language of engineering
  • Explains modeling tradeoffs in plain business terms to Product/leadership without dumbing it down or using too much jargon
  • Comfortable owning ambiguity — this role is defining the pattern, not following one.

⌘Required experience

  • 4–7 years in a data scientist / ML engineer role, with at least one model you personally took from prototype to live production serving real users or real traffic.
  • Quantitative background (CS, stats, engineering or equivalent hands-on experience).
  • B2C, subscription, or marketplace experience is a strong plus
  • Fluent English.

⌘Recruitment process

Introduction Call - 30min with Talent Acquisition Manager

Business Interview - 30min with VP Data

Case Study - Async assessment

Panel Interview - Case study Q&A

Final interview - Interview with Product Manager

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against Timeleft's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.

  3. We apply on Timeleft's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.

  4. Every reply, sorted

    Timeleft's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.

  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.