Product Lead, New Ventures

We need to output HTML fragment with sections: About the role (or maybe "About This Role" heading?), Responsibilities, Requirements, maybe Benefits? The posting includes "Our Total Rewards Philosophy" and salary ranges. That's pay info. Also location info. Should we include Pay section? The posting includes base salary range. So we should include Pay section with that info. Benefits: they mention benefits and link but not specifics. The instruction: never create Benefits section unless posting actually states them. It mentions "Our total rewards package goes beyond great earnings potential and provides the means to a healthy lifestyle with the flexibility to meet Toasters’ changing needs. Learn more about our benefits at ..." That's vague but it's stating benefits exist. However we should not create a Benefits section with filler like "not specified". The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The benefits description is vague but still says they have benefits and link. Could we include a Benefits section with a short paragraph summarizing that they offer benefits and link? That is substantive? It's not specific but it's stating they have benefits and a link. Might be okay. However they said "Prefer a few substantive sections over many thin ones." Might be better to omit Benefits if not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but not details. Might be considered stating them. Safer to include Pay section (salary ranges) and maybe Schedule? Not mentioned. Location/hybrid info could be in a short p. Not a heading. We need headings: About the role (maybe "About This Role") as h3. Responsibilities as h3. Requirements as h3. Pay as h3 (since salary range given). Possibly "Special sauce (Nice to Haves)" could be part of Requirements? But we could include a "Nice-to-haves" as part of Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements and maybe Nice-to-haves as part of Requirements or separate? Could treat "Special sauce (Nice to Haves)" as part of Requirements but maybe better to include as a subsection? Not required. We'll include Requirements covering both required and nice-to-haves? Might be okay. We need to preserve all substantive information. So we need to include location info, description about Toast, about the role, responsibilities list, requirements list, nice-to-haves list, AI at Toast, Total Rewards Philosophy (including salary ranges), maybe mention of hybrid work model, etc. But we should not repeat job title. Also we should not include application instructions, EEO, legal boilerplate, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we need to strip out: "Apply today!", "Toast is committed to creating an accessible and inclusive hiring process..." etc. Also remove the sections about AI in hiring process, hybrid working, People Are the Secret Ingredient, etc? Those are not boilerplate but they are about culture. Might be considered substantive? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those sections are not boilerplate; they are about culture and values. Could keep them? But they might be considered fluff. However they are part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep them unless they are boilerplate. The sections about AI in hiring process, hybrid working, People Are the Secret Ingredient are not boilerplate; they are specific to Toast. So we should keep them. However we need to decide where to place them. Could be under a section like "About Toast" or "Culture". But we only have allowed headings list; we could add a heading like "About Toast" but not in list. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. So we need to fit extra info into existing sections or paragraphs without headings. Could add a

under About the role that includes company description. Or we could add a

before sections. Thus structure: maybe start with a

containing location and brief company description. Then

About the role

with paragraph describing role. Then

Responsibilities

with

