Business Development Representative

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - About Us paragraph (company description). Should we include? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must include About Us. It says "include a section ONLY when the posting has real, specific content for it". The posting includes "About Us" but not listed as a standard heading. The allowed headings list includes "About the role". Not "About Us". So we probably should not include About Us as a heading; maybe we can incorporate that info into About the role? But we must not invent sections. The instruction says use those headings for sections. It doesn't forbid other headings, but says use

for section headings (e.g. About the role, Responsibilities...). Likely they expect only those headings. So we should map content to those headings. We have: About The Role: paragraph describing role. What You'll Be Doing: list of duties (responsibilities). Could be under Responsibilities. What (we Think) You'll Need To Do It: list of requirements/qualifications/skills. OTE Range: pay. Benefits: mention equity and premium health and wellness benefits. Schedule: mention commuting to NYC or SF office 3-4x a week (implies schedule/hybrid). Could be under Schedule. We need to avoid filler like "commensurate with experience". Not present. We need to ensure we don't include boilerplate like "#prowork". Remove. We need to preserve all substantive info. Let's extract: About Us: maybe we can ignore as not a standard heading. But maybe we could put under About the role? However About the role heading is for role description, not company. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding other headings like About Us, but they gave examples. Safer to stick to given headings. Thus we will have sections: - About the role (maybe combine About Us and About The Role? But About The Role is explicit. We'll put that content under About the role. - Responsibilities: from "What You'll Be Doing". - Requirements: maybe from "What (we Think) You'll Need To Do It" includes communication, perspective, high bar, feedback, pride, organized, commuting, unique, inclusive. Also maybe "You are an excellent communicator..." etc. That's more like skills/qualities. Could split into Requirements and Skills. - Qualifications: maybe not explicit; we could omit if no specific qualifications like years of experience, degree. Not present. So we skip Qualifications. - Skills: maybe list of tech stack: Outreach.io, Clay, LinkedIn Sales Navigator, Nooks, Apollo.io, 6Sense, Attention, Salesforce, Hubspot. Also maybe "technology savvy". Could be under Skills. - Benefits: equity and premium health and wellness benefits. - Pay: OTE Range: $70,000 - $95,000. - Schedule: commuting to NYC or SF office 3-4x a week. We must not include filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive info; do not invent or summarize away detail. Thus we need to capture each bullet point as list items. Let's extract responsibilities list from "What You'll Be Doing". The text is a run-on sentence with periods separating items. We need to split into distinct duties. Original: "Learning what makes our customers tick, infusing yourself into their day to day lives to understand their challenges. Connecting the dots between the most painful parts of an operators job (the manual, data heavy, dynamic processes that have the business on their backs) and how Parabola can help. You will drive revenue growth by empowering our Sales team with top-quality leads through strategic outbound outreach across various channels and warm inbound inquiries. You are not just in it for yourself. When you find approaches that work or signals that made the difference in a prospects engagement, you are eager to codify them and share them with the team. You are a part of the building of this program and company. You’ll be setting up meetings for Account Executives post-lead qualification, and nurturing leads post-meeting to boost attendance rates. You love the phone. You’re making 50+ dials per day, not to dial but to connect and add value to the market. You are using LinkedIn, Loom, email, phone, other social media to diversify and personalize outreach to our ideal potential customers. You master our product, buyer persona, Ideal Customer Profile (ICP), customer journey and know that leaning in here will allow you to add value and excel in your current role but also give you a foundation to grow within Parabola (and your overall career). You are doing what works and constantly thinking about new and creative experiments to test messaging, industries, and use cases. You leverage a modern tech stack including Outreach.io, Clay, LinkedIn Sales Navigator, Nooks, Apollo.io, 6Sense, Attention, Salesforce, and Hubspot." We need to treat each sentence as a duty. Some sentences contain multiple ideas but we can keep as is. We'll create

  • for each. Now requirements/qualities from "What (we Think) You'll Need To Do It": "You are an excellent communicator over both email and phone. As a result, you’re able to catch the attention and interest of really busy people. You have perspective. You don’t take rejection too personally because you know life is short. You have a high bar for what ‘good’ looks like and are constantly striving to exceed metrics and generate high-quality leads. You are excited to receive feedback and actively seek coaching opportunities to enhance performance and professional growth. You take pride in your craft. You are organized and thoughtful and don’t make the same mistakes three times. You're comfortable commuting to the NYC or SF office 3-4x a week. You are you. You are unique. You bring something great and uniquely awesome to the team. You are proud of who you are and you care about fostering an environment that is inclusive and empathetic." We could split into Requirements (maybe communication, perspective, high bar, feedback, pride, organized, commuting) and Skills (maybe tech stack). But commuting also appears in schedule. Might be better to put commuting under Schedule. However the instruction says include a section only when posting has real specific content for it. The posting mentions commuting under that paragraph; we could still include schedule section with that detail. We could also keep commuting under Requirements but then schedule would be empty; we should not create schedule if no content. So we should put commuting under Schedule. Thus we need to decide: schedule content: "You're comfortable commuting to the NYC or SF office 3-4x a week." That's specific. So schedule section will have that. Thus requirements section will exclude commuting. Now skills: tech stack list. Also maybe "technology savvy" but that's vague. We'll list skills as the tech stack. Benefits: "Our OTE is one component of Parabola’s competitive total package, which also includes equity and premium health and wellness benefits." Thus benefits: equity, premium health and wellness benefits. Pay: OTE Range: $70,000 - $95,000. Now About the role: we have the paragraph under "About The Role". Also maybe include the initial "About Us" paragraph? Not sure. The instruction says include a section only when posting has real specific content for it. The posting has "About Us" paragraph. But we don't have a heading for About Us. Could we treat that as part of About the role? It's about company, not role. Might be better to include a separate section "About the company"? Not allowed. Safer to ignore About Us? But that would lose substantive info. However the instruction says "Preserve ALL substantive information". So we must keep About Us info somewhere. We could incorporate it into About the role section as a preamble, but that might be mixing. However the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. It might be okay to add an About Us heading as

    as well, but they didn't list it. The safer approach is to include About Us content under About the role heading, maybe as a first paragraph. That would preserve info. Thus About the role section will contain two paragraphs: the About Us description and the About The Role description. We must not repeat job title. Not an issue. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

    About the role

    About Us paragraph...

    About The Role paragraph...

    Responsibilities

    • ...
    ...

    Requirements

    • ...
    ...

    Skills

    • ...
    ...

    Benefits

    • Equity
    • Premium health and wellness benefits

    Pay

    OTE Range: $70,000 - $95,000

    Schedule

    You're comfortable commuting to the NYC or SF office 3-4x a week.

    We must ensure we didn't miss any substantive info. Check About Us paragraph: "Parabola is a workflow builder that makes it easy to organize and transform messy data from anywhere—even PDFs, emails, and spreadsheets—so that forward-thinking teams can automate the work they thought would always be manual. Teams at fast-moving companies like Brooklinen, On Running, and Flexport use Parabola to save hundreds of hours and finally take on the projects that used to feel out of reach. Whether it’s reconciling inventory across multiple 3PLs, auditing invoices, or manually exporting the same report every Monday, Parabola gives teams the power to automate it—all without needing engineering support. Parabola is backed by OpenView Partners, Matrix Partners, Thrive Capital and more." We need to keep that exactly. About The Role paragraph: "We've built a product our customers love. Operators describe Parabola as giving them dignity, making them feel powerful, and a mission critical tool in their tool-belt. Our customers are excited to talk with us and are equipped to deploy new use cases that drive quantifiable business outcomes for their company. The power and impact on our customers today make us bullish on our ability to grow. We’re on a mission to get Parabola into the hands of as many operators as possible and we need your help. The Business Development Representative will play a pivotal role in bringing in new customers and expanding within our existing user base at Parabola. You’re on the front lines, representing a brand, product, team and customers we care about. As a member of our BDR team, you will help set the standard for a truly excellent, modern BD org at Parabola. The ideal candidate is always asking questions, loves to learn, is technology savvy but still wants to flex their creativity and humanity to connect with people and create opportunities. This person is not afraid of failure, they see it as valuable learning and it fuels them to improve. You consider yourself resourceful, resilient,