Venture Specialist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. The posting includes: - "Our Journey" description (company overview). Not a heading per list; we could put under About the role? Actually "About The Role" heading present. So we can have

About the role

with prose. - Then "What You'll Own" list of duties. That's responsibilities. - Then "Essentials To Succeed" (requirements/qualifications). Also "Nice to Have" (nice-to-have). Also "ShopBacker Traits" (maybe skills or values). Also "What's in it for ShopBackers" (benefits). Also note location: "Note: This role is based in Austin, Texas." That's schedule? Actually location; could be included in a short paragraph under About the role or separate? Not a heading. We need to avoid cookie/navigation/legal/EEO etc. The posting includes EEO statement at end; we must remove that. Also remove AI usage note etc? The instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI usage note is not exactly EEO but maybe considered legal? It's about AI usage in recruitment; could be considered boilerplate. Probably remove that paragraph. Also remove "We are committed to protecting your data..." etc. Also remove "ShopBack is an equal opportunity employer..." etc. Also remove "Join our team and help us make a difference!" maybe considered boilerplate? It's a call to action; maybe keep? It's not substantive; but it's not a list. Safer to remove. We need to preserve all substantive information: company overview, role description, responsibilities, requirements, nice-to-have, traits, benefits. We must not invent or summarize away detail. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide sections: - About the role: includes company overview? Actually "About The Role" heading present. So we can put the paragraph after that heading: "This is a single AI-native seat that owns monetization, CRM, and product marketing, and directs campaigns end-to-end from strategy through results. You'll work very closely with the General Manager and cross-functional counterparts day-to-day, especially in your first 6-12 months, as your strategic judgment and independence develop. You'll be one of the most cross-functional people in the US org: partnering with Business Development on monetization, with Growth on campaign strategy, and with Marketing Ops to bring campaigns to life. Note: This role is based in Austin, Texas." That's prose. - Responsibilities: "What You'll Own" bullet list. We'll make

  Responsibilities

  then
  • each item. List items: Own and support monetization strategy for app, web, and browser extension, in direct partnership with the Business Development team. Manage the CRM journey end-to-end: acquisition, activation, retention, and win-back. Enhance product marketing: sign-up flow optimization, new feature launches, and upgrades to existing features. Own our core marketing systems, including Needle and Braze. Support campaigns end-to-end: set the strategy, brief the work, and stay accountable for results, from idea through measurement and iteration. Translate platform and customer data into GTM strategy, then shape the campaigns that bring that strategy to life. Partner cross-functionally with Growth, Business Development, and Product on launches that require GTM's involvement. - Requirements / Qualifications: "Essentials To Succeed" includes bullet points? It's a paragraph with multiple sentences each describing a requirement. Could treat as list. Let's extract each bullet: Fresh graduate or early-career (0-2 years) in business, economics, marketing, or a related field. Prior experience in marketing ideally in a startup/growth environment. AI-native. You already use AI tools as your default way of working, not as a novelty. You'll be expected to operate at a fluency level the rest of the org is actively building toward. Strong business acumen with genuine marketing curiosity and intuition. You notice why a campaign, funnel, or feature works and want to know how to make the next one work better. Comfortable being closely coached. This is a junior seat working shoulder-to-shoulder with the General Manager; you should want that level of proximity and be ready to grow into more independence over time. High ownership, low ego. Equally comfortable in the strategy conversation and in the details when it's needed. Data-driven decision-maker with strong analytical skills. We could make

    Requirements

    with
    • each. - Nice to Have: "Nice to Have" bullet list: Prior experience with CRM platforms (Braze, Iterable, or similar). Familiarity with e-commerce, fintech, or rewards/cashback business models. Comfort with SQL or a similar data-querying tool. Make

      Nice to Have

      maybe under Skills? But we have Skills section possible. Could treat as Skills. But we have separate Nice to Have. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could map Nice to Have to Skills. Or we could create a Skills section and include those. However we also have ShopBacker Traits which could be considered Skills or values. Might be better to have a Skills section that includes both Nice to Have and Traits? But we need to preserve all substantive information; we can create separate sections: Skills (for Nice to Have) and maybe Values (ShopBacker Traits) but not in allowed headings list. The allowed headings list is examples; we can use others? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should stick to those headings; but we could also add other headings if needed? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we need to map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Skills, Benefits. Possibly Qualifications (similar to Requirements). We'll decide. We have: - About the role: company overview + role description. - Responsibilities: What You'll Own. - Requirements: Essentials To Succeed (mandatory). - Skills: Nice to Have (CRM platforms, e-commerce familiarity, SQL). Also maybe ShopBacker Traits could be considered Skills? But they are more like cultural traits. Could we put them under Skills? Might be okay. - Benefits: What's in it for ShopBackers (career growth opportunities, winning team, competitive compensation, candid culture). Also maybe note about location? Not needed. We should not include Pay or Schedule sections because not specified. We must not include placeholder text like "competitive compensation based on performance" is specific enough; it's okay. We need to ensure we don't include boilerplate like EEO etc. Remove that. Now produce HTML fragment. Structure:

      About the role

      ... (company overview + role description)

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Skills

      • Prior experience with CRM platforms (Braze, Iterable, or similar).
      • Familiarity with e-commerce, fintech, or rewards/cashback business models.
      • Comfort with SQL or a similar data-querying tool.
      Maybe also include ShopBacker Traits under Skills? Could add as separate list items? But they'd be more like values; but we can include them as skills? Might be okay to add them under Skills as additional bullet points. However the instruction: "Prefer a few substantive sections over many thin ones." Adding traits may make Skills section thicker but still okay. Let's include them. ShopBacker Traits list: Agency - We take ownership and act, rather than waiting for permission. When something's blocking progress, we find a way through it and follow through until it's done. Judgement - We aim for high-impact decisions, not just easy wins, and we put the bigger picture ahead of individual interests. That means moving quickly and confidently, while staying thoughtful about when a call really matters. Learning Velocity - We pick up new skills fast and let go of old habits just as quickly when something better comes along. We benchmark ourselves against the best and keep raising our own bar. Tenacity - We stay in it when things get hard, keeping a level head under pressure. We debate openly before deciding, then commit fully — and support each other along the way. We could format each as a bullet with the trait name and description. Thus Skills section will have both nice-to-have and traits. Alternatively we could have a separate section for "ShopBacker Traits" but not in allowed headings; maybe we can still use

      ShopBacker Traits

      but the instruction says use those headings as examples, not exclusive. Safer to stick to allowed headings. So include them under Skills. Now Benefits section:

      Benefits

      • Career growth opportunities to take on greater challenges that help you realise your ambitions.
      • Be part of a winning team on a journey to global scale.
      • Competitive compensation based on performance.
      • Candid, open, and collaborative culture where feedback is valued.
      We might also include note about data protection etc? That's boilerplate; remove. Now ensure we preserve location note: "Note: This role is based in Austin, Texas." We included that in About the role paragraph. Now check for any duplicated lines: we should not repeat. Now produce HTML. Make sure no extra markdown fences. Let's craft the About the role paragraph: combine company overview and role description. Company overview: "Our Journey The ShopBack Group is Asia-Pacific’s leading shopping, rewards, and payments platform, serving over 20 million active members across 13 markets. In 2025, the Group continued its global growth with its expansion into North America. Driven by the vision to make every day more rewarding, ShopBack is dedicated to saving members money and time, and delivering delight every day. The platform also enables merchants and brands to engage with their members in a cost-effective manner. Founded in 2014, ShopBack now powers over US$5.5 billion in annual sales for over 20,000 online and in-store partners, and has rewarded shoppers with more than US$900 million (over S$1 billion) in Cashback to date. Through its innovative offerings, ShopBack continues to create value for both members and merchants. Notably, its payment solution, ShopBack Pay, offers members a convenient and rewarding payment option at checkout." Role description: "About The Role This is a single AI-native seat that owns monetization, CRM, and product marketing, and directs campaigns end-to-end from strategy through results. You'll work very closely with the General Manager and cross-functional counterparts day-to-day, especially in your first 6-12 months, as your strategic judgment and independence develop. You'll be one of the most cross-functional people in the US org: partnering with Business Development on monetization, with Growth on campaign strategy, and with Marketing Ops to bring campaigns to life. Note: This role is based in Austin, Texas." Combine into one paragraph? Could be two paragraphs but we can keep as one

      with both. It