Lead Product Manager, Banners & Content Cards

We need to output HTML fragment with sections: About the role? Actually the posting includes sections: WHAT YOU'LL DO (responsibilities), WHO YOU ARE (requirements/qualifications), WHAT WE OFFER (benefits), ABOUT BRAZE (company description), maybe Pay (they gave pay range). Also Schedule? Not mentioned. So we include sections with real content: About the role? The intro paragraph before WHAT YOU'LL DO could be considered "About the role". We'll include that as a section with heading

About the role

and paragraph(s). Then Responsibilities (

Responsibilities

) with list from "Main responsibilities:" bullet list. Then Requirements/Qualifications (

Qualifications

) maybe combine WHO YOU ARE and Bonus points? Could separate Requirements and Skills? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose appropriate ones. We'll include About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Ensure we don't create empty sections. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove the AI-powered recruitment process notice? That's likely boilerplate/legal; we should remove it. Also remove the "Notice Regarding Automated" at end. We need to keep pay range and OTE. Also benefits list. We need to keep the "WHAT WE OFFER" content. We need to keep the "ABOUT BRAZE" content (company description). That could be a section maybe "About Braze" but not in list of headings; but we could include as "About the company"? Not in allowed headings list but we could still include? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". Likely they expect those headings only. But we could include About Braze as a paragraph under About the role? Might be okay. However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine About Braze into About the role? Might be mixing. Better to have separate section "About Braze" but not in list; risk of being considered not following instruction. Safer to stick to allowed headings. We can put company description under "About the role" as part of role context? Might be okay. Let's parse content: Intro paragraph before WHAT YOU'LL DO: "At Braze, we have found our people.... If Braze sounds like a place where you can thrive, we can’t wait to meet you." That's about company culture and role. We'll put that as About the role. WHAT YOU'LL DO: includes description of role, then bullet list under "Main responsibilities:" with items. We'll output Responsibilities section with

