Lead Product Manager, Banners & Content Cards
Braze · Austin, TX · 1 mo ago
HybridMarketing$169k–$266k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "WHAT YOU'LL DO", "Main responsibilities", "WHO YOU ARE", "Bonus points:", "For candidates based in the United States, the pay range...", "WHAT WE OFFER", "ABOUT BRAZE", etc.
We must use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings appropriately. Not repeat job title. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove AI recruitment process etc? That's likely boilerplate/legal. Should remove sections about AI-powered recruitment process, Equal Opportunity Employer, etc. Also remove "Notice Regarding Automated". Also remove "BRAZE IS AN EQUAL OPPORTUNITY EMPLOYER" etc. Also remove "OUR AI-POWERED BRAZE RECRUITMENT PROCESS". Also remove "Notice Regarding Automated". Also remove "BRAZE IS AN EQUAL OPPORTUNITY EMPLOYER". Also remove "At Braze, we strive..." etc.
We need to preserve substantive info: role description, responsibilities, qualifications, bonus points, pay range, benefits, about Braze (company description). Also maybe "WHAT YOU'LL DO" corresponds to Responsibilities. "Main responsibilities" also responsibilities. Could combine. "WHO YOU ARE" corresponds to Qualifications/Requirements/Skills. "Bonus points:" could be Skills or Qualifications. "For candidates based in the United States, the pay range..." => Pay section. "WHAT WE OFFER" => Benefits. "ABOUT BRAZE" => About the role? Actually About the role is about the role, but we have company description; maybe we can put under "About the role" or maybe we can create a section "About Braze"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings appropriately. Not repeat job title. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove AI recruitment process etc? That's likely boilerplate/legal. Should remove sections about AI-powered recruitment process, Equal Opportunity Employer, etc. Also remove "Notice Regarding Automated". Also remove "BRAZE IS AN EQUAL OPPORTUNITY EMPLOYER" etc. Also remove "OUR AI-POWERED BRAZE RECRUITMENT PROCESS". Also remove "Notice Regarding Automated". Also remove "BRAZE IS AN EQUAL OPPORTUNITY EMPLOYER". Also remove "At Braze, we strive..." etc.
We need to preserve substantive info: role description, responsibilities, qualifications, bonus points, pay range, benefits, about Braze (company description). Also maybe "WHAT YOU'LL DO" corresponds to Responsibilities. "Main responsibilities" also responsibilities. Could combine. "WHO YOU ARE" corresponds to Qualifications/Requirements/Skills. "Bonus points:" could be Skills or Qualifications. "For candidates based in the United States, the pay range..." => Pay section. "WHAT WE OFFER" => Benefits. "ABOUT BRAZE" => About the role? Actually About the role is about the role, but we have company description; maybe we can put under "About the role" or maybe we can create a section "About Braze"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings only. So we need to map content to those.
Thus sections:
- About the role: could include brief description of role and team (Lead Product Manager for Banners team, what they own). Use info from first paragraphs and WHAT YOU'LL DO.
- Responsibilities: list of duties (drive adoption, make creation faster, programmable, own technical product work, set measurement bar, define roadmap, partner with engineers, own commercial outcomes, establish expectations, understand tech, build infrastructure, partner across division). Use bullet list.
- Requirements/Qualifications/Skills: Could combine. Perhaps we have Requirements (8+ years PM experience, owning product line at scale), Qualifications (strong communication, collaboration, organization, persuasion skills, proactive attitude, comfortable being technical, build rich user experiences, data-driven, customer-focused, eagerness to learn), Skills (technical reasoning about client-side rendering, SDK integration, API design, caching, etc). Bonus points could be extra skills.
We need to avoid filler like "commensurate with experience". Not present.
Pay: include pay range and OTE, equity grants.
Benefits: list benefits from WHAT WE OFFER.
Schedule: not present, so omit.
We must not include sections with no real content.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
First, About the role: About the role
About the role
...
Responsibilities:Responsibilities
- ... ...
Requirements
- ... but we have many items. Could split into Requirements and Qualifications and Skills. But we can combine into Requirements (experience) and Qualifications (skills). Let's decide: Use Requirements for experience, Qualifications for skills/attributes, Skills for technical abilities? Might be redundant. The instruction says prefer few substantive sections over many thin ones. So maybe just two sections: Responsibilities and Qualifications (including experience, skills, bonus). But they gave examples of headings; we can use multiple if substantive.
We have substantive content for: About the role, Responsibilities, Requirements (8+ years PM experience), Qualifications (communication, collaboration, etc), Skills (technical reasoning, etc), Benefits, Pay.
That's many sections but each substantive. However instruction: "Prefer a few substantive sections over many thin ones." Could combine Requirements and Qualifications into one section "Requirements". But they'd be thin? Let's think.
We could have:
- About the role
- Responsibilities
- Qualifications (includes experience, skills, bonus points)
- Benefits
- Pay
That's 5 sections.
Let's map:
About the role: brief description of role and team.
Qualifications: bullet list combining experience (8+ years PM, owning product line at scale), communication, collaboration, organization, persuasion, proactive attitude, comfortable being technical, data-driven, customer-focused, eagerness to learn, plus bonus points (experience with in-product messaging, content creation flows, AI features, SDK integration, high-growth/high-scale startup). Also maybe "Strong technical experience and ability to understand and discuss product architecture". That's covered.
We need to ensure we don't repeat content.
Let's extract details:
From posting:
WHAT YOU'LL DO (list):
- 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
Main responsibilities (bullet):
- 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
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.
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
Pay:
- 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.
Benefits (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®
About Braze (company description):
- 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 Greatest Companies by Newsweek, and a 2025 Fortune Best Workplace in Technology™ by Great Place To Work®, among other accolades. Braze is