Senior Account Executive - Commercial Print
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. We must include sections only when posting has real, specific content. We need to extract content: Overview (maybe "Overview" is a heading but not listed as allowed? The allowed headings list includes "About the role". Overview could be considered "About the role". We can treat Overview as "About the role". The posting includes "Overview" then description. Then "Responsibilities" with bullet list. Then "Why You’ll Love It" maybe could be considered part of Overview? Not a standard heading; we could either omit or treat as part of Overview. The instruction: prefer a few substantive sections over many thin ones. So we could combine "Overview" and "Why You’ll Love It" into one section "About the role". Or we could keep Overview as "About the role" and include the "Why You’ll Love It" paragraphs within that section.
Then "Qualifications" heading is allowed. The posting includes "Qualifications What You Bring". So we will have Qualifications
with content.
Also there is "About Us" and "About Konica Minolta" etc. Those are not standard headings; they could be considered "About the role"? Probably not; they are company description. Should we include? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The company description is substantive but not one of the allowed headings. The allowed headings list is examples, not exhaustive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings where applicable. For company description, maybe we could use "About the role"? No, that's not correct. Could we omit company description? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep company description somewhere. Perhaps we can put it under a generic About the company
but that's not in the list. However the list is examples; we could still use other headings if needed, but they gave examples. Safer to stick to allowed headings; but we need to preserve info. Could we incorporate company description into "About the role" section? That would be mixing role description with company info, but still preserving. The instruction: "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
About the company
but that's not in the list. However the list is examples; we could still use other headings if needed, but they gave examples. Safer to stick to allowed headings; but we need to preserve info. Could we incorporate company description into "About the role" section? That would be mixing role description with company info, but still preserving. The instruction: "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 shortor drop it." It doesn't forbid other headings. It just gives examples. So we can add a section like "About the company". However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This suggests we should use those headings where applicable, but we could also use others if needed. But to be safe, we could treat the company description as part of "About the role" (since it's about the role's context). However that may be mixing.
Alternatively we could create a section "About Konica Minolta" as About Konica Minolta
. That is a heading not in examples but still an h3. The instruction didn't forbid other headings; it just gave examples. So it's okay.
We also need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the Salary Disclaimer, AI Disclosure, EOE Statement, and the French duplicates? Actually there are French translations of many sections. We need to keep substantive information; but the French duplicates are essentially same content in French. Should we keep both? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we drop the French duplicate, we are losing some content (the French translation). However the French duplicate is essentially same info; but it's still substantive. However it's likely considered boilerplate duplication? The instruction says remove duplicated lines. The French version is duplicated content but in another language. Might be considered duplicated lines? Probably they want to keep only one language version (English). Since the job posting is likely English, we can drop the French duplicate as redundant. Also the "Salary Disclaimer" and AI Disclosure and EOE Statement are boilerplate legal; we should remove them.
Also there is "Overview Overview" repeated at start; we need to keep only one.
Now we need to produce HTML fragment with sections.
Let's extract content:
Overview (English):
"Ready to run your own territory and close big deals? As a Senior Field Account Executive, you will own the full sales cycle from prospecting to closing, while meeting customers face-to-face and driving real revenue growth. This is a field-first, high-impact role where you will build pipelines, deliver tailored solutions, and consistently win new business. If you’re competitive, confident, and love being out in front of customers—this is where you level up."
Why You’ll Love It:
"Run your business: full ownership of your territory
Face-to-face selling: where deals actually happen
Uncapped impact: your results drive your success
Fast growth: build your career while winning deals"
We can combine these into About the role section.
Responsibilities (bullet list):
- Own your territory and hit (and beat) revenue goals
- Build a strong pipeline through prospecting, networking, and referrals
- Spend the majority of time in the field—meeting customers at their locations, running discovery, and closing deals
- Deliver solution-focused presentations across our tech portfolio
- Run full-cycle sales: discover → propose → negotiate → close
- Grow key accounts with upsell and cross-sell opportunities
- Partner with internal teams to deliver a great customer experience
- Keep your pipeline tight with accurate CRM tracking and forecasting
Qualifications:
"What You Bring
Bachelor’s degree preferred, or equivalent experience.
3-6 years of B2B sales experience with demonstrated sales quota achievement.
Ability to customarily and regularly travel within the assigned territory for in-person customer/prospect meetings and field-based selling
Valid driver’s license and reliable transportation for daily field travel.
Alignment to company values: Open & Honest, Customer-Centric, Innovative, Passionate, Inclusive & Collaborative, Accountable.
Familiarity with Salesforce CRM required.
If you’re ready to own the number, close deals, and make your mark, let’s go!"
About Us / About Konica Minolta: This is a long description about company history, achievements, etc. We'll keep that as a section maybe "About Konica Minolta". We need to preserve all substantive information. We'll include the English version only (skip French duplicate). The English version includes:
"This posting reflects an existing vacancy that we are actively recruiting for." (maybe minor metadata; could be folded into a short p or dropped? It's not minor but it's about vacancy status. Could keep as a short paragraph.)
Then "About Konica Minolta Konica Minolta Business Solutions' (Konica Minolta) journey started more than 150 years ago, with a vision to see and do things differently. The company partners with clients to Give Shape to Ideas by supporting their digital transformation through its expansive Intelligent Connected Workplace portfolio. Its business technology offerings include IT Services, intelligent information management, video security solutions and managed print services, as well as office technology and industrial and commercial print solutions. 2025 marks Konica Minolta’s 20th anniversary in production print, for which it celebrates "20 Years of Excellence, Innovation and Impact,” and continues to lead the way in digital commercial printing. This year also commemorates 20 years of Konica Minolta’s bizhub brand. Over the past two decades, the bizhub series has revolutionized office technology and redefined how businesses operate. It has continuously evolved to meet the needs of modern workplaces, fueled by advances in technology and a commitment to innovation. Konica Minolta is proud to be ranked on the Forbes 2025 America's Best Large Employers list, included on CRN’s MSP 500 list numerous times; recognized as the #1 Brand for Customer Loyalty in the MFP Office Copier Market by Brand Keys for eighteen consecutive years and presented with Keypoint Intelligence’s BLI 2025 and 2021 A3 Line of The Year and BLI 2021-2023 Most Color Consistent A3 Brand Awards for its bizhub One i-Series. For more information, please visit Konica Minolta online and follow it on Facebook, YouTube, LinkedIn and Twitter. Konica Minolta operates on a North American Shared Services model, which aligns cross-border priorities and enhances delivery to its field organization. This combines service functions in the U.S. and Canada, ultimately providing more resources to support areas such as sales administration, logistics and supply chain, marketing, product planning, finance, IT, HR and legal."
We should keep that.
Now we need to output HTML fragment only, no markdown fences.
We'll structure:
About the role
Overview paragraph(s) + Why You’ll Love It bullets? Actually Why You’ll Love It is a list; we could make a
- for those points. But the instruction: Use
- for any list of duties/requirements/benefits. Why You’ll Love It is a list of benefits? It's more like selling points; could be treated as list. We'll make a
- for those.
Thus:
About the role
Ready to run your own territory and close big deals? As a Senior Field Account Executive, you will own the full sales cycle from prospecting to closing, while meeting customers face-to-face and driving real revenue growth. This is a field-first, high-impact role where you will build pipelines, deliver tailored solutions, and consistently win new business. If you’re competitive, confident, and love being out in front of customers—this is where you level up.
- Run your business: full ownership of your territory
- Face-to-face selling: where deals actually happen
- Uncapped impact: your results drive your success
- Fast growth: build your career while winning deals
Responsibilities
- Own your territory and hit (and beat) revenue goals
- Build a strong pipeline through prospecting, networking, and referrals
- Spend the majority of time in the field—meeting customers at their locations, running discovery, and closing deals
- Deliver solution-focused presentations across our tech portfolio
- Run full-cycle sales: discover → propose → negotiate → close
- Grow key accounts with upsell and cross-sell opportunities
- Partner with internal teams to deliver a great customer experience
- Keep your pipeline tight with accurate CRM tracking and forecasting
Qualifications
Bachelor’s degree preferred, or equivalent experience.
- 3-6 years of B2B sales experience with demonstrated sales quota achievement.
- Ability to customarily and regularly travel within the assigned territory for in-person customer/prospect meetings and field-based selling
- Valid driver’s license and reliable transportation for daily field travel.
- Alignment to company values: Open & Honest, Customer-Centric, Innovative, Passionate, Inclusive & Collaborative, Accountable.
- Familiarity with Salesforce CRM required.
If you’re ready to own the number, close deals
- for those.
Thus:
- for any list of duties/requirements/benefits. Why You’ll Love It is a list of benefits? It's more like selling points; could be treated as list. We'll make a