Product Engineer - Conversion & Retention

About the product

Many professional exams require you to memorize thousands of facts. Bar exam candidates need hundreds of legal rules and exceptions. Nursing students memorize drug interactions and lab values. IT cert takers drill protocols and port numbers. Every exam has its own mountain of facts — and most people just re-read notes and hope for the best.

The hard part isn't learning — it's retaining. Research shows people forget up to 70% of new information within 24 hours. The forgetting curve is brutal, and almost nobody studies in a way that accounts for it.

Cueprep makes retention systematic instead of random. We've seen strong usage and feedback on our first exam, and are expanding fast — getting more people from "just signed up" to "can't imagine studying without this" is the core of this role.

The Role

You'll own the full path from signup to paying customer — and then keeping them. This means you're part product manager (deciding what to build), part engineer (building it yourself), and part analyst (measuring whether it worked).

You won't write PRDs and hand them to a dev team. You'll look at where users drop off, form a hypothesis, ship a fix, and check if the numbers moved. Repeat daily.

What you'll do

• Instrument and analyze the full user journey — signup, onboarding, first session, habit formation, conversion, retention

• Identify the biggest drop-off points and ship fixes directly

• Run lightweight experiments on onboarding flows, paywalls, nudges, and lifecycle emails

• Build retention mechanics — streaks, progress milestones, study reminders, re-engagement triggers

• Own lifecycle comms — transactional emails, push notifications, in-app messages

• Set up and maintain dashboards that show what's actually happening (not vanity metrics)

• Work directly with the project lead to prioritize what moves the needle

What this looks like in practice

• Week 1: You notice 40% of trial users never start a second study session. You add a "pick up where you left off" prompt + a reminder email at hour 18. Second-session rate goes up 12%.

• Week 3: You realize users who hit 50 cards reviewed are 3x more likely to convert. You redesign the first session to get users to that milestone faster and add a progress indicator.

• Week 6: You build a lightweight paywall A/B test — one that triggers after the user's first "aha moment" vs. the current fixed-day trigger. Conversion rate improves.

That's the job. Small, fast, compounding bets on the user journey.

You're a fit if

• You can build full-stack features end-to-end in Next.js and React Native (or similar) — not just mockups or specs

• You think in funnels and retention curves, not feature lists

• You've used tools like Mixpanel, Amplitude, or PostHog to find and fix drop-off points

• You're comfortable writing SQL to answer your own questions

• You move fast — a hypothesis in the morning, a shipped experiment by evening

• You've worked on a product where conversion or retention was the primary metric

You're NOT a fit if

• You see yourself as "just an engineer" or "just a PM" — this role requires both

• You want to build big features from scratch more than you want to optimize existing flows

• You need a detailed spec before you start coding

• You've never looked at a funnel chart and made a product decision from it

• You think retention is someone else's problem

Details

• Remote

• One of the first hires — high ownership, direct access to the founder

• There will be a short assignment as part of the process

Apply with

• A short note on a product you've used where the onboarding or conversion flow was notably good (or bad) — and what you'd change

• A link to something you've shipped (product, feature, side project — anything with real users)

• Bonus: a quick Loom walking through how you'd diagnose a drop-off in our trial-to-paid funnel for bar exam.