UPS Digital Business Development Officer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, there is a preamble: "Before you apply to a job, select your language preference..." etc. That's boilerplate, remove. Then "Explore your next opportunity..." etc. That's generic marketing, likely boilerplate; remove. Then "Job Description: The Business Development Officer (BDO) is a consultative, new‑business sales role..." This is about the role. So we can have an

About the role

with paragraph(s) containing that description. Then "Responsibilities:" list bullet points. We'll put

Responsibilities

with

• each bullet. Then "Job Qualifications" then subheadings: Digital & Data Fluency, Consultative & Value-Based Selling Skills, Cross-Functional Collaboration, Sales Skills. Those are sections of qualifications/skills. The instruction says we can have sections like Qualifications, Skills. We need to decide how to structure. The posting includes "Job Qualifications" with bullet groups. Also later "Qualifications Requirements" with bullet list: Bachelor’s Degree..., Hold or obtain..., 2-3 years of sales experience. Then "Preferred Experience" bullet list. Then "Other Criteria:" bullet list (internal grade level, location, last day to apply, Employee Type). Then EEO statements etc. Then "Basic Qualifications:" bullet about citizenship. We need to preserve all substantive information, but remove boilerplate like EEO, equal opportunity, etc. Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. Also remove "Other Criteria:" maybe some are substantive: internal grade level, location requirement, last day to apply, Employee Type. Those are specifics; we should keep them. However "Other Criteria:" appears twice; we need to deduplicate. We need to decide sections: About the role, Responsibilities, Qualifications (maybe combine Job Qualifications and Qualifications Requirements and Preferred Experience and Other Criteria and Basic Qualifications), Skills (maybe separate). But we have to avoid thin sections. We could have sections: About the role, Responsibilities, Qualifications, Skills. Within Qualifications we can list bullet points for education, license, experience, preferred experience, other criteria, basic qualifications. Within Skills we can list the skill groups: Digital & Data Fluency, Consultative & Value-Based Selling Skills, Cross-Functional Collaboration, Sales Skills. But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use those headings. They didn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. So we should map content to those headings. If a section doesn't have content, we omit it. Thus we need to decide which of those headings have content. - About the role: yes. - Responsibilities: yes. - Requirements: maybe we can put the "Qualifications Requirements" (Bachelor's, license, 2-3 years) under Requirements. - Qualifications: maybe we can put the "Job Qualifications" groups (Digital & Data Fluency etc.) under Qualifications? But they also have Skills heading. Could treat Qualifications as the skill groups? Or we could put skill groups under Skills. The instruction gave both Qualifications and Skills as possible headings. We need to decide distribution. We have "Job Qualifications" with subheadings: Digital & Data Fluency, Consultative & Value-Based Selling Skills, Cross-Functional Collaboration, Sales Skills. Those are skill areas. So we could put those under Skills heading. Then we have "Qualifications Requirements" (education, license, experience) under Requirements heading. Then "Preferred Experience" could also go under Requirements or Qualifications? Probably under Requirements as well (preferred). Or we could have a separate "Qualifications" heading for preferred experience and other criteria. But we already used Requirements for mandatory qualifications. Could use Qualifications for preferred experience and other criteria. Then "Other Criteria:" (grade level, location, last day to apply, Employee Type) could go under Requirements or Qualifications? Might be considered Requirements as well. But we already used Requirements for mandatory. Could put other criteria under Qualifications. Then "Basic Qualifications:" citizenship requirement could go under Requirements as well (mandatory). So we may combine all mandatory under Requirements. Thus: - About the role: paragraph. - Responsibilities: list. - Requirements: list of mandatory qualifications: Bachelor's degree or equivalent, hold/obtain property & casualty insurance license, 2-3 years sales experience, Basic Qualifications (citizenship/work authorization), maybe also internal grade level? Actually internal grade level is not a qualification but a criteria; but we could include it under Requirements as well. However internal grade level is more like job level; could be considered a requirement. We'll include it. - Skills: list of skill groups: Digital & Data Fluency, Consultative & Value-Based Selling Skills, Cross-Functional Collaboration, Sales Skills. Each group has bullet points; we could either make each group a subheading? But we only allowed

  for sections; we could embed

  ? Not allowed? The instruction only mentions using

  for section headings; doesn't forbid other headings but 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 like

  or . Safer to just use

  • and maybe include the group titles as inside
  • or as a preceding

    . But we need to preserve all substantive information. We could format each skill group as a

  • with a heading. Thus Skills section:

    Skills

    then
    • Digital & Data Fluency: ...
    etc. We must not include Benefits, Pay, Schedule sections because no info. We must remove boilerplate: EEO, equal opportunity, etc. Also remove "Explore your next opportunity..." etc. Also remove "Before you apply..." etc. Also remove "Job Description:" maybe we keep the content but not the label. Also remove "Other Criteria:" duplicates. We need to preserve all substantive information: So we need to include the internal grade level, location requirement, last day to apply, Employee Type. Let's extract specifics: From text: - Job Description paragraph: "The Business Development Officer (BDO) is a consultative, new‑business sales role focused on acquiring new customers and driving revenue growth through UPS Capital’s risk management and financial protection solutions. This role owns the full sales cycle, from outbound prospecting and discovery through solution design and close, and partners closely with UPS sales teams and internal stakeholders to deliver measurable customer value. Successful candidates are curious, data‑driven sellers who thrive in a hunter environment, can translate complex solutions into clear business outcomes, and are motivated to help customers protect their businesses while enabling growth." That's About the role. Responsibilities bullet list (as given): - Achieve assigned revenue and growth targets by prospecting, developing, and closing new customers - Proactively identify, qualify, and pursue new business opportunities through outbound prospecting, referrals, and partnerships across the UPS ecosystem - Conduct discovery‑based, consultative sales conversations to understand customer risk, business and shipping challenges - Position and sell solutions that solve customer problems and deliver measurable value - Own the full sales cycle, from initial outreach through close, including pipeline management, forecasting, and deal progression - Collaborate with UPS sales partners and internal stakeholders to expand wallet share and accelerate new customer acquisition - Deliver a high‑quality customer experience through clear, professional verbal and written communication - Address and escalate customer issues as needed to support deal success and long‑term relationship growth - Maintain accurate activity, pipeline, and opportunity data in CRM systems Job Qualifications groups: Digital & Data Fluency: - Ability to understand and articulate the value of digital products, data insights, and analytics and translate them into business outcomes (cost reduction, risk mitigation, efficiency) - Ability to leverage existing databases and tools to build targeted prospecting lists and prioritize opportunities - Proactively stays current on products, services, and market conditions to effectively position solutions and add customer insight - Comfort discussing concepts such as APIs, system integrations, dashboards, automation, and data flows (no coding required) Consultative & Value-Based Selling Skills: - Proven experience in consultative selling, discovery-based conversations, and solution design - Ability to uncover customer workflows, pain points, and operational gaps Cross-Functional Collaboration: - Experience collaborating with product, technology, operations, underwriting, or analytics teams - Ability to act as the “voice of the customer” back into product and solution design to improve market fit and sales effectiveness - Comfort participating in pilots, betas, or early-stage product rollouts Sales Skills: - Digital and data literacy with the ability to translate technical concepts into customer value - Consultative, insight-led selling approach - Strong CRM and pipeline discipline (Salesforce) - Comfort selling evolving products and solutions in a changing environment - Ability to collaborate cross-functionally with product, technology, and operations teams - Strong learning agility and curiosity about technology-enabled solutions - Ability to build ROI-based business cases - Understanding of negotiation techniques, identifying stakeholders, demonstrating an understanding of each stakeholder's objectives Qualifications Requirements: - Bachelor’s Degree or International equivalent - Hold or obtain (post-hire) a valid property & casualty insurance license - 2-3 years of sales experience Preferred Experience: - SaaS, fintech, Insurtech, insurance, logistics tech, or supply-chain platforms - Selling solutions that combine product + service + insight - 3+ years of B2B sales experience Other Criteria: - The internal Grade Level is a 03A - Candidate must be geographically located in the same region as position or willing to self-relocate - The last day to apply is 10/1/2026 at 11:59pm ET - Employee Type: Permanent Basic Qualifications: - Must be a U.S. Citizen or National of the U.S., an alien lawfully admitted for permanent residence, or an alien authorized to work in the U.S. for this employer. Also there is duplicate "Other Criteria:" later with EEO statements; we ignore. Thus we need to include all these. Now decide sections: About the role: paragraph. Responsibilities: ul. Requirements: combine mandatory qualifications: Bachelor's degree, license, 2-3 years sales experience, Basic Qualifications (citizenship/work auth), internal grade level? maybe include internal grade level as a requirement. Also location requirement? Could be considered requirement. Also last day to apply? That's not a requirement for the role but a deadline; maybe we could put under Requirements as well? But it's more metadata. Could we put under Requirements? The instruction says we can include minor metadata in a short

    or drop it. The last day to apply is metadata; we could drop it? But they said preserve ALL substantive information; is the deadline substantive? Probably yes, it's info for applicant. However they said "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." The deadline is minor metadata; we could fold into a short

    maybe under Requirements or at end. But they also said "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 include a short

    inside Requirements or maybe after sections. But we need to decide. Employee Type: Permanent is also metadata. We could create a short