Account Executive (Central)
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.
Thus we need to decide which sections to include based on content.
We have:
- About Kinaxis (company description) – could be "About the role"? Actually "About the role" is a heading we can use for description of role? The posting includes "About The Team" and "What you will do" (responsibilities), "What we are looking for" (requirements/qualifications/skills). Also there is "Work With Impact", "Social Responsibility", "People matter at Kinaxis and here are some of the perks and benefits we offer". Also location: "Location This is a remote position. You can work from home and be located in Texas, USA." That could be a short paragraph maybe under a heading? Not required but we could include as a
maybe under a heading "Location"? But the allowed headings list includes only certain ones: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However the instruction says: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning these are examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings where appropriate. But we can also use other 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 suggests using those for typical sections. However they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to map content to these headings.
We have:
- About the role: could be a brief description of the role (maybe from "About The Team" and "What you will do"? Actually "About The Team" describes the role of Account Executive. So we could put that under About the role.
- Responsibilities: "What you will do" list.
- Requirements/Qualifications/Skills: "What we are looking for" list (includes experience, qualifications, skills). Could split into Requirements and Qualifications and Skills but we can combine? The instruction says prefer a few substantive sections over many thin ones. So maybe we just have one section for Requirements (or Qualifications) that includes all. But we need to use headings from list; we could use Requirements
and include the list.
- Benefits: there is a section about perks and benefits: "People matter at Kinaxis and here are some of the perks and benefits we offer, which may vary by location and employee: Flexible vacation and Kinaxis Days (company-wide days off) Flexible work options Physical and mental well-being programs Regularly scheduled virtual fitness classes Mentorship programs, training, and career development Recognition programs and referral rewards Hackathons". That's specific benefits. So we can include a Benefits section.
- Pay: not mentioned. So we should not include Pay.
- Schedule: not mentioned (though remote, flexible work options). But schedule not explicitly stated. So we should not include Schedule.
- Location: not in the list but we could include as a
maybe under About the role? Or we could just include a short paragraph before sections. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a short
before sections.
Thus final HTML: maybe:
Location: This is a remote position. You can work from home and be located in Texas, USA.
About the role
The role of Account Executive will be responsible for winning new business and revenue with net new accounts, working with Kinaxis senior management to contribute to the overall growth strategy of Kinaxis. In return Kinaxis can offer an excellent environment to work where you will be a valued person and given all the associated benefits of an organization geared for growth and success.
Responsibilities
- Leads efforts for identifying opportunities and growing revenue in new name accounts.
- Working with Kinaxis senior management to develop the relevant account strategies and engagements to drive pipeline growth and close deals within agreed timelines.
- Establishing and maintaining high-level, executive relationships with New Name Accounts and our existing customers, focusing on the establishment and maintenance of strategic relationships (direct and reseller).
- Qualifying prospects according to Kinaxis’ capabilities and applicability.
- Providing accurate sales forecasts and relevant reporting based upon realistic close timelines.
- Communicating product improvements and recommendations that originate in the field.
Requirements
- 8+ years’ experience in selling strategic, enterprise level mission critical solutions (SCM, ERP, BI)
- Highly credible and able to demonstrate understanding of the relevant client operations and strategies and linking them to the relevant solutions and high value propositions that go beyond just technology
- Team player who is able to work and help ensure delivery of client sales propositions
- Sales experience in High Tech Electronics, Industrial, Pharmaceutical, Automotive and similar manufacturing oriented industries with the ability to ultimately lead the sales for a particular industry vertical
- Degree qualified with industry and SCM/SCP experience preferred
- Highly motivated who has achieved or exceeded consulting or sales quotas in new or emerging markets with leading and of “Best of Breed” technologies.
- Experience working in different North American markets, geographies in complex deals
- Ability to effectively and strategically engage with executive level decision makers, and develop joint strategies for growth
- Ability to sell to multiple constituencies within an organization (Manufacturing Operations, Demand Management, Finance, IT)
- Consultative, value-proposition/business case driven sales methodology experience.
- Must be an articulate, persuasive and passionate communicator with excellent presentation skills
- Ability to work and act independently and be pro-active
- Ability to travel as required
Benefits
- Flexible vacation and Kinaxis Days (company-wide days off)
- Flexible work options
- Physical and mental well-being programs
- Regularly scheduled virtual fitness classes
- Mentorship programs, training, and career development
- Recognition programs and referral rewards
- Hackathons
We should also maybe include a brief About Kinaxis description? The instruction says "Preserve ALL substantive information". The About Kinaxis paragraph at start is substantive. Should we include it? It could be placed under About the role? Or maybe a separate section like "About the company"? But not in allowed headings. Could we include it as a before About the role? The instruction says we can include short
for metadata. But About Kinaxis is not metadata; it's substantive. Perhaps we should include it as a paragraph under About the role? But About the role heading is for role description, not company. However we could treat About the role as including both company and role? The example headings list includes About the role, which could be used for role description. The company description could be placed before any heading as a
. 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 other paragraphs. So we can include a
with the company description.
Thus we will have:
About Kinaxis: At Kinaxis we are serious about culture, we are serious about technology, we are serious about customers, and we are serious about not taking ourselves too seriously. If you are looking to be part of an incredible growth story, then we might just be the place for you! In 1984, we started out as a team of three engineers. Today, we have grown to become a global organization with over 2000 employees around the world, 6 global office and a best-in-class HQ in Ottawa, Canada. As winners of several Top Employer awards globally, we are proud to work with our customers and employees towards solving some of the biggest challenges facing supply chains today. Kinaxis is a global leader in modern supply chain orchestration, powering complex global supply chains, and supporting the people who manage them. Our powerful, AI infused platform provides full transparency and visibility across end-to-end supply chains, enabling our customers to make faster, better decisions. We are trusted by renowned global brands to provide the agility and predictability needed to navigate today’s volatility and disruption. With more than 40,000 users in over 100 countries, we are expanding our team as we continue to innovate and revolutionize how we support our customers.
Then location paragraph, then About the role paragraph, etc.
We must ensure we don't include boilerplate like EEO, accommodation request, AI tools, etc. Those are at the end: "Kinaxis welcomes candidates to apply to our inclusive community. We provide accommodations upon request..." etc. That's boilerplate/legal/EEO. Must remove.
Also remove duplicated lines, navigation, cookie, etc. The posting includes "Work With Impact: Our platform directly helps companies power the world’s supply chains..." and "Social Responsibility at Kinaxis:" and "People matter at Kinaxis and here are some of the perks and benefits we offer". We already captured benefits. The "Work With Impact" and "Social Responsibility" are substantive but not covered by headings. Could we include them as separate sections? The instruction says prefer a few substantive sections over many thin ones. But we could incorporate them into Benefits or About the role? However they are distinct: Work With Impact describes impact of platform; Social Responsibility describes DEI, sustainability, community involvement. These are substantive and not covered elsewhere. Should we include them? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we could add sections for "Impact" and "Social Respons
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. Thus we need to decide which sections to include based on content. We have: - About Kinaxis (company description) – could be "About the role"? Actually "About the role" is a heading we can use for description of role? The posting includes "About The Team" and "What you will do" (responsibilities), "What we are looking for" (requirements/qualifications/skills). Also there is "Work With Impact", "Social Responsibility", "People matter at Kinaxis and here are some of the perks and benefits we offer". Also location: "Location This is a remote position. You can work from home and be located in Texas, USA." That could be a short paragraph maybe under a heading? Not required but we could include as a
maybe under a heading "Location"? But the allowed headings list includes only certain ones: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However the instruction says: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning these are examples, not exclusive? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect we use those headings where appropriate. But we can also use other 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 suggests using those for typical sections. However they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to map content to these headings.
We have:
- About the role: could be a brief description of the role (maybe from "About The Team" and "What you will do"? Actually "About The Team" describes the role of Account Executive. So we could put that under About the role.
- Responsibilities: "What you will do" list.
- Requirements/Qualifications/Skills: "What we are looking for" list (includes experience, qualifications, skills). Could split into Requirements and Qualifications and Skills but we can combine? The instruction says prefer a few substantive sections over many thin ones. So maybe we just have one section for Requirements (or Qualifications) that includes all. But we need to use headings from list; we could use Requirements
and include the list.
- Benefits: there is a section about perks and benefits: "People matter at Kinaxis and here are some of the perks and benefits we offer, which may vary by location and employee: Flexible vacation and Kinaxis Days (company-wide days off) Flexible work options Physical and mental well-being programs Regularly scheduled virtual fitness classes Mentorship programs, training, and career development Recognition programs and referral rewards Hackathons". That's specific benefits. So we can include a Benefits section.
- Pay: not mentioned. So we should not include Pay.
- Schedule: not mentioned (though remote, flexible work options). But schedule not explicitly stated. So we should not include Schedule.
- Location: not in the list but we could include as a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for typical sections. However they also say "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to map content to these headings.
We have:
- About the role: could be a brief description of the role (maybe from "About The Team" and "What you will do"? Actually "About The Team" describes the role of Account Executive. So we could put that under About the role.
- Responsibilities: "What you will do" list.
- Requirements/Qualifications/Skills: "What we are looking for" list (includes experience, qualifications, skills). Could split into Requirements and Qualifications and Skills but we can combine? The instruction says prefer a few substantive sections over many thin ones. So maybe we just have one section for Requirements (or Qualifications) that includes all. But we need to use headings from list; we could use Requirements
and include the list.
- Benefits: there is a section about perks and benefits: "People matter at Kinaxis and here are some of the perks and benefits we offer, which may vary by location and employee: Flexible vacation and Kinaxis Days (company-wide days off) Flexible work options Physical and mental well-being programs Regularly scheduled virtual fitness classes Mentorship programs, training, and career development Recognition programs and referral rewards Hackathons". That's specific benefits. So we can include a Benefits section.
- Pay: not mentioned. So we should not include Pay.
- Schedule: not mentioned (though remote, flexible work options). But schedule not explicitly stated. So we should not include Schedule.
- Location: not in the list but we could include as a
maybe under About the role? Or we could just include a short paragraph before sections. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata; we could include a short
before sections. Thus final HTML: maybe:
Location: This is a remote position. You can work from home and be located in Texas, USA.
About the role
The role of Account Executive will be responsible for winning new business and revenue with net new accounts, working with Kinaxis senior management to contribute to the overall growth strategy of Kinaxis. In return Kinaxis can offer an excellent environment to work where you will be a valued person and given all the associated benefits of an organization geared for growth and success.
Responsibilities
- Leads efforts for identifying opportunities and growing revenue in new name accounts.
- Working with Kinaxis senior management to develop the relevant account strategies and engagements to drive pipeline growth and close deals within agreed timelines.
- Establishing and maintaining high-level, executive relationships with New Name Accounts and our existing customers, focusing on the establishment and maintenance of strategic relationships (direct and reseller).
- Qualifying prospects according to Kinaxis’ capabilities and applicability.
- Providing accurate sales forecasts and relevant reporting based upon realistic close timelines.
- Communicating product improvements and recommendations that originate in the field.
Requirements
- 8+ years’ experience in selling strategic, enterprise level mission critical solutions (SCM, ERP, BI)
- Highly credible and able to demonstrate understanding of the relevant client operations and strategies and linking them to the relevant solutions and high value propositions that go beyond just technology
- Team player who is able to work and help ensure delivery of client sales propositions
- Sales experience in High Tech Electronics, Industrial, Pharmaceutical, Automotive and similar manufacturing oriented industries with the ability to ultimately lead the sales for a particular industry vertical
- Degree qualified with industry and SCM/SCP experience preferred
- Highly motivated who has achieved or exceeded consulting or sales quotas in new or emerging markets with leading and of “Best of Breed” technologies.
- Experience working in different North American markets, geographies in complex deals
- Ability to effectively and strategically engage with executive level decision makers, and develop joint strategies for growth
- Ability to sell to multiple constituencies within an organization (Manufacturing Operations, Demand Management, Finance, IT)
- Consultative, value-proposition/business case driven sales methodology experience.
- Must be an articulate, persuasive and passionate communicator with excellent presentation skills
- Ability to work and act independently and be pro-active
- Ability to travel as required
Benefits
- Flexible vacation and Kinaxis Days (company-wide days off)
- Flexible work options
- Physical and mental well-being programs
- Regularly scheduled virtual fitness classes
- Mentorship programs, training, and career development
- Recognition programs and referral rewards
- Hackathons
before About the role? The instruction says we can include short
for metadata. But About Kinaxis is not metadata; it's substantive. Perhaps we should include it as a paragraph under About the role? But About the role heading is for role description, not company. However we could treat About the role as including both company and role? The example headings list includes About the role, which could be used for role description. The company description could be placed before any heading as a
. 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 other paragraphs. So we can include a
with the company description. Thus we will have:
About Kinaxis: At Kinaxis we are serious about culture, we are serious about technology, we are serious about customers, and we are serious about not taking ourselves too seriously. If you are looking to be part of an incredible growth story, then we might just be the place for you! In 1984, we started out as a team of three engineers. Today, we have grown to become a global organization with over 2000 employees around the world, 6 global office and a best-in-class HQ in Ottawa, Canada. As winners of several Top Employer awards globally, we are proud to work with our customers and employees towards solving some of the biggest challenges facing supply chains today. Kinaxis is a global leader in modern supply chain orchestration, powering complex global supply chains, and supporting the people who manage them. Our powerful, AI infused platform provides full transparency and visibility across end-to-end supply chains, enabling our customers to make faster, better decisions. We are trusted by renowned global brands to provide the agility and predictability needed to navigate today’s volatility and disruption. With more than 40,000 users in over 100 countries, we are expanding our team as we continue to innovate and revolutionize how we support our customers.
Then location paragraph, then About the role paragraph, etc. We must ensure we don't include boilerplate like EEO, accommodation request, AI tools, etc. Those are at the end: "Kinaxis welcomes candidates to apply to our inclusive community. We provide accommodations upon request..." etc. That's boilerplate/legal/EEO. Must remove. Also remove duplicated lines, navigation, cookie, etc. The posting includes "Work With Impact: Our platform directly helps companies power the world’s supply chains..." and "Social Responsibility at Kinaxis:" and "People matter at Kinaxis and here are some of the perks and benefits we offer". We already captured benefits. The "Work With Impact" and "Social Responsibility" are substantive but not covered by headings. Could we include them as separate sections? The instruction says prefer a few substantive sections over many thin ones. But we could incorporate them into Benefits or About the role? However they are distinct: Work With Impact describes impact of platform; Social Responsibility describes DEI, sustainability, community involvement. These are substantive and not covered elsewhere. Should we include them? The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we could add sections for "Impact" and "Social Respons