Senior Director, Sales & Business Development

We need to output HTML fragment with sections: About the role? Actually we have Company Overview, Why Work at Brother?, Role Overview, Duties & Responsibilities (with sub-sections), Experience & Qualifications, Additional Details For This Role (including remote, travel, base salary, additional compensation), Our Mission, Vision & Culture, About Where We Work. Also we need to follow rules: use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - Company Overview (substantive) - Why Work at Brother? (substantive) - Role Overview (substantive) - Duties & Responsibilities (multiple sub-sections: Sales Strategy & Revenue Growth, Channel Partner Development, Sales Leadership, Cross-Functional Leadership, Business Operations Management) – these are duties. - Experience & Qualifications (Education, Experience, Technical Skills, Other Skills/Knowledge/Abilities) - Additional Details For This Role (remote field-based, travel, base salary, additional compensation) - Our Mission, Vision & Culture (substantive) - About Where We Work (substantive) We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instructions say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings where appropriate. Not required to use all; only if content exists. We need to decide mapping: - About the role: could contain Role Overview (maybe also Company Overview? but "About the role" is about the role itself). Could also include Why Work at Brother? maybe as part of company culture but not exactly. However we have separate sections for Mission etc. Might be better to follow the given headings: About the role (role overview), Responsibilities (duties), Requirements (education/experience), Qualifications (maybe skills?), Skills (technical skills), Benefits (maybe additional compensation?), Pay (base salary), Schedule (remote/travel). But we must only include sections if posting has real specific content. We have base salary range: $190k-$220k. Additional compensation: 50% bonus, auto allowance. So we can have Pay section with base salary and bonus info. Benefits? Not explicitly listed besides maybe flexible Fridays, hybrid schedule, casual dress code, facilitated courses, certificate programs, self-paced learning. Those are benefits. So we could have Benefits section. Schedule: remote field-based, travel up to 75%, hybrid schedule expectation if near office. So we can have Schedule section. Requirements: education and experience (minimum years). Qualifications: maybe technical skills? Or we could combine. But we must not create sections with filler like "not specified". We have specifics. We need to use

  • for any list of duties/requirements/benefits. So for duties we should list each duty as
  • . For requirements list education and experience as
  • . For benefits list items as
  • . For skills list maybe as
  • . For pay maybe not a list but could be

    . For schedule maybe

    . We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specifics of duties (the bullet points). We need to capture all bullet points from Duties & Responsibilities sub-sections. Also from Experience & Qualifications we need to capture education, experience, technical skills, other skills. We need to remove boilerplate: EEO statement, etc. Also remove duplicated lines. Also remove application instructions (none present). Also remove navigation etc. We need to output only HTML fragment. Let's structure:

    About the role

    Role Overview: The Senior Director, Sales & Business Development is an executive sales leader responsible for driving revenue growth, expanding market share, and leading a high-performing sales & business development organization for Brother Mobile Solutions (BMS), a division of Brother International Corporation. This position develops and executes sales strategies across direct, channel, and strategic accounts while partnering closely with product management, marketing, operations, engineering, finance & human resource groups to achieve business objectives. This role is accountable for sales performance, customer & partner relationships, organizational development, and profitable growth. This executive will lead a large team of sales & business development professionals dedicated to drive growth in new and existing vertical markets such as Retail, Transportation/Logistics, Public Sector, Industrial Solutions & more.

    Maybe also include Company Overview and Why Work at Brother? Could be part of About the role? But maybe better to have separate sections: Company Overview and Why Work at Brother? Not in allowed headings list but we could still use

    for any heading? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we could still use other headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. But we could also include other headings if needed? 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 suggests those are typical. However to be safe, we should stick to those headings. So we need to map all content into those categories. Thus we need to fit Company Overview and Why Work at Brother? maybe under About the role? Or maybe we can omit them? But we must preserve ALL substantive information. So we need to include them somewhere. Could put them under About the role as a preamble. Similarly, Mission, Vision & Culture and About Where We Work could go under Benefits? Not exactly. Could be part of About the role? Or maybe we could create a section "About the role" that includes role overview, company overview, why work at brother, mission, vision, culture, where we work. That might be too much but permissible as long as we preserve details. Alternatively, we could create multiple sections: About the role (role overview), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. And then we could also include additional sections like "Company Overview" but that's not in the list; maybe we should avoid extra headings. The instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are given. However the instruction also says "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create a section for Company Overview if we want, but we need to decide if it's considered filler? It's substantive. The instruction didn't restrict to only those headings; they just gave examples. So we could use headings like Company Overview, Why Work at Brother?, Mission, Vision & Culture, About Where We Work. But the examples given are typical sections; they didn't forbid others. However the earlier sentence: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This could be interpreted as we should use those headings for the sections we create. It might be safer to follow that and map all content into those eight possible sections. Let's try to map: - About the role: Role Overview (maybe also include Company Overview and Why Work at Brother? as context). But we need to preserve all details; we can include them in the paragraph. - Responsibilities: list of duties (all bullet points from Duties & Responsibilities). We'll need to capture each bullet. - Requirements: Education and Experience (minimum years). Could also include "Prior experience with some or all of the following: Enterprise Hardware, AIDC, Mobile Computing, Barcode Scanning, Label & Mobile Printing, RFID". That's more like qualifications/skills. But we can put under Requirements. - Qualifications: maybe technical skills? Or we could treat Qualifications as education/degree preferences? Actually the posting has Education, Experience, Technical Skills, Other Skills/Knowledge/Abilities. So we could split: Requirements = Education + Experience; Qualifications = Technical Skills + Other Skills/Knowledge/Abilities. But the instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have both Qualifications and Skills separate. So we need to decide what goes where. We could put: - Requirements: Education and Experience (minimum years). - Qualifications: Technical Skills (Microsoft Office, Salesforce) and maybe also "Prior experience with some or all of the following: Enterprise Hardware, AIDC, Mobile Computing, Barcode Scanning, Label & Mobile Printing, RFID". - Skills: Other Skills/Knowledge/Abilities (executive presence, strategic sales growth strategies, pipeline management, etc.) But we need to avoid duplication. Alternatively, we could put all skill-related items under Skills, and Qualifications could be empty? But we must not create empty sections. So we need to ensure each section has content. Let's examine the posting's "Experience & Qualifications" section: Education Bachelor's Degree (or equivalent experience) Business, Marketing, or related field preferred Master's Degree MBA Experience Minimum 15 years Progressive B2B technology or hardware sales experience; Proven success managing $100M+ annual revenue responsibilities; Experience selling through direct and indirect sales channels; Strong background in enterprise sales, strategic accounts, and complex solution selling Minimum 8 years Experience leading regional or national sales organizations; Experience with CRM platforms such as Salesforce Minimum 5 years Prior experience with some or all of the following: Enterprise Hardware, Automatic Identification & Data Capture (AIDC), Mobile Computing, Barcode Scanning, Label & Mobile Printing, RFID Technical Skills Knowledge of Microsoft Office (Word, PowerPoint, Excel, Outlook) Knowledge of Salesforce or similar Customer RelationshipManagement (CRM) system Other Skills/Knowledge/Abilities Strong executive presence & alignment to our leadership attributes: trustworthiness, talent engagement, and ability to manage through complexity Build-up and execution of strategic sales growth strategies to achieve business growth and divisional profit Knowledge in all aspects of sales management, including but not limited to: Pipeline Management, Sales forecasting, enterprise account management account mapping, resource management, financial acumen, contract negotiation, channel management, analytics Executive communication skills (written/verbal/interpersonal) and ability to build productive relationships internally and externally Ability to effectively lead, coach, develop and mentor others Strong change management & negotiation skills Ability to follow-up on commitments and take appropriate action Thus