Major Account Manager
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.
We need to decide which sections to include based on content.
We have:
- Who We Are: description of company. Could be "About the company" but not listed as allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely we should stick to those headings. "Who We Are" could be considered "About the role"? Not exactly. Maybe we can treat it as "About the role"? But that is about the role, not company. However we could still include a section like "About the company" but not in list? The instruction says use those headings for section headings (e.g. ...). It might be okay to use other headings if needed, but they gave examples. Safer to stick to those headings. We can map content:
- About the role: could include description of what you'll do (role overview). Could be "What You'll Do" and "Role". So we can put that under About the role.
- Responsibilities: list of duties (the bullet list under "In this role you will:").
- Requirements: maybe "What You'll Bring" (experience, skills). Could be Requirements.
- Qualifications: maybe Education And Experience.
- Skills: maybe specific skills like Salesforce CRM, etc. Could be separate.
- Benefits: "What We Offer" includes benefits list.
- Pay: Not mentioned explicitly (no salary). So we should NOT create Pay section.
- Schedule: Not mentioned (remote, location). Could be schedule? Not explicit. So we should not create Schedule.
We need to preserve all substantive information. Remove boilerplate like ADA Notice? That's legal but maybe not boilerplate? It's about accommodation; could be considered legal. Might be removed? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. ADA notice is legal; we could remove it. Also remove "MGT Impact Solutions, LLC is an equal opportunity employer..." That's EEO boilerplate; remove.
Also remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Who We Are: paragraph about MGT. Keep.
What You'll Do: paragraphs describing role. Could be under About the role.
Role: paragraph about position requires frequent outbound... Could also be part of About the role or Responsibilities.
Then bullet list under "In this role you will:" with many items. Those are responsibilities.
Performance Expectations: bullet-like sentences (achieve or exceed...). Could be responsibilities or maybe separate? Could be considered responsibilities as well.
What You'll Bring: experience requirements.
Education And Experience: education.
What We Offer: benefits list.
We need to decide sections.
Option: About the role (overview), Responsibilities (duties), Requirements (experience/skills), Qualifications (education), Benefits.
We could also include Skills separate but maybe combine with Requirements.
Let's craft.
First, About the role: combine Who We Are? Actually Who We Are is about company, not role. But we could still include as part of About the role? Might be odd. However we could create a section "About the company" but not in allowed list. The instruction says use those headings for section headings (e.g. ...). It doesn't forbid other headings, but 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. So we need to map company description maybe under About the role? Could be considered "About the role" includes company context? Might be okay.
Alternatively we could omit Who We Are? But we must preserve ALL substantive information. So we need to include it somewhere. Could put it in a
before any headings? The instruction says 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. It doesn't forbid having a paragraph before headings. So we could have a
for Who We Are, then headings for sections.
Thus we can have:
Who We Are ...
Then About the role
with description of role (What You'll Do, Role paragraph).
Then Responsibilities
with of duties from "In this role you will:" plus maybe performance expectations.
Then Requirements
with of What You'll Bring (experience, skills).
Then Qualifications
with for Education And Experience.
Then
Benefits
with of What We Offer.
We must not include Pay or Schedule.
Check for any filler: none.
Now extract specifics.
Who We Are paragraph:
"MGT is a leading provider of technology and advisory solutions serving state, local, and education government agencies (SLED) across the United States. Through client partnerships, MGT’s almost 1,200 employees impact communities for good by managing and securing critical networks, solving complex human capital and fiscal problems, elevating education systems, and advancing equity as a performance imperative. MGT partners with thousands of agencies as a trusted advisor delivering solutions that improve technology, operational, and economic performance to help communities thrive. Founded in 1975, MGT initiated an ambitious restart in 2016, broadening the solutions portfolio to provide the most specialized solutions, tackling the most mission-critical problems that live at the top of the public agency leadership agenda. MGT drives over 20% compound annual organic growth and utilizes programmatic mergers and acquisitions to grow capabilities, attract top talent, and accelerate growth scale. Since 2020, MGT has successfully completed 13 acquisitions, driving over 60% compound annual inorganic growth. Celebrating its 50th year in 2025, the firm attracts exceptional talent and empowers them to exceed client expectations as they navigate the dynamic demands of the clients we serve."
We could keep as is.
About the role: combine What You'll Do and Role paragraph.
What You'll Do paragraph:
"The Major Account Manager is responsible for driving profitable growth by expanding existing Public Sector SLED customer relationships while developing new business within strategically targeted medium-to-large government and education organizations across an assigned territory of approximately 20–50 accounts. This activity-based sales role focuses on identifying, qualifying, developing, and advancing complex technology opportunities across Networking, Data Center, Cybersecurity, Collaboration, Cloud & Data, Physical Security, AI, Digital Infrastructure, and Managed Services. The Major Account Manager serves as a trusted advisor to customers and collaborates closely with strategic technology partners, manufacturer sales teams, solution architects, and internal cross-functional resources to deliver business outcomes aligned with customer objectives. Success in this role requires strong consultative selling skills, executive relationship development, strategic account planning, and disciplined opportunity management. The Major Account Manager is expected to lead customers through the complete sales lifecycle while consistently achieving revenue, profitability, and customer satisfaction objectives."
Role paragraph:
"This position requires frequent outbound customer engagement, executive meetings, virtual collaboration, local travel throughout the assigned territory, participation in industry events, and close partnership with internal sales, engineering, and manufacturer teams. In this role you will:"
Then bullet list.
We could combine the role paragraph into About the role as well, but we might keep it as part of About the role.
Thus About the role section will have two paragraphs: the What You'll Do and the Role paragraph (maybe combined). We'll output as elements.
Now Responsibilities: bullet list from "In this role you will:" plus maybe performance expectations.
Bullet list items:
- Manage and grow a portfolio of approximately 20–50 medium-to-large Public Sector SLED customer accounts within an assigned territory.
- Develop and execute strategic territory and account plans designed to increase wallet share within existing customers while identifying and penetrating targeted white-space opportunities.
- Generate new business through executive networking, customer referrals, manufacturer partnerships, RFP/RFQ responses, industry events, and proactive prospecting.
- Build trusted advisor relationships with executive leadership, technology leaders, procurement officials, and operational stakeholders.
- Identify, qualify, and lead complex technology opportunities through the entire sales lifecycle.
- Conduct executive business reviews and account planning sessions to identify future initiatives, funding opportunities, and technology refresh cycles.
- Collaborate with Solution Architects, Engineering, Sales Support, Renewals Support, Professional Services, and Managed Services teams to design and deliver comprehensive technology solutions.
- Develop opportunities across MGT's portfolio of Networking, Data Center, Cybersecurity, Collaboration, Cloud, Physical Security, AI, Professional Services, and Managed Services.
- Maintain accurate opportunity management, forecasting, customer activity, and pipeline information within Salesforce CRM.
- Develop and execute joint business plans with strategic technology manufacturers and ecosystem partners.
- Coordinate customer meetings, executive briefings, technology demonstrations, and solution workshops.
- Represent MGT at industry conferences, customer events, trade shows, and professional associations throughout the territory.
Performance Expectations (list of sentences):
- Achieve or exceed assigned revenue, gross profit, and margin objectives.
- Maintain a healthy pipeline capable of supporting quarterly and annual sales goals.
- Consistently achieve sales activity expectations, including executive meetings, prospecting activities, opportunity creation, and account planning.
- Increase revenue within existing customer accounts while acquiring new strategic SLED customers.
- Develop productive relationships with strategic manufacturer account teams and channel partners.
- Deliver accurate sales forecasts and maintain CRM data integrity.
- Demonstrate high levels of customer satisfaction and long-term account retention.
We could include these as part of Responsibilities as well (they are expectations). Could be separate but we can merge.
Thus Responsibilities
with all those items.
Now Requirements: What You'll Bring bullet points:
- Five (5) or more years of successful technology sales experience, preferably within the Public Sector SLED market.
- Demonstrated success selling complex infrastructure, cloud, cybersecurity, networking, or managed services solutions.
- Experience developing executive relationships and navigating complex, multi-stakeholder sales cycles.
- Working knowledge of Public Sector procurement processes, including RFPs, RFQs, cooperative purchasing vehicles, and contract vehicles.
- Experience developing proposals, statements of work (SOWs), executive presentations, and solution pricing.
- Proficiency using Salesforce CRM or equivalent customer relationship management platforms.
We could also include any other skills like consultative selling etc but those are in role description.
Now Qualifications: Education And Experience:
"Bachelor's degree preferred; equivalent professional sales experience will be considered."
We'll output as .
Now Benefits: What We Offer paragraph plus list.
Paragraph: "
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. We need to decide which sections to include based on content. We have: - Who We Are: description of company. Could be "About the company" but not listed as allowed headings? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They gave examples but not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely we should stick to those headings. "Who We Are" could be considered "About the role"? Not exactly. Maybe we can treat it as "About the role"? But that is about the role, not company. However we could still include a section like "About the company" but not in list? The instruction says use those headings for section headings (e.g. ...). It might be okay to use other headings if needed, but they gave examples. Safer to stick to those headings. We can map content:
- About the role: could include description of what you'll do (role overview). Could be "What You'll Do" and "Role". So we can put that under About the role.
- Responsibilities: list of duties (the bullet list under "In this role you will:").
- Requirements: maybe "What You'll Bring" (experience, skills). Could be Requirements.
- Qualifications: maybe Education And Experience.
- Skills: maybe specific skills like Salesforce CRM, etc. Could be separate.
- Benefits: "What We Offer" includes benefits list.
- Pay: Not mentioned explicitly (no salary). So we should NOT create Pay section.
- Schedule: Not mentioned (remote, location). Could be schedule? Not explicit. So we should not create Schedule.
We need to preserve all substantive information. Remove boilerplate like ADA Notice? That's legal but maybe not boilerplate? It's about accommodation; could be considered legal. Might be removed? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. ADA notice is legal; we could remove it. Also remove "MGT Impact Solutions, LLC is an equal opportunity employer..." That's EEO boilerplate; remove.
Also remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
Let's extract content.
Who We Are: paragraph about MGT. Keep.
What You'll Do: paragraphs describing role. Could be under About the role.
Role: paragraph about position requires frequent outbound... Could also be part of About the role or Responsibilities.
Then bullet list under "In this role you will:" with many items. Those are responsibilities.
Performance Expectations: bullet-like sentences (achieve or exceed...). Could be responsibilities or maybe separate? Could be considered responsibilities as well.
What You'll Bring: experience requirements.
Education And Experience: education.
What We Offer: benefits list.
We need to decide sections.
Option: About the role (overview), Responsibilities (duties), Requirements (experience/skills), Qualifications (education), Benefits.
We could also include Skills separate but maybe combine with Requirements.
Let's craft.
First, About the role: combine Who We Are? Actually Who We Are is about company, not role. But we could still include as part of About the role? Might be odd. However we could create a section "About the company" but not in allowed list. The instruction says use those headings for section headings (e.g. ...). It doesn't forbid other headings, but 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. So we need to map company description maybe under About the role? Could be considered "About the role" includes company context? Might be okay.
Alternatively we could omit Who We Are? But we must preserve ALL substantive information. So we need to include it somewhere. Could put it in a
before any headings? The instruction says 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. It doesn't forbid having a paragraph before headings. So we could have a
for Who We Are, then headings for sections. Thus we can have:
Who We Are ...
ThenAbout the role
with description of role (What You'll Do, Role paragraph). ThenResponsibilities
with- of duties from "In this role you will:" plus maybe performance expectations.
Then
Requirements
with- of What You'll Bring (experience, skills).
Then
Qualifications
withfor Education And Experience. Then
Benefits
with- of What We Offer.
We must not include Pay or Schedule.
Check for any filler: none.
Now extract specifics.
Who We Are paragraph:
"MGT is a leading provider of technology and advisory solutions serving state, local, and education government agencies (SLED) across the United States. Through client partnerships, MGT’s almost 1,200 employees impact communities for good by managing and securing critical networks, solving complex human capital and fiscal problems, elevating education systems, and advancing equity as a performance imperative. MGT partners with thousands of agencies as a trusted advisor delivering solutions that improve technology, operational, and economic performance to help communities thrive. Founded in 1975, MGT initiated an ambitious restart in 2016, broadening the solutions portfolio to provide the most specialized solutions, tackling the most mission-critical problems that live at the top of the public agency leadership agenda. MGT drives over 20% compound annual organic growth and utilizes programmatic mergers and acquisitions to grow capabilities, attract top talent, and accelerate growth scale. Since 2020, MGT has successfully completed 13 acquisitions, driving over 60% compound annual inorganic growth. Celebrating its 50th year in 2025, the firm attracts exceptional talent and empowers them to exceed client expectations as they navigate the dynamic demands of the clients we serve."
We could keep as is.
About the role: combine What You'll Do and Role paragraph.
What You'll Do paragraph:
"The Major Account Manager is responsible for driving profitable growth by expanding existing Public Sector SLED customer relationships while developing new business within strategically targeted medium-to-large government and education organizations across an assigned territory of approximately 20–50 accounts. This activity-based sales role focuses on identifying, qualifying, developing, and advancing complex technology opportunities across Networking, Data Center, Cybersecurity, Collaboration, Cloud & Data, Physical Security, AI, Digital Infrastructure, and Managed Services. The Major Account Manager serves as a trusted advisor to customers and collaborates closely with strategic technology partners, manufacturer sales teams, solution architects, and internal cross-functional resources to deliver business outcomes aligned with customer objectives. Success in this role requires strong consultative selling skills, executive relationship development, strategic account planning, and disciplined opportunity management. The Major Account Manager is expected to lead customers through the complete sales lifecycle while consistently achieving revenue, profitability, and customer satisfaction objectives."
Role paragraph:
"This position requires frequent outbound customer engagement, executive meetings, virtual collaboration, local travel throughout the assigned territory, participation in industry events, and close partnership with internal sales, engineering, and manufacturer teams. In this role you will:"
Then bullet list.
We could combine the role paragraph into About the role as well, but we might keep it as part of About the role.
Thus About the role section will have two paragraphs: the What You'll Do and the Role paragraph (maybe combined). We'll output as
elements. Now Responsibilities: bullet list from "In this role you will:" plus maybe performance expectations. Bullet list items: - Manage and grow a portfolio of approximately 20–50 medium-to-large Public Sector SLED customer accounts within an assigned territory. - Develop and execute strategic territory and account plans designed to increase wallet share within existing customers while identifying and penetrating targeted white-space opportunities. - Generate new business through executive networking, customer referrals, manufacturer partnerships, RFP/RFQ responses, industry events, and proactive prospecting. - Build trusted advisor relationships with executive leadership, technology leaders, procurement officials, and operational stakeholders. - Identify, qualify, and lead complex technology opportunities through the entire sales lifecycle. - Conduct executive business reviews and account planning sessions to identify future initiatives, funding opportunities, and technology refresh cycles. - Collaborate with Solution Architects, Engineering, Sales Support, Renewals Support, Professional Services, and Managed Services teams to design and deliver comprehensive technology solutions. - Develop opportunities across MGT's portfolio of Networking, Data Center, Cybersecurity, Collaboration, Cloud, Physical Security, AI, Professional Services, and Managed Services. - Maintain accurate opportunity management, forecasting, customer activity, and pipeline information within Salesforce CRM. - Develop and execute joint business plans with strategic technology manufacturers and ecosystem partners. - Coordinate customer meetings, executive briefings, technology demonstrations, and solution workshops. - Represent MGT at industry conferences, customer events, trade shows, and professional associations throughout the territory. Performance Expectations (list of sentences): - Achieve or exceed assigned revenue, gross profit, and margin objectives. - Maintain a healthy pipeline capable of supporting quarterly and annual sales goals. - Consistently achieve sales activity expectations, including executive meetings, prospecting activities, opportunity creation, and account planning. - Increase revenue within existing customer accounts while acquiring new strategic SLED customers. - Develop productive relationships with strategic manufacturer account teams and channel partners. - Deliver accurate sales forecasts and maintain CRM data integrity. - Demonstrate high levels of customer satisfaction and long-term account retention. We could include these as part of Responsibilities as well (they are expectations). Could be separate but we can merge. Thus Responsibilities
- with all those items.
Now Requirements: What You'll Bring bullet points:
- Five (5) or more years of successful technology sales experience, preferably within the Public Sector SLED market.
- Demonstrated success selling complex infrastructure, cloud, cybersecurity, networking, or managed services solutions.
- Experience developing executive relationships and navigating complex, multi-stakeholder sales cycles.
- Working knowledge of Public Sector procurement processes, including RFPs, RFQs, cooperative purchasing vehicles, and contract vehicles.
- Experience developing proposals, statements of work (SOWs), executive presentations, and solution pricing.
- Proficiency using Salesforce CRM or equivalent customer relationship management platforms.
We could also include any other skills like consultative selling etc but those are in role description.
Now Qualifications: Education And Experience:
"Bachelor's degree preferred; equivalent professional sales experience will be considered."
We'll output as
. Now Benefits: What We Offer paragraph plus list. Paragraph: "