Business Development Representative

We need to output HTML fragment with sections: About the role? Actually the posting includes description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to extract content. Let's parse. The posting: At Breeze, we're building... (intro). Then "We are hiring a Business Development Representative!" Then description of role. We need sections: - About the role: maybe a brief overview paragraph. Could be the first paragraph after hiring line: "As our Business Development Representative, reporting to our Head of Sales, you'll own the top of the funnel..." That's about role. So we can put that in

About the role

with

content. - Responsibilities: list of duties: "What You'll Do" bullet list. So we can create

Responsibilities

with

• items. - Requirements: maybe "What We're Looking For" bullet list. That's requirements. So

  Requirements

  with list. - Qualifications: maybe "Nice to Have" could be qualifications? But we could treat "Nice to Have" as Qualifications? Actually Qualifications often includes required and preferred. Could split: Requirements = required; Qualifications = nice to have. We'll follow that. - Skills: maybe not explicit separate; could be part of requirements. But we could create Skills section if there is specific skill list. The posting includes "Hands-on with CRM and sales engagement tooling..." etc. That's skill. Could be part of Requirements. But we need to decide: we should only create sections when there is real specific content. We have content for About the role, Responsibilities, Requirements (what we're looking for), Qualifications (nice to have), Benefits (Benefits & Perks), Pay (Compensation Philosophy maybe includes compensation but not specific numbers; we should not create Pay unless posting states specific pay. It says "Compensation Philosophy" but no numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have specific benefits listed, so we can include Benefits. Pay: we have no specific salary, just philosophy; we should not create Pay section. Schedule: we have In-Office Expectations (hybrid, 3 days/week NYC, 5 days/week Singapore). That's schedule info. So we can create Schedule section with that content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive information; do not invent or summarize away detail. Must keep details. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits, and

    for prose. We must not include boilerplate like EEO etc. There's none. We need to output only HTML fragment. Let's extract content precisely. About the role: Could be the paragraph: "As our Business Development Representative, reporting to our Head of Sales, you'll own the top of the funnel: identifying the companies that should be running on Breeze, getting through to the people who actually make the decision, and turning cold accounts into conversations our sales team can close. This is an execution role with real judgment attached. You'll build target lists from scratch, work accounts across email, LinkedIn, phone, and wherever else your buyers pay attention, and write outreach that earns a reply from operators who get pitched by a payments company every week of their lives. It's also a build role. Outbound at Breeze is still early, and the targeting, sequences, and messaging you prove out become the playbook the next set of hires runs. We're looking for someone who thrives in fast-moving environments, wants meaningful ownership, and is excited to build rather than simply maintain." That seems good. Responsibilities: Under "What You'll Do" there are subheadings: Pipeline generation, Research and targeting, Messaging and experimentation, Systems and reporting. Each has bullet points. We need to capture each bullet as list items. Let's extract: Pipeline generation: - Own outbound pipeline for your territory and hit weekly and monthly meeting targets. - Run high-volume, multi-channel outbound across email, LinkedIn, phone, and other channels where your buyers are reachable. - Qualify inbound and outbound interest against our ICP, and hand off meetings with enough context that the account executive can run the first call properly. - Manage multi-touch sequences and persistent follow-up across long buying cycles. Research and targeting: - Build and maintain target account lists: who they are, what they sell, how they take payments today, and why Breeze is a better answer. - Map buying committees and find the person who actually owns the payments decision, not just the person who is easiest to reach. - Use data and account research to prioritize the accounts most likely to convert. Messaging and experimentation: - Write outreach that is specific to the account and worth reading, not templated filler. - Run structured experiments on subject lines, angles, channels, and sequencing, and keep what works. - Feed what you're hearing in the market back to sales and marketing so our messaging keeps getting sharper. Systems and reporting: - Keep CRM and outbound tooling clean and current: activity, accounts, contacts, and opportunity stages. - Track your own funnel metrics and know where your conversion is breaking down before anyone has to ask. - Use AI and automation to remove the repetitive work from research, list building, and personalization. We'll put all these under Responsibilities as a single list? Could group but spec says use

    • for any list of duties/requirements/benefits. So we can just flatten all items into one list. That's fine. Requirements: "What We're Looking For" bullet list. Extract: - 1–3+ years in sales development, business development, or outbound prospecting, with a track record of hitting meeting or pipeline targets. - Demonstrated comfort with high-volume outbound across multiple channels, including phone. - Strong written communication. You can hold a stranger's attention in four sentences and make a specific, credible case. - Genuine persistence and organization. You run dozens of accounts in parallel without letting follow-ups slip. - Hands-on with CRM and sales engagement tooling (Salesforce, HubSpot, Outreach, SalesLoft, Apollo, LinkedIn Sales Navigator, or equivalents). - Enough commercial curiosity to learn how payments actually work and explain it plainly to a prospect. - Comfortable operating in fast-moving environments without an established playbook. - A builder mentality with a strong bias toward action. - Excited to use AI and automation to work smarter and rethink existing processes. - Comfortable getting into the details and doing the work, regardless of seniority. That's required. Qualifications (Nice to Have): - Experience prospecting into fintech, payments, ecommerce, gaming, or other high-volume digital commerce verticals. - Experience at an early-stage or high-growth startup, especially as an early outbound hire. - Ability to pull and analyze your own outbound data rather than waiting on a report. - Experience building a sequence or territory from zero. Benefits: Under "Benefits & Perks": - Health coverage: Breeze covers 100% of employee premiums on our competitive base plan and 75% of dependent premiums. - PTO: 21 days, plus applicable company holidays. - 401(k): Breeze covers all plan administration fees. - Equity: Meaningful ownership in the company you're helping build. - Equipment: A new MacBook Air and whatever else you need to do your best work. - Office & education allowance: An annual budget for your workspace, tools, and professional development. - Wellness: A monthly reimbursement to support your well-being. - Annual global offsite: We bring the global Breeze team together every year. Previous destinations include Bali and Singapore, with Japan coming next. We'll list as
      • . Schedule: Under "In-Office Expectations": - Employees based in our New York City, NY office follow a hybrid work model and are expected to work from the office three days per week. - Employees based in our Singapore office are expected to work on-site five days per week. - In-office expectations may vary slightly depending on role, team, and business needs. - Certain roles that require closer cross-functional collaboration or operational support may have additional requirements, which will be discussed during the interview process. - Our approach is designed to support meaningful in-person collaboration, team building, and real-time decision-making while providing flexibility where applicable. - We believe this structure enables strong execution, close collaboration, and effective teamwork across our global offices. We'll list as
        • . Now ensure we don't include any boilerplate like "Come Build With Us!" etc. That's marketing but could be considered substantive? It's more like closing. Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The closing motivational paragraphs might be considered not boilerplate but could be considered fluff. However they contain substantive info about why join. Might be okay to include but we have no section for that. Could incorporate into About the role? But we already have About the role. Could add a final

          after sections? The instruction: Output ONLY the HTML fragment. It didn't forbid extra paragraphs not under headings. But we should follow pattern: use headings for sections; we can have prose

          outside headings? Probably okay but better to keep within sections. The closing paragraphs could be considered "Why Join Breeze" etc. Could be a section but we don't have a heading for that (maybe "Why Join Breeze"). Not in allowed headings list. So we might omit them to stay within allowed headings. The instruction: Use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to add other headings but better to stick to those. The closing paragraphs are not covered by those headings; we could drop them as they are somewhat promotional but still substantive. However the instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we drop them, we lose substantive info. But maybe they are considered boilerplate? They are motivational but still substantive about company. Hard to decide. I'd include them as a

          after the sections, maybe under a heading like "About the company"? Not allowed. Could incorporate into About the role? Could add a paragraph after About the role that describes company mission etc. The initial intro already covers mission. The closing paragraphs repeat some of that. Might be okay to drop as duplicate. The intro already mentions building AI-powered infrastructure, backed by Sequoia etc. The closing repeats similar. So dropping may be okay as it's duplicate. We'll keep the intro content in About the role. Thus final HTML:

          About the role

          As our Business Development Representative, reporting to our Head of Sales, you'll own the top of the funnel: identifying the companies that should be running on Breeze, getting through to the people who actually make the decision, and turning cold accounts into conversations our sales team can close. This is an execution role with real judgment attached. You'll build target lists from scratch, work accounts across email, LinkedIn, phone, and wherever else your buyers pay attention, and write outreach that earns a reply from operators who get pitched by a payments company every week of their lives. It's also a build role. Outbound at Breeze is still early, and the targeting, sequences, and messaging you prove out become the playbook the next set of hires runs. We're looking for someone who thrives in fast-moving environments, wants meaningful ownership, and is excited to build rather than simply maintain.

          Responsibilities