Product Manager

Full-Time | Remote

Prepd is a marketplace where influencer-crafted recipes become real food brands. We bridge the gap between a creator's following and a customer's doorstep.

We've proven product-market fit. We have paying customers on both on-demand and subscription (Prepd Subscription) models. The product is live, operations are running, and the data infrastructure is in place. What we need now is someone to own the product day-to-day and take it from validated to category-defining.

You'll own the Prepd product. Not a slice of it, not a backlog someone else fills. You decide what gets built, on what evidence, in what order, and you're accountable for whether it moved the number you said it would.

You'll report directly to the Managing Director, Product and Technology, and you'll lead the engineering team's day-to-day delivery. There is no product layer between you and the decision, and none between you and the team building it. That's the whole point of the role.

This is not a delivery coordination job. Running the board is the smallest part of it. You'll be in customer conversations weekly, in the data daily, in the kitchen and the support queue regularly, and you'll be expected to arrive at opinions and defend them. Short decision cycles, high exposure, real ownership. The trade is that you bring judgment and finish what you start, not wait to be assigned tasks.

• Run structured research weekly: interviews, surveys, session reviews, support ticket and app store review analysis
• Build the sharpest view in the company of the Saudi food delivery customer: ordering patterns, preferences, pain points, willingness to pay
• Translate influencer partner needs into product: brand pages, content integration, performance visibility
• Maintain journey maps, ICPs and jobs-to-be-done as living documents, and keep a current read on the competitor landscape

• Own an outcomes-first roadmap across the mobile app, subscription and operations surfaces
• Define north star metrics, OKRs and success criteria for every initiative before it starts
• Prioritize on evidence: analytics, CDP behavior, dashboards, direct customer input. Not on who asked loudest
• Identify and validate new opportunities: menu personalization, loyalty, subscription tiers, referral, B2B catering

• Lead the engineering team's delivery: sprint planning, backlog, scope, sequence and release readiness
• Write PRDs with acceptance criteria, edge cases and success metrics, and hold scope once development starts
• Own the release gate: acceptance testing, QA sign off, store submission, post-release monitoring
• Ship iteratively, weekly releases, not quarterly launches. Track defects to closure and close the loop with whoever reported them

• Build and maintain your own dashboards in Metabase. Pull your own data, don't queue for an analyst
• Define and verify analytics events before a feature ships, not after
• Run funnel, cohort and retention analysis, and report every release against its stated metric, including the ones that didn't work
• Design and read experiments: A/B tests, holdouts, sample sizing, honest readouts

• Own activation, engagement, and retention end-to-end
• Optimize the subscription funnel: onboarding, trial to paid conversion, churn reduction
• Own the ordering and checkout funnel, the wallet, referral and loyalty mechanics
• Shape push notifications, in-app messaging, and lifecycle campaigns with the growth team

• Learn cloud kitchen operations properly: menu cycles, kitchen utilization, delivery logistics, quality control
• Pressure test every product decision against operational constraints before committing it
• Build product solutions for operational problems: demand forecasting, order batching, kitchen load balancing
• Work with operations on menu availability, pre-order windows and supply-demand planning

• Roadmap sequence and release scope
• PRDs, acceptance criteria, defect priority
• Go or no-go on release quality
• Metric definitions, events and dashboards

• Quarterly strategy and major trade-offs
• Pricing and subscription structure
• New product lines and new surfaces
• Team capacity and hiring needs

• Commercial terms with chefs, partners or suppliers
• Budget, vendor and resourcing decisions
• Legal, regulatory and data protection questions
• Anything affecting another company in the portfolio

• 2 to 4 years as a Product Manager shipping consumer-facing mobile apps
• Track record of moving metrics through product changes, not just shipping features. Bring the numbers
• Strong analytical skills: SQL or equivalent, Metabase or a comparable BI tool, cohort analysis, funnel optimization. You can answer your own questions with data
• Experience leading delivery with engineering teams, including scoping, sequencing and holding a quality bar
• Excellent PRD writing and stakeholder communication
• Fluent Arabic and English, written and verbal. The product is Arabic-first and the operations team works in Arabic

• Marketplace, FoodTech, quick commerce, delivery or subscription product experience
• Hands-on with a customer data platform, mobile attribution, and product analytics tooling
• Experience working with distributed or agency engineering teams
• Experiment design background: you've run tests that were properly powered and honestly read
• A technical, design, or operations background you converted into product

• Data-obsessed. You check dashboards before checking email. You trust metrics, not opinions. You can pull your own data.
• User-obsessed. You talk to users regularly. You read the reviews nobody else reads. You can articulate their problems better than they can.
• Outcome-driven. You measure success by retention curves, conversion rates and revenue impact, not by features shipped or story points completed.
• Finisher. You close loops. Half-shipped features, unverified fixes, and undocumented decisions bother you.
• Bias for action. You ship MVPs to learn, not decks to align. You'd rather launch and iterate than plan and perfect.
• Ownership mentality. You own the outcome end to end. If something falls between the cracks, you pick it up.
• Operational empathy. You understand that product decisions have real-world consequences in kitchens, delivery routes and customer meals.
• Coachable, not passive. You take direction well and argue back when you disagree. Both matter.

• Month 1. Full working knowledge of every product surface, integration, and open defect. Time spent with customers, in the support queue, and with operations. First prioritized list of what's broken, with evidence.
• Month 2. Owning delivery. Roadmap drafted and agreed, PRDs written, releases shipping on cadence, defects tracked to closure.
• Month 3. Running your own research and experiment cycle, reporting release outcomes against stated metrics, and bringing evidence-backed proposals that change what we build next.

• Application review: CV plus a short written note on a consumer product you improved and how you measured it
• Screening conversation with the hiring manager
• Practical exercise: audit the live Prepd app and come back with a prioritized list of what you'd fix and why. Time boxed
• Final conversation with studio leadership, then offer.