OG.com - Senior Product Manager - Predictions
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading (not present). Do not put Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Are you ready to kickstart your future with us?" maybe considered call to action; but it's not boilerplate? Might be considered application instruction? It's a motivational line; but we can keep as prose? Probably safe to keep as part of "Life @ Crypto.com" or separate? It's under "Life @ Crypto.com" heading? Actually after "Life @ Crypto.com" there is a paragraph about empowered etc. Then "Work Flexibility Adoption." then "Benefits". Then "About Crypto.com". Then EEO etc. We'll remove EEO etc.
We need to preserve all substantive information. So we need to include content from each section.
Let's parse the posting:
- About Us: paragraph about OG.com.
- Role Overview: paragraph describing role.
- What You'll Actually Do: bullet-like sentences? It's a paragraph with multiple sentences each starting with a bold phrase? Actually it's a list of responsibilities: "Own the consumer trading roadmap....", "Ship the product fans actually use....", "Bridge native prediction (or perps) into regulated event contracts....", "Hold the design bar....", "Wireframe and partner in Figma....", "Talk to users like a peer....", "Drive cross-functional execution....". We'll turn each into
- under a
inside a section with heading What You'll Actually Do
.
- Requirements: list of bullet points? It's a paragraph with multiple sentences each starting with bold? Actually it's a list: "Trading product ownership in one of these worlds....", "Sports fluency or trader-to-fan translation....", "Design sensibility as a product skill....", "Data ownership....", "User empathy in the product....", "We care what you’ve built and owned -not MBA, pedigree, or a certain number of years." We'll turn each into - .
- Preferred: bullet points: "Hands-on prediction-market or sports-trading as a user: accelerates ramp...", "You’ve done more than one of the three worlds...", "Fiat / onboarding familiarity: helpful...", "Deep Figma / design-system fluency...", "AI player and pilot...". We'll turn each into
- .
- Why This Role: paragraph with bullet-like sentences: "Direct volume impact....", "Frontier....", "Access....", "Leverage....", "Upside....", "Team....". We'll turn each into
- .
- Life @ Crypto.com: paragraph(s) about empowered etc. We'll keep as
.
- Work Flexibility Adoption: appears twice? Actually appears under Life @ Crypto.com? There's "Work Flexibility Adoption." then "Flexi-work hour and hybrid set-up Aspire career alternatives through us - our internal mobility program offers employees a new scope." Then later under Benefits there is "Work Flexibility Adoption. Flexi-work hour and hybrid set-up Aspire career alternatives through us. Our internal mobility program can offer employees a diverse scope." It's duplicated. We'll keep only one instance under Work Flexibility Adoption section? The instruction: include a section ONLY when posting has real, specific content for it. There is content about work flexibility. We'll create a section
Work Flexibility Adoption
with Flexi-work hour and hybrid set-up. Aspire career alternatives through us - our internal mobility program offers employees a new scope.
(maybe combine). Avoid duplication.
- Benefits: list: "Competitive salary", "Attractive annual leave entitlement including: birthday, work anniversary", "401(k) plan with employer match", "Eligible for company-sponsored group health, dental, vision, and life/disability insurance", "Work Flexibility Adoption. Flexi-work hour and hybrid set-up Aspire career alternatives through us." (but we already have that). Also "Our Crypto.com benefits packages vary depending on region requirements, you can learn more from our talent acquisition team." We'll keep as list items.
- About Crypto.com: paragraph(s). We'll keep as .
We must not include boilerplate like EEO etc. Also remove duplicated lines.
Now produce HTML fragment: start with
About Us
then ...
. Then Role Overview
...
. Then What You'll Actually Do
- ...
...
. Then Requirements
...
. Then Preferred
...
. Then Why This Role
...
. Then Life @ Crypto.com
...
. Then Work Flexibility Adoption
...
. Then Benefits
...
. Then About Crypto.com
...
.
Make sure no extra markdown.
Let's craft content precisely, preserving all substantive info.
About Us paragraph: "OG.com is a fast-growing, CFTC-regulated Prediction Market platform powered by cutting-edge technology. We’re building an engaging marketplace where users trade on real-world outcomes - from major sports and elections to cultural and financial events. With a sleek mobile-first app and a passionate community, we’re redefining how people interact with news, probabilities, and financial markets. OG.com runs on the rails of North American Derivatives Exchange, Inc. (NADEX), a CFTC-regulated exchange operating since 2004 and was acquired by crypto.com in 2022."
Role Overview paragraph: "We are looking for a Senior Product Manager to own the consumer prediction-market trading experience end-to-end - web and mobile - once someone can fund: discovery, order entry, positions, parlays / live, and the fan UX that makes OG the default place to trade on real-world outcomes. Your mandate is to make OG fast, clear, and design-obsessive for sports and prediction users: the core trading surfaces that keep them coming back, the workflows that feel native to fans (and to retail traders), and the translation of that craft into regulated U.S. event contracts. Fiat, KYC, and payment rails sit with a partner PM. You own what they do after they’re funded. You will run this roadmap with independence. You make the call on UX tradeoffs, what ships when design quality isn’t there yet, and which trading patterns we borrow from sportsbooks, prediction apps, or retail perps -and which we refuse. You report to the Chief Product Officer, who sets product strategy and priorities across OG. You own the how and the when. You can come from one of three product worlds: Native consumer predictions - sports fluency, parlays / live, fan UX - and you can bridge that into regulated event contracts. Prediction / event markets -you’ve already shipped this category. Retail perps / derivatives / advanced trading -you know trader-grade workflows and can make them accessible for fans, not only power users. If you’ve shipped any of those, this will feel familiar. The difference is you’ll be doing it in regulated U.S. prediction markets -where sports energy, consumer accessibility, and compliance collide, and the playbook for “best consumer trading experience in the category” is yours to write."
What You'll Actually Do items:
- Own the consumer trading roadmap. You are the DRI for web and mobile trading on OG -from first funded session through confident, repeat use. You set milestones, sequence work, and resolve cross-team dependencies. Nothing in this charter goes live without your sign-off on product and UX bar.
- Ship the product fans actually use. You prioritize market discovery, order entry, positions, parlays / multi-leg, live, and the workflows that keep sports and prediction users engaged. You kill “nice ideas” that don’t move outcomes.
- Bridge native prediction (or perps) into regulated event contracts. You take patterns fans already know -sportsbooks, prediction apps, or retail advanced trading -and make them work under U.S. event-contract rules. You don’t copy a sportsbook blindly. You decide what translates.
- Hold the design bar. You champion usability and aesthetics as non-negotiable. You live in design reviews and give specific, actionable UX feedback -spacing, interaction patterns, information density, not vibes. Fan UX is a product skill, not a polish pass.
- Wireframe and partner in Figma. You create your own wires and drive design conversations. You catch pixel misalignments and clunky trade flows before users do.
- Talk to users like a peer. You run research, interviews, and community feedback. You ask “Show me how you currently place this parlay / live bet / perp,” not “Would you use this feature?” You distinguish what users say from what their behavior reveals.
- Drive cross-functional execution. You align engineering, design, data, compliance, and ops around trading outcomes. You partner with the Fiat/Onboarding PM on funded → first contract. You own the backlog and the ship cadence for trading.
Requirements items:
- Trading product ownership in one of these worlds. You have owned a surface end-to-end in consumer prediction / sports (parlays, live, fan UX), prediction or event markets, or retail perps / derivatives / advanced trading -including what broke in cross-team delivery and how you still got it out. You can explain how that craft maps to regulated event contracts. We care what you owned, not the logo.
- Sports fluency or trader-to-fan translation. Either you already speak fan (games, legs, live, why UX has to be instant) or you have taken complex trading UX and made it usable for a broader retail audience -and you can show the before/after.
- Design sensibility as a product skill. You can evaluate and improve UI/UX with specifics (hierarchy, density, interaction cost), not “it looks nicer.” You can point to a product users loved because of craft, and what you refused to ship.
- Data ownership. You instrument your own funnel, size the opportunity, and prioritize without waiting for someone to hand you the analysis.
- User empathy in the product. You are willing to use OG regularly (discover markets, trade, manage positions) to feel friction firsthand. You ask behavioral questions before feature questions.
- We care what you’ve built and owned -not MBA, pedigree, or a certain number of years.
Preferred items:
- Hands-on prediction-market or sports-trading as a user: accelerates ramp on parlays, live markets, and what fans expect.
- You’ve done more than one of the three worlds (e.g. sportsbook + prediction, or perps + consumer app): you ramp faster on what to steal and what to leave behind.
- Fiat / onboarding familiarity: helpful so you respect the funded → first-trade handoff. Not required -a partner PM owns rails.
- Deep Figma / design-system fluency: you move faster with design as a peer, not a handoff.
- AI player and pilot: you use AI tools with human-in-the-loop judgment to move faster on research, specs, and iteration.
Why This Role items:
- Direct volume impact. Consumer trading UX is where prediction markets win or lose share of wallet after someone funds. Your craft bar shows up in trades, parlays,
for prose. Do not repeat job title as heading (not present). Do not put Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Are you ready to kickstart your future with us?" maybe considered call to action; but it's not boilerplate? Might be considered application instruction? It's a motivational line; but we can keep as prose? Probably safe to keep as part of "Life @ Crypto.com" or separate? It's under "Life @ Crypto.com" heading? Actually after "Life @ Crypto.com" there is a paragraph about empowered etc. Then "Work Flexibility Adoption." then "Benefits". Then "About Crypto.com". Then EEO etc. We'll remove EEO etc. We need to preserve all substantive information. So we need to include content from each section. Let's parse the posting: - About Us: paragraph about OG.com. - Role Overview: paragraph describing role. - What You'll Actually Do: bullet-like sentences? It's a paragraph with multiple sentences each starting with a bold phrase? Actually it's a list of responsibilities: "Own the consumer trading roadmap....", "Ship the product fans actually use....", "Bridge native prediction (or perps) into regulated event contracts....", "Hold the design bar....", "Wireframe and partner in Figma....", "Talk to users like a peer....", "Drive cross-functional execution....". We'll turn each into
- inside a section with heading
- . - Preferred: bullet points: "Hands-on prediction-market or sports-trading as a user: accelerates ramp...", "You’ve done more than one of the three worlds...", "Fiat / onboarding familiarity: helpful...", "Deep Figma / design-system fluency...", "AI player and pilot...". We'll turn each into
- . - Why This Role: paragraph with bullet-like sentences: "Direct volume impact....", "Frontier....", "Access....", "Leverage....", "Upside....", "Team....". We'll turn each into
- .
- Life @ Crypto.com: paragraph(s) about empowered etc. We'll keep as
. - Work Flexibility Adoption: appears twice? Actually appears under Life @ Crypto.com? There's "Work Flexibility Adoption." then "Flexi-work hour and hybrid set-up Aspire career alternatives through us - our internal mobility program offers employees a new scope." Then later under Benefits there is "Work Flexibility Adoption. Flexi-work hour and hybrid set-up Aspire career alternatives through us. Our internal mobility program can offer employees a diverse scope." It's duplicated. We'll keep only one instance under Work Flexibility Adoption section? The instruction: include a section ONLY when posting has real, specific content for it. There is content about work flexibility. We'll create a section
Work Flexibility Adoption
withFlexi-work hour and hybrid set-up. Aspire career alternatives through us - our internal mobility program offers employees a new scope.
(maybe combine). Avoid duplication. - Benefits: list: "Competitive salary", "Attractive annual leave entitlement including: birthday, work anniversary", "401(k) plan with employer match", "Eligible for company-sponsored group health, dental, vision, and life/disability insurance", "Work Flexibility Adoption. Flexi-work hour and hybrid set-up Aspire career alternatives through us." (but we already have that). Also "Our Crypto.com benefits packages vary depending on region requirements, you can learn more from our talent acquisition team." We'll keep as list items. - About Crypto.com: paragraph(s). We'll keep as. We must not include boilerplate like EEO etc. Also remove duplicated lines. Now produce HTML fragment: start with
About Us
then...
. ThenRole Overview
...
. ThenWhat You'll Actually Do
- ... ...
Requirements
- ...
Preferred
- ...
Why This Role
- ...
Life @ Crypto.com
...
. ThenWork Flexibility Adoption
...
. ThenBenefits
- ...
About Crypto.com
...
. Make sure no extra markdown. Let's craft content precisely, preserving all substantive info. About Us paragraph: "OG.com is a fast-growing, CFTC-regulated Prediction Market platform powered by cutting-edge technology. We’re building an engaging marketplace where users trade on real-world outcomes - from major sports and elections to cultural and financial events. With a sleek mobile-first app and a passionate community, we’re redefining how people interact with news, probabilities, and financial markets. OG.com runs on the rails of North American Derivatives Exchange, Inc. (NADEX), a CFTC-regulated exchange operating since 2004 and was acquired by crypto.com in 2022." Role Overview paragraph: "We are looking for a Senior Product Manager to own the consumer prediction-market trading experience end-to-end - web and mobile - once someone can fund: discovery, order entry, positions, parlays / live, and the fan UX that makes OG the default place to trade on real-world outcomes. Your mandate is to make OG fast, clear, and design-obsessive for sports and prediction users: the core trading surfaces that keep them coming back, the workflows that feel native to fans (and to retail traders), and the translation of that craft into regulated U.S. event contracts. Fiat, KYC, and payment rails sit with a partner PM. You own what they do after they’re funded. You will run this roadmap with independence. You make the call on UX tradeoffs, what ships when design quality isn’t there yet, and which trading patterns we borrow from sportsbooks, prediction apps, or retail perps -and which we refuse. You report to the Chief Product Officer, who sets product strategy and priorities across OG. You own the how and the when. You can come from one of three product worlds: Native consumer predictions - sports fluency, parlays / live, fan UX - and you can bridge that into regulated event contracts. Prediction / event markets -you’ve already shipped this category. Retail perps / derivatives / advanced trading -you know trader-grade workflows and can make them accessible for fans, not only power users. If you’ve shipped any of those, this will feel familiar. The difference is you’ll be doing it in regulated U.S. prediction markets -where sports energy, consumer accessibility, and compliance collide, and the playbook for “best consumer trading experience in the category” is yours to write." What You'll Actually Do items: - Own the consumer trading roadmap. You are the DRI for web and mobile trading on OG -from first funded session through confident, repeat use. You set milestones, sequence work, and resolve cross-team dependencies. Nothing in this charter goes live without your sign-off on product and UX bar. - Ship the product fans actually use. You prioritize market discovery, order entry, positions, parlays / multi-leg, live, and the workflows that keep sports and prediction users engaged. You kill “nice ideas” that don’t move outcomes. - Bridge native prediction (or perps) into regulated event contracts. You take patterns fans already know -sportsbooks, prediction apps, or retail advanced trading -and make them work under U.S. event-contract rules. You don’t copy a sportsbook blindly. You decide what translates. - Hold the design bar. You champion usability and aesthetics as non-negotiable. You live in design reviews and give specific, actionable UX feedback -spacing, interaction patterns, information density, not vibes. Fan UX is a product skill, not a polish pass. - Wireframe and partner in Figma. You create your own wires and drive design conversations. You catch pixel misalignments and clunky trade flows before users do. - Talk to users like a peer. You run research, interviews, and community feedback. You ask “Show me how you currently place this parlay / live bet / perp,” not “Would you use this feature?” You distinguish what users say from what their behavior reveals. - Drive cross-functional execution. You align engineering, design, data, compliance, and ops around trading outcomes. You partner with the Fiat/Onboarding PM on funded → first contract. You own the backlog and the ship cadence for trading. Requirements items: - Trading product ownership in one of these worlds. You have owned a surface end-to-end in consumer prediction / sports (parlays, live, fan UX), prediction or event markets, or retail perps / derivatives / advanced trading -including what broke in cross-team delivery and how you still got it out. You can explain how that craft maps to regulated event contracts. We care what you owned, not the logo. - Sports fluency or trader-to-fan translation. Either you already speak fan (games, legs, live, why UX has to be instant) or you have taken complex trading UX and made it usable for a broader retail audience -and you can show the before/after. - Design sensibility as a product skill. You can evaluate and improve UI/UX with specifics (hierarchy, density, interaction cost), not “it looks nicer.” You can point to a product users loved because of craft, and what you refused to ship. - Data ownership. You instrument your own funnel, size the opportunity, and prioritize without waiting for someone to hand you the analysis. - User empathy in the product. You are willing to use OG regularly (discover markets, trade, manage positions) to feel friction firsthand. You ask behavioral questions before feature questions. - We care what you’ve built and owned -not MBA, pedigree, or a certain number of years. Preferred items: - Hands-on prediction-market or sports-trading as a user: accelerates ramp on parlays, live markets, and what fans expect. - You’ve done more than one of the three worlds (e.g. sportsbook + prediction, or perps + consumer app): you ramp faster on what to steal and what to leave behind. - Fiat / onboarding familiarity: helpful so you respect the funded → first-trade handoff. Not required -a partner PM owns rails. - Deep Figma / design-system fluency: you move faster with design as a peer, not a handoff. - AI player and pilot: you use AI tools with human-in-the-loop judgment to move faster on research, specs, and iteration. Why This Role items: - Direct volume impact. Consumer trading UX is where prediction markets win or lose share of wallet after someone funds. Your craft bar shows up in trades, parlays,