Senior Product Manager, Engagement & Promotions
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Key sections:
- About the role / Opportunity: description of role, what they'll build, impact, etc. Could be "About the role" or "Opportunity". Use About the role
maybe.
- Responsibilities: bullet list of duties: set vision, deliver results, own roadmap, ship ML-driven promotions, enable execution, build culture of evidence, stay ahead of ML/AI evolution. Also "What You'll Build & Own" bullet points.
- Requirements / Qualifications: experience: 5+ years PM owning engagement/retention/loyalty in high-volume B2C tech-driven environment; experience working with senior leaders; analytical hunter mindset; AI-driven curiosity; technical curiosity and fluency; Bachelor's degree in technical field a plus; bonus: building recommendation engines or ML driver promotion services; experience in consumer fintech, especially short-term lending.
- Skills: maybe list: product strategy, ML concepts, experimentation frameworks, data analysis, cross-functional leadership, etc. Could be derived.
- Benefits: list of benefits & perks: opportunity to tackle challenges, flexible hours, home office stipend, premium medical/dental/vision, generous paid parental/caregiver leave, 401(k) matching, financial advisor/wellness support, flexible PTO and generous company holidays including Juneteenth and Winter Break, all-company in-person events once or twice a year and virtual events.
- Pay: not mentioned. So we should NOT include Pay section.
- Schedule: not mentioned (maybe flexible hours). There's "Flexible hours and virtual-first work culture". That could be schedule info. But schedule section is for explicit schedule like full-time, remote, etc. Could include schedule? The instruction: include a section ONLY when posting has real, specific content for it. "Flexible hours" is specific content about schedule. Could put under Benefits or maybe a Schedule section. But we already have Benefits section; we could include schedule info under Benefits or as separate Schedule. The instruction: prefer a few substantive sections over many thin ones. So maybe incorporate schedule info into Benefits (flexible hours). But we already have Benefits; we could add a bullet about flexible hours and virtual-first work culture. That seems fine.
- Also mention "virtual-first company, team members can live and work anywhere in the United States, except Hawaii." That's location info, could be under Benefits or maybe a separate section like "Location". Not in list of allowed headings; we could put under Benefits or maybe under About the role. Probably include in Benefits.
- Also mention "Reports to: Director, Product Management – Growth". That's metadata; we could fold into a short
maybe under About the role. - Also mention "Why Join Dave" and "Why You’ll Love Working Here". Those are basically benefits/culture. Could incorporate into Benefits or maybe a separate "Culture" but not allowed headings. So incorporate into Benefits. - Also mention "Dave Operating LLC is proud to be an Equal Employment Opportunity employer..." That's boilerplate EEO; remove. - Also mention "Don’t let imposter syndrome get in the way..." that's motivational; could be part of About the role or maybe a short paragraph. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like "ExtraCash product providing members up to $500 within minutes", "launch several new product offerings in 2026, including a Buy Now Pay Later (BNPL) option", "serving Americans who are financially vulnerable or living paycheck to paycheck". Those are about company; maybe include in About the role or a brief company overview. Could be part of "About the role" section. We must not repeat job title as heading. So no
Senior Product Manager, Engagement & Promotions
. We need to output only HTML fragment, no /, no markdown fences. Let's structure:About the role
...
Maybe include a short paragraph about Dave mission and product. ThenResponsibilities
- ... each bullet
Qualifications
- ... each bullet
Skills
but we could incorporate into Qualifications. However the instruction allows Skills heading if there is real specific content. We have skills like "quantitative rigor, working command of ML concepts, product judgment, experimentation frameworks, AI-driven curiosity, technical curiosity, ability to work cross-functional, simplify complex ideas, use data to align teams". Could be separate Skills section. But we already have Qualifications covering experience and education; Skills could be separate. To avoid many thin sections, maybe combine Qualifications and Skills into one section called "Requirements". But the allowed headings include Requirements. UseRequirements
for experience, education, skills. That seems appropriate. ThenBenefits
- ... each bullet