Account Coordinator - Sports and Predictions

We need to produce HTML fragment with sections: About the role? Actually the posting includes "About Us" then description of role. We need headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use only those headings if content exists. We must not repeat job title. We must not include Job ID etc. Remove boilerplate like EEO, legal, application instructions. Keep substantive info. We need to parse content: - About Us: description of company. Could be "About the role" maybe? Actually "About Us" is about company. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" heading containing description of role and maybe company overview? The "About Us" could be considered "About the role"? But they said "About the role" as example. We could put company description under "About the role" or maybe we could omit if not specific to role. However we need to preserve substantive info; we can include company overview under "About the role" as it's relevant. Responsibilities: list bullet points. Qualifications: list bullet points. Benefits: list bullet points. Pay: not mentioned explicitly; there is "Competitive salary" under Benefits. That's pay info. So we could create a Pay section with "Competitive salary". But they said only create Pay section if posting actually states them. It does state "Competitive salary". So we can include Pay section with that sentence. Schedule: mention "Work Flexibility Adoption. Flexi-work hour and hybrid set-up". Also "Comfortable with a non-traditional schedule; this role may require responsiveness to partners outside of standard business hours, including occasional weekends". So we have schedule info. So we can create Schedule section. Skills: maybe we can extract from qualifications: "Strong written and verbal communicator", "Highly organized and detail-oriented", "Proficient with Slack, Google Workspace, and comfortable leveraging AI tools", "Some knowledge of or interest in sports, predictions, or trading", "Background in sports betting, prediction markets, or financial markets is a plus", "Self-starting and proactive", "Thrives in a fast-paced environment", "Comfortable with a non-traditional schedule", "Technical skills or knowledge is a plus, but not required". Those could go under Skills or Qualifications. The instruction: we have headings for Skills and Qualifications separate. We need to decide what goes where. Usually Qualifications are experience/education; Skills are abilities. We can put experience years under Qualifications, and abilities under Skills. But we can also just put all under Qualifications and omit Skills if thin. However they prefer few substantive sections over many thin ones. So we could combine Qualifications and Skills into one Qualifications section. But we have headings list; we can omit Skills if not enough distinct content. Let's see: we have qualifications bullet list includes experience, communication, organization, proficiency, knowledge, background, self-starting, fast-paced, schedule comfort, technical skills plus. That's a mix. Could be considered Qualifications. We'll put all under Qualifications. Benefits: we have bullet list: Competitive salary (but we moved to Pay), 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 benefits packages vary depending on region requirements, you can learn more from our talent acquisition team. We need to avoid filler like "varies". The sentence "Our benefits packages vary depending on region requirements, you can learn more from our talent acquisition team." is somewhat generic but still substantive? It says varies depending on region; that's not specific detail. Might be considered filler. We could keep the earlier parts and drop that sentence. Pay: "Competitive salary". That's it. Schedule: we have "Flexi-work hour and hybrid set-up" and "Comfortable with a non-traditional schedule; this role may require responsiveness to partners outside of standard business hours, including occasional weekends". Also maybe "Work Flexibility Adoption." We'll combine. Now we need to output HTML fragment with headings

