AFS Application Specialist
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can combine similar items. Perhaps we have:
- About the role (intro + role description)
- Responsibilities (list of duties)
- Requirements (knowledge, skills, education, experience, language, math, reasoning, computer, other qualifications)
- Benefits
- Pay
We could also separate Qualifications and Skills but we can combine into Requirements.
We must not create headings with filler text. Ensure each heading has substantive content.
We need to use - for any list of duties/requirements/benefits. For prose, use
.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to remove boilerplate: EEO, accommodation, etc. Also remove "Job Family: Sales Business Unit: Hale" maybe we can keep as short p? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short p for Job Family and Business Unit.
We also need to remove duplicated lines.
Let's extract substantive content.
Intro paragraph(s):
1. "If you’re looking for a special place to build or grow your career, you’ve found it. Whether you’re an experienced professional, a recent college graduate or somewhere in between, IDEX is a place where you can apply your existing skills and learn new ones in an environment where you can make an impact. With interesting opportunities in engineering, marketing, sales, supply chain, operations, HR, finance, and more across more than 40 diverse businesses (https://www.idexcorp.com/our-businesses/business-segments/) around the globe, chances are, we have something special for you."
2. "This role assists customers with Advanced Flow Solutions (AFS) product applications and provide technical and field support for AFS systems. Report field issues and findings to production and engineering."
We can combine into About the role.
Responsibilities list:
- Provide IDEX AFS training for customers at all levels of the organization.
- Install, functional test and report on IDEX Fire and Safety AFS products.
- Help craft training curriculum and content.
- Assist in the development of OEM and End user specifications.
- Assist in collecting and reporting VOC data.
- Perform sales and customer service duties both on and off site
- Assist the IDEX commercial team as the subject matter expert for IDEX AFS systems.
- Identify product line gaps and communicate them to product management and engineering.
- Design Wiring Harness As Required.
- Assist engineering with practical application testing of new product.
- Assist OEM customers and dealers with education of end users by attending preconstruction meetings as required.
- All Other Duties As Assigned.
We need to keep each as
- .
Knowledge, Skills and Required Abilities:
List:
- Knowledgeable of vehicle electrical systems both on and off highway.
- Knowledgeable of vehicle multiplexing systems (Class1 ES-Key or Weldon V-MUX systems are a plus).
- Knowledgeable of engine systems and controls.
- Knowledgeable of Hydraulic systems and controls.
- A detailed understanding of apparatus pumping systems.
- Must be able to work and communicate with all levels of a customer’s organization.
Education And Experience:
- Associate's degree or a minimum of 5 years related experience and training; or equivalent combination of education and experience.
Language Skills:
- Ability to read, analyze and interpret general business periodicals, professional journals, technical procedures, or governmental regulations.
- Ability to write reports, business correspondence, and procedure manuals.
- Ability to effectively present information and to respond to questions from groups of managers, clients, customers and the general public.
Mathematical Skills:
- Ability to calculate figures and amounts such as discounts, interest, commissions, proportions, percentages, area, circumference, and volume.
- Ability to apply concepts of basic algebra and geometry.
REASONING ABILITY:
- Ability to define problems collects data, establish facts, and draw valid conclusions.
- Ability to interpret an extensive variety of technical instructions in mathematical or diagram form and deal with several abstract and concrete variables.
Computer Skills:
- Proficient with MS Office products
- MRP Systems Experience (JD Edwards Experience Is a Plus)
- CRM system experience (Sales Force is a plus)
Other Qualifications:
- Demonstrated problem solving and negotiation skills
- Excellent Oral And Written Communication Skills
- Advanced technical knowledge across all IDEX Fire and Safety product lines
- Hands-on knowledge of fire truck manufacturing and plumbing techniques
- Excellent formal presentation skills before both small and large groups
- The ability to travel on short notice at a rate of 50%+.
Physical Demands: we could include as a section? Not in allowed headings list but we could maybe put under Requirements? But it's not a typical heading. The instruction: "Prefer a few substantive sections over many thin ones." We could include Physical Demands and Work Environment as part of Requirements or maybe as a separate section like "Working Conditions". But not in the list of allowed headings. The allowed headings are examples; we can use others? It says: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are typical 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; we can omit Physical Demands and Work Environment if not covered. But we must preserve ALL substantive information; we cannot drop it. However we could fold them into a section like "Requirements" or "Working Conditions" but not in the list. The instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid other headings, but the examples given are typical. I think we can include a section like "Working Conditions" if we have content. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be interpreted that we should use those headings only; but it's not explicit that we cannot use others. Safer to include them under a heading like "Requirements" or maybe "Working Conditions" as a subsection? But we need to output only HTML fragment; we can include a for "Working Conditions" and include Physical Demands and Work Environment there. That seems reasonable.
But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Physical Demands and Work Environment into one section "Working Conditions". That's substantive.
Thus sections: About the role, Responsibilities, Requirements, Working Conditions, Benefits, Pay.
We also have metadata Job Family: Sales Business Unit: Hale. Could be a short p after Pay or before.
We must not repeat job title as heading.
Now construct HTML.
We'll start with About the role
then
containing intro paragraphs combined.
Then
Responsibilities
then - ... each duty.
Then
Requirements
then we need to include knowledge, skills, education, language, math, reasoning, computer, other qualifications. Could be a with all items. But that would be huge list; still okay. However we might want to group but instruction says use - for any list of duties/requirements/benefits. So we can make one big list.
But we need to preserve all detail; we can just list each bullet as
- .
Let's compile all requirement bullets:
Knowledge:
- Knowledgeable of vehicle electrical systems both on and off highway.
- Knowledgeable of vehicle multiplexing systems (Class1 ES-Key or Weldon V-MUX systems are a plus).
- Knowledgeable of engine systems and controls.
- Knowledgeable of Hydraulic systems and controls.
- A detailed understanding of apparatus pumping systems.
- Must be able to work and communicate with all levels of a customer’s organization.
Education:
- Associate's degree or a minimum of 5 years related experience and training; or equivalent combination of education and experience.
Language Skills:
- Ability to read, analyze and interpret general business periodicals, professional journals, technical procedures, or governmental regulations.
- Ability to write reports, business correspondence, and procedure manuals.
- Ability to effectively present information and to respond to questions from groups of managers, clients, customers and the general public.
Mathematical Skills:
- Ability to calculate figures and amounts such as discounts, interest, commissions, proportions, percentages, area, circumference, and volume.
- Ability to apply concepts of basic algebra and geometry.
Reasoning Ability:
- Ability to define problems collects data, establish facts, and draw valid conclusions.
- Ability to interpret an extensive variety of technical instructions in mathematical or diagram form and deal with several abstract and concrete variables.
Computer Skills:
- Proficient with MS Office products
- MRP Systems Experience (JD Edwards Experience Is a Plus)
- CRM system experience (Sales Force is a plus)
Other Qualifications:
- Demonstrated problem solving and negotiation skills
- Excellent Oral And Written Communication Skills
- Advanced technical knowledge across all
. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: EEO, accommodation, etc. Also remove "Job Family: Sales Business Unit: Hale" maybe we can keep as short p? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short p for Job Family and Business Unit. We also need to remove duplicated lines. Let's extract substantive content. Intro paragraph(s): 1. "If you’re looking for a special place to build or grow your career, you’ve found it. Whether you’re an experienced professional, a recent college graduate or somewhere in between, IDEX is a place where you can apply your existing skills and learn new ones in an environment where you can make an impact. With interesting opportunities in engineering, marketing, sales, supply chain, operations, HR, finance, and more across more than 40 diverse businesses (https://www.idexcorp.com/our-businesses/business-segments/) around the globe, chances are, we have something special for you." 2. "This role assists customers with Advanced Flow Solutions (AFS) product applications and provide technical and field support for AFS systems. Report field issues and findings to production and engineering." We can combine into About the role. Responsibilities list: - Provide IDEX AFS training for customers at all levels of the organization. - Install, functional test and report on IDEX Fire and Safety AFS products. - Help craft training curriculum and content. - Assist in the development of OEM and End user specifications. - Assist in collecting and reporting VOC data. - Perform sales and customer service duties both on and off site - Assist the IDEX commercial team as the subject matter expert for IDEX AFS systems. - Identify product line gaps and communicate them to product management and engineering. - Design Wiring Harness As Required. - Assist engineering with practical application testing of new product. - Assist OEM customers and dealers with education of end users by attending preconstruction meetings as required. - All Other Duties As Assigned. We need to keep each as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are typical 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; we can omit Physical Demands and Work Environment if not covered. But we must preserve ALL substantive information; we cannot drop it. However we could fold them into a section like "Requirements" or "Working Conditions" but not in the list. The instruction says "Prefer a few substantive sections over many thin ones." It doesn't forbid other headings, but the examples given are typical. I think we can include a section like "Working Conditions" if we have content. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be interpreted that we should use those headings only; but it's not explicit that we cannot use others. Safer to include them under a heading like "Requirements" or maybe "Working Conditions" as a subsection? But we need to output only HTML fragment; we can include a for "Working Conditions" and include Physical Demands and Work Environment there. That seems reasonable.
But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Physical Demands and Work Environment into one section "Working Conditions". That's substantive.
Thus sections: About the role, Responsibilities, Requirements, Working Conditions, Benefits, Pay.
We also have metadata Job Family: Sales Business Unit: Hale. Could be a short p after Pay or before.
We must not repeat job title as heading.
Now construct HTML.
We'll start with About the role
then
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It may be interpreted that we should use those headings only; but it's not explicit that we cannot use others. Safer to include them under a heading like "Requirements" or maybe "Working Conditions" as a subsection? But we need to output only HTML fragment; we can include a for "Working Conditions" and include Physical Demands and Work Environment there. That seems reasonable.
But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Physical Demands and Work Environment into one section "Working Conditions". That's substantive.
Thus sections: About the role, Responsibilities, Requirements, Working Conditions, Benefits, Pay.
We also have metadata Job Family: Sales Business Unit: Hale. Could be a short p after Pay or before.
We must not repeat job title as heading.
Now construct HTML.
We'll start with About the role
then
About the role
thencontaining intro paragraphs combined. Then
Responsibilities
then- ... each duty.
Then
Requirements
then we need to include knowledge, skills, education, language, math, reasoning, computer, other qualifications. Could be a- with all items. But that would be huge list; still okay. However we might want to group but instruction says use
- for any list of duties/requirements/benefits. So we can make one big list. But we need to preserve all detail; we can just list each bullet as
- . Let's compile all requirement bullets: Knowledge: - Knowledgeable of vehicle electrical systems both on and off highway. - Knowledgeable of vehicle multiplexing systems (Class1 ES-Key or Weldon V-MUX systems are a plus). - Knowledgeable of engine systems and controls. - Knowledgeable of Hydraulic systems and controls. - A detailed understanding of apparatus pumping systems. - Must be able to work and communicate with all levels of a customer’s organization. Education: - Associate's degree or a minimum of 5 years related experience and training; or equivalent combination of education and experience. Language Skills: - Ability to read, analyze and interpret general business periodicals, professional journals, technical procedures, or governmental regulations. - Ability to write reports, business correspondence, and procedure manuals. - Ability to effectively present information and to respond to questions from groups of managers, clients, customers and the general public. Mathematical Skills: - Ability to calculate figures and amounts such as discounts, interest, commissions, proportions, percentages, area, circumference, and volume. - Ability to apply concepts of basic algebra and geometry. Reasoning Ability: - Ability to define problems collects data, establish facts, and draw valid conclusions. - Ability to interpret an extensive variety of technical instructions in mathematical or diagram form and deal with several abstract and concrete variables. Computer Skills: - Proficient with MS Office products - MRP Systems Experience (JD Edwards Experience Is a Plus) - CRM system experience (Sales Force is a plus) Other Qualifications: - Demonstrated problem solving and negotiation skills - Excellent Oral And Written Communication Skills - Advanced technical knowledge across all