• each item. WHO YOU ARE: includes requirements: 8+ years PM experience, etc. Also bonus points list. We'll put Qualifications section with required items, and Skills section with bonus points? Or combine. Let's make Qualifications for required, Skills for bonus points. WHAT WE OFFER: benefits list. We'll put Benefits section. Pay: they gave pay range and OTE. We'll put Pay section. Schedule: not mentioned, so omit. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. Ensure we capture all substantive info. Let's extract details. About the role paragraph: combine the intro paragraphs up to "If Braze sounds like a place where you can thrive, we can’t wait to meet you." That's multiple sentences. We'll keep as one

  . Responsibilities: The text after WHAT YOU'LL DO includes a paragraph describing the role, then "Here's what you'd focus on in your first year:" with bullet-like sentences (Drive adoption..., Make creation faster..., Make these surfaces..., Own hard technical product work..., Set the measurement bar.). Then after that, "Main responsibilities:" then bullet list items. We need to preserve all substantive info; we can combine the first-year focus items as part of responsibilities list as well. So we will create a

  with items: - Drive adoption, not just delivery. The work is turning shipped capability into activated customers and sustained usage. That means better defaults, faster time to first banner, self-serve setup, and out-of-the-box integrations with platforms like Shopify - Make creation faster and more intelligent. Banners already supports three ways to build: drag-and-drop, raw HTML, and AI-generated. Braze is investing heavily in Operator, our AI assistant, and a big part of this role is making sure these surfaces are ones Operator can actually work with. Marketers are shifting from building things themselves to letting AI build it for them. A core part of this role is pushing that path forward: making Operator, our AI assistant, a natural and differentiated way to act on a marketer’s intent - Make these surfaces first-class programmable products. You'd drive REST API parity, translations support, enterprise-grade access scoping, and the path to serving in-product content over a public API without an SDK dependency - Own hard technical product work at scale. Render latency at the 99th percentile, the SDK dependencies these surfaces sit on top of, unifying the technical foundation for these channels–in this role, product judgment and technical judgment are the same judgment - Set the measurement bar. You'd define what good looks like for adoption, usage, and performance, and hold the team to baselines and targets that are real - Define and own the roadmap for Content Cards and Banners, pulling from customers, sales, support, usage data, and competitive signal to figure out what matters most next - Partner with engineers and designers to execute that roadmap in a lean, entrepreneurial start-up environment - Own the commercial outcomes for your area (adoption, consumption, expansion) and understand the unit economics well enough to make good investment tradeoffs - Establish and manage internal and external customer expectations, including with enterprise accounts and in renewal and expansion conversations - Deeply understand our technology, business, customers, and market - Build best-in-class infrastructure for your products, treating reliability, performance, and observability as product requirements rather than cleanup work - Partner across the division to build reusable capability instead of channel-specific implementations. Shared editors, shared design patterns, shared APIs We need to ensure we didn't miss any. Now Qualifications (required): from WHO YOU ARE: - 8+ years of Product Management experience, including owning a product line at scale - Strong communication, collaboration, organization, and persuasion skills. This is a senior IC role with no direct reports and a lot of influence. You'll need to align engineering, design, our SDK team, and go-to-market without positional authority - A proactive, positive, can-do attitude. You drive projects to completion excellently, and you're always looking for new ways that processes and products can be improved - Comfortable being technical. You can reason about client-side rendering, SDK integration, API design, and caching well enough to make real tradeoffs with engineers rather than relaying them - You build rich user experiences and work closely with designers. These are content creation products, so the quality of the authoring experience is the product - Data-driven by instinct. You go to the adoption funnel and the usage data before the anecdote, and you're rigorous about baselines - Customer-focused and commercially fluent. You understand how your product area drives consumption and expansion, and you can hold a credible conversation with an enterprise customer about why they should adopt a new channel - Eagerness to learn and grow. We'll put each as
  • . Skills (bonus points): from Bonus points: - Experience with in-product or embedded messaging surfaces. Inbox, feed, banner, or in-app content products - Experience building rich content creation flows. Drag-and-drop editors, template systems, or WYSIWYG authoring - Experience shipping AI features inside an existing authoring tool - Experience with products that depend on customer-side SDK integration, and the adoption dynamics that come with that - Strong technical experience and the ability to understand and discuss product architecture - Experience at a high-growth technology startup - Experience at a high-scale technology startup. We operate at the scale of billions of users We'll put each as
  • . Benefits: from WHAT WE OFFER: - Competitive compensation that may include equity - Retirement and Employee Stock Purchase Plans - Flexible paid time off - Comprehensive benefit plans covering medical, dental, vision, life, and disability - Family services that include fertility benefits and equal paid parental leave - Professional development supported by formal career pathing, learning platforms, and a yearly learning stipend - A curated in-office employee experience, designed to foster community, team connections, and innovation - Opportunities to give back to your community, including an annual company-wide Volunteer Week and donation matching - Employee Resource Groups that provide supportive communities within Braze - Collaborative, transparent, and fun culture recognized as a Great Place to Work® We'll put each as
  • . Pay: from "For candidates based in the United States, the pay range for this position at the start of employment is expected to be between $169,000 and $266,000/year, with an expected On Target Earnings (OTE) between $188,000 and $296,000/year (including bonus or commission). Your exact offer may vary depending on multiple individualized factors, including market location, job-related knowledge, skills, and experience. In addition to cash compensation, this role qualifies for a comprehensive Total Rewards package that includes equity grants of restricted stock (RSUs) so that you will own a piece of our company." We'll put that as

    maybe with two sentences. We should not include the "BRAZE IS AN EQUAL OPPORTUNITY EMPLOYER" etc. Also remove the AI-powered recruitment process notice and the "Notice Regarding Automated". Also remove the "ABOUT BRAZE" section? We might incorporate some of that into About the role? But we already used intro about Braze culture. The ABOUT BRAZE section includes more detail about Braze as a company, product, accolades. That is substantive; we should keep it. Where to place? Could be a separate section "About Braze" but not in allowed headings. However we could put it under About the role as additional paragraph. That would be okay: About the role includes both role description and company overview. The instruction says "Prefer a few substantive sections over many thin ones." So merging is fine. Thus About the role will contain the intro paragraph plus the ABOUT BRAZE description. Let's extract ABOUT BRAZE content: "Braze is the leading customer engagement platform that empowers brands to Be Absolutely Engaging.™ Braze helps brands deliver great customer experiences that drive value both for consumers and for their businesses. Built on a foundation of composable intelligence, BrazeAI™ allows marketers to combine and activate AI agents, models, and features at every touchpoint throughout the Braze Customer Engagement Platform for smarter, faster, and more meaningful customer engagement. From cross-channel messaging and journey orchestration to Al-powered decisioning and optimization, Braze enables companies to turn action into interaction through autonomous, 1:1 personalized experiences. The company has repeatedly been recognized as a Leader in marketing technology by industry analysts, and was voted a G2 “Best of Marketing and Digital Advertising Software Product” in 2025. Braze was also named a 2025 Best Companies To Work For by U.S. News & World Report, a 2025 America’s