Account Manager, Software Sales
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have description (About the role) content: first paragraph describing role. Then responsibilities list (Essential Duties and Responsibilities). Then Requirements (Education/Experience etc). Then Minimum Qualifications, Preferred Qualifications. Also note about export control etc. That's part of requirements? Could be under Requirements or Qualifications. We'll treat Minimum Qualifications and Preferred Qualifications as sub-sections under Qualifications? But we have only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can put Qualifications heading and include both Minimum and Preferred under it. Skills maybe separate? Could include skills under Qualifications or separate Skills heading if we have skill details. The posting mentions proficiency in Microsoft Office Suite, professional written and oral communication, visual presentation capabilities, organizational skills, ability to work independently and collaboratively, demonstrated ability to manage and grow customer relationships, prior success growing company revenue. Those could go under Skills. We'll create Skills section. We have no explicit Benefits, Pay, Schedule info. So we omit those sections. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO etc. Remove lines about PADT complies etc. Also remove "Reasonable accommodations may be made..." maybe keep? It's part of Requirements but it's generic; but it's substantive? It's a statement about accommodations; could keep but it's not specific detail. Might be considered boilerplate but it's part of requirements. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The accommodations line is not EEO but it's a standard statement; might be considered legal boilerplate. Safer to remove it. Also remove "Other duties may be assigned." maybe keep? It's generic; could be considered boilerplate. Might remove. We need to preserve all substantive information. So we keep the core duties, requirements, qualifications. Let's extract: About the role: 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: Remote Home Office. We can put that as
under About the role. Responsibilities: list of duties. Let's list bullet points: - 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 could combine some sentences but keep as list. 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 experience is welcomed. We could also include "Minimum Qualifications" and "Preferred Qualifications" under Qualifications heading. Qualifications: Minimum 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: Demonstrated knowledge of Simulation (Ansys) products/services, and software pricing practices is considered a plus. 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. 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. We could also include Skills section: maybe list skills like Microsoft Office proficiency, communication, presentation, organizational, relationship management, revenue growth. But we already have many skills in Qualifications. Could still create Skills section summarizing: Proficiency in Microsoft Office Suite, professional written and oral communication, visual presentation capabilities, organizational skills, ability to work independently and collaboratively, ability to manage and grow customer relationships, prior success growing company revenue. We must avoid duplication. Might be okay to have Skills separate. We must not create sections with filler. We have content for About the role, Responsibilities, Requirements, Qualifications, Skills. Benefits, Pay, Schedule omitted. Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
...
Qualifications
Minimum Qualifications
?? But we only allowed h3 for section headings. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings inside? It says use for section headings. Could we use for subheadings? Might be okay but safer to keep only h3 sections. We could embed Minimum and Preferred as paragraphs within Qualifications. Or we could make separate sections: Minimum Qualifications and Preferred Qualifications as h3? But they are not in the list; but we could still use h3 for them? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed section headings; we should not create other headings like Minimum Qualifications. So we should keep Qualifications as a single section and include both minimum and preferred content inside, perhaps separated by
for subheadings? Might be okay but safer to keep only h3 sections. We could embed Minimum and Preferred as paragraphs within Qualifications. Or we could make separate sections: Minimum Qualifications and Preferred Qualifications as h3? But they are not in the list; but we could still use h3 for them? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are the allowed section headings; we should not create other headings like Minimum Qualifications. So we should keep Qualifications as a single section and include both minimum and preferred content inside, perhaps separated by
or . We'll do that.
Similarly Skills could be its own section.
Thus:
Minimum 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: Demonstrated knowledge of Simulation (Ansys) products/services, and software pricing practices is considered a plus. 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. 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. Bachelor's degree in an engineering discipline, or a 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 experience is welcomed.Qualifications
Skills
Now Requirements section: include Education/Experience and maybe Military experience.
Requirements