Enterprise Account Executive - WA, OR, AK, HI
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for any list of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting has:
- Company description (Granicus)
- Job Summary
- "What Your Impact Will Look Like" - list of responsibilities
- "You Will Love This Job If You Have" - list of requirements/qualifications
- Pay Range: USD $110,000.00 - USD $125,000.00 /Yr.
- About Us (diversity statement)
- Security And Privacy Requirements
- The Team (remote-first, globally distributed)
- The Culture (culture highlights)
- The Impact
- The Benefits (detailed benefits for U.S.-based team members)
- Equal Opportunity Employer statement (boilerplate - should remove)
I need to structure this into appropriate sections with h3 headings.
Possible sections:
1. About the role (or Job Summary) - prose
2. Responsibilities - list from "What Your Impact Will Look Like"
3. Requirements (or Qualifications) - list from "You Will Love This Job If You Have"
4. Pay - since it's specified
5. Benefits - since detailed benefits are listed
6. Company Overview - could combine company description, team, culture, impact
7. Security & Privacy Requirements - list
But need to be careful: "Prefer a few substantive sections over many thin ones." So maybe combine some.
Let me think about the structure:
- Company Overview (prose about Granicus)
- Job Summary (prose)
- Responsibilities (list)
- Requirements (list)
- Pay (prose with range)
- Benefits (list)
- Security & Privacy Requirements (list)
- Team & Culture (prose)
But "Team & Culture" might be thin. The posting has "The Team", "The Culture", "The Impact" - could combine into one section.
Also need to remove EEO boilerplate.
Let me draft the HTML.
First, Company Overview: combine the first big paragraph about Granicus.
Job Summary: the "Job Summary" paragraph.
Responsibilities: the bullet points under "What Your Impact Will Look Like" - they are already listed as separate lines, but in the text they are separated by periods. Actually looking at the text: "Drive sales generation and foster market expansion within the designated territory.Collaborate closely with the Marketing Team..." It seems like each sentence is a separate responsibility. I should split them into list items. They are separated by periods but no line breaks. I'll need to parse them. The text: "Drive sales generation and foster market expansion within the designated territory.Collaborate closely with the Marketing Team to ensure a robust lead pipeline and effective lead nurturing.Craft and communicate compelling value propositions to prospective clients, highlighting the unique benefits of our solutions.Facilitate collaborative selling opportunities with partners, leveraging synergies to maximize sales potential.Lead pursuit teams for larger-scale opportunities, orchestrating efforts for comprehensive client engagement.Guide and educate prospects through the purchasing journey, providing insights and assistance as needed.Develop and execute a comprehensive sales plan aimed at surpassing predefined sales targets.Gain deep insight into intricate customer requirements across operational, business, and technical domains, tailoring solutions accordingly.Independently create and deliver customized presentations on Granicus, showcasing its potential to revolutionize public engagement strategies.Coordinate internal resources, including sales support, marketing, and solution consultants, to deliver compelling pitches and proposals.Oversee all aspects of sales activities within the assigned territory, from prospecting and tracking to opportunity management, revenue forecasting, and contract negotiation.Actively pursue leads generated through personal efforts and marketing initiatives, ensuring no opportunity is left untapped.Assist in formulating sales strategies in collaboration with the management team, drawing on market insights and client feedback.Maintain meticulous documentation of all interactions, activities, and correspondence in our Salesforce CRM system.Prepare and deliver quarterly business reviews to Sales Management, Senior Management, and peers, providing comprehensive insights into sales performance and market trends.Be prepared to travel up to 50% of the time to engage with clients and prospects effectively."
That's 18 responsibilities. I'll make each a list item.
Requirements: "You Will Love This Job If You Have" list. The text: "5+ years of Public Sector sales experience in IT, information services, or business services sold on a subscription model.Demonstrated effectiveness selling through partners, resellers and/or integrators Effective Prospecting and Opportunity Closure: Demonstrates a track record of successfully identifying and nurturing sales leads through both direct outreach and in-person engagements, culminating in the successful closure of opportunities.Proficient in CRM Utilization: Proficiently utilizes customer relationship management software to efficiently track leads, manage opportunities, and streamline sales processes, ensuring effective follow-up and nurturing of prospects.Adaptability in Fast-Paced Environments: Thrives in dynamic, fast-paced environments, adept at managing multiple tasks and priorities under tight deadlines to maximize sales productivity and responsiveness to client needs.Client-Centric Problem-Solving: Possesses a genuine passion for helping clients overcome challenges, employing exceptional problem-solving skills to tailor solutions that address their specific pain points and drive value.Solution-Oriented Sales Approach: Executes sales processes within a solution-oriented framework, focusing on building strong relationships with clients and delivering persuasive oral and written communication to effectively communicate value propositions and drive sales outcomes.Utilization of Technology for Sales Enhancement: Comfortable and experienced in leveraging technology tools and platforms to enhance sales effectiveness, utilizing digital resources to streamline processes, gather insights, and drive engagement with prospects.Navigating Complex Sales Environments: Skilled in navigating committee-driven sales environments characterized by multiple stakeholders and decision-makers, adept at building consensus and overcoming objections to drive successful sales outcomes.Influencing Abilities and Persuasive Communication: Capable of effectively persuading and influencing potential clients to consider our solutions, using compelling arguments and persuasive communication techniques to close deals.Interpersonal Effectiveness and Collaborative Relationship-Building: Skilled in building strong, trust-based relationships with clients and internal teams alike, fostering collaboration and cooperation to drive successful sales outcomes.Forward-Thinking and Strategic Mindset: Possesses a forward-thinking approach and strategic mindset, able to anticipate market trends and client needs to proactively tailor sales strategies for long-term success.Strong Customer Orientation and Result Orientation: Demonstrates a deep commitment to understanding and meeting customer needs, coupled with a relentless focus on achieving sales targets and delivering measurable results Business Acumen: Exhibits a strong understanding of business principles and market dynamics, leveraging this knowledge to identify opportunities, mitigate risks, and make informed decisions that contribute to sales growth and profitability."
That's a list of requirements. I'll make each a list item. Note that the first two are separate: "5+ years..." and "Demonstrated effectiveness..." then the rest are colon-separated. I'll treat each as a separate requirement.
Pay: "Pay Range USD $110,000.00 - USD $125,000.00 /Yr." - include as Pay section.
Benefits: detailed list under "The Benefits". It has categories: Flexibility & Balance, Health & Wellness, Family & Future, Growth & Recognition. Each with bullet points. I'll include as a list, maybe with subheadings? But the rule says use
- for any list. Could make a single list with all benefits, or separate lists per category. Since the categories are headings within benefits, I could use
? But the rule only mentions for section headings. It doesn't forbid but says use for section headings. Probably okay to use for sub-sections within benefits. However, to keep it simple, I'll make a single list with all benefit items, maybe grouping by category in the text. But the posting has clear categories. I'll create a list where each item includes the category. Or I could make multiple with headings. The instruction: "Use - for any list of duties/requirements/benefits". It doesn't specify subheadings. I think using
is acceptable as long as main sections are . I'll do:
Benefits
Flexibility & Balance
- ...
Health & Wellness
- ...
etc.
But the rule says "use for section headings". It doesn't say not to use other headings. I'll use for sub-sections.
Security & Privacy Requirements: two bullet points.
Team & Culture: combine "The Team", "The Culture", "The Impact" into one section with prose.
About Us diversity statement: could be part of Company Overview or separate. I'll include in Company Overview.
Now, remove EEO statement.
Also remove "Want to know more? See more of what we do here ." and "See more of our impact here ." as they are links/navigation.
Remove "Don’t have all the skills/experience mentioned above? ..." that's part of About Us diversity statement, keep.
Now, write HTML.
Let me structure:
Company Overview
Granicus is driven by the excitement of building, implementing, and maintaining technology that is transforming the Govtech industry by bringing governments and its constituents together. We are on a mission to support our customers with meeting the needs of their communities and implementing our technology in ways that are equitable and inclusive. Granicus has consistently appeared on the GovTech 100 list over the past 5 years and has been recognized as the best companies to work on BuiltIn. Over the last 25 years, we have served 5,500 federal, state, and local government agencies and more than 300 million citizen subscribers power an unmatched Subscriber Network that use our digital solutions to make the world a better place. With comprehensive cloud-based solutions for communications, government website design, meeting and agenda management software, records management, and digital services, Granicus empowers stronger relationships between government and residents across the U.S., U.K., Australia, New Zealand, and Canada. By simplifying interactions with residents, while disseminating critical information, Granicus brings governments closer to the people they serve—driving meaningful change for communities around the globe.
We are a remote-first company with a globally distributed workforce across the United States, Canada, United Kingdom, India, Armenia, Australia, and New Zealand. Our culture highlights include Employee Resource Groups to encourage diverse voices, Coffee with Mark sessions where employees interact with our CEO on important issues, Microsoft Teams communities focused on wellness, art, furbabies, family, parenting, and more, and special guests discussing issues that impact our employee population. We are proud to serve dynamic organizations around the globe that use our digital solutions to make the world a better place.
At Granicus, we are trying to build diverse, inclusive teams. We do not have degree requirements for most of our roles. If you don’t
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Company description (Granicus) - Job Summary - "What Your Impact Will Look Like" - list of responsibilities - "You Will Love This Job If You Have" - list of requirements/qualifications - Pay Range: USD $110,000.00 - USD $125,000.00 /Yr. - About Us (diversity statement) - Security And Privacy Requirements - The Team (remote-first, globally distributed) - The Culture (culture highlights) - The Impact - The Benefits (detailed benefits for U.S.-based team members) - Equal Opportunity Employer statement (boilerplate - should remove) I need to structure this into appropriate sections with h3 headings. Possible sections: 1. About the role (or Job Summary) - prose 2. Responsibilities - list from "What Your Impact Will Look Like" 3. Requirements (or Qualifications) - list from "You Will Love This Job If You Have" 4. Pay - since it's specified 5. Benefits - since detailed benefits are listed 6. Company Overview - could combine company description, team, culture, impact 7. Security & Privacy Requirements - list But need to be careful: "Prefer a few substantive sections over many thin ones." So maybe combine some. Let me think about the structure: - Company Overview (prose about Granicus) - Job Summary (prose) - Responsibilities (list) - Requirements (list) - Pay (prose with range) - Benefits (list) - Security & Privacy Requirements (list) - Team & Culture (prose) But "Team & Culture" might be thin. The posting has "The Team", "The Culture", "The Impact" - could combine into one section. Also need to remove EEO boilerplate. Let me draft the HTML. First, Company Overview: combine the first big paragraph about Granicus. Job Summary: the "Job Summary" paragraph. Responsibilities: the bullet points under "What Your Impact Will Look Like" - they are already listed as separate lines, but in the text they are separated by periods. Actually looking at the text: "Drive sales generation and foster market expansion within the designated territory.Collaborate closely with the Marketing Team..." It seems like each sentence is a separate responsibility. I should split them into list items. They are separated by periods but no line breaks. I'll need to parse them. The text: "Drive sales generation and foster market expansion within the designated territory.Collaborate closely with the Marketing Team to ensure a robust lead pipeline and effective lead nurturing.Craft and communicate compelling value propositions to prospective clients, highlighting the unique benefits of our solutions.Facilitate collaborative selling opportunities with partners, leveraging synergies to maximize sales potential.Lead pursuit teams for larger-scale opportunities, orchestrating efforts for comprehensive client engagement.Guide and educate prospects through the purchasing journey, providing insights and assistance as needed.Develop and execute a comprehensive sales plan aimed at surpassing predefined sales targets.Gain deep insight into intricate customer requirements across operational, business, and technical domains, tailoring solutions accordingly.Independently create and deliver customized presentations on Granicus, showcasing its potential to revolutionize public engagement strategies.Coordinate internal resources, including sales support, marketing, and solution consultants, to deliver compelling pitches and proposals.Oversee all aspects of sales activities within the assigned territory, from prospecting and tracking to opportunity management, revenue forecasting, and contract negotiation.Actively pursue leads generated through personal efforts and marketing initiatives, ensuring no opportunity is left untapped.Assist in formulating sales strategies in collaboration with the management team, drawing on market insights and client feedback.Maintain meticulous documentation of all interactions, activities, and correspondence in our Salesforce CRM system.Prepare and deliver quarterly business reviews to Sales Management, Senior Management, and peers, providing comprehensive insights into sales performance and market trends.Be prepared to travel up to 50% of the time to engage with clients and prospects effectively." That's 18 responsibilities. I'll make each a list item. Requirements: "You Will Love This Job If You Have" list. The text: "5+ years of Public Sector sales experience in IT, information services, or business services sold on a subscription model.Demonstrated effectiveness selling through partners, resellers and/or integrators Effective Prospecting and Opportunity Closure: Demonstrates a track record of successfully identifying and nurturing sales leads through both direct outreach and in-person engagements, culminating in the successful closure of opportunities.Proficient in CRM Utilization: Proficiently utilizes customer relationship management software to efficiently track leads, manage opportunities, and streamline sales processes, ensuring effective follow-up and nurturing of prospects.Adaptability in Fast-Paced Environments: Thrives in dynamic, fast-paced environments, adept at managing multiple tasks and priorities under tight deadlines to maximize sales productivity and responsiveness to client needs.Client-Centric Problem-Solving: Possesses a genuine passion for helping clients overcome challenges, employing exceptional problem-solving skills to tailor solutions that address their specific pain points and drive value.Solution-Oriented Sales Approach: Executes sales processes within a solution-oriented framework, focusing on building strong relationships with clients and delivering persuasive oral and written communication to effectively communicate value propositions and drive sales outcomes.Utilization of Technology for Sales Enhancement: Comfortable and experienced in leveraging technology tools and platforms to enhance sales effectiveness, utilizing digital resources to streamline processes, gather insights, and drive engagement with prospects.Navigating Complex Sales Environments: Skilled in navigating committee-driven sales environments characterized by multiple stakeholders and decision-makers, adept at building consensus and overcoming objections to drive successful sales outcomes.Influencing Abilities and Persuasive Communication: Capable of effectively persuading and influencing potential clients to consider our solutions, using compelling arguments and persuasive communication techniques to close deals.Interpersonal Effectiveness and Collaborative Relationship-Building: Skilled in building strong, trust-based relationships with clients and internal teams alike, fostering collaboration and cooperation to drive successful sales outcomes.Forward-Thinking and Strategic Mindset: Possesses a forward-thinking approach and strategic mindset, able to anticipate market trends and client needs to proactively tailor sales strategies for long-term success.Strong Customer Orientation and Result Orientation: Demonstrates a deep commitment to understanding and meeting customer needs, coupled with a relentless focus on achieving sales targets and delivering measurable results Business Acumen: Exhibits a strong understanding of business principles and market dynamics, leveraging this knowledge to identify opportunities, mitigate risks, and make informed decisions that contribute to sales growth and profitability." That's a list of requirements. I'll make each a list item. Note that the first two are separate: "5+ years..." and "Demonstrated effectiveness..." then the rest are colon-separated. I'll treat each as a separate requirement. Pay: "Pay Range USD $110,000.00 - USD $125,000.00 /Yr." - include as Pay section. Benefits: detailed list under "The Benefits". It has categories: Flexibility & Balance, Health & Wellness, Family & Future, Growth & Recognition. Each with bullet points. I'll include as a list, maybe with subheadings? But the rule says use
- for any list. Could make a single list with all benefits, or separate lists per category. Since the categories are headings within benefits, I could use
? But the rule only mentions
for section headings. It doesn't forbid
but says use
for section headings. Probably okay to use
for sub-sections within benefits. However, to keep it simple, I'll make a single list with all benefit items, maybe grouping by category in the text. But the posting has clear categories. I'll create a list where each item includes the category. Or I could make multiple
- with
- for any list of duties/requirements/benefits". It doesn't specify subheadings. I think using
is acceptable as long as main sections are
. I'll do:
Benefits
Flexibility & Balance
- ...
Health & Wellness
- ...
for section headings". It doesn't say not to use other headings. I'll use
for sub-sections. Security & Privacy Requirements: two bullet points. Team & Culture: combine "The Team", "The Culture", "The Impact" into one section with prose. About Us diversity statement: could be part of Company Overview or separate. I'll include in Company Overview. Now, remove EEO statement. Also remove "Want to know more? See more of what we do here ." and "See more of our impact here ." as they are links/navigation. Remove "Don’t have all the skills/experience mentioned above? ..." that's part of About Us diversity statement, keep. Now, write HTML. Let me structure:
Company Overview
Granicus is driven by the excitement of building, implementing, and maintaining technology that is transforming the Govtech industry by bringing governments and its constituents together. We are on a mission to support our customers with meeting the needs of their communities and implementing our technology in ways that are equitable and inclusive. Granicus has consistently appeared on the GovTech 100 list over the past 5 years and has been recognized as the best companies to work on BuiltIn. Over the last 25 years, we have served 5,500 federal, state, and local government agencies and more than 300 million citizen subscribers power an unmatched Subscriber Network that use our digital solutions to make the world a better place. With comprehensive cloud-based solutions for communications, government website design, meeting and agenda management software, records management, and digital services, Granicus empowers stronger relationships between government and residents across the U.S., U.K., Australia, New Zealand, and Canada. By simplifying interactions with residents, while disseminating critical information, Granicus brings governments closer to the people they serve—driving meaningful change for communities around the globe.
We are a remote-first company with a globally distributed workforce across the United States, Canada, United Kingdom, India, Armenia, Australia, and New Zealand. Our culture highlights include Employee Resource Groups to encourage diverse voices, Coffee with Mark sessions where employees interact with our CEO on important issues, Microsoft Teams communities focused on wellness, art, furbabies, family, parenting, and more, and special guests discussing issues that impact our employee population. We are proud to serve dynamic organizations around the globe that use our digital solutions to make the world a better place.
At Granicus, we are trying to build diverse, inclusive teams. We do not have degree requirements for most of our roles. If you don’t
headings. The instruction: "Use
- for any list of duties/requirements/benefits". It doesn't specify subheadings. I think using