Enterprise Account Executive - SLED
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 parse the posting.
Content:
- Intro about Boomi: "About Boomi and What Makes Us Special" paragraph.
- "How you'll make an impact:" paragraph.
- "What you'll do:" bullet list? Actually it's a paragraph with sentences separated by line breaks? It lists responsibilities.
- "The experience you bring:" bullet list of requirements.
- "Bonus points if you have:" bullet list.
- "Key Competencies:" bullet list.
- "Boomi is committed to fair and equitable compensation practices. The On Target Earnings (OTE) for this role are $330K - $375K (inclusive of commission). This position is remote-friendly and, as such, final compensation will be determined by various factors including the candidate’s knowledge, skills, experience, and geographic location. Click here for an overview of our benefits at Boomi!"
- Duplicate: "Boomi is committed to fair and equitable compensation practices. The expected annual pay range for this position represents base salary or On-Target Earnings (OTE) for commission-based roles.Final compensation will be determined by various factors including the candidate's knowledge, skills, experience, geographic location, and role type. Non-commissioned roles may also be eligible for an annual performance bonus.Click here for an overview of our benefits at Boomi!"
- "Compensation - United States: $344,160 USD - $375,000 USD"
- Then culture statements.
We need to remove boilerplate: "Click here for an overview of our benefits at Boomi!" is application instruction? It's a link to benefits; maybe we can keep mention of benefits? The instruction says remove application instructions. "Click here for an overview of our benefits at Boomi!" is likely a link; we can drop that sentence.
Also duplicate compensation statements: we need to preserve substantive info: OTE $330K-$375K inclusive of commission; remote-friendly; final compensation determined by factors; compensation US $344,160 - $375,000 USD. Also mention benefits overview? We could keep a Benefits section if there is actual content about benefits. The posting only says "Click here for an overview of our benefits at Boomi!" which is not substantive detail; we should not create a Benefits section because no actual benefit details given. So we omit Benefits.
Pay section: we have concrete numbers: OTE $330K-$375K, compensation US $344,160-$375,000. Also remote-friendly (schedule? location). So we can create a Pay section with those details. Also maybe a Schedule/Location section? The posting says "This position is remote-friendly". That's about work arrangement, could be Schedule or Location. Since we have no explicit schedule, we could include a short paragraph under Pay or maybe a separate "Work Arrangement" but not required headings. The instruction says use headings like Pay, Schedule, Benefits only if posting actually states them. It does state remote-friendly, which is about work arrangement; could be considered Schedule? Might be better to include a short paragraph under Pay or maybe a separate "Work Arrangement" but not in allowed headings. Since only allowed headings are those listed, we could put remote-friendly info in Pay section as a note.
We need to avoid duplicate lines. We'll consolidate.
Now structure:
We need sections: About the role? Actually we have "About Boomi and What Makes Us Special" which is about company. Could be "About the role"? But we should not repeat job title. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if we have content.
We have:
- About the role: maybe a brief description of role impact? Could use "How you'll make an impact:" as About the role? Or we could treat "About Boomi and What Makes Us Special" as company overview, not required. Might be better to have sections: Responsibilities, Requirements (experience), Qualifications (maybe bonus points), Skills (key competencies), Pay.
We need to avoid thin sections. Let's decide:
- Responsibilities: from "What you'll do:" list.
- Requirements: from "The experience you bring:" list (7-10 years etc.)
- Qualifications: maybe "Bonus points if you have:" list.
- Skills: from "Key Competencies:" list.
- Pay: compensation details.
We could also include an introductory paragraph about the role impact as a
before sections.
We must not repeat job title as heading. So no heading for job title.
We need to preserve all substantive information. Let's extract.
Company intro: "About Boomi and What Makes Us SpecialAre you ready to work at a fast-growing company where you can make a difference? Boomi, the data activation company for AI, powers the agentic enterprise by bringing data to life across the business. The award-winning Boomi Enterprise Platform is the active data foundation that delivers essential agentic infrastructure enabling organizations to drive agentic transformation and harness the power of AI with secure, scalable connectivity. Trusted by over 30,000 customers and supported by a network of 800+ partners, Boomi helps organisations of all sizes achieve agility, efficiency, and innovation at scale. At Boomi, you’ll work with world-class people and industry-leading technology. We hire trailblazers with an entrepreneurial spirit who can solve challenging problems, make a real impact, and want to be part of building something big. If this sounds like a good fit for you, check out boomi.com or visit our Boomi Careers page to learn more."
We can keep that as a
maybe under an "About Boomi" heading? But not in allowed headings. Could just be a leading paragraph before sections.
Then "How you'll make an impact:" paragraph: "From developing brand new accounts, focused on SLED vertical, our Direct Sales team transforms opportunity into action every day. Whether focusing on a geographical area, product line, industry, channel or market segment, their goal is the same: to develop relationships with the executives and end-users of the organization and generate meaningful sales. As a SLED Enterprise Account Executive in the US, you are the direct line between our ground-breaking portfolio of product solutions, and the desks of satisfied customers. You will build strong customer relationships in the field, ensuring an outstanding customer experience with existing and/or potential customers."
We can keep that as a
maybe under a heading "About the role"? Actually that describes impact. Could be "About the role". We'll use
About the role
and put that paragraph.
Then responsibilities: list items from "What you'll do:".
Let's extract each bullet:
- Formulate and execute a sales strategy within an assigned region- focused on State and Local Government and Education prospects.
- Work in partnership with existing channel owners and the BDR team
- Carry quota for the entire Boomi suite of products and drive revenue growth in your region, with a keen focus on new logo acquisition
- Work closely with current customers and prospective customers as a trusted advisor to deeply understand their unique company challenges and goals
- Consult with customers on the Boomi Platform to evangelize solutions that will help them reach their business goals and blaze new trails within their organizations
- Contribute to our business growth in a fast-paced, collaborative, and fun atmosphere, as a valued member of our sales community
- Participate in the development and management of local field events
We need to put each as - inside
.
Then requirements: "The experience you bring:" list:
- 7-10 years of Enterprise sales experience in technology field sales, selling into SLED accounts
- 5+ years of experience with identifying, qualifying, developing, negotiating, and closing large-scale technology projects with enterprise accounts
- 5+ years of experience creating and implementing long-term transformational account strategies in a customer-facing role
- Data Integration, SaaS or similar domain experience
- Experience working with and presenting to C-level executives, IT, and lines of businesses across organizations
- Cross-functional selling experience (Architect, CTO, VP Ecommerce, Professional Services) and selling with GSI/SI
- Experience selling technical platform solutions and aligning technical solutions to business initiatives
We'll put as - .
Then bonus points: "Bonus points if you have:"
- Experience using Salesforce, Clari, and MEDPPIC model
We'll put as
- maybe under Qualifications heading.
Then key competencies: list:
- Consultative selling experience
- Prospecting
- Strong Communication
- Excellent presentation skills
- Competitive Spirit
- Collaboration and influence in a “win as a team” environment.
- Resourceful
- Coachable
- Drive for results
- Can articulate ROI.
- Solution Selling Ability
- Strong Discovery Skills
- Objection Handling Skills
- Planning and Closing Skills
We'll put as
- under Skills heading.
Pay: we have:
- On Target Earnings (OTE) for this role are $330K - $375K (inclusive of commission).
- This position is remote-friendly and, as such, final compensation will be determined by various factors including the candidate’s knowledge, skills, experience, and geographic location.
- Compensation - United States: $344,160 USD - $375,000 USD
Also duplicate about expected annual pay range etc. We'll combine.
We'll create
Pay
and a with those details.
We should not include the "Click here for an overview of our benefits at Boomi!" lines.
We should also not include the culture statements at end? They are substantive but not under allowed headings. Could be placed as a
after Pay maybe under a heading like "About Boomi"? But we already have About the role. Could add a section "About Boomi" but not in allowed headings. 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 says use those for those categories. It might be okay to add other headings but better to stick to those. The culture statements could be placed as a
after Pay without a heading, or we could incorporate into About the role paragraph. But we already used About the role for impact paragraph. Could we merge company intro and impact into About the role? That might be okay: About the role could include both company overview and impact. But we need to preserve all substantive info; we can include company overview in that paragraph.
Thus:
About the role
Boomi, the data activation company for AI, powers the agentic enterprise by bringing data to life across the business.
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 parse the posting. Content: - Intro about Boomi: "About Boomi and What Makes Us Special" paragraph. - "How you'll make an impact:" paragraph. - "What you'll do:" bullet list? Actually it's a paragraph with sentences separated by line breaks? It lists responsibilities. - "The experience you bring:" bullet list of requirements. - "Bonus points if you have:" bullet list. - "Key Competencies:" bullet list. - "Boomi is committed to fair and equitable compensation practices. The On Target Earnings (OTE) for this role are $330K - $375K (inclusive of commission). This position is remote-friendly and, as such, final compensation will be determined by various factors including the candidate’s knowledge, skills, experience, and geographic location. Click here for an overview of our benefits at Boomi!" - Duplicate: "Boomi is committed to fair and equitable compensation practices. The expected annual pay range for this position represents base salary or On-Target Earnings (OTE) for commission-based roles.Final compensation will be determined by various factors including the candidate's knowledge, skills, experience, geographic location, and role type. Non-commissioned roles may also be eligible for an annual performance bonus.Click here for an overview of our benefits at Boomi!" - "Compensation - United States: $344,160 USD - $375,000 USD" - Then culture statements. We need to remove boilerplate: "Click here for an overview of our benefits at Boomi!" is application instruction? It's a link to benefits; maybe we can keep mention of benefits? The instruction says remove application instructions. "Click here for an overview of our benefits at Boomi!" is likely a link; we can drop that sentence. Also duplicate compensation statements: we need to preserve substantive info: OTE $330K-$375K inclusive of commission; remote-friendly; final compensation determined by factors; compensation US $344,160 - $375,000 USD. Also mention benefits overview? We could keep a Benefits section if there is actual content about benefits. The posting only says "Click here for an overview of our benefits at Boomi!" which is not substantive detail; we should not create a Benefits section because no actual benefit details given. So we omit Benefits. Pay section: we have concrete numbers: OTE $330K-$375K, compensation US $344,160-$375,000. Also remote-friendly (schedule? location). So we can create a Pay section with those details. Also maybe a Schedule/Location section? The posting says "This position is remote-friendly". That's about work arrangement, could be Schedule or Location. Since we have no explicit schedule, we could include a short paragraph under Pay or maybe a separate "Work Arrangement" but not required headings. The instruction says use headings like Pay, Schedule, Benefits only if posting actually states them. It does state remote-friendly, which is about work arrangement; could be considered Schedule? Might be better to include a short paragraph under Pay or maybe a separate "Work Arrangement" but not in allowed headings. Since only allowed headings are those listed, we could put remote-friendly info in Pay section as a note. We need to avoid duplicate lines. We'll consolidate. Now structure: We need sections: About the role? Actually we have "About Boomi and What Makes Us Special" which is about company. Could be "About the role"? But we should not repeat job title. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if we have content. We have: - About the role: maybe a brief description of role impact? Could use "How you'll make an impact:" as About the role? Or we could treat "About Boomi and What Makes Us Special" as company overview, not required. Might be better to have sections: Responsibilities, Requirements (experience), Qualifications (maybe bonus points), Skills (key competencies), Pay. We need to avoid thin sections. Let's decide: - Responsibilities: from "What you'll do:" list. - Requirements: from "The experience you bring:" list (7-10 years etc.) - Qualifications: maybe "Bonus points if you have:" list. - Skills: from "Key Competencies:" list. - Pay: compensation details. We could also include an introductory paragraph about the role impact as a
before sections. We must not repeat job title as heading. So no heading for job title. We need to preserve all substantive information. Let's extract. Company intro: "About Boomi and What Makes Us SpecialAre you ready to work at a fast-growing company where you can make a difference? Boomi, the data activation company for AI, powers the agentic enterprise by bringing data to life across the business. The award-winning Boomi Enterprise Platform is the active data foundation that delivers essential agentic infrastructure enabling organizations to drive agentic transformation and harness the power of AI with secure, scalable connectivity. Trusted by over 30,000 customers and supported by a network of 800+ partners, Boomi helps organisations of all sizes achieve agility, efficiency, and innovation at scale. At Boomi, you’ll work with world-class people and industry-leading technology. We hire trailblazers with an entrepreneurial spirit who can solve challenging problems, make a real impact, and want to be part of building something big. If this sounds like a good fit for you, check out boomi.com or visit our Boomi Careers page to learn more." We can keep that as a
maybe under an "About Boomi" heading? But not in allowed headings. Could just be a leading paragraph before sections. Then "How you'll make an impact:" paragraph: "From developing brand new accounts, focused on SLED vertical, our Direct Sales team transforms opportunity into action every day. Whether focusing on a geographical area, product line, industry, channel or market segment, their goal is the same: to develop relationships with the executives and end-users of the organization and generate meaningful sales. As a SLED Enterprise Account Executive in the US, you are the direct line between our ground-breaking portfolio of product solutions, and the desks of satisfied customers. You will build strong customer relationships in the field, ensuring an outstanding customer experience with existing and/or potential customers." We can keep that as a
maybe under a heading "About the role"? Actually that describes impact. Could be "About the role". We'll use
About the role
and put that paragraph. Then responsibilities: list items from "What you'll do:". Let's extract each bullet: - Formulate and execute a sales strategy within an assigned region- focused on State and Local Government and Education prospects. - Work in partnership with existing channel owners and the BDR team - Carry quota for the entire Boomi suite of products and drive revenue growth in your region, with a keen focus on new logo acquisition - Work closely with current customers and prospective customers as a trusted advisor to deeply understand their unique company challenges and goals - Consult with customers on the Boomi Platform to evangelize solutions that will help them reach their business goals and blaze new trails within their organizations - Contribute to our business growth in a fast-paced, collaborative, and fun atmosphere, as a valued member of our sales community - Participate in the development and management of local field events We need to put each as- .
Then requirements: "The experience you bring:" list:
- 7-10 years of Enterprise sales experience in technology field sales, selling into SLED accounts
- 5+ years of experience with identifying, qualifying, developing, negotiating, and closing large-scale technology projects with enterprise accounts
- 5+ years of experience creating and implementing long-term transformational account strategies in a customer-facing role
- Data Integration, SaaS or similar domain experience
- Experience working with and presenting to C-level executives, IT, and lines of businesses across organizations
- Cross-functional selling experience (Architect, CTO, VP Ecommerce, Professional Services) and selling with GSI/SI
- Experience selling technical platform solutions and aligning technical solutions to business initiatives
We'll put as
- .
Then bonus points: "Bonus points if you have:"
- Experience using Salesforce, Clari, and MEDPPIC model
We'll put as
- maybe under Qualifications heading.
Then key competencies: list:
- Consultative selling experience
- Prospecting
- Strong Communication
- Excellent presentation skills
- Competitive Spirit
- Collaboration and influence in a “win as a team” environment.
- Resourceful
- Coachable
- Drive for results
- Can articulate ROI.
- Solution Selling Ability
- Strong Discovery Skills
- Objection Handling Skills
- Planning and Closing Skills
We'll put as
- under Skills heading.
Pay: we have:
- On Target Earnings (OTE) for this role are $330K - $375K (inclusive of commission).
- This position is remote-friendly and, as such, final compensation will be determined by various factors including the candidate’s knowledge, skills, experience, and geographic location.
- Compensation - United States: $344,160 USD - $375,000 USD
Also duplicate about expected annual pay range etc. We'll combine.
We'll create
Pay
and awith those details. We should not include the "Click here for an overview of our benefits at Boomi!" lines. We should also not include the culture statements at end? They are substantive but not under allowed headings. Could be placed as a
after Pay maybe under a heading like "About Boomi"? But we already have About the role. Could add a section "About Boomi" but not in allowed headings. 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 says use those for those categories. It might be okay to add other headings but better to stick to those. The culture statements could be placed as a
after Pay without a heading, or we could incorporate into About the role paragraph. But we already used About the role for impact paragraph. Could we merge company intro and impact into About the role? That might be okay: About the role could include both company overview and impact. But we need to preserve all substantive info; we can include company overview in that paragraph. Thus:
About the role
Boomi, the data activation company for AI, powers the agentic enterprise by bringing data to life across the business.
- under Skills heading.
Pay: we have:
- On Target Earnings (OTE) for this role are $330K - $375K (inclusive of commission).
- This position is remote-friendly and, as such, final compensation will be determined by various factors including the candidate’s knowledge, skills, experience, and geographic location.
- Compensation - United States: $344,160 USD - $375,000 USD
Also duplicate about expected annual pay range etc. We'll combine.
We'll create
- maybe under Qualifications heading.
Then key competencies: list:
- Consultative selling experience
- Prospecting
- Strong Communication
- Excellent presentation skills
- Competitive Spirit
- Collaboration and influence in a “win as a team” environment.
- Resourceful
- Coachable
- Drive for results
- Can articulate ROI.
- Solution Selling Ability
- Strong Discovery Skills
- Objection Handling Skills
- Planning and Closing Skills
We'll put as