Account Manager, Software Sales
PADT, Inc · Denver, CO · 3 wk ago
On-siteBusiness DevelopmentFull-time
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. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate like EEO etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must not invent.
We need to parse the description.
First paragraph: "Description The Account Manager is primarily responsible for supporting Ansys software sales and expansion activities, from lead generation through opportunity close, into a set of assigned accounts within an assigned geographic territory. Also responsible for maximizing sales profitability, revenue growth and renewal success in their assigned Accounts. Responsibility within an Account could range from supporting established Existing Customers to developing New Account sites. Products and services are sold directly to end-user customers, primarily via face-to-face engagements. The role will require collaboration with internal teammates and with our Ansys Partner team. Expectations for a successful Account Manager would typically include performing the duties and responsibilities outlined below. Work Location: Local Lakewood, Colorado Office."
We can treat that as "About the role" section. It includes description of role, responsibilities overview. Could also include "Work Location" maybe as part of About.
Then "Essential Duties and Responsibilities include the following. Other duties may be assigned." Then list of duties (sentences). We need to put them as
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no summarizing away detail. Remove boilerplate like EEO etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must not invent.
We need to parse the description.
First paragraph: "Description The Account Manager is primarily responsible for supporting Ansys software sales and expansion activities, from lead generation through opportunity close, into a set of assigned accounts within an assigned geographic territory. Also responsible for maximizing sales profitability, revenue growth and renewal success in their assigned Accounts. Responsibility within an Account could range from supporting established Existing Customers to developing New Account sites. Products and services are sold directly to end-user customers, primarily via face-to-face engagements. The role will require collaboration with internal teammates and with our Ansys Partner team. Expectations for a successful Account Manager would typically include performing the duties and responsibilities outlined below. Work Location: Local Lakewood, Colorado Office."
We can treat that as "About the role" section. It includes description of role, responsibilities overview. Could also include "Work Location" maybe as part of About.
Then "Essential Duties and Responsibilities include the following. Other duties may be assigned." Then list of duties (sentences). We need to put them as - items.
Let's extract duties:
- Perform sales activities for new and renewal business in assigned accounts and into an assigned geographic area to achieve or exceed assigned revenue objectives.
- Establish, develop and maintain “win-win” business relationships with current and prospective customers to secure license renewals, generate new software business for PADT and ensure customer satisfaction.
- As a result, account plans for a select group of existing customers will highlight growth opportunities and tactics to be followed up on.
- Execute a regular schedule of contact with customers and prospects via phone, or face-to-face on-site visits in travel throughout assigned territory.
- In collaboration with internal technical resources, identifies customer's problems, key business initiatives and creates clearly communicated ROI-based proposals and quotes aligned to customer initiatives and business outcomes.
- Research and compile lists of prospective customers through sales leads, internet searches, periodicals, business directories, industry ads, trade shows, and other sources.
- Remain knowledgeable and abreast of PADT’s new, and existing products & services to alert customers to improved capabilities, facilitating opportunity generation.
- Coordinate a variety of sales efforts with Sales Management, Accounting, Engineering Services and Marketing teams, to include supporting trade shows and conventions, plus schedule training and seminars to enhance new business opportunities.
- Frequent data updates into the PADT SFDC instance (and Ansys SFDC as required) to maintain sales records, accurately forecast sales revenues (New Business and Renewal) and prepare Territory and Account sales reports as requested.
We need to keep them as bullet points.
Now "Requirements" section: The requirements listed below are representative of the knowledge, skill, and/or ability required. Reasonable accommodation may be made to enable individuals with disabilities to perform the essential functions.
Then subheadings: Education/Experience, Minimum Qualifications, Preferred Qualifications, plus note about export control and EEO.
We need to decide sections: "Requirements" could contain Education/Experience etc. Or we could split into Requirements and Qualifications. The instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- About the role: description paragraph.
- Responsibilities: list of duties.
- Requirements: maybe Education/Experience and Minimum Qualifications? Or we could treat Requirements as the "Education/Experience" bullet.
- Qualifications: Minimum Qualifications and Preferred Qualifications.
- Skills: maybe we can extract skills from qualifications: Proficiency in Microsoft Office Suite, Professional written and oral communication skills, Visual presentation capabilities, organizational skills, ability to work independently and collaboratively, Demonstrated ability to manage and grow customer relationships, Prior success growing company revenue, Demonstrated basic understanding of industrial product development process, CAD, Design Analysis, PLM or Engineering Simulation marketspaces, Demonstrated knowledge of Simulation (Ansys) products/services, and software pricing practices (preferred), track record of successful business transactions at industrial companies (Automotive, Aerospace & Defense, High Tech) (preferred), 2 years of field sales experience (preferred). Also maybe "Military or National Lab experience is welcomed." That could be a qualification.
We need to avoid filler like "commensurate with experience". Not present.
We need to include only sections with real specific content. Benefits, Pay, Schedule: not mentioned in posting. So we should NOT include those headings.
Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
We must not repeat job title. Must not include Job ID etc.
We need to preserve all substantive info: include Work Location, mention of collaboration, etc.
We must remove boilerplate: EEO statements, "PADT, Inc. complies with applicable Federal civil rights laws..." etc. Also remove "Reasonable accommodation may be made..." maybe that's part of Requirements but it's boilerplate? It's a standard statement; but it's not specific to the job; but it's about accommodation. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That includes reasonable accommodation statement? Probably yes, it's legal boilerplate. So we should remove that line.
Also remove "This role requires access to U.S. export-controlled information..." That's not EEO but maybe relevant? It's a specific requirement about citizenship/export control. That is substantive; we should keep it as part of Requirements or Qualifications. It's not boilerplate; it's a specific condition. So keep.
Also remove duplicated lines.
Now craft HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
Education/Experience: Bachelor's degree in an engineering discipline or, bachelor’s degree with technical sales experience. Minimum of 1 year software license and/ or renewal sales experience with a proven track record of success. Military or National Lab experience is welcomed.
This role requires access to U.S. export-controlled information. Therefore, for applicants who are not asylees, refugees, lawful permanent residents or U.S. Citizens (i.e., not a protected individual under the Immigration and Naturalization Act, 8 U.S.C. 1324b(a)(3), otherwise known as a U.S. Person), final offers will be contingent on the ability to obtain authorization for access to U.S. export-controlled information from the U.S. Government.
Maybe also include note about reasonable accommodation removed.
Qualifications
- Demonstrated basic understanding of the industrial product development process, CAD, Design Analysis, PLM or Engineering Simulation marketspaces.
- Proficiency in Microsoft Office Suite.
- Professional written and oral communication skills.
- Visual presentation capabilities (including for executive level), organizational skills and the ability to work independently and collaboratively.
- Demonstrated ability to manage and grow customer relationships.
- Prior success growing company revenue.
Then Preferred Qualifications maybe as part of Qualifications? Could add another Preferred Qualifications
but we only have allowed headings list includes Qualifications (not Preferred). Could embed preferred within Qualifications as separate list with heading? But instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add Preferred Qualifications as separate heading unless we treat it as part of Qualifications. Could still include a but not allowed. Better to incorporate preferred qualifications into Qualifications section as bullet points with label "Preferred:" maybe.
Alternatively we could create a Skills section for skills like Microsoft Office, communication, presentation, organizational, etc. But we already have those in Qualifications. Could split: Qualifications for minimum qualifications, Skills for skills like Microsoft Office, communication, presentation, organizational, ability to work independently, manage relationships, revenue growth. Preferred qualifications could go under Skills? Hmm.
Better to follow the allowed headings strictly: About the role, Responsibilities, Requirements, Qualifications, Skills. So we need to map content to these.
Let's decide:
- About the role: description paragraph.
- Responsibilities: duties list.
- Requirements: Education/Experience and export control note.
- Qualifications: Minimum Qualifications (list) plus maybe Preferred Qualifications (list) but we can label them as "Preferred" within same section.
- Skills: maybe we can extract specific skill items like "Proficiency in Microsoft Office Suite", "Professional written and oral communication skills", "Visual presentation capabilities", "Organizational skills", "Ability to work independently and collaboratively", "Demonstrated ability to manage and grow customer relationships", "Prior success growing company revenue". However those are also qualifications. But we can shift some to Skills.
We need to avoid duplication. Let's think: Minimum Qualifications list includes: Demonstrated basic understanding of industrial product development process, CAD, Design Analysis, PLM or Engineering Simulation marketspaces. Proficiency in Microsoft Office Suite. Professional written and oral communication skills. Visual presentation capabilities (including for executive level), organizational skills and the ability to work independently and collaboratively. Demonstrated ability to manage and grow customer relationships. Prior success growing company revenue.
Preferred Qualifications: Demonstrated knowledge of Simulation (Ansys) products/services, and software pricing practices is considered a plus. A track record of successful business transactions at industrial companies (Automotive, Aerospace & Defense, and High Tech) is welcomed. 2 years of field sales experience is preferable.
Military or National Lab experience is welcomed (already in Requirements/Education/Experience).
Thus we could put Minimum Qualifications under Qualifications, and Preferred Qualifications also under Qualifications but maybe as a sub-list with label "Preferred". Or we could put Preferred under Skills? But Skills heading is for skills like Microsoft Office, communication, etc. However those are already in Minimum Qualifications.
Maybe better: Qualifications = Minimum Qualifications + Preferred Qualifications (both). Skills = maybe we can extract "Proficiency in Microsoft Office Suite", "Professional written and oral communication skills", "Visual presentation capabilities", "Organizational skills", "Ability to work independently and collaboratively", "Demonstrated ability to manage and grow customer relationships", "Prior success growing company revenue". But that duplicates.
Alternatively we could treat Skills as the specific technical skills: "Proficiency in Microsoft Office Suite", "Professional written and oral communication skills", "Visual presentation capabilities", "Organizational skills", "Ability to work independently and collaboratively". And Qualifications as the experience/knowledge requirements: education, experience, understanding of product development process, ability to manage relationships, prior success growing revenue, etc. Preferred qualifications could be added to Skills or Qualifications.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine Qualifications and Skills into one section? But we must use headings only when there is real specific content. We could have About the role, Responsibilities, Requirements, Qualifications (which includes both minimum and preferred qualifications and skills). That would be 4 sections. That seems acceptable.
Thus we will output:
About the role
... (including work location)
Responsibilities
...
Requirements
Education/Experience: Bachelor's degree in an engineering discipline or, bachelor’s degree with technical sales experience. Minimum of 1 year software license and/ or renewal sales experience with a proven track record of success. Military or National Lab experience is welcomed.
This role requires access to U.S. export-controlled information. Therefore, for applicants who are not asylees, refugees, lawful permanent residents or U.S. Citizens (i.e., not a protected
About the role
...
Responsibilities
- ... ...
Requirements
Education/Experience: Bachelor's degree in an engineering discipline or, bachelor’s degree with technical sales experience. Minimum of 1 year software license and/ or renewal sales experience with a proven track record of success. Military or National Lab experience is welcomed.
This role requires access to U.S. export-controlled information. Therefore, for applicants who are not asylees, refugees, lawful permanent residents or U.S. Citizens (i.e., not a protected individual under the Immigration and Naturalization Act, 8 U.S.C. 1324b(a)(3), otherwise known as a U.S. Person), final offers will be contingent on the ability to obtain authorization for access to U.S. export-controlled information from the U.S. Government.
Maybe also include note about reasonable accommodation removed.Qualifications
- Demonstrated basic understanding of the industrial product development process, CAD, Design Analysis, PLM or Engineering Simulation marketspaces.
- Proficiency in Microsoft Office Suite.
- Professional written and oral communication skills.
- Visual presentation capabilities (including for executive level), organizational skills and the ability to work independently and collaboratively.
- Demonstrated ability to manage and grow customer relationships.
- Prior success growing company revenue.
Preferred Qualifications
but we only have allowed headings list includes Qualifications (not Preferred). Could embed preferred within Qualifications as separate list with heading? But instruction says use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add Preferred Qualifications as separate heading unless we treat it as part of Qualifications. Could still include a but not allowed. Better to incorporate preferred qualifications into Qualifications section as bullet points with label "Preferred:" maybe.
Alternatively we could create a Skills section for skills like Microsoft Office, communication, presentation, organizational, etc. But we already have those in Qualifications. Could split: Qualifications for minimum qualifications, Skills for skills like Microsoft Office, communication, presentation, organizational, ability to work independently, manage relationships, revenue growth. Preferred qualifications could go under Skills? Hmm.
Better to follow the allowed headings strictly: About the role, Responsibilities, Requirements, Qualifications, Skills. So we need to map content to these.
Let's decide:
- About the role: description paragraph.
- Responsibilities: duties list.
- Requirements: Education/Experience and export control note.
- Qualifications: Minimum Qualifications (list) plus maybe Preferred Qualifications (list) but we can label them as "Preferred" within same section.
- Skills: maybe we can extract specific skill items like "Proficiency in Microsoft Office Suite", "Professional written and oral communication skills", "Visual presentation capabilities", "Organizational skills", "Ability to work independently and collaboratively", "Demonstrated ability to manage and grow customer relationships", "Prior success growing company revenue". However those are also qualifications. But we can shift some to Skills.
We need to avoid duplication. Let's think: Minimum Qualifications list includes: Demonstrated basic understanding of industrial product development process, CAD, Design Analysis, PLM or Engineering Simulation marketspaces. Proficiency in Microsoft Office Suite. Professional written and oral communication skills. Visual presentation capabilities (including for executive level), organizational skills and the ability to work independently and collaboratively. Demonstrated ability to manage and grow customer relationships. Prior success growing company revenue.
Preferred Qualifications: Demonstrated knowledge of Simulation (Ansys) products/services, and software pricing practices is considered a plus. A track record of successful business transactions at industrial companies (Automotive, Aerospace & Defense, and High Tech) is welcomed. 2 years of field sales experience is preferable.
Military or National Lab experience is welcomed (already in Requirements/Education/Experience).
Thus we could put Minimum Qualifications under Qualifications, and Preferred Qualifications also under Qualifications but maybe as a sub-list with label "Preferred". Or we could put Preferred under Skills? But Skills heading is for skills like Microsoft Office, communication, etc. However those are already in Minimum Qualifications.
Maybe better: Qualifications = Minimum Qualifications + Preferred Qualifications (both). Skills = maybe we can extract "Proficiency in Microsoft Office Suite", "Professional written and oral communication skills", "Visual presentation capabilities", "Organizational skills", "Ability to work independently and collaboratively", "Demonstrated ability to manage and grow customer relationships", "Prior success growing company revenue". But that duplicates.
Alternatively we could treat Skills as the specific technical skills: "Proficiency in Microsoft Office Suite", "Professional written and oral communication skills", "Visual presentation capabilities", "Organizational skills", "Ability to work independently and collaboratively". And Qualifications as the experience/knowledge requirements: education, experience, understanding of product development process, ability to manage relationships, prior success growing revenue, etc. Preferred qualifications could be added to Skills or Qualifications.
Given the instruction to prefer a few substantive sections over many thin ones, we could combine Qualifications and Skills into one section? But we must use headings only when there is real specific content. We could have About the role, Responsibilities, Requirements, Qualifications (which includes both minimum and preferred qualifications and skills). That would be 4 sections. That seems acceptable.
Thus we will output:
About the role
... (including work location)
Responsibilities
- ...
Requirements
Education/Experience: Bachelor's degree in an engineering discipline or, bachelor’s degree with technical sales experience. Minimum of 1 year software license and/ or renewal sales experience with a proven track record of success. Military or National Lab experience is welcomed.
This role requires access to U.S. export-controlled information. Therefore, for applicants who are not asylees, refugees, lawful permanent residents or U.S. Citizens (i.e., not a protected