and lists

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which sections to include: - About the role: could include company description and role summary. We'll put prose. - Responsibilities: list. - Qualifications: list. - Benefits: list (maybe separate from Pay and Schedule). But we have Pay and Schedule separate sections. We could have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. We must not create empty sections. Now let's extract content. About the role: combine "About Us" paragraph and role description: "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. We're looking for a self-starting, high-energy Account Coordinator to join our Sports and Predictions business. In this role, you'll support the partnerships team in managing relationships with top-tier operators and market makers. You'll help keep things running smoothly across partner conversations, internal coordination, and the day-to-day operational work that keeps our prediction market products moving forward. This is a wear-many-hats role where no two days look the same." That's good. Responsibilities: list each bullet: - Support the partnerships team as an additional point of contact for operators and market makers - Coordinate meetings and conversations across partners, internal teams, and leadership - Prepare materials, updates, and briefing documents for partner meetings and strategic conversations - Translate technical product updates into clear, partner-facing communications - Engage with market makers on performance, coverage, and operational topics - Track market maker coverage across sports, leagues, and market types, and flag gaps or opportunities - Develop a strong understanding of how the business functions so you can field questions and route them to the right people - Manage multiple open items and follow-ups simultaneously, ensuring nothing falls through the cracks - Collaborate cross-functionally with engineers, designers, analysts, and marketers - Support the sales and onboarding process for new partners and market makers Qualifications: list: - 2-4 years of experience in account management, partnerships, trading ops, or a client-facing role - Strong written and verbal communicator with a polished presentation; comfortable interfacing with executives - Highly organized and detail-oriented, with the ability to juggle many things at once - Proficient with Slack, Google Workspace, and comfortable leveraging AI tools to work more efficiently - Some knowledge of or interest in sports, predictions, or trading - Background in sports betting, prediction markets, or financial markets is a plus - Self-starting and proactive; comfortable working independently and figuring out what to prioritize - Thrives in a fast-paced environment where priorities evolve quickly - Comfortable with a non-traditional schedule; this role may require responsiveness to partners outside of standard business hours, including occasional weekends - Technical skills or knowledge is a plus, but not required Benefits: list: - 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. We could also include "Competitive salary" but we moved to Pay. Pay: list: - Competitive salary Schedule: list maybe: - Flexi-work hour and hybrid set-up - May require responsiveness to partners outside of standard business hours, including occasional weekends But note we already have Flexi-work hour under Benefits; could duplicate. Better to keep schedule separate: mention non-traditional schedule and occasional weekends. The Flexi-work hour and hybrid set-up is more about work arrangement; could be considered Benefits. But we already have it under Benefits. To avoid duplication, maybe keep Flexi-work hour under Benefits and schedule just mention occasional weekends. However schedule section should have substantive content; we can mention "May require responsiveness to partners outside of standard business hours, including occasional weekends". That's enough. Now we need to output HTML. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Qualifications

  ...

  Benefits

  ...

  Pay

  • Competitive salary

  Schedule

  • May require responsiveness to partners outside of standard business hours, including occasional weekends
  Make sure no extra whitespace? It's fine. Check we didn't include boilerplate: removed EEO, legal, application instructions, personal data usage, etc. Check we didn't repeat job title. Check we didn't include "About OG" etc. That's boilerplate about product; could be considered part of About the role? Might be considered extra but it's substantive about the product. However it's after "About OG" heading; but we could incorporate some of that into About the role? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The "About OG" paragraph describes the product offering; it's substantive about the company/product. Should we include? It's not about the role directly but about the company's offering. Could be considered part of About the role or maybe we could add another section like "About the company". But we only have headings list; we could put it under About the role as additional prose. However we already have a long About the role paragraph; we could append that info. But we must not create sections with filler. Adding more prose under About the role is fine. Let's incorporate the "About OG" paragraph: "OG, a Crypto.com company, offers CFTC-compliant technology to offer access to a federally regulated derivatives platform to trade, engage with others, climb the leaderboard, and where it pays to be right. OG provides sports fans and consumers with the opportunity to act on uncertainty, capitalize on the future, and celebrate triumph through a most comprehensive offering of sports and cultural event contracts. Make your call now at https://OG.com." Also "About Crypto.com" paragraph: maybe also substantive but could be considered boilerplate? It's about the parent company; could be included. However it's quite generic but still substantive about the company's vision. Might be okay to include. But to keep sections few, we could add to About the role. But we must avoid duplication and keep it concise. The instruction: Prefer a few substantive sections over many thin ones. So we can have About the role containing all company description. Thus About the role will include: - OG.com description (fast-growing, CFTC-regulated Prediction Market platform...) - Role description (self-starting..., wear-many-hats...) - About OG (product offering) - About Crypto.com (vision, etc.) We'll combine into a few paragraphs. Now ensure we don't include "Personal data provided by applicants will be used for recruitment purposes only." etc. That's boilerplate; remove. Also remove "Please note that only shortlisted candidates will be