OG.com - Senior Product Manager - Fiat Onboarding

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, etc. Must not include placeholder sections like Pay if not specified. The posting includes Benefits (list). It does not include explicit Pay or Schedule. So we should not include Pay or Schedule sections. We need sections: About the role (maybe from Role Overview), Responsibilities (What You'll Actually Do), Requirements (Requirements), Preferred maybe as Skills? The instructions: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Qualifications if there is content (maybe Requirements covers qualifications). Preferred could go under Skills. We need to decide. We have content: About Us (company description) maybe not needed as About the role? The "About Us" is company overview; could be placed under About the role? Usually About the role includes role overview. We'll put About the role: combine Role Overview and maybe company description? But we should not repeat job title. We'll include a short paragraph about the role and company. Responsibilities: from "What You'll Actually Do:" bullet list. Requirements: from "Requirements:" bullet list. Skills: from "Preferred:" bullet list. Benefits: from "Benefits" section. We must not include Pay or Schedule. We must output only HTML fragment, no markdown fences. We need to use

for each section heading. Use

• for lists. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all points from those sections. Let's extract. About Us: 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: We are looking for a Senior Product Manager to own how money and identity get into OG -signup, KYC, fiat funding, payouts, and the payments/banking product behind them. Fans don’t trade until they can fund. Every drop-off in onboarding or fiat costs volume, trust, and share of wallet. Your mandate is to make funded accounts fast, trustworthy, and design-obsessive: the path from signup → KYC/fiat → ready to trade, the rails and payment methods that actually clear, the failure states that kill conversion, and the feedback loops that move the funnel. Trading surfaces (markets, parlays, live) sit with a partner PM. You own the front door. You will run this roadmap with independence. You make the call on friction vs. compliance, which funding methods ship, and what waits when the UX or ops bar isn’t there. You report to the Chief Product Officer, who sets product strategy and priorities across OG. You own the how and the when. If you’ve shipped consumer onboarding, fiat, payments, or banking products before, this will feel familiar. The difference is you’ll be doing it as the on-ramp into regulated U.S. prediction markets -where accessibility and bank-grade compliance collide, and the playbook for “best funded-user experience in the category” is yours to write. What You'll Actually Do: list: - Own onboarding and fiat end-to-end. You are the DRI for signup, verify, deposit, and time-to-funded. You make the friction vs. compliance call. - Ownership isn’t shipping a KYC screen; it’s moving signup → funded → ready for first trade. - Own the payments and banking product. You decide funding methods, payouts, limits, retries, and partner UX (ACH, cards, instant funding, and whatever clears in the U.S.). You treat rails, authorization, and flow of funds as product -not a vendor ticket. - Own the money-in funnel as a growth surface. You instrument drop-off, attack the leaks, and sequence work against conversion -not a feature list. - You partner with the Predictions PM on the handoff from funded → first contract. - Hold the design bar on trust and money UX. You champion clarity, hierarchy, and error states as non-negotiable. You push back on “good enough” when users are putting in a debit card or waiting on an ACH. - Specific feedback: interaction cost, copy, recovery -not vibes. - Wireframe and partner in Figma. You create your own wires and drive design conversations. You catch clunky funding and KYC interactions before users do. - Talk to users like a peer. You run research on how people currently sign up, verify, and move money. You ask “Show me how you fund this account,” not “Would you use instant deposit?” You distinguish what users say from what the funnel reveals. - Drive cross-functional execution. You align engineering, design, data, compliance, payments, banking partners, and ops around funded-user outcomes. You own the backlog and the ship cadence for this charter. Nothing in onboarding/fiat goes live without your sign-off on product and UX bar. Requirements: - Fiat and onboarding ownership. You have owned money-in and/or user onboarding (signup, KYC/identity, deposits, funding) and can walk the funnel you owned, the drop-offs you attacked, and the number that moved. - Payments / banking product, not adjacent fintech. You have owned payment rails, funding methods, or banking/on-ramp product (ACH, cards, PSP, payouts, crypto on/off-ramp, or similar) and can point to a flow of funds, a partner integration, or a failure mode you actually ran. - Résumé logos without rails ownership don’t clear the bar. - Design sensibility as a product skill. You can evaluate money-in and identity UX with specifics (hierarchy, density, recovery, trust), not “it looks nicer.” You can point to a flow you refused to ship until it was clear. - 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 (onboard, fund, withdraw) 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: - Crypto exchange, crypto bank, or regulated on/off-ramp PM work: you’ve already sat in compliance + rails + consumer conversion at once. - Consumer growth / activation: you’ve owned a signup or first-value funnel, not only the bank core. - Hands-on OG / prediction-market / sportsbook use: you know why funding has to feel instant for a live game. - 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: (maybe could be part of About the role or separate but not required headings). Since we only need to include sections with real content, we could incorporate Why This Role into About the role or maybe a separate section like "Why This Role" but not in the list of allowed headings. The allowed headings are limited to those; we could put it under About the role as additional prose. Benefits: - 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 - our internal mobility program offers employees a new scope. - Are you ready to kickstart your future with us? (maybe not benefit) - Benefits 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 - our internal mobility program offers employees a new scope. Are you ready to kickstart your future with us? Benefits 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. Our internal mobility program can offer employees a diverse scope. Our Crypto.com benefits packages vary depending on region requirements, you can learn more from our talent acquisition team. There's duplication. We need to preserve all substantive information but remove duplicated lines. So we need to deduplicate. Let's extract unique benefit points: - 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 - our internal mobility program offers employees a new scope. (or diverse scope) - Our Crypto.com benefits packages vary depending on region requirements, you can learn more from our talent acquisition team. Also "Are you ready to kickstart your future with us?" is more a call to action, maybe not benefit; could be omitted as boilerplate? It's not a benefit; but it's part of the Benefits section. Might be considered filler; but we should preserve substantive info. It's a sentence encouraging application; could be considered boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Are you ready to kickstart your future with us?" is like application instruction? It's a motivational line; maybe treat as application instruction and drop. Safer to drop. Thus 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 - our internal mobility program offers employees a new scope; Our Crypto.com benefits packages vary depending on region requirements, you can learn more from our talent acquisition team. Now we need to output HTML. Structure:

  About the role

  ... (combined About Us + Role Overview + Why This Role maybe)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...
  We must not include empty sections. Now craft prose for About the role: Should include company description and role overview and why this role. Ensure we don't repeat job title. Use paragraphs. Let's write:

  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‑