• ... Then

  Requirements

  with
  • ... including required and nice-to-haves? Could separate required and nice-to-haves within same list? Might be okay. Then

    Pay

    with paragraph containing salary ranges and note about total rewards. Then maybe a

    for hybrid work model etc. But we need to avoid extra headings. Could add a

    after Pay for "Hybrid work model" etc. We must not repeat job title. Not include Job ID. Let's extract content. Location(s): US (remote), Boston (hybrid), or New York (hybrid) - EST preferred Company description: Toast builds technology that helps food and beverage businesses run smoother, serve customers better, and grow with confidence. Our platform brings together the tools teams need to power daily operations—while turning complexity into clear, actionable insights. We're purpose-built for the pace of hospitality, and we're investing in new experiences that make great businesses easier to run at any scale. About This Role (Responsibilities) heading: Actually the text says "About This Role (Responsibilities)" then paragraph. We'll treat heading as About the role. Paragraph: We're looking for a Product Lead to join our New Ventures team and help grow one of Toast's newest products. We've shipped an MVP and have early customers. Now we need to reach product-market fit and then scale. This is a senior individual contributor role. You'll work directly with a small team of engineers and a design engineer. You spend a lot of time with customers: on calls, in person, and watching how they use the product. You're good at taking complex problems and making them simple. You have a strong sense for the next right thing to build, and you keep scope tight so the team ships what matters most. You think in workflows and systems, not just individual features. You collaborate well with engineers, weighing tradeoffs and making calls together. You know when to keep testing and when it's time to invest in scale. You use AI tools every day to prototype, research, analyze data, and check your own thinking. Then bullet list under "In this role, you will:" with items. Let's capture those bullets: - Help shape the product's strategy and roadmap as we move from MVP to product-market fit and scale. - Own outcome briefs (our lightweight version of a PRD) end to end. That means framing the problem, working with the team through shipping, and measuring results. - Run weekly cycle planning. You'll partner with the engineers, the design engineer, and the team lead to decide what we'll build each week and why. - Learn where early customers get value and where they get stuck, and use that to decide what to double down on and what to drop. - Define what success looks like, make sure it's measured, and use the data to change course when needed. - Keep quality high where it counts, and know where good enough is fine. - When the product is ready to scale, invest in what growth needs: onboarding, reliability, self-serve, and integrations. - Work with sales, marketing, support, and operations on positioning, pricing, and launches, and bring what they hear back to the team. - Share clear updates with engineers, leadership, and partners on what we're learning and what's next. Then "Do you have the right ingredients?" heading then Requirements. Requirements paragraph: 5+ years of product management experience, including owning a product or major product area and its results. You've taken an early product from MVP to product-market fit and meaningful growth. You can point to product decisions that came directly from time spent with customers. You've made complex workflows simple for the people using them. You understand how software gets built well enough to weigh tradeoffs with engineers, spot risks, and ask the right questions. You've worked directly with engineering teams without a dedicated engineering manager, and you've owned planning and priorities week to week. You're comfortable with metrics. You set goals up front and let the data change your mind. You use AI tools regularly in your work and can explain specifically how. You write and speak clearly for both technical and non-technical audiences. You're self-directed and low ego, and you keep things moving without perfect clarity. Then "Special sauce (Nice to Haves)" list: - Experience in operationally complex industries. - Founder or early-startup experience, or time on an internal incubation or new ventures team. - You've built with LLMs or shipped AI-powered product experiences. - Experience pricing and packaging a new product. - You're comfortable pulling your own data with SQL or similar tools. - You've coded, or you prototype in code today. Then "AI at Toast" paragraph: At Toast, one of our company values is that we're hungry to build and learn. We believe learning new AI tools empowers us to build for our customers faster, more independently, and with higher quality. We provide these tools across all disciplines, from Engineering and Product to Sales and Support, and are inspired by how our Toasters are already driving real value with them. The people who thrive here are those who embrace changes that let us build more for our customers; it’s a core part of our culture. Then "Our Total Rewards Philosophy" paragraph: We strive to provide competitive compensation and benefits programs that help to attract, retain, and motivate the best and brightest people in our industry. Our total rewards package goes beyond great earnings potential and provides the means to a healthy lifestyle with the flexibility to meet Toasters’ changing needs. Learn more about our benefits at https://careers.toasttab.com/toast-benefits. The base salary range for this role is listed below. The starting salary will be determined based on skills, experience, and geographic location. In addition to base salary, our total rewards components include cash compensation (overtime, bonus/commissions if eligible), equity, and benefits. You can learn more about how we align pay with local labor markets in our Geographic Pay Zone Philosophy. Zone A $190,000—$304,000 USD Zone B $165,000—$264,000 USD Zone C $149,000—$238,000 USD Then "How Toast Uses AI In Its Hiring Process" paragraph: Throughout the hiring process, our goal is to get to know you. We use AI tools to support our recruiters and interviewers with tasks like note-taking, summarization, and documentation of interviews to ensure they can be fully focused on your conversation. All hiring decisions are made by people. We ask that you complete interviews and assessments on your own, without real-time AI tools, recording, or transcription bots, unless we tell you otherwise in advance. To learn more: https://careers.toasttab.com/ai-in-hiring Then "Our Approach to Hybrid Working" paragraph: We embrace a hybrid work model that fosters in-person collaboration while valuing individual needs. Our goal is to build a strong culture of connection as we work together to empower the hospitality community, regardless of location. Please visit the Locations page on our career site to learn more about our in-office expectations by region: https://careers.toasttab.com/locations-toast Then "People Are the Secret